You already havea QA team.It’s everyone.
On a team with no QA function, whoever is free checks the work, often the person who wrote it. Smoketest is an AI QA teammate that takes over that first check. When a ticket reaches QA, it tests the change in a real browser and posts the proof on the ticket.
QA stops being everyone’s side job.
Your tickets, statuses, and sprint stay as they are. You stop hearing these four lines.
It takes the checking. You keep the decisions.
Moves to Smoketest
- Reading the ticket and the pull request
- Working out what to test, beyond the ticket
- Testing the change in a real browser
- Posting the result and a recording link on the ticket
- Testing again when a fix comes back
- Remembering what it learns about your product
Stays with you
- Deciding what ships, with one named owner
- Setting the rules it follows
- Telling it which flows matter most
- Fixing what it finds
- Answering when it needs a person
- Changing the rules as your team changes
Fixed in PR #1209. Back to QA.
Passed · 4 of 4 requirements · 2m 12s · Attempt 2
- ✓Admin can open Billing
- ✓Adding one seat updates the Billing page
- ✓Invoice preview shows the proration
- ✓Invoice PDF shows the same amount
Not tested: other invoice languages, because the ticket only covers English.
Watch the recording · View attempt
Recording looks right. This goes out today.
The one checking the work did not write it.
It marks every requirement
Each one reads met or not met, so you can see what a pass covers.
It says what it did not test
Anything it left out is named on the ticket, with the reason.
A person makes the call
Read the result, watch the recording if you want, and decide.
We can test your first ticket the day we talk.
You do not need a QA process before you start. We set it up with you on the call, and each piece takes someone you already have.
Your ticket board
Connect Jira or Linear and choose the status that means QA.
Takes a board adminYour code
Connect GitHub so it can read the pull request behind each ticket.
Takes a GitHub adminA place to test
Share a staging URL and a test account for each role you want tested.
Takes a developerYour rules
Say what matters most and where passed and failed tickets go.
Takes youQuestions founders ask first
Weighing a first QA hire? See how the two compare
No. You need tickets that say what should happen, a staging URL, and a test account. It works from the tickets you write today, and if one is too thin to test, it says what is missing and leaves the ticket in QA.
Every result links to the recording, the steps, and the reasoning, and says what it did not test, so you can check its work the way you would check a teammate's.
It can, and so can a person. Every result says what it checked and what it did not, so you can see the gaps. Add what it missed to your playbook and it applies on later tickets.
You do. Smoketest gives you the evidence, and a named person on your team makes the go or no-go call. If someone changes a ticket's status by hand, that change stands.
Claude Code is good for a quick check while you build. The catch is that the agent that wrote the change is then grading its own work. Smoketest starts from the ticket, did not write the code, and leaves the proof where your team reviews it.
No. It picks up tickets as they reach QA, so nobody waits for a person to be free. The result lands on the ticket and names the requirement that failed.
It depends on what you need. A QA engineer brings judgment across the product and can own your quality process. Smoketest covers every ticket from the day it starts. If you start here, a later hire inherits the results, the playbook, and the regression tests.
It starts at $399 a month for 1,000 runs. Each run is up to 10 minutes, and a longer test counts as two runs or more, one for every 10 minutes. If your team needs more, we design a Scale plan with you, so you stop buying extra runs.
Bring one real ticket to the call.
We connect your board with you and run that ticket, so you see what a result looks like on your own work.