A configured ICP turns a stalled audience line into a concrete draft by defining who has the problem, what they are trying to do, and why the current approach fails them. It gives a solo founder language to review against the product instead of guessing at a broad category.
In 1970, the Apollo 13 crew had a carbon dioxide problem: the lunar module carried round canisters, while the command module’s spare filters were square. The people in Mission Control could not make the parts fit by repeating the instruction they already had. They had to work from the materials actually available in the spacecraft and build an adapter the crew could use. Jim Lovell and Jeffrey Kluger document the episode in Lost Moon.
That is the moment behind the blinking cursor after “Built for teams who...”
The founder has a real product. They may have spent nights on the workflow, fixed the rough edges, and shipped something useful. Then they open the website editor and reach the line meant to explain who it serves. “Teams who want to work better.” “Modern businesses.” “Anyone managing projects.”
None gives a buyer a reason to keep reading.
Broad audience language cannot guide a product description
“Built for teams” sounds safe because it avoids excluding anyone. It also leaves the reader to decide whether the product applies to them.
A product description needs enough detail for a buyer to recognize their own situation. A developer building an API monitoring tool may serve small engineering teams that need to catch failed integrations before customers report them. A solo founder building a mobile app may serve people preparing a release who need the listing, screenshots, privacy details, and launch content in one place.
Those descriptions make choices. They identify a person, a job, and a pressure point.
The audience line becomes useful when it can answer three practical questions:
- Who is already feeling this problem?
- What are they trying to complete or avoid?
- Why does the existing process cost them time, attention, or confidence?
A founder can review those answers against the product. They can remove claims the product cannot support. They can see where the audience is still too broad.
That review matters because the same vague audience line tends to spread. It becomes the homepage headline, the LinkedIn post, the product launch description, and the prompt handed to an AI writing tool. By the time the copy reaches a buyer, every version is polished and still unclear.
A configured ICP supplies the missing constraints
Marketing Agent starts with product-specific context: target market, ideal customer profile, positioning, competitors, pricing, offers, keywords, and brand voice. The point is to give each draft a working set of constraints.
For a solo founder, that can turn this:
“Built for teams who want to get more from their marketing.”
Into something a human can challenge:
“Built for developers and solo founders with a real product and no dedicated marketer, who need a repeatable way to define their positioning, create launch content, and publish it to connected channels.”
The second version still needs review. A founder may decide “developers” is too broad, or that launch content is less important than ongoing product updates. That is progress. The draft has something specific enough to edit.
A configured ICP also keeps the description connected to evidence. If the product strategy says buyers dislike repetitive promotion and have limited time, the copy can acknowledge that directly. If the product is still early and lacks customer proof, the draft should avoid claiming market leadership or guaranteed results.
This is the same kind of constraint Mission Control faced during Apollo 13. The solution had to work with the materials available. Product messaging has the same discipline. The strongest description uses the product’s actual capabilities, real buyer pressure, and honest limits.
For a useful starting point, compare the audience line with the questions in Who Is Your Product Actually For Before You Announce It?.
Review the draft before you distribute it everywhere
Once the audience is concrete, it can inform the rest of the marketing system. The blog topics can address the buyer’s actual questions. Social posts can name the frustrating task the product helps with. Videos can show the relevant workflow using authentic product screens. A marketing audit can flag gaps in positioning, customer evidence, offers, and acquisition plans before those gaps become public copy.
That does not mean every channel needs the same sentence. A website may lead with the buyer and outcome. A technical article may lead with the workflow. A short social post may begin with the failure the buyer wants to avoid. They should all draw from the same product strategy.
Set a simple test for the next draft: could a person in the intended audience say, “That sounds like my week”? If the answer is uncertain, return to the ICP. Look for the job, the moment of friction, and the existing workaround.
The square canister was not useful until Mission Control understood the exact shape of the constraint. Your product description works the same way. Give the cursor a real buyer, a real problem, and a claim your product can carry.
Comments
No comments yet.