offer-validation-and-pricing

Offer Validation and Pricing

Two questions sit between "we could sell something" and "we are reaching out to buyers": what exactly are we selling, and what argument makes its price feel right. This skill answers both. It drafts and analyses; it never publishes or sends.

---

Part 1: Validate before you build

The default failure is inventing a product, then hunting for someone who wants it. Start from evidence that already exists instead.

1a. Mine competitor reviews for a pain gap

Collect reviews of the products your buyer already pays for (not the ones you imagine you compete with). Review sites, app-store reviews, community threads and support forums all work. Then ask a model to analyse them with these constraints:

1. Find recurring complaints, unmet expectations and desired outcomes.
2. Discard isolated complaints. Keep only problems that show up across several different products. This is the instruction that matters most and the one people drop. A complaint that appears against every product in a category is a structural gap; a complaint against one product is a bug report.
3. Name the single biggest gap none of the existing products solve.
4. Return four fields: a short name for the gap, supporting evidence, why it is underserved, and the product opportunity.

Two rules when you run it:

• Supporting evidence must be real quotes with sources, not the model's paraphrase. If it cannot quote, it did not find the reviews; it produced a plausible complaint. Re-run with the actual review text pasted in.
• Check the frequency yourself on a sample. If the "recurring" complaint appears twice in two hundred reviews, it is not your market.

A simple three-step frame to wrap around it: gather the top products and their reviews, hunt for the complaint everyone shares and nobody fixes, then build the smallest thing that solves that one pain.

1b. Proof of payment

From the opposite direction: confirm someone already pays for this outcome. Not that people say they want it, not that it polls well, but that money has moved. Acceptable evidence:

• A competitor with public pricing and named customers or case studies.
• A live marketplace listing with a visible, plausible sales count.
• A budget line the buyer already defends (a tool they pay for, a contractor they hire, a role they staff).

Apply the discipline to the evidence you are shown, including evidence from whoever taught you the discipline. Income screenshots, "real, verified" listings that are actually mockups, and revenue figures that do not reconcile with the price times the stated customer count are common in content about this exact topic. A number without an external receipt is a caveat, not proof.

1c. Name where the buyers already gather

Finish by naming specific rooms where people with this pain already are: communities, forums, newsletters, directories, events. If you cannot name three, you have a hypothesis, not a market. Public, filterable company directories (for example startup-accelerator portfolio directories) are a good free source of funded companies by sector.

Validation checklist

• Reviews from at least three products the buyer already pays for.
• The gap recurs across products, with real quotes attached.
• At least one piece of proof that money already moves for this outcome.
• Three named places where the buyers gather.
• The smallest version that solves the one pain is scoped.

---

Part 2: Match the argument to the price point

The price does not change how loudly you sell. It changes which argument you make.

Compressed: low ticket fights risk, mid ticket fights inertia, high ticket sells identity. The tier boundaries are approximate and depend on the buyer; a team buying software has a very different "impulse" threshold from an individual.

The most common pricing error

Arguing a commitment-tier offer with impulse-tier logic. "It's only a few hundred dollars" is a risk argument aimed at a buyer whose real objection is that change is hard. Cheapness stops persuading once the obstacle is inertia, and it also signals the work is small.

Diagnose a stuck offer before changing the number

Identify the objection first. Most "price problems" are argument problems.

• "It might not work for us." Risk. Reduce risk with proof, a guarantee, or a free first deliverable rather than cutting the price.
• "Not right now." Inertia. Move to the cost-of-not-buying argument and quantify the ongoing loss in their terms.
• "Let me think about it" after one conversation. Evidence. You are priced at a tier your proof does not yet support. Build the case study first.
• They never ask the price. Identity or trust is already doing the work. Do not discount.

Designing a ladder of offers

If you sell several rungs (for example a free proof of work, a paid fixed-scope project, then an ongoing engagement), each rung should use a different argument class: risk removal, then inertia removal, then evidence and identity. Rungs that argue differently invite less direct price comparison, which reduces the anchoring problem where a cheap entry offer makes the next rung look expensive. The paid project is often the best case study for the ongoing engagement.

Saying the number

• State one number, plainly. A range in a proposal invites negotiation toward the bottom. (In a quick reply to an early "how much?", a starting point or range is fine; a firm proposal is not the same as a first answer.)
• Payment terms and rails are a closing detail, not an opening line.
• Do not mix tier arguments in one piece of copy. Pick the rung, write only that rung's argument. Mixed arguments are what make offer copy sound unsure of itself.

---

Part 3: When to present the next offer

Price arguments decide how to argue a rung. Timing decides when to put it in front of a buyer who has already bought. Alex Hormozi has popularised a timing model with four windows after the first purchase:

1. At the moment of purchase.
2. A day or two later, while the buyer is still in a buying frame of mind. Make the next thing available without pressure.
3. At their first real result. Acknowledge the milestone, then offer the next step.
4. At the halfway point of the engagement. If it is going well, the next offer continues the momentum; if it is going badly, the next offer is the extra help they need.

Waiting until the end ("last chance") is the weakest window, because by then the buyer's attention has moved on. Hormozi has stated that the earlier windows convert dramatically better and that he prices the follow-on offer at several times the front-end price; those figures are his own claims, not independently published data, so quote them as his or not at all.

---

Part 4: Numbers discipline

Never repeat a number you cannot reproduce from a live source, and never repeat it without the qualifiers that make it true.

The common way a real statistic becomes false: someone keeps the headline number and drops the population, the comparison group and the time window. "Top founders earn N times more" might originally have meant "top-decile versus median founders, among one specific cohort, measured over their first six months". The number survived; everything that made it meaningful did not. Also check whether a series is actually monotonic before describing it as a steady trend.

Rules:

• Quote the source, the population, the comparison and the time window, or do not quote it.
• Prefer qualitative claims in your own copy over borrowed numbers you cannot defend.
• Treat creator screenshots of revenue, conversion rates or customer counts as marketing, not data.

---

How to use this skill

1. New paid offer? Part 1 first. Do not price something whose demand you have not evidenced.
2. Price not converting? Part 2's diagnostic. Name the objection before touching the number.
3. Writing offer copy, a proposal or outreach? Pick the tier, write only that tier's argument.
4. Have existing buyers? Part 3 for when to present the next rung.
5. About to cite a market statistic? Part 4.