Cold outreach without case studies: what works

How to write cold outreach for a product with no case studies yet

Selling without case studies is the cold-start problem every early-stage rep eventually faces. New product, new category, or a logo-shy customer base — whatever the cause, you're walking into accounts without the social proof that normally does half the persuasion. Most reps respond by either lying gently ("we work with companies like yours") or going generic and hoping volume saves them. Both lose.

The good news: buyers in 2026 are more sceptical of vendor case studies than they've been in years. Logo slides get skimmed. What actually moves a reply is specificity about the buyer's situation and a credible reason to take a meeting. You can build both without a single customer quote.

Replace proof-of-results with proof-of-thinking

The job of a case study in cold outreach is to answer one buyer question: do you understand my world well enough that this conversation will be worth my time? A logo answers it lazily. A sharp observation about how their team actually operates answers it better.

Write outreach that demonstrates you've thought harder about their workflow than the last ten vendors who emailed them. That means naming the specific tool, process, or trade-off they're living with right now.

Compare these two openers to a RevOps leader at a 400-person SaaS company:

"We help RevOps teams streamline their tech stack and improve forecast accuracy."

"Most RevOps teams running Clari forecasts on top of Salesforce opportunity data hit the same wall around Q3: the AI commit number drifts from the human roll-up by 15-20%, and nobody trusts either. Curious how you're handling the reconciliation."

The second has no customer story behind it. It doesn't need one. It signals competence by describing a specific operational headache the buyer recognises immediately.

The mechanism here is what some call earned credibility: you trade the absence of proof-by-customer for proof-by-insight. The buyer infers that if you understand the problem this precisely, the product probably reflects that understanding too.

What to put in the email instead of logos

You have several substitutes for case studies. Use them in combination, not isolation.

A specific point of view on the problem. Not "we solve X" but "here's what we think most teams get wrong about X." This works because it's falsifiable — the buyer can disagree, which gives them a reason to reply. Vague value props give them nothing to push back on.

Founder or builder credibility. If your founders came from companies the buyer respects, say so plainly. "Our founding team built the alerting system at Datadog before starting this" carries weight even with zero customers. Borrowed authority is legitimate authority when it's real.

Design partner framing. Don't pretend you have a customer base you don't have. Invert it: "We're working with six design partners shaping the product right now and looking to add two more in your segment before locking the roadmap." This reframes "no case studies" as "ground-floor access." It also creates genuine scarcity, which is hard to manufacture later.

The specific anomaly you've noticed. If your team has looked at, say, 30 sales orgs' Gong call libraries while building the product, the patterns you've seen are themselves the asset. "Across the demo recordings we've reviewed, the discovery calls that convert share one structural thing in common, and it's not what most enablement decks teach." That's a hook. No customer required.

A concrete artefact. A teardown, a benchmark methodology, a checklist, a 12-minute Loom walking through how their competitor likely structures something. Artefacts replace testimonials because they let the buyer evaluate your thinking directly.

A worked example

Say you're selling a new AI-powered contract review tool. No customers in production yet, three design partners under NDA. Your ICP is in-house legal at Series C-D startups. Here's a cold email built without case studies:

Subject: the MSA redlines your eng team is doing

Liam — at most Series C startups we've looked at, ~40% of vendor MSAs end up partially redlined by engineers or PMs because legal is the bottleneck. Most legal leads we've talked to know it's happening and quietly hate it.

We've built a contract review layer that handles the first pass on standard vendor agreements (DPA, MSA, SaaS terms) so the requester gets cleaned redlines back in under an hour, with your playbook applied. No more eng-as-lawyer.

We're not public yet. Three design partners in your stage band are running it now. We have room for two more before September.

Worth 15 minutes next week to show you the playbook configuration? If the workflow doesn't match how your team operates, I'll tell you.

Note what's doing the work: a specific observation ("eng team doing redlines"), a clear mechanism, honest framing about stage, scarcity that's real, and a soft commitment to disqualify. The "~40%" inside the email is an editorial illustration of how a rep might phrase their own internal observation; the reader treats it as the sender's framing, not as a research citation. If you don't have a defensible number, use "most" or "a meaningful share" — the email still works.

What to cut

Three things to strip from any cold email when you're case-study-light:

1. Vague social proof substitutes. "Trusted by leading teams," "used by fast-growing companies." Buyers read these as code for "we have no logos to share." Better to say nothing.

2. Aspirational ROI claims. Without customer data, any number you put in the email ("save 10 hours a week") is a guess presented as fact. Sophisticated buyers will mentally discount the entire email. Describe the mechanism, not the outcome.

3. The phrase "early access." Overused to the point of meaninglessness. "Design partner," "founding customer," or just naming the specific commercial terms ("locked pricing for the first ten customers in your segment") all land harder.

The takeaway

• Lead with a specific operational observation about the buyer's world, not a value prop. Proof-of-thinking substitutes for proof-of-results when you write it sharply enough.
• Use design partner framing honestly. Turning "no case studies" into "ground-floor access with roadmap influence" is accurate and converts better than logo-mimicry.
• Strip vague social proof ("trusted by leading teams") and invented ROI numbers. Sophisticated buyers downgrade the whole email when they spot either.
• Build one concrete artefact this week — a teardown, a benchmark, a Loom — that you can attach or reference in every sequence until your first customer quotes land.