1.2.1 - Can You Explain This in 30 Seconds Without Mentioning the Tech?

The earlier files (user.md, problem.md, promise.md) are written for the builder and the AI tools they prompt: who the user is, what pain we are solving, what the product promises. positioning.md is written for everyone else. It is the answer to "what is it?" when someone asks at a meetup, lands on the homepage or pastes a competitor's URL into AI chat. The three lines borrow from the earlier files because they pull from the same source of truth, but they are written to be said out loud, not read.

30-second explanation

Can you explain this in 30 seconds before users ask?

The call

If the explanation takes longer than 30 seconds, the idea is still too loose. AI can rewrite it quickly, but only you can decide whether the boundaries are right.

Explainer

A short explanation is not about compression alone. It is a test of whether you actually understand the user, the problem and the outcome. If the explanation needs a follow-up paragraph to land, the idea is still too loose. AI can help rewrite the message, but it cannot create clarity that is not there.

Make the 30-second explanation concrete

Compare the broad version with a version you can actually test.

• Too vague: This is an AI search tool that helps people find better answers.
• Concrete enough to test: This helps a content creator find gaps in what they have already published so they can decide what to write next, using AI search shaped by their saved context.

The second version lets two people describe the same product from it.

Check the 30-second explanation

• Pass: You can explain who it is for, what problem it fixes and what useful result appears without adding a second paragraph.
• Fail: If the explanation depends on follow-up clarification to make sense, it is still too vague.

Do not move into messaging, review or build work until this passes.

What you'll walk away with

In the members-only section below we put this into practice. You'll come out with a 30-second explanation clear enough that every later decision flows from it. Landing-page copy, how you describe it in conversation, the README and the prompts you write to AI all inherit that clarity.

How it fits together

This is how the work is done in practice on the Cloudflare Workers stack with AI-assisted coding tools. The thoughts and ideas apply equally on any other platform.

The project is a monorepo so the 30-second explanation (alongside the rest of the framework files) lives in one shared knowledge-base/ folder that every app, every package and every AI prompt reads from. The three products in the vibe2value build-in-public stack (subCancel, ghostMarketingFlow and flowRun) each carry this layout, so look at any of them to see the structure in practice.

You write the positioning before you start describing the product publicly, so you have one source of truth when the question comes up in person, on a landing page or inside an AI prompt. The file is called positioning.md because that is what it is: how this product positions itself in plain language. The post calls it a 30-second explanation because that is how the positioning shows up in practice, in the moment someone asks "what is it?"

If you sign up, this idea continues with how it all fits together, a worked example, how to use it with AI, how to evaluate it on a real change, the risks worth naming and how to mitigate them, the key takeaways and a copy-paste AI prompt you can drop straight into your next chat. Examples are shown on the Cloudflare Workers stack with AI-assisted coding tools; the ideas apply equally on any other platform.