Funding-round opener — 4 variants.
Four templates for the four funding-event shapes: Seed/Series A (small round, sharp angle), Series B+ (saturated field, must cut through), debt facility (uncrowded, technical), and M&A / acquisition (stack rebuild). Each variant has a fill-in template, the worked example we sent, and reply-rate context from the campaign. Designed to work alongside the funding-round playbook.
Seed / Series A — sharp angle
Smaller rounds at smaller companies. The inbox isn't as saturated (~ 115–200 emails/week vs 300+ at Series B), so the variant can be more conversational and the angle can be a single sharp observation rather than a multi-layered one.
The round mentions {{use_of_funds_quote}} — which usually means {{operational_implication}} lands in the next 60 days.
{{our_one_liner}} — we work with 2–3 other Series-A teams hitting exactly this shape.
{{org_chart_question}}
{{microsmall_ask}}
— [your_first_name]
The round mentions 8 platform-engineering hires by EOY — which usually means the on-call rotation needs to grow from 3 to 8 people inside 6 months.
We built the structured-incident-summary layer for that exact transition — we work with 2 other Series-A infra teams hitting this shape.
Are you the right person to talk about this, or has the on-call rotation moved under the new SRE lead?
If useful, I'll send the 1-page write-up of how the others handled the new-hire ramp — no deck, just the doc.
— Jess
Series B+ — cut through saturation
The hardest funding-round inbox to land in. ~300 cold emails in week 1 at Series B, ~420 at Series C+. The template has to do more work in line 1 because the buyer is filtering hard. Every word has to earn its place. Saturation-aware design: subject names a specific decision, not the round.
The B announcement leads with {{use_of_funds_quote}} as the use-of-funds line — usually means {{operational_implication}} in the next two quarters.
The pattern most teams miss here: {{specific_pitfall}}. We helped 4 teams at the same shape rebuild this before it became the post-launch fire.
{{org_chart_question}}
If you want the {{artifact}} we wrote for one of the other teams, it's 2 pages — I'll send if useful.
— [your_first_name]
The B announcement leads with EU GTM as the use-of-funds line — usually means hiring AEs in London + Berlin in the next two quarters.
The pattern most US-led teams miss: launching with the same pricing tiers in EUR and watching the close-rate drop by 30% because the package-vs-feature mix doesn't fit how EU buyers procure. We helped 4 US SaaS teams rebuild this before the post-launch fire.
Curious whether pricing localization is on your Q3 roadmap, or whether it's deferred until the first EU hires onboard?
If you want the EU-vs-US tier-mapping doc we wrote, it's 2 pages — I'll send if useful.
— Noah
Debt facility — uncrowded, technical
The highest-yield funding-round variant we ship. Debt facilities generate ~ 28 cold emails/week (vs 300 at Series B), so the field is uncrowded enough that the template can be more technical and specific. The buyer's CFO actually reads these.
Most {{round_amount}}+ debt facilities at growth stage carry {{specific_covenant}} — which usually means {{operational_implication}} lands on the CFO's desk inside 30 days of close.
The reason I'm reaching out: we built {{artifact}} for {{n}} venture-debt-backed companies last year, and the one consistent issue is that {{specific_pitfall}}. Most teams build a manual spreadsheet for the lender review and regret it by month 3.
Are you handling that internally, or has the FP&A lead taken it on?
If useful, I can send the {{artifact_short}} we wrote for one of the lender teams — covers the {{n_edge}} edge cases. 1 page.
— [your_first_name]
Most $25M+ debt facilities at growth stage carry an AR-aging covenant (≤ 60 day average) — which usually means a finance-ops project lands on the CFO's desk inside 30 days of close to tighten collections.
The reason I'm reaching out: we built the AR-aging dashboard for 6 venture-debt-backed companies last year, and the one consistent issue is that AR aging in NetSuite doesn't ladder cleanly to lender-defined "qualified receivables." Most teams build a manual spreadsheet for the lender review and regret it by month 3.
Are you handling that internally, or has the FP&A lead taken it on?
If useful, I can send the qualified-receivables spec we wrote for one of the lender teams — covers the 12 edge cases. 1 page.
— Tash
M&A — stack rebuild
Acquisitions create two distinct buying windows: the acquirer is rebuilding the stack for the combined entity (60–120 day window), and the acquired company is renegotiating every vendor contract (immediate). The variant below targets the acquirer side — the bigger ARR opportunity. For the acquired-company side, anchor the email on the renewal-conversation timing instead.
The {{acquired_company}} close means the {{stack_layer}} stack between the two orgs is one of the first integration decisions — usually 60–90 days from close to "we picked one."
The pattern most acquirers hit: {{specific_pitfall}}. We worked with {{n}} acquirers in the last {{period}} on the same stack-consolidation question.
{{org_chart_question}}
Happy to send the {{artifact}} from one of the others — covers the 3 main decision paths. 1 page.
— [your_first_name]
The Atlasware close means the observability stack between Northport and Atlasware is one of the first integration decisions — usually 60–90 days from close to "we picked one."
The pattern most acquirers hit: both teams have strong opinions about Datadog vs Honeycomb, and the decision gets stuck in a 6-week parallel-run that no one wanted. We worked with 3 acquirers in the last 12 months on the same observability-consolidation question.
Are you running this from the platform side or has the integration PMO taken it on?
Happy to send the decision-framework doc from one of the others — covers the 3 main paths and the timeline trade-offs. 1 page.
— Dev
How to use these.
A few notes on running the templates well — based on what works across the four variants and what we've seen fail in customer campaigns.
Pick the variant by stage, not by personal preference. The B+ variant doesn't work for seed companies (over-engineered), and the seed variant doesn't work for B+ (under-engineered for the inbox saturation). Match the variant to the recipient's round shape.
Don't reuse the same use-of-funds quote across multiple accounts. The whole point of the receipts test is that line 1 is specific to this company. If your template makes it easy to swap one company's quote for another, you've defeated the framework. Use Mama (or whatever research tool) to pull the actual quote per account.
Skip 60–70% of the funding announcements you see. The discipline of skipping is what separates the operators who get 13% reply rates from the ones who get 2%. See the playbook for when not to use this signal at all.
Use the artifact offer (line 4) as the real selling tool. The 1-page doc you offer is doing real work — it's the demonstration that you have something specific to say, packaged in a low-commitment format. If you don't actually have a useful 1-page doc to send when they reply, build one before you send the campaign.
The template is the easy part. Getting the use-of-funds quote per account is the hard part.
Mama's funding signal pulls the use-of-funds quotes, named hires, named geographies, and named investor leads — so when you sit down to fill the {{use_of_funds_quote}} slot, the right detail is already there per account.