The honest truth about business one-pagers
A one-pager is supposed to distill an entire business concept onto a single sheet. In practice, most of them are garbage because people try to include everything. I spent years watching founders hand executives stacks of information disguised as brevity. It doesn't work. The trick is knowing what to leave out. Start with the problem statement. Not your solution, the problem. If you can't describe the pain point in one sentence, you don't understand it well enough yet. I once had a client who spent three weeks on a one-pager for a logistics platform. The problem was that small manufacturers couldn't track shipments in real time. That's it. The rest of the document was just noise. Your structure should follow this order: problem, solution, market size, business model, traction, team, and the ask. That's it. Seven sections maximum. Each one gets two or three sentences at most. Don't go deeper than that. If something needs more explanation, it belongs in a separate document.
The hardest part is the business model section. Most people write "we make money through subscriptions" and call it a day. That's not a business model. You need to specify the price point, the customer acquisition cost, and the lifetime value. Investors can calculate the rest. They just need the inputs.
Business One Pager Examples
Here are a couple of formats that actually work in practice. Format A: The lean startup version. This works best when you're still validating. Top third is the problem and solution. Middle third covers market and traction. Bottom third is the team and ask. Keep the total word count under 300 words. I use this for early-stage pitches where the numbers aren't solid yet. Format B: The investment ready version. This assumes you have revenue and traction. Same seven sections but each one gets a specific number. Problem: two sentences. Solution: three sentences. Market: TAM, SAM, SOM with sources. Business model: pricing, CAC, LTV. Traction: revenue, growth rate, key metrics. Team: relevant experience only. Ask: how much, what for, what milestone.
Get the Full Details
I've seen both formats convert at roughly similar rates when executed well. The difference is honesty about where you are in the journey.
What nobody tells you about one-pagers
The biggest mistake I see is treating the one-pager as a standalone document. It isn't. It's a map, not the territory. Anyone reading it should be able to ask follow-up questions and get detailed answers from your main deck or data room. If the one-pager tries to answer everything, it fails at its actual purpose. Another thing: your design matters more than your content. I had a one-pager rejected by a VC who later told me, "I couldn't find anything in five seconds." The content was fine. The layout was cluttered. I redid it with more white space and larger section headers. Got the meeting the next week. Same content, different treatment. There's also a hard limit to how much you can compress. If your business has four revenue streams, a regulatory dependency, and operates in three countries, a one-pager will lie by omission. In those cases, give people a two-pager or a brief executive summary instead. Don't force it into one page if it breaks the narrative.
Common failures and how to avoid them
Too much jargon. Write for a smart person who knows nothing about your industry. If you need an acronym explained, either define it or don't use it. False precision. "We'll capture 5% of the market by year three" means nothing without showing your reasoning. Better to say "we're targeting 50 enterprise accounts in year one based on our pilot results with twelve companies." Specific beats precise every time. Ignoring the ask. Every one-pager should end with a clear request. Funding amount, partnership type, hiring need, whatever it is. Leaving it implicit wastes everyone's time.
The best one-pagers I've ever written were the ones where I cut half of what I thought I needed to include. Brevity isn't about removing words. It's about removing ideas you're not ready to defend yet.
