Get your first verification in 5 minutes

1. Sign up and get 30 credits

First, create an account with Start for free. There are three ways to sign up.

• Sign up with email and password
• Sign up with your Google account
• Sign up with your GitHub account

If you sign up by email, a verification email arrives at the address you entered. Click the link inside to finish verifying. With Google or GitHub, this step is handled automatically.

Once you're signed up, 30 credits land right away. A credit is the point you spend each time you run a verification. No credit card needed — you can run your first verification immediately with the credits you got.

2. Create a project (Spec)

The first time you log in, you'll see your workspace — the home for your projects and scenarios. Create your first project here.

A project only needs two things.

• Title — the name of the service you want to check (e.g. "Our Shop")
• One-line description — a quick summary (e.g. "an online shop that sells clothes")

In the pricing pages, a project is counted as a unit called a Spec. The free plan lets you create one project; the paid plans (Standard and Pro) let you create as many as you want.

3. Write your first scenario

With a project created, it's time to describe what you want to check — in plain words. Don't overthink it. Just write, in one sentence, the thing you'd normally check by hand.

A welcome email should arrive after signup

Write it like that, and the AI lines it up into a step-by-step scenario on its own. That one sentence usually unfolds into steps like these.

1. Open the signup page
2. Enter email and password
3. Complete signup
4. Confirm the welcome email arrives

Here's one tip: write one thing at a time. Rather than cramming "check signup and payment and notifications all at once," the more clearly you describe a single thing you want to check, the more accurately the AI lines it up.

There are a few other ways to create scenarios besides writing them yourself — pulling them automatically from your code, building them through a chat with the AI, or letting Specnote browse your screens and suggest them. We cover those in Creating scenarios. For now, writing one sentence yourself is plenty.

4. Run a verification

With a scenario ready, press the verification (test) button. A real browser opens and starts clicking through your screens one by one, just as the scenario describes — exactly as a person would fill out a signup form and press a button.

While it runs, the screen shows verifying. Each run uses 1 credit. With the 30 credits you got at signup, that's 30 runs.

Feel free to do other things while it runs. The result appears automatically when it finishes.

5. Read the result

When verification finishes, the result comes in just two colors.

• Green = pass. It worked the way your scenario described.
• Red = fail. Somewhere along the way, it didn't behave as expected.

A video and screenshots are saved with the result. You can see with your own eyes how the AI clicked through the screens and where it stopped. Even without reading code, "ah, this is where it broke" is plain to see.

If it failed, a fix report is created alongside. The report lays out where it stopped, why, and how to fix it. For example:

Failed step: Cancel payment — the button isn't responding. Cause: the confirmation dialog never opened, so the flow stopped. Suggestion: check the handler wired to the cancel button.

Paste this report into an AI coding tool like Cursor or Claude Code, and the fix begins right away. Specnote doesn't edit the code itself. Instead, it clearly lays out what went wrong and why, then hands the fixing over to your AI tool.

Next steps

Once you've run your first verification, you've got the basic flow down. Go deeper with these.

• More ways to create scenarios → Creating scenarios
• Running verifications and reading results in detail → Running and results
• Connecting your code for more accuracy → Connect your code
• How credits and plans work → Credits and plans

By the way, even without connecting your code, everything above works as is. Connecting your code is an optional step for more accurate scenarios — so we recommend experiencing a verification with one light scenario first.