What is Specnote

What problem does it solve

These days you can tell an AI "build me a signup screen" and the code appears in seconds. But when the AI says "all done," who checks that the screen actually behaves the way you planned?

If you can read code, you can look for yourself. But if you're a planner or a solo maker who can't read code, you end up signing up, paying, and checking for the welcome email by hand — every single time. And you have to repeat the whole thing from scratch whenever you change a feature.

What happens if you skip that check? Usually, your customers find the bug first. You only learn about the problem after messages like "the pay button doesn't work" or "I signed up but no email arrived." Building is fun, but checking is tedious — and easy to forget.

Specnote takes over exactly that "checking" step. Without reading a line of code, it confirms whether the app you (or your AI) built works as planned, by clicking through it like a real person.

How Specnote works

The core is a simple three-step loop.

1. You describe a scenario in plain words. Write what you want to check — like "a welcome email should arrive after signup" — and the AI turns it into a step-by-step scenario. A scenario is just a checklist of "this is how it should behave." Add one at a time.
2. AI clicks through it like a real person. A real browser walks through that scenario, from signup to checkout, clicking each button. It looks at the screen and presses buttons the same way a real visitor would. Pass turns green, fail turns red.
3. A report comes out. When something breaks, you get a fix report that shows where it stopped, why, and how to fix it. Paste that report into an AI coding tool like Cursor or Claude Code, and the fix begins right away.

Here, "verification" simply means testing — but you never write a line of test code. The AI clicks through your plain-language scenario in a real browser. That's what verification means in Specnote.

Who it's for

Specnote was built for people like these.

• Non-developer planners who vibe-code apps. You hand the coding to AI but have no way to confirm the result matches your plan.
• PMs and product planners. You find it awkward to ask a developer "please check this" after every change.
• Solo makers and founders. You build and check everything yourself, so time is always short.

It's useful for developers too — handy when you'd rather describe a scenario in words and verify it fast than write test code by hand. In one line:

AI writes the code. Specnote does the checking.

What makes it different

Plenty of tools already automate testing. Most are built for developers to drive with code or commands. Specnote differs in three ways.

• You start with words. Instead of commands or test code, you write what you want to check in plain language. You can begin even if you can't read code.
• It reads your real code. If you choose to connect Specnote to your codebase, the AI uses your code structure to line up more accurate scenarios. It checks based on what you actually built, not just the surface of the screen. (You can also start without connecting your code.)
• It analyzes impact step by step. When you change one feature, it points out which step of which scenario is affected — so you can gauge in advance what this change might break.

Ready to start

That's enough concept. The fastest way to get it is to try it yourself.

• To follow the path from signup to your first verification in five minutes → Get your first verification in 5 minutes
• To line up terms like scenario, step, and verification first → Key concepts
• To learn more about how the AI clicks like a real person → How verification works

Signing up takes 30 seconds with just an email, and no credit card is needed. Start light with Start for free.