For companies selling to platform teams, SREs, and backend engineers. Built for the post-Heroku generation: the buyers who read your changelog before they read your homepage.
Detection runs across hiring posts, GitHub repos, public incident retros, conference talks, and changelogs. Frequency counts are rolling 30-day mention volume across the operator pool.
| Angle | Triggered by | Sample subject line | Reply rate |
|---|---|---|---|
| runbook_automation | stale_runbooks · on_call_burnout | the 3am rollback you wrote up last month | |
| oncall_rotation_pain | on_call_burnout · staff_eng_gap | your sev-2 graph from the q4 incident report | |
| platform_ramp_cost | platform_team_ramp · finops_role_open | 4 platform-eng job posts in 6 weeks — what's the plan | |
| post_migration_audit | heroku_migration · terraform_drift | after the heroku cutover, the second bill | |
| observability_gap | observability_gap · slo_violations | the metric you wish you'd been emitting in march | |
| k8s_consolidation | kubernetes_sprawl · multi_cloud_cost | the 14th cluster question | |
| deploy_freeze_winback | deploy_freeze · ci_flake_rate | thursdays without a deploy | |
| datadog_bill_intervention | datadog_bill_shock · finops_role_open | the line item nobody on your team knows how to lower | |
| first_sre_hire | first_sre_hire · platform_team_ramp | before you write that sre job posting | |
| secrets_hygiene | secrets_leaked · dx_metrics_open | the credential rotation nobody scheduled | |
| dx_metric_starter | dx_metrics_open · staff_eng_gap | your first dora dashboard | |
| generic_intro | (no signal — control) | quick question about your stack |
Three real drafts, redacted. Each opens with a citation — a public incident, a hiring post, a recent talk — and closes with a small ask. No deck. No "10 minutes."
From: [REDACTED-OPERATOR] To: [REDACTED-PROSPECT] Subject: the 3am rollback you wrote up last month Maya — saw your incident retro on the February regional failover. The bit where an SRE had to grep commit history to find the last working runbook is exactly the fire we help platform teams put out. Two engineers at [REDACTED-CUSTOMER] cut MTTR 41% after we replaced their wiki runbooks with structured ones tied to alert IDs. No deck. 12-min loom if useful. — Jordan
From: [REDACTED-OPERATOR] To: [REDACTED-PROSPECT] Subject: 4 platform-eng job posts in 6 weeks — what's the plan Pat — noticed you opened a fourth platform-eng req on March 11th, and your golden-path doc on the eng blog hasn't been touched since November. fwiw the math usually goes: every new platform hire spends ~6 weeks reverse-engineering what the last one built. We sit in between — codify the path so the next req ramps in 9 days, not 9 weeks. Worth a 10-min look at how [REDACTED-CUSTOMER] did it? If timing's wrong, ignore. No follow-up cadence on this one. — Sam
From: [REDACTED-OPERATOR] To: [REDACTED-PROSPECT] Subject: the line item nobody on your team knows how to lower Hey Ravi — your finops req went up last Tuesday. The JD calls out "observability spend optimization" twice. tl;dr: that's almost always custom metrics cardinality, and it's almost always fixable in a week without dropping coverage. We mapped it for [REDACTED-CUSTOMER] last quarter — 38% off the monthly bill, same alert fidelity. Happy to send the audit template even if you don't talk to us. — Iris
pack: devtools_infrastructure version: 1.4 weights: digitalMaturity: 0.28 # public eng blog, github org, conference talks channelDependency: 0.16 # platform-led growth signals productFit: 0.22 # explicit pain match (top 3 signals) companySize: 0.18 # 50–800 engineers accessibility: 0.16 # contact route exists, not gated by sdr-only forms tier_thresholds: A: 0.78 B: 0.62 C: 0.45 hard_disqualifiers: - engineering_headcount: < 20 - infrastructure: bare_metal_only - last_funding_round_age_months: < 12 - no_public_facing_infra: true half_life_days: 45 # signal staleness decay refresh_cadence_hours: 168 # weekly re-score
Override any weight per campaign. Disqualifiers are hard — if a company trips one, it's not scored, it's removed. We'd rather miss a fit than waste a domain.
Dry. Lowercase when in doubt. Code references over adjectives. Sentences sometimes start with "fwiw" or "tl;dr" because that's how Slack messages start. The signoff is a first name, not a title — "Jordan", not "Jordan Reyes, GTM Lead." A devtools email that begins with "Hope this finds you well" is dead on arrival. The voice is engineer-to-engineer, even when it isn't. If your draft sounds like it was written for a CMO, you've already lost.
Anonymized by request. We share names on a private call.