· startup-ideas · claude-code · skills · indie-hackers · knack-starter-pack
How to clarify a startup idea in five minutes
Most idea-clarification ends in fog. Here's the four-section pattern that turns a rough brief into audience, pain, offer, and a ranked first-action plan.
Most attempts to clarify a startup idea end with the same fog they began with. The audience is still “founders” or “small businesses”. The pain is still “inefficient workflows” or “no time”. The next step is still “build an MVP and talk to users”. Two hours have passed and nothing has actually narrowed.
This post is about why that fog is the default and how a four-section pattern (audience, pain, offer, first-action plan) cuts through it. The pattern is now a Claude Code skill in the free Knack Starter Pack, but the discipline works without the tooling. The skill’s job is to enforce the bits you skip when you do this in your own head on a Sunday evening.
Why most attempts to clarify a startup idea end in fog
The fog is not the absence of thought. It is a specific pattern of substitution. Three substitutions, all common, all expensive:
Categories instead of stages. “Indie hackers” is a category. The actual audience is “indie hackers shipping their second project who haven’t broken £500 MRR yet, who have a Twitter audience under 1,000, and who lose the launch-week thread to bigger accounts on day three.” The first one cannot be marketed to in any specific way. The second can. Most idea sessions end at the first because narrowing past “indie hackers” feels arbitrary at the moment of choice. It is not arbitrary; it is the work.
Hypotheses instead of quotes. “They struggle with pricing” is a hypothesis. “I lost a £4k logo project to someone quoting £400. I don’t know what to charge so I just lowball every time” is a quote. The hypothesis can be true or false; you cannot tell from the inside. The quote is data. Every idea-clarification session that produces a hypothesis-shaped pain section is one round-trip away from being correct, and almost no one does the round-trip.
Templates instead of plans. “Build an MVP, talk to users, iterate” is a template. It is true for almost every product, which means it provides almost no signal for any specific one. A plan is “post the question, not the offer, in r/graphic_design this Sunday; read every reply; pull out the ten most common pricing-anxiety patterns by Friday.” A plan has dates, channels, success criteria. A template has none.
The fog persists because each of these substitutions is the easier of two answers in the moment, and they compound. You start with a category audience, write a hypothesis-shaped pain because that is what fits a category, and finish with a template plan because the rest does not give you anything specific to plan against.
Four sections that hold the structure
The fix is to refuse all three substitutions in the same artefact. Four sections, in this order:
Audience. One sentence naming a stage and a situation. Not a label. The test is: would the audience themselves read it and say “yes, that’s me, that’s specifically me”? “Solo consultants” fails the test. “Solo consultants 1 to 3 years in, charging £500 to £900 a day, who lose half a Sunday a month to client admin” passes.
Pain. One paragraph in the audience’s own words, with at least one direct quote where you have one. End with a sentence the audience would themselves say is exactly how it feels. If you have no quote at all, that is itself the result: the entire artefact is deferred and the first action becomes “go and find one.” That deferral is uncomfortable and almost always the right call.
Offer (positioning). One product, one price, one channel. Not three options. “A £19 Notion-and-PDF pricing toolkit for early-career freelance designers, sold via Gumroad, distributed through r/graphic_design” is an offer. “A pricing tool for designers, somewhere between £19 and £49, distributed online” is a wish. The constraint that forces the choice is what makes the offer testable.
First-action plan. Three to five next actions, each with a one-line reason and a date. Ranked by leverage, not by sequence. The first action is always the smallest test that produces the most signal. Not the MVP. The pre-MVP move that tells you whether the MVP is worth building. A single DM, a one-page landing, a five-question survey, a question posted to one community.
The four sections work together. Each one is hard to write past the substitution failure mode. Doing all four in one sitting is the discipline; the artefact is just the shape that proves you did it.
A run-through against a real brief
Take the example from the Knack Starter Pack worked example. The user starts with a rough brief about “something for freelance graphic designers around pricing”, an audience guess of “freelance graphic designers”, and the constraint of “evenings and weekends only, no paid ads.”
The skill rejects the audience as a category, not a stage: “a 10-year-in studio owner charging £8k brand sprints has a different problem from a 1-year-in Upwork designer charging £200 logos. Which one is this for?” The user comes back with “1 to 2 years in, Upwork-sourced, doing logos and small brand work, who keep losing on price.”
The skill then asks for a quote. The user could not have written the pain section without one. They paste a real comment from r/graphic_design: “I lost a £4k logo project to someone quoting £400. I don’t know what to charge so I just lowball every time. I’m scared if I quote my real rate they’ll ghost.”
The artefact then writes itself. Audience: 1 to 2 years in, Upwork-sourced. Pain: priced from the visible competitor anchor, not from any internal model of the work. Offer: a £19 Notion pricing toolkit, distributed through r/graphic_design (the same thread where the pain showed up). First action: post a question, not the offer, in that subreddit this week. Read every reply. Build the toolkit’s six questions from the audience’s own pricing-anxiety patterns.
That last move is the load-bearing one. The first action is not “build the toolkit”. It is “go and gather the words the toolkit will be made of.” The audience writes the product, in their own phrasing, in a thread that already has their attention.
Where this breaks
The pattern produces weaker artefacts when the audience is genuinely broad. A consumer mobile game pitched at “people who like puzzles” cannot be narrowed without market data we do not have at idea stage. The pattern is sharper for tools and services aimed at named communities than for entertainment products aimed at general taste.
It also breaks when the user pushes against their own stated constraint. If you said “no paid ads” and then ask the skill to recommend paid ads anyway, it will comply, because honoring the user is the contract. The constraint is yours to keep; the artefact only fits the life you actually have.
And it does nothing about the discipline of execution. A clean four-section artefact and a £19 Gumroad page that never goes up are the same outcome. The skill produces the plan; the next-action date in the plan is the only thing that produces the result.
What this looks like with the Knack Starter Pack
The free Knack Starter Pack ships two skills. idea-clarifier runs the four-section pattern above, with the input validation that rejects categories and demands quotes. first-skill-template scaffolds your own first Claude Code skill from the same canonical body the rest of the Knack catalogue uses, so once you have an idea you want to build into reusable behaviour, the second skill gets you most of the way to a structured SKILL.md.
MIT-licensed, no licence key, no subscription. The pattern is portable; the tooling makes the pattern fast.