The Persuasion Framework

Every technical founder communicates in features: 'We use transformer-based NLP models with fine-tuning on your proprietary dataset.' This sentence means something to an engineer and almost nothing to the buyer — a CTO, CEO, or Head of Operations who wants to know what problem you solve and what outcome they'll get. The Features-Advantages-Benefits (FAB) ladder is a communication reframe that translates technical capability into business value: Feature: what the product or service does ('fine-tuned NLP model'). Advantage: why that's better than alternatives ('more accurate than off-the-shelf models because it's trained on your specific language and data'). Benefit: the outcome the buyer actually cares about ('reduces mis-categorised support tickets by 40%, cutting resolution time and freeing your support team for complex issues'). Buyers buy benefits. They justify purchases with advantages. Features are table stakes that they assume you have. When you lead with benefits, you're speaking directly to what matters to the person who will sign the contract. A practical test: read any piece of writing you've created for sales or marketing and underline every sentence that talks about you (your methodology, your tools, your process). Then count the sentences that talk about your client's outcomes. The ratio should be at least 2:1 in favour of outcomes. Most technical founders have it backwards — and that's why their proposals sound like technical documentation rather than business cases.

PAS (Problem-Agitate-Solve) is one of the most durable copywriting frameworks in existence, and it's directly applicable to every piece of sales writing you'll create: cold emails, LinkedIn posts, proposal introductions, pitch deck openings. Problem: State the specific problem your prospect is experiencing. Be precise, not generic. Not 'most companies struggle with AI implementation' — but 'most logistics companies that hire an AI consultant end up with a working prototype that never reaches production because the internal team lacks the context to maintain it.' Agitate: Explore the consequences of that problem in more depth. What does it cost them? What decisions does it prevent? What opportunities do they miss? What frustration does it create? This step is uncomfortable to write because it feels like twisting the knife — but it's actually what makes prospects feel seen and understood. If you can accurately describe their problem better than they can, they assume you know how to solve it. Solve: Introduce your solution as the resolution to the specific problem you've described. The solution should feel inevitable after the problem and agitation — not a jarring pivot to a sales pitch, but a natural progression. Critical constraint: the problem you state must be real and specific to your target client. Generic problems produce generic writing that doesn't resonate with anyone. The more specifically you can name the problem — including using your prospect's own language for it — the more your writing will feel like it was written for them personally.