Send the one-pager immediately after the demo. Save the case study for when the deal stalls or a new person joins the buying committee. Mixing up those two moments is the single most common mistake I see founders make in the week after a good call.
A one-pager exists to survive being forwarded. It has to make sense in under 30 seconds to someone who was never on the call, usually a CFO or a VP who only sees the summary. A case study exists to reduce risk for someone who is already leaning toward yes but needs proof it will work for someone like them. They answer different questions, for different readers, at different points in the deal. Send the wrong one at the wrong stage and you either overwhelm a prospect who just wanted a recap, or leave a skeptical one without the evidence they actually needed.
What each document is actually for
A sales one-pager is a summary, not a pitch. Its job is to answer three questions in the time it takes to skim a Slack message: what does this do, who is it for, and why does it matter now. If a forwarded one-pager needs a follow-up call to make sense, it failed.
A case study is evidence, not a summary. Its job is to show a specific customer, ideally one that looks like the prospect, getting a specific result. It exists to answer the question every buyer is quietly asking: has this actually worked for someone in my position, or am I the experiment?
The three signals that tell you which to send
Three signals decide which asset earns the send, not gut feel or habit.
- Who receives it next. If your champion is about to forward your email to a CFO or a committee who never saw the demo, send the one-pager. If your champion already believes you and needs ammunition to defend that belief internally, send the case study.
- How many calls have happened. After a first or second call, send the one-pager. It closes information gaps. After the third call or a stalled deal, send the case study. It closes trust gaps, not information gaps.
- What kind of objection you're hearing. "I don't fully understand what this does" is a one-pager problem. "I'm not sure this will work for a company like mine" is a case study problem. Sending a one-pager to answer a trust objection just restates what they already know.
What most founders get wrong
Most early-stage founders default to the case study too early, because it feels like the stronger asset. It isn't stronger at every stage, it's stronger at a specific stage.
Sending a full case study after a first demo asks a prospect to do the connecting work themselves: read someone else's story and translate it into their own situation. Most prospects won't do that translation in week one. They'll skim it, forward nothing, and the deal goes quiet.
The other common mistake is sending both at once. Two documents dilute the ask. Pick the one that matches the reader and the stage, and let the other one wait for the next signal.
The move that gets a stalled deal moving again
When a deal goes quiet after the demo, the fix usually isn't another check-in email. It's a case study, sent to the person in the deal who has the least visibility into your product but the most influence over the budget.
The mechanism is simple: your champion already believes you, but they can't win an internal argument on your behalf using only their own opinion. A case study gives them someone else's result to point to. It turns "I think this is worth it" into "here's a company like us that got this result," which is a much easier sentence to defend in a budget meeting you're not in the room for.
What to send this week
If you don't have a one-pager yet, build it before anything else. It gets used on almost every deal, while a case study only gets used on deals that stall or involve a committee.
Structure it in six parts: the problem in one sentence, the fix in one sentence, three concrete outcomes with numbers, one line on who it's for, one line on implementation time, and a single next step. Nothing else. If it doesn't fit on one page without shrinking the font, cut content, don't shrink the font.
Frequently asked questions
Can I combine a one-pager and a case study into one document?
Not well. A one-pager has to work in 30 seconds. A case study needs room to build a narrative. Combining them usually produces a document too long to skim and too short to convince.
Should I send a case study before the first call instead of after?
Only if the prospect asked for proof before booking, which is rare. Sending it earlier than needed makes buyers skip straight to comparing you against competitors before they understand what you actually do.
What if I don't have a real case study yet?
Use a single-customer story instead of a placeholder logo wall. A specific number from one real customer beats a vague claim about results every time.
How long should a case study be for early-stage sales?
Long enough to name the problem, the fix, and one hard number. That's usually 300 to 500 words, not a full page of prose.
The one-pager and the case study aren't competing for the same job. One earns attention from someone who's never heard of you. The other earns trust from someone who already believes you but needs backup. Build both, but only send the one the deal actually needs right now.