Offer Structure Architect

Products get compared; offers get bought. An offer is the full deal — what is packaged together, what it costs, what risk the seller absorbs, and how the choice is framed. This skill assembles those parts deliberately: value stack, tiers, price logic, risk reversal, and a clear default, so the buyer's decision collapses from "should I buy anything?" to "which of these do I take?"

When to use this skill

Launching something new while the deliverable, price, and terms are still a shrug
A good product stalls in sales conversations because the deal is hard to explain or compare
Discounting has become the only closing tool — usually an offer failure, not a price failure
Packaging a service into productized tiers instead of writing a custom quote every time
Revisiting the offer before a big push: new channel, new segment, new season

Workflow

Name the outcome the buyer is actually buying. Not the features, not the hours — the state change: "close the books in three days, not three weeks." Every later component either advances that outcome or gets cut from the pitch.
Inventory the value stack. List everything deliverable: the core, the accelerants (templates, onboarding, priority support), and the risk-reducers (audits, check-ins, guarantees). Price each on its value to the buyer, not its cost to you — that gap is where offers get their power.
Structure two or three tiers, never five. An anchor tier — premium, complete, priced for the few. A default tier where you want most buyers to land; make it the obviously sane choice. An entry tier that is a real product, not a crippled one, for the risk-averse. Name tiers by buyer situation, not by metal-grade adjectives.
Set the price logic before the price. Decide what price scales with — seats, volume, outcomes, flat — by asking what grows when the buyer wins. A metric the buyer resents watching is the wrong metric, whatever the margin math says.
Design the risk reversal. The buyer's real fear is wasting money and looking foolish for choosing you. Absorb it explicitly: a results-conditional guarantee, a paid pilot that credits forward, a clean exit clause. The strongest version you can honor beats the strongest version you can write.
Add urgency only where it is true. Cohort start dates, real capacity limits, bonuses that genuinely expire. Fabricated countdowns train buyers to wait you out, and the trust they burn does not come back at any price.
Write the one-pager and read it as a skeptic. If a stranger cannot repeat the offer to a colleague after one read, simplify until they can.

Output format

An offer one-pager: the outcome statement; a tier table with name, who it is for, what is included, price, and the default flagged; guarantee terms in plain language; urgency terms if any exist; and a three-line FAQ answering the objection you expect most.

Quality bar

The default tier is identifiable in five seconds and defensible in one sentence
Every guarantee is stress-tested: if ten percent of buyers invoke it, the business survives
No tier exists merely to make another look good without being a legitimate purchase itself
Price appears after value in every artifact; sequence is part of the offer
The price objection has a designed response that is not a discount — trade scope, term, or timing instead

Worked example: tier sketch for a bookkeeping service

Outcome statement: "your monthly close done by the 5th, every month, without hiring." Entry — "Solo Close": monthly reconciliation and close, async questions, for founders still under one entity. Default — "Growth Close": everything in Solo plus payables workflow, a monthly review call, and quarter-end reporting pack; flagged as the tier most clients choose, priced roughly double Solo. Anchor — "Audit-Ready": everything in Growth plus controls documentation and an annual audit-prep sprint, priced for the few who need it. Guarantee on all tiers: miss the close date two months running and the third month is free. One glance tells a buyer where they belong — which is the entire point of structure.