💼 Product, business, and monetization
The commands in family 08: analyze the market and customer, segment and position, build the offer, set the price, model the business, and design growth — in the right order.
🌐 /market — analyze the market and its dynamics
Assess problem, demand, segments, competition, dynamics, and barriers. It’s the command you run before falling in love with the solution—because you don’t persuade a market; you discover it.
🔭 Six /market questions
- •Problem: who is dealing with this today and what are they doing about it?
- •Demand: is anyone already paying for a solution (even a bad one)? How much?
- •Competition: who serves, how they charge, where they fail?
- •Dynamics: is the market growing, shrinking, or changing shape?
- •Barriers: what keeps a new entrant out — regulation, capital, distribution, trust?
New here? Market dynamics is the direction of movement: who is gaining power, which channel is becoming saturated, and which technology is making what used to be expensive cheaper. A large market with poor dynamics is worse than a small market with good dynamics.
🎯 Copy and run
/market para <ideia ou segmento>; responda problema, demanda com evidência de pagamento, 3-5 concorrentes com preço e ponto fraco, dinâmica dos últimos 2 anos e barreiras de entrada
How to verify: the “demand” section mentions someone paying for something — if it only mentions “potential,” the market is still a hypothesis.
💡 Practical tip
Combine with Track 1: /truth /market. “Market size” figures from consulting reports are inferences dressed up as facts—the /truth separates them.
🧑💼 /customer — jobs, pains, and desires
Define jobs, pain points, desires, context, current alternatives, and purchase criteria. The central question: what job would this person "hire" your product to do — and what do they use in its place today?
✓ Customer described by job
- ✓"Solo consultant who needs to send a proposal within 24h to avoid losing the lead; currently adapts an old Word document and loses 2h per proposal."
- ✓Named current alternative: the old Word. That’s where you take the customer from.
✗ Customer described by demographics
- ✗"Men and women ages 25 to 45, middle class, interested in productivity."
- ✗No pain points, no alternatives, no buying criteria — a slide-deck persona.
New here? Job to be done (job to be done) is the progress someone wants to make in a particular situation—not the technical task. Nobody wants “a CRM”; they want “to remember to call back someone who almost bought.”
🎯 Copy and run
/customer para <produto ou ideia>; descreva o cliente por job principal, 3 dores com situação concreta, desejos, contexto de uso, o que usa hoje no lugar e os 3 critérios que fariam ele trocar
How to verify: the “what you use today” column names a product or a workaround — it’s never empty. If it is, the problem doesn’t hurt enough.
🎯 /segment + /position — segment and position
/segment creates segments useful — by need, behavior, value, or usage context, not by age. /position answers in one sentence: who it’s for, what problem it solves, which category it’s in, what makes it different, and what is the proof.
Illustrative: positioning is a ladder—skip a rung and you fall into the "offer for everyone."
Segment by what changes the purchase decision
Two customers with the same age and income can have opposite jobs. Segment by urgency, context, or current alternative.
Choose a segment to start with
What has the most acute pain point and is easiest to reach—not the biggest. “Everyone” is just “too big” in disguise.
Write the positioning statement
"Stop
🎯 Copy and run
/segment /position para <produto>; 3-4 segmentos por necessidade/contexto com tamanho estimado e dor, escolha um segmento inicial com justificativa e escreva a frase de posicionamento com prova
How to verify: the positioning statement includes verifiable proof (“used by 40 clinics,” “reduces 2h per proposal”) — not an adjective (“innovative”).
🎁 /offer — build the offer
Organizes promise, deliverables, price, proof, perceived risk, and call to action. An offer is the packaging that helps the customer understand in 10 seconds what they get, what they pay, and why they should trust you.
| Component | Customer question | Example |
|---|---|---|
| Promise | What changes in my life? | "Commercial proposal ready in 15 minutes" |
| Deliverables | What exactly do I get? | Template + generator + 3 reviews per month |
| Proof | Why should I believe it? | "38 consultants use it; average of 1h47 saved" |
| Perceived risk | What if it doesn’t work for me? | 14-day guarantee or first proposal free |
| CTA | What do I do now? | "Generate your first proposal" (one button, one verb) |
A complete offer answers all five questions without the customer having to ask.
🎯 Copy and run
/offer para <produto> e <segmento escolhido>; promessa em uma frase, entregáveis listados, preço, prova concreta, mecanismo de reversão de risco e chamada à ação única
How to verify: you can read the offer aloud in 30 seconds, and someone outside the project can say what they would buy and for how much.
⚠️ An offer that promises too much
The deliverable must fulfill the promise in 100% of typical cases. A promise that depends on the customer "putting in the effort" leads to refunds and a bad reputation. Promise what the product does on its own.
💰 /pricing — pricing and value capture
Compares value capture models, willingness to pay, unit economics, and commercial simplicity. Price isn’t cost plus margin: it’s the share of the value generated that you can capture without stalling the sale.
⚖️ Four axes of /pricing
- •Model: subscription, pay-per-use, outcome-based, one-time license — each changes who assumes the risk.
- •Willingness to pay: how much does the problem cost the customer today (in money or hours)? The price sits below that.
- •Unit economics: how much it costs to serve a customer vs. how much they pay over time.
- •Simplicity: if the customer needs a calculator to understand the price, they won't buy.
New here? Unit economics (unit economics) is the calculation for a single customer: the revenue they bring over the course of the relationship minus the cost of acquiring and serving them. If the unit loses money, scaling only multiplies the loss.
🎯 Copy and run
/pricing para <oferta>; compare 3 modelos de cobrança com prós e contras, estime disposição a pagar a partir do custo atual do problema, mostre a unidade econômica de cada modelo e recomende o mais simples que fecha a conta
How to verify: the recommendation includes the underlying economics (revenue per customer, cost to serve, margin) — not just the price figure.
📊 Anchor it to the cost of the problem
If the client loses 2 hours per proposal and makes 10 a month, the problem costs ~20h/month. At 100 R$/h, that's R$ 2.000. A price of R$ 200/month captures 10% of the value generated—easy to justify. Calculating this before looking at a competitor's price helps you avoid copying their mistake.
💎 /monetize — turn assets into revenue
Converts assets, audience, data, software, knowledge, or distribution in revenue models. The question isn't "what can I create to sell," but "what do I already have that someone would pay to access?"
✓ Monetized asset
- ✓Community of 800 people → premium plan with a monthly meeting and exclusive materials.
- ✓Internal pricing spreadsheet used for 3 years → paid template + 2-hour workshop.
- ✓Supplier database → paid quarterly report for the industry.
✗ Wasted asset
- ✗Audience treated only as reach for selling a third-party product.
- ✗Ten years of know-how given away for free on a "just to chat" call.
- ✗Internal software that would solve the pain point for 50 competitors, kept secret out of habit.
🎯 Copy and run
/monetize a partir de <lista dos meus ativos: audiência, conteúdo, dados, ferramentas, relacionamentos>; para cada ativo, 2 formatos de receita possíveis, quem pagaria, esforço para lançar e o mais rápido de testar
How to verify: at least one option can be tested in 2 weeks with what already exists — without building anything new.
💡 Practical tip
Run /monetize once every six months. Assets accumulate without you noticing—the list of "things I already have" grows faster than the list of "things I charge for."
🏰 /businessmodel + /moat — model and defend
/businessmodel maps how value is created, delivered, and captured, with costs, channels, and advantages. /moat asks what happens when someone copies—and which of the eight sources of defensibility you actually have.
| Source of the moat | Test question | Sign that it’s real |
|---|---|---|
| Mark | Does the client ask for it by name? | Search by exact name > generic search |
| Data | Does each use improve the product? | Longtime customers get better results than new ones |
| Network | Does each new user increase the value for others? | Churn falls as the customer base grows |
| Switching cost | Does exiting hurt? | Migration requires rework, training, or loss of history |
| Distribution / speed | Can you arrive sooner and at a lower cost? | Lower CAC than the competitor, shorter release cycle |
Teaching example: a moat is what you can prove with a signal, not what you write in the pitch.
New here? Moat (moat) is the advantage that makes copying expensive, slow, or useless. “Being first” isn’t a moat—it’s a temporary advantage. A moat is what still holds up after the second player arrives.
🎯 Copy and run
/businessmodel /moat para <negócio>; mapa de criação, entrega e captura de valor com custos e canais; depois avalie as 8 fontes de defesa com sinal concreto de cada uma e diga qual fortalecer primeiro
How to verify: each moat marked "present" comes with an observable signal today — and the list of absent moats is longer than the list of present ones. If not, be skeptical.
📈 /growth — growth loops
Identifies loops, channels, bottlenecks, metrics, experiments, and retention mechanisms. A loop is when the output of one cycle becomes the input for the next: a satisfied customer refers someone, the referral becomes a customer, and that customer refers someone. A campaign is when you push—and stop when you get tired.
Retention first
Filling a leaky bucket is the most expensive way to grow. Before acquisition, measure who stays after 30, 60, 90 days—and why.
Find the loop that already exists
Where did the last 10 customers come from? If 4 came from referrals, that loop is already running on its own — it just needs fuel.
Find the bottleneck and experiment
Every loop has a point where conversion drops. Run one experiment at a time, with a metric and a deadline—never five at once.
🎯 Copy and run
/growth para <negócio>; retenção atual e causa de churn, loops existentes com a conversão de cada etapa, o gargalo principal, 3 experimentos com métrica e prazo e a métrica-norte única
How to verify: there is ONE north star metric, and each experiment specifies which step of the loop it aims to move — experiments without a step are campaigns.
💡 Composite recipe
Complete business thesis, straight from the document: /truth /market /pushback /businessmodel /moat /growth /bet. Facts first, attack before the model, bet with kill criteria at the end.
Quick self-check (optional): what's the correct reasoning order for family 08?
🎓 Module Summary
Next Module:
5.2 - Prototyping and AI agents — the business case holds up; now build the smallest testable version and design the agent that delivers it.