4 min read ·
What Does a One Pager Look Like? A Startup Example
See a realistic startup one-pager layout, what each section should contain, and how to present technical insight, traction and a funding ask clearly.

A one-pager is a single-page document with a clear headline, short labeled sections, and enough white space to scan easily. For a startup pitching investors, it should look like a compact company brief—not a pitch deck squeezed onto one sheet.
The reader should be able to identify the customer, problem, product, evidence, team, and next step without hearing you explain them. Its job is to earn a useful follow-up conversation, not complete diligence.
A practical one-page layout
Use a portrait A4 or US Letter page. A simple structure is:
- Top: Company name, one-sentence description, and product link.
- Middle: Customer and problem; product and technical insight; traction; business model and market opportunity.
- Bottom: Relevant founder background, funding ask or next milestone, and contact details.
One column works well for a text-led brief. Two columns can work if each section remains short. Start with readable body text—roughly 11–12 points—and cut copy rather than shrinking it to fit. Use one accent color and consistent section headings. Add a screenshot or diagram only if it explains something faster than words.
This is a suggested layout, not an investor-mandated template. Y Combinator’s seed fundraising guide recommends a one- or two-page executive summary, preferably one, covering vision, product, team and contact information, traction, market size, revenue, and prior and current fundraising.
What a startup one-pager looks like
The example below is fictional. All company details, metrics, and funding amounts are illustrative—not benchmarks or claims about a Lunera investment.
ChangeSignal — fictional startup example
Catch breaking data-schema changes before they reach production.
Customer and problem Data-platform teams at B2B software companies manually review upstream schema changes. A renamed field or changed type can break downstream pipelines; existing checks often catch the failure only after deployment.
Product and technical insight ChangeSignal checks proposed schema changes in CI against downstream dependencies and flags incompatible changes before merge. Its initial advantage is tracing producer-to-consumer dependencies, rather than checking each schema in isolation. Coverage is currently limited to supported SQL workflows.
Evidence — as of October 2026 Five teams are testing the product, including three paid pilots at $500 per month each. Two teams have used it weekly for eight weeks. There are no annual contracts yet; renewal and broader deployment remain unproven.
Business model and market Initial buyer: the head of data at a software company with a dedicated data-platform team. The pricing hypothesis is an annual subscription based on monitored pipelines. Expansion into larger enterprises depends on supporting more data systems and meeting security requirements.
Team Two technical cofounders: one previously built internal data-platform tooling; the other worked on database query planning. Both are building the product and working directly with pilot teams.
Funding and next milestone Bootstrapped to date. Seeking $750,000 to add two integrations and test whether pilots convert to annual contracts over the next 12 months.
Next step A 20-minute product walkthrough covering dependency tracing and pilot results.
In your version, add a working product or demo link and a founder’s contact details. If you have a defensible market estimate, include the calculation and its source. If not, describe the initial customer segment and label the market-sizing work still to be done.
What makes the page useful
Explain the mechanism, not just the category. “AI-powered data infrastructure” says little. Describe what enters the system, what it does, and what changes in the customer’s workflow. State a material limitation rather than implying universal coverage.
Separate evidence from ambition. Paid pilots, recurring contracts, free users, and customer interviews are different signals. Give metrics a date and define what they measure. If you are pre-product, describe what you have learned and what you will test next; do not manufacture a traction section.
Connect money to a testable milestone. “Hiring and growth” is less informative than specifying what the funding should help prove. Keep the detailed budget elsewhere; use the page to make the plan understandable.
Leave out material that needs a longer format. Full architecture diagrams, financial models, cap tables, and lengthy founder biographies belong in follow-up materials. For the broader narrative, use the business pitch guide.
Before sending, export to PDF, confirm it is actually one page, check every link, and ask someone unfamiliar with the company to explain it back to you.
For Lunera specifically, a designed one-pager is optional: the firm’s homepage says a concise note covering what you are building, why now, who the customer is, and a helpful product link is enough to start.