Wiki
One-pager
On this page
Consulting firm's transformation one-pager
A one-pager is exactly what it sounds like: a single page (sometimes two) that tells someone everything they need to know about your product, service, or idea, without making them read a 30-page document. In B2B it's the thing you leave behind after a sales call, the sheet a buyer forwards to their colleagues, or the summary an exec drops into a board pack. Unlike a case study or a whitepaper, it has to land the core value in the time someone spends scanning, which is about 30 seconds before they decide whether to keep reading.
A good one-pager has a clear shape: a headline that names the problem you solve, two or three sentences of context and pain, a tight description of your solution, three or four quantified benefits (hours saved, errors cut, revenue added), one piece of proof (a testimonial or a number), and a single obvious next step. Vague benefits like "we save you time" are weak. "Average customer saves 12 hours a week on manual data entry" is what people remember and repeat.
The reason it matters is leverage. You're rarely in the room when a buying committee actually decides. The one-pager carries your message into rooms you'll never see, and keeps it consistent no matter which salesperson sent it. It also doubles as a filter: prospects who actually read and engage tend to be the ones worth chasing.
Where it gets practical is in how you make it. Say you're a SaaS founder building a CFO-targeted one-pager, headline "Reduce planning cycle time from 6 weeks to 3 days". You can draft the whole thing in Gamma by typing the situation, the four benefits, and a one-line case study, and letting it lay out a clean scannable page you export as a PDF leave-behind. If your brand cares about pixel-level polish, design the master template in Figma once, with locked type and colour styles, so every rep produces an on-brand sheet instead of mangling the layout in slides. And if you're running three or four versions for different buyer profiles, keep them as a living set in Notion: one source page per profile, so when the messaging changes you update it in one place and the whole team is instantly on the latest version.
Two habits separate good one-pagers from forgettable ones. Use headings that make a claim instead of a label, "How we cut implementation from 4 months to 4 weeks" beats "Our Solution". And keep it genuinely scannable: short paragraphs, a few bullets, one diagram only if it clarifies. A cluttered page gets skimmed and binned.
A management consulting firm created a one-pager for their organisational transformation services targeting VP-level operations leaders. Rather than describing consulting services generically, the one-pager told a story: situation (organisation struggling with cross-functional execution), challenge (typical transformation takes 18 months and costs £2m+ with high failure risk), solution (their proprietary four-month engagement model), benefits (reduced timeline, lower cost, proven methodology with 87% success rate), and case study (financial services company completed transformation in 4 months with £400k investment, generating £12m annual savings).
How to apply
Start by identifying your target audience for the one-pager. Are you selling to technical buyers, procurement teams, or executive sponsors? Tailor the messaging and emphasis accordingly. A technical one-pager emphasises integration requirements and architecture; a procurement one-pager emphasises cost and implementation timeline; an executive one-pager emphasises strategic impact and risk mitigation.
Structure the one-pager to tell a story: situation, complication, resolution, benefits, evidence, next step. Use headings that pose questions or make assertions rather than generic labels. Instead of "Our Solution," try "How we reduce implementation time from 4 months to 4 weeks." This narrative approach keeps reader attention and makes the value proposition immediate.
Include quantifiable benefits wherever possible. Instead of "We save you time," state "Average customer saves 12 hours per week on manual data entry." Instead of "We improve quality," state "Reduce errors from 8% to 0.5%." Specific numbers are more persuasive and memorable than generic benefits. When creating multiple one-pagers, A/B test different versions with your sales team to identify which version generates more engagement and higher conversion rates.
Why it matters
For B2B growth teams, one-pagers accelerate the sales process by providing prospects with organised information they can share with buying committee members. Rather than relying on sales calls to communicate the value proposition to each stakeholder, the one-pager standardises your message. This is especially valuable in B2B sales where multiple stakeholders may need to evaluate your solution independently before the buying group meets.
One-pagers also reduce sales team inefficiency. Instead of customising slides or creating ad-hoc materials for each prospect, your team uses a standard one-pager tailored to 3-4 common prospect profiles. This standardisation ensures consistent messaging across your sales team and reduces the time spent creating sales materials rather than selling.
One-pagers serve as quality filters. Prospects who take time to read and engage with a one-pager often signal greater buying intent. Conversely, prospects who don't engage with a one-pager often become long sales cycles with low close probability. Early identification of engagement helps your sales team prioritise efforts toward truly interested prospects.
SaaS vendor's technical one-pager
An API platform company created a technical one-pager for engineering teams evaluating integration options. Headline: "Connect to 500+ applications without custom coding." The page included architecture diagram showing how pre-built connectors eliminated development work, benefits (faster integration, lower development cost, reduced maintenance), and social proof (used by 1,200+ companies including three of the top five insurance providers). This one-pager was the primary document technical buyers shared with their procurement teams to justify the platform choice.
Software company's ROI-focused one-pager
A financial planning software company created a one-pager targeting CFOs with a headline: "Reduce planning cycle time from 6 weeks to 3 days." The page included a situation statement (annual planning is time-consuming), the challenge (finance teams spend 400+ hours annually on spreadsheet wrangling), the solution (cloud-based planning platform with collaborative modeling), key benefits (reduced planning time, improved forecast accuracy, better stakeholder alignment), and a one-sentence case study ("A £500m healthcare company reduced annual planning from 8 weeks to 2 weeks"). This one-pager became the sales team's most effective leave-behind, with 45% of recipients requesting a demo.