Cold email examples for 10 top companies

Hi [Name], Stripe's enterprise motion has accelerated hard — custom pricing, dedicated AEs, longer sales cycles. Teams at that stage usually hit the same wall: CRM data that doesn't reflect what's actually happening in the pipeline. We give enterprise sales leaders real-time deal health signals so you can call your number with confidence instead of gut feel. Worth 20 minutes to see if it fits? Happy to pull up a live demo.

Hi [Name], When a sales org grows as fast as Stripe's has, the gap between what's in the CRM and what will actually close widens fast. Reps update deals optimistically, managers roll up with gut feel, and the number you give the board is more hope than data. We surface deal risk signals automatically — no rep behavior change required. Happy to show you what it looks like for an org your size.

Hi [Name], We work with revenue ops teams at a few high-growth fintech companies going through the same enterprise transition Stripe is — the pattern is always the same: the CRM isn't telling the truth, and the forecast suffers. One team went from 60% to 88% forecast accuracy in a single quarter using our signals layer. I think Stripe would see similar results. Can I send the case study?

Hi [Name], Notion's partner ecosystem has grown quickly — which usually means the team managing it is stretched thin. Onboarding new partners manually doesn't scale past a certain point. We automate partner intake, credentialing, and early enablement so your team can focus on the relationships that move revenue. Would a 15-minute call this week make sense?

Hi [Name], The problem with fast-growing partner programs is that onboarding becomes the bottleneck. Every new integration partner needs hand-holding, and your best people end up doing admin work instead of strategic relationship-building. We cut partner time-to-activation by eliminating the manual steps in the process. Is this something you're thinking about for this year?

Hi [Name], A productivity SaaS we work with had a similar challenge — their partnership team was growing the program but couldn't activate partners fast enough to see ROI. After automating their onboarding flow, they tripled their active partner rate without adding headcount. I think Notion could see similar results. Happy to share the specifics if it's relevant.

Hi [Name], Linear's own product is built around making engineering teams faster — but most eng leaders I talk to still can't answer a simple question: where is the time actually going? We give VPs of Engineering a real-time view of cycle time, bottlenecks, and delivery predictability — across teams, without requiring engineers to do anything differently. Worth a quick look?

Hi [Name], Once you have more than 3 or 4 squads, the signals that tell you where things are slowing down stop being obvious. Sprint retrospectives become post-mortems, and by the time you see a problem in the data it's already cost you two weeks. We surface leading indicators — not lagging ones — so you can intervene before the delay lands. Is delivery predictability something you're tracking closely right now?

Hi [Name], A developer tools company similar to Linear used our platform to diagnose a recurring bottleneck in their code review process — something that wasn't visible in Linear or Jira alone. After fixing it, their average cycle time dropped 30% in 6 weeks. Happy to share what that analysis looked like if it's relevant to what your team is working on.

Hi [Name], Shopify's merchant base is enormous — which makes it nearly impossible to manually identify which stores are struggling before they downgrade or leave. We give merchant success teams early warning signals: GMV trends, feature adoption gaps, and support ticket patterns that predict churn 60–90 days out. Would it be worth a conversation to see if this fits your scale?

Hi [Name], The merchants who churn quietly are the hardest to retain. They don't raise their hand — they just stop selling, stop using features, and eventually downgrade or leave. By the time a CSM notices, the relationship is already cold. We flag these accounts 2–3 months early using behavioral signals, so your team can intervene when there's still time to make a difference. Is proactive retention something your team is actively working on?

Hi [Name], We work with a few large e-commerce platforms with similarly large and diverse merchant bases. The common thread: reactive CS teams waiting for support tickets miss the merchants who leave quietly. One platform reduced their silent churn rate by 22% in one year after deploying our early warning layer. Happy to share how they structured the rollout if it's relevant.

Hi [Name], HubSpot's sales team is large and growing — which means SDR ramp is a recurring cost center. Most teams I talk to accept 3–5 months to full productivity as normal, but it doesn't have to be. We run structured onboarding programs that get new SDRs to quota in 6–8 weeks, built around your existing playbooks and ICP. Worth a conversation to see if the timing makes sense?

Hi [Name], When you're hiring SDRs at scale, a 30-day delay in ramp per rep compounds fast. At 20 hires a year, that's 600 person-days of lost productivity before anyone hits their stride. Most of that delay is fixable — it's onboarding structure, not raw talent. We specialize in compressing ramp through structured, repeatable enablement programs. Would it be useful to show you what that looks like?

Hi [Name], A B2B SaaS company with a similar-sized SDR org to HubSpot came to us after noticing their ramp times were creeping up with each new hiring class. After rebuilding their onboarding program with our framework, they cut median ramp time from 14 weeks to 7 — and first-quarter attainment went up 40%. Happy to share the structure we used if it's relevant to what you're thinking about for this year.

Hi [Name], Figma's own design system is a reference point for the industry — but managing asset governance across a large, fast-moving design org is a different challenge than building great tooling. We help design ops teams at Figma's scale track component usage, flag outdated assets in production, and enforce system adoption without slowing teams down. Would a quick demo be useful?

Hi [Name], Even at companies that are obsessed with design quality, the same problem shows up: the design system is updated, but no one knows which product surfaces are still running old components. The drift is invisible until it becomes a visual consistency problem in production. We make it visible — automatically scanning repos and flagging where outdated components are still in use. Is this something your team is thinking about?

Hi [Name], A design-forward product company similar to Figma struggled with the same internal challenge: their design system was excellent, but adoption across product teams was inconsistent. After implementing our governance layer, they reached 95% component adoption across all new features within two quarters. Happy to share what the rollout looked like — might be relevant to what your team is working on.

Hi [Name], Rippling is growing fast, which means your comp plans are probably getting more complex every quarter — new segments, new SPIFs, new accelerators. Most teams manage this in spreadsheets until something breaks. We give sales ops and finance a single source of truth for comp modeling, approvals, and payouts — no more reconciliation every month. Worth 20 minutes to see if it fits where you are right now?

Hi [Name], When a sales org grows quickly, comp plan complexity compounds — more tiers, more exceptions, more manual calculation. The spreadsheet that worked at 10 reps breaks at 50, and finance and sales ops end up spending a week per month on reconciliation. We eliminate that entirely. Comp is calculated automatically, reps can see their earnings in real time, and disputes drop significantly. Is comp administration a pain point for your team right now?

Hi [Name], We work with a few HR tech companies that went through the same scaling pain — their comp process was held together by spreadsheets and heroics from one or two people. After moving to our platform, one team saved over 40 hours per month in comp admin and reduced rep payout disputes by 70%. Happy to share what the transition looked like — might be relevant given where Rippling is right now.

Hi [Name], Brex is competing in an increasingly crowded space — which means revenue predictability matters more than ever. Most CRMs give you a number, not a story. You can see deal amounts but not deal health. We layer behavioral signals on top of your CRM data so you can see which deals are actually moving and which ones are stalling before it shows up in the forecast. Would it be worth a quick conversation?

Hi [Name], Enterprise fintech deals are complex — multiple stakeholders, compliance reviews, long procurement cycles. The risk signals are there, but they're buried in email threads, call notes, and Slack messages. By the time a deal shows up as "at risk" in Salesforce, it's usually already lost. We surface those signals automatically, so your team can act when it still matters. Is this a challenge you're actively working on?

Hi [Name], We work with a few high-growth fintech companies selling into a similar enterprise buyer profile — long cycles, multiple stakeholders, lots of deal complexity. One company used our pipeline intelligence layer to identify a consistent pattern in deals they were losing, fixed their approach, and improved their win rate by 18% over two quarters. Happy to share the specifics if it's relevant to what your team is working on.

Hi [Name], Vercel produces some of the best developer content in the industry — docs, blog posts, conference talks. But most DevRel teams still can't answer a simple question: which content is actually driving activation and retention? We connect content engagement to product usage so you can see what's moving the needle and double down on what works. Would a quick conversation be useful?

Hi [Name], Developer relations is notoriously hard to measure — you produce content, run events, ship docs, and the results show up months later buried in activation metrics. Leadership wants ROI, and it's nearly impossible to show. We give DevRel teams a clear line between content touchpoints and downstream product behavior, so you can finally answer the attribution question with data. Is proving DevRel impact something you're thinking about right now?

Hi [Name], A developer infrastructure company similar to Vercel used our analytics layer to map their content and community activity to product signups and activation rates for the first time. They discovered that one documentation series was driving 30% of new signups — something they never would have known without connecting the data. Happy to share how they set it up. Might be relevant to how your team is thinking about measurement.

Hi [Name], Airtable's own product is built for teams that want to move faster — but most sales orgs I talk to still have reps manually updating records, copying data between tools, and chasing approvals. We automate those handoffs inside your existing stack, so your reps spend more time selling and less time doing data entry. Worth a quick look at what that would look like for Airtable's team?

Hi [Name], The hidden cost in most sales orgs isn't headcount — it's the hours each rep spends on tasks that shouldn't require a human. CRM updates, handoff emails, quote generation, approval requests. At 30–60 minutes per rep per day, that adds up to weeks of selling time lost every month. We eliminate the most common of those steps automatically. Is sales process efficiency something you're focused on right now?

Hi [Name], We worked with a work management SaaS company similar to Airtable whose reps were spending nearly an hour a day on post-call admin. After automating their handoff and update workflows, reps got back an average of 5 hours per week. That translated directly into more pipeline activity — and closed-won went up 12% the following quarter. Happy to share the specifics if it's relevant to what your team is thinking about.