The scoping framework — free
Your business in 12 questions.
This is the exact framework we use to turn vague problems into build-ready specs. No AI jargon. No sales pitch. Try it yourself.
Four phases, twelve questions
We ask until we understand your week better than you do.
Run these one at a time, on yourself or with your team. No tech words — dig until each answer is a scene, not a summary.
Find the bleed
- 1Walk me through your worst Tuesday. What was supposed to happen, and what actually happened?
- 2How many times a day does someone interrupt you with a question you've already answered?
- 3What's the thing you dread doing every week — the thing you'd pay someone to take off your plate?
Why this phase: We start with pain, not features. The task you dread every week is where a system earns its place — so we hunt for the bleed before anyone says the word 'AI'.
Trace the workflow
- 4When that pain happens, walk me through it step by step. What do you open first, who do you ask, where does it live?
- 5What's the moment it usually breaks? Where does someone go off-script or things fall through?
- 6If you could wave a wand and make one step disappear, which one?
Why this phase: A problem you can't draw, you can't build. We follow the exact steps — what you open, who you ask, where it lives — until we can describe the workflow better than you can.
Define the moment
- 7When exactly does this hit you? Time of day, day of week, trigger event?
- 8Who else touches this? Name the person who catches it when you're not there.
- 9What happens if it doesn't get done? What's the cost of dropping it for a week?
Why this phase: Every painful task has a trigger — a time, a day, a person. We pin down the exact moment it hits, because the smallest tool that kills the pain lives right there.
Size the prize
- 10If this was automated tomorrow, what would you do with the time?
- 11Has anyone else tried to solve this? What happened?
- 12What would make you say 'this was worth it' six months from now?
Why this phase: Before building anything, we anchor on what solving it is actually worth — the time you'd get back, the cost of dropping it. Price follows the cost of the problem, never a tier sheet.
The push-back library
When founders say…
Half-answers hide the real problem. Here's how we push — use the same lines on yourself.
They say
Life just gets in the way.
We ask
That's half an answer. Give me the scene — what time, what happened, who was there?
They say
We lose about $2K a month.
We ask
Gut, or did you count?
They say
Everyone would use it.
We ask
Name the one person who reaches for it first.
They say
We need AI for everything.
We ask
Pick the one thing. The rest comes later.
They say
That sounds too expensive.
We ask
What's it cost you every time it doesn't get done?
Try it on yourself
Got 20 minutes?
Run through these 12 questions on your own business. Write the answers down. Then book a $150 build hour and we'll turn your answers into a real spec — the smallest tool that kills your biggest bleed.
One focused hour. We build something real, or you pay nothing.