The VC one-pager that gets a meeting (2026 structure + 5 examples)

The VC one-pager has quietly become the most underrated piece of fundraising collateral in 2026. A well-structured one-pager — six sections, fits on one page, no marketing fluff — gets a partner meeting at 2-3x the rate of a cold email with no attachment, and at higher rate than a 15-slide deck. This is the structure, the screen-reading patterns partners use to evaluate it in 60-90 seconds, and 5 real examples that worked.

For most of the 2010s, the seed fundraising attachment was the deck. For the last 18 months, it's been shifting toward the one-pager — partly because partner inboxes have gotten worse, partly because the AngelList Syndicates / OpenVC / cold-DM outbound shift has trained partners to triage on a single page before opening the deck. Founders who haven't migrated their cold outreach to the one-pager-first model are losing meetings.

This guide is the 6-section structure I've used at Causo, the patterns I see partners scan for, and the failure modes that put one-pagers in the trash.

The 6 sections, in scan order

A partner reading your one-pager goes in this order, every time:

1. Header — company name, one-line description, raise size, date.
2. Problem — what specifically is broken, for who, how often.
3. Solution — what you built, how it works in one mechanism.
4. Traction — numbers and dates. The single most important section.
5. Team — who, briefly, and why this team for this problem.
6. Ask — what you're raising, what it gets you, who you've already closed.

Hit them in that order. Reverse them, hide them, or merge them, and the partner's scan path breaks. Partners read by lane; one-pagers that respect the lane structure get processed in 60 seconds.

Section-by-section: what to put, what to cut

Section 1 — header (10% of page). Company name + one-line description, raise size + date ("May 2026" — not just the year), one link. Cut: tagline, mission statement, founder photo.

Section 2 — problem (15%). Who the buyer is, what they do today, why it's getting worse — all specific. "B2B SaaS sales reps at 50-500-rep companies spending 11 hours/week on CRM entry" beats "a $400B market is broken."

Section 3 — solution (15%). What you built, in one sentence. The concrete mechanism (input → process → output). Optionally one screenshot or diagram. Cut: "AI-powered platform," "transforming the way" anything, brand color blocks.

Section 4 — traction (25% — biggest section). ARR/MRR/users with date stamp. Growth rate with cohort. One named customer or three logos. One non-obvious signal ("44 inbound demos in April, no paid acquisition"). Cut: hockey-stick projections, vanity TAM, "users love us." This is the section that decides the meeting — weight it accordingly.

Section 5 — team (15%). Each founder's name + one specific operational credential. Why-this-team-for-this-problem in one sentence. Cut: full LinkedIn bios, college names, advisor names, photos.

Section 6 — ask (20%). Raise size and structure ("$1.5M seed on a SAFE at $14M cap, $300k closed from [Lead] + [Angel]"). Use of funds in 3-4 bullets. What "good" looks like 18 months out. Cut: detailed budgets, ownership-percentage offers, "happy to discuss."

The 5 example one-pagers

Five real one-pagers that worked, simplified into the patterns. (Names and numbers are altered; structure and texture preserved.)

Example 1: Foundry (B2B SaaS, $1.5M seed)

Header: Foundry — AI agents for outbound sales reps. Raising $1.5M seed. May 2026. foundry.ai

Problem: B2B SaaS sales reps at companies with 50-500 reps spend 11 hours per week on CRM data entry. Post-2024 enrichment costs spiked 40%, making the manual workaround the only economic option. Output: reps prospect 30% less time per week than they did in 2022.

Solution: Foundry deploys an AI agent that lives inside the rep's inbox, watches outbound activity, auto-updates the CRM, and generates the next-best-action queue. Eight reps using us in Q1 saved an average of 9.2 hours/week, redeployed to live prospecting. Loom demo

Traction: $18k MRR as of May 2026, +24% MoM since January. 8 paying customers including Vercel, Linear (eval), and 6 Series A SaaS companies. 44 inbound demo requests in April with no paid acquisition.

Team: Sarah Chen (CEO) — sold Phantom Buster to Walnut for $15M in 2021, ran growth at Pipedrive 2017-2019. Mike Park (CTO) — staff engineer at Salesforce 2018-2024, owned the Einstein agent codebase.

Ask: $1.5M seed, post-money SAFE at $14M cap. $300k closed from First Round (lead) + Garry Tan + Lenny Rachitsky. Use of funds: Sr engineer + GTM lead, agent-builder GA in Q3, $80k MRR target by Q1 2027.

Why this worked: every section is dense with specifics. Numbers are dated. The team credentials are operational, not academic. The raise is partially closed.

Example 2: Loamlabs (devtools, $2.2M seed)

Header: Loamlabs — observability for AI agent infrastructure. Raising $2.2M seed. May 2026.

Problem: Engineering teams shipping agent-based products have no equivalent of Datadog/Sentry. Per a Q1 2026 Linear survey, 76% of agent-shipping teams cite "no visibility into why an agent failed in production" as their top pain. Time-to-debug has increased 4x since baseline LLM-only services.

Solution: A distributed tracing layer purpose-built for agent loops. Wraps any LLM tool-call, captures the decision tree, and surfaces the failure point in one click. Live in 4 dev environments today.

Traction: $7k MRR + 22 design partners committed (4 paying, 18 in 30-day pilot). 3 of 4 paying customers are Series A+ companies (Anthropic, Vercel, [redacted]). NPS 67 across the design-partner cohort.

Team: Two founders, both ex-Datadog (engineering 2018-2024). Built and shipped Datadog's first ML-ops feature in 2022. Personal project mode since Sept 2025.

Ask: $2.2M seed, SAFE at $18M cap, $500k closed from Susa Ventures (lead) + 3 angels. Use of funds: 4 engineers in 12 months, ship the Python + TS SDKs, hit $50k MRR by Q4 2026.

Why this worked: the design-partner numbers are credible (4 paying, 18 piloting), the team's operational credential is specific to the problem, the ask is partially closed.

Example 3: Vellum (consumer, $800k seed)

Header: Vellum — book recommendations for adult readers. Raising $800k seed. May 2026.

Problem: Goodreads has 90M MAU and a 1.4-star average review on the app stores in 2026. Book discovery for serious adult readers is broken: discovery happens through individual influencers (Substack, Goodreads listicles) at the cost of breadth.

Solution: Vellum is an AI-curated reading queue that learns from your last 50 books, pulls patterns across 10K+ Substack book newsletters, and surfaces the next 5 you should read. 12K active users, 7K paying $4/month.

Traction: $28k MRR May 2026, +31% MoM since Feb. 7K paying users (avg cohort retention 71% at week 12). Featured in Lenny's Newsletter, Atlantic, Vox in March 2026.

Team: Solo founder, former senior PM at Audible 2019-2024. Personal Substack on book curation has 14K subscribers.

Ask: $800k seed, SAFE at $8M cap. Closed: $200k from Long Journey Ventures + 4 individual angels. Use of funds: hire a senior eng + designer, scale recommendations to 30K paying users by EOY 2026.

Why this worked: the consumer numbers are unambiguous (paying conversions and retention), the founder's credibility is matched to the product (personal Substack already proves audience), the press coverage validates the timing.

Example 4: Sterling (deep tech, $4M seed)

Header: Sterling — silicon photonic interconnect for AI training clusters. Raising $4M seed. May 2026.

Problem: Cluster bandwidth has scaled 8x since 2023; copper interconnect caps at 800Gb/s/lane. The optical bottleneck now limits 70% of new H200/B200 designs.

Solution: Silicon photonic transceiver hitting 1.6Tb/s/lane at 40% less power than the closest competitor. Two prototypes shipped to design partners March 2026.

Traction: Two LOIs from Tier-1 hyperscalers (one signed, one verbal Q3 2026). Three peer-reviewed papers from the founder team in 2024-2025. Patents filed: 7.

Team: Three founders: ex-Lightmatter principal engineer, ex-Intel optical lead, ex-Stanford photonics PhD. Combined 28 years in silicon photonics, 41 prior patents.

Ask: $4M seed, SAFE at $20M cap. $1M closed (Lux + DCVC + strategic). Funds: 4 photonics engineers, production-grade prototype, 100-unit pilot scale by Q2 2027.

Why this worked: team credentials are individually verifiable, the LOIs and patents prove non-vapor, the ask is partially closed by the right kind of investor.

Example 5: Lattice (vertical SaaS, $1.2M seed)

Header: Lattice — operating system for independent dental practices. Raising $1.2M seed. May 2026.

Problem: 76% of US dental offices still run software designed before 2010. Modernizing the tech is the #1 reason a dentist sells to a DSO — and the product for solo practices doesn't exist.

Solution: Cloud-native practice OS (scheduling, billing, charts, insurance) for the 50K solo and small-group practices that don't want to sell. Live in 8 practices, paid pilot in 12 more from June 2026.

Traction: $14k MRR across 8 paying practices ($1,750 average per-practice MRR). 12-practice pilot signed Q1 2026, expected to convert 8+ to paying by August.

Team: Two founders. One ex-Toast (vertical-SaaS playbook, 2019-2024). One 2nd-generation dentist who ran a 3-practice operation 2017-2024.

Ask: $1.2M seed, SAFE at $10M cap. $300k closed (Bonfire + 4 dentist-operator angels). Funds: customer success + 2 engineers, 50 paying practices by EOY 2026.

Why this worked: the niche is bounded, the team has both software and operator credibility, the 8-paying + 12-piloting pattern is the right shape for vertical SaaS at this stage.

What partners actually scan for

A partner opening a one-pager makes a yes/no/maybe call in roughly this order:

1. Section 4 (traction): are the numbers credible? Three checks: are they dated, are they sourced, and are they unambiguous (MRR not "users")? A partner who doesn't trust the numbers stops reading.
2. Section 5 (team): does the team match the problem? "Operator at exact problem space" is the strongest signal. "Generic-impressive credentials" is the weakest.
3. Section 2 (problem): is the problem real and specific? The check: would a buyer in this segment recognize themselves in the problem statement?
4. Section 6 (ask): is the round actually moving? Partial-close signal ("$300k closed from [named lead]") is the moment a partner shifts from skim to engaged read.

If a one-pager fails any one of these four checks, the meeting doesn't happen. Sections 1 and 3 are scaffolding — they support the four that decide.

Forbidden moves on a one-pager

Things that put your one-pager in the trash within 30 seconds:

• No date. A one-pager without a "May 2026" stamp signals it's been circulating for months. Always date.
• Tagline instead of problem. "We're disrupting the future of work" is a tagline; "B2B SaaS sales reps lose 11 hours/week to CRM entry" is a problem.
• Logos with no number context. A row of customer logos without MRR or activity context reads as posturing. Specific numbers beat designer logo grids every time.
• Open-ended ask. "We're raising a seed round" without an amount or close status is a signal that the founder isn't actually running the process.
• Generic AI claim with no mechanism. "Powered by AI" is meaningless in 2026. Either you describe the input → process → output specifically, or you don't mention it.

When this matters for your raise

The one-pager is the document that decides whether a partner takes the cold email seriously. A founder with a great one-pager and an average outreach cadence outperforms a founder with a great cadence and an average one-pager. The investment is two hours and pays compounding returns across the round.

If you're 30-90 days from opening your raise, Causo handles the partner targeting and outreach mechanics so the time you save goes into the one-pager and the customer references that decide it. Built by founders who've handed out a lot of one-pagers. Start free.