Map the stages around a goal and name the entries, exits and interruptions the flow forgot.
map_journey
Before: what you give it
The example input, as sent.
A new agency owner connects Google Search Console, adds their first three client sites and sends the first client report first_use
After: what comes back
A real run of this tool has not been captured for this page yet, so there is no sample to show. Run the request below to see the answer for yourself.
What you get
Ordered stages for the objective, the ways people arrive that the flow ignores, the ways they leave, and how interruptions are handled.
What gets better
You see the journey around the feature, not only the screens inside it.
When to use it
When you are designing onboarding, a setup flow or any task that spans several sessions.
What it cannot do
It maps what the objective implies. It has no analytics or research behind it, so treat the stages as a hypothesis to check.
Run it
Two free calls a day with no key. Send your own Anthropic key in an x-anthropic-key header to lift the limit.
curl -X POST https://verdict.allthepossibles.com/api/map_journey -H 'content-type: application/json' -d '{"objective":"A new agency owner connects Google Search Console, adds their first three client sites and sends the first client report","user_maturity":"first_use"}'
The other reviews
- critique_experience
Find the problems in a design before a user or an engineer does, ranked by how badly each one hurts.
- generate_state_matrix
List every state a feature can be in, including the ones nobody drew.
- audit_copy
Review buttons, errors, empty states, confirmations and notifications, and rewrite the ones that fail.
- find_assumptions
Pull the unchecked beliefs out of a brief and turn each into a question you could answer this week.
- check_terminology
Find one concept that goes by several names across your UI, docs and API.