This is a sample playbook for a fictional product.Jump to GTM plan ↓
Sample · fictional product

Sample ICP and GTM Playbook

Pulsegraph: OpenTelemetry-native error analytics for backend teams.

Sample only — create a playbook to enable these actions.

Pulsegraph turns raw OpenTelemetry traces into ranked error stories — so backend teams stop drowning in noisy alerts and ship fixes for the errors that actually move revenue.

3 ranked ICPs

#1Mid-market SaaS platform teams
Fit 94
high priority
B2B SaaS · 200–1,000 employees
Vertical SaaS, fintech, devtools
$30k–$120k / year

Why this ICP

  • “Pulsegraph's revenue-blast-radius ranking maps directly to how VPEs at this stage justify observability spend to the CFO.”
  • “Two existing design partners came from this exact segment (200–800 employee B2B SaaS with a new platform leader).”
  • “OTel-native is the buying criterion that disqualifies most incumbents and qualifies us in the first 10 minutes of a call.”

Buyer persona

Role: Staff Platform Engineer

Seniority: IC5 / Tech Lead

Other decision makers:

  • • VP Engineering
  • • Director of Platform
  • • Head of SRE

Buying triggers

  • •Hired a Director of Platform or VP Eng in the last 60 days.
  • •Rolled out an OTel collector or service mesh in the last quarter.
  • •Public commitment to consolidate observability tooling (board update, all-hands, eng blog).

Pain points

  • •Sentry + Datadog alerts fire constantly but rarely on the bugs hurting paying customers.
  • •On-call rotations burn out senior engineers; juniors can't triage 4am pages confidently.
  • •Leadership wants a single number for 'error health' tied to revenue, not noisy event counts.

Goals

  • •Cut P1 incident MTTR by half without hiring.
  • •Stop paying for two observability tools when one team uses 20% of each.

Market & sales

Addressable: ~14,000 B2B SaaS companies globally at 200–1,000 employees

Sales cycle: 45–75 days inbound, 60–120 days outbound

Tech stack

Go
TypeScript
Kubernetes
Postgres
Kafka
Sentry
Datadog
Grafana

Where they hang out

  • • CNCF Slack #opentelemetry-collector
  • • rands-leadership Slack (#sre, #platform)
  • • SREcon NA / EMEA attendees
  • • Hacker News (Show HN + Ask HN: on-call)
#2Series-B fintech infra teams
Fit 88
high priority
Fintech / payments · 100–400 employees
Payments, lending, neobanks
$50k–$200k / year

Why this ICP

  • “Money-movement-step taxonomy is unique to us — every fintech reliability team we've shown it to has asked when they can pilot.”
  • “SOC 2 audit-prep pain is acute and recurring at this stage; we directly shorten the cycle.”
  • “Heads of Reliability at Series-B fintechs are a small, high-signal community — references travel fast.”

Buyer persona

Role: Head of Reliability

Seniority: Director / Sr. Director

Other decision makers:

  • • CTO
  • • Head of Reliability
  • • VP Engineering
  • • Director of Compliance

Buying triggers

  • •Shipped a new payment rail (ACH, FedNow, RTP) in the last 90 days.
  • •Entered a new regulated market (UK FCA, EU PSD2, Singapore MAS).
  • •Hired a Director of Compliance or Head of Reliability in the last quarter.
  • •Started a SOC 2 Type II or PCI-DSS audit cycle.

Pain points

  • •A single failed transaction can mean a regulator letter or a chargeback storm.
  • •Compliance demands an audit trail per error class, not a raw event log.
  • •Existing APM doesn't know what a 'failed settlement' is — only what a slow HTTP 500 is.

Goals

  • •Tie every backend error to a specific money-movement step.
  • •Pass SOC 2 + PCI audit prep without a custom data pipeline.

Market & sales

Addressable: ~600 Series-B+ fintech infra teams globally with a dedicated reliability function

Sales cycle: 90–180 days (compliance and procurement-gated)

Tech stack

Go
Rust
Python
Kubernetes
Kafka
Temporal
Datadog
Vanta / Drata
PagerDuty

Where they hang out

  • • Rands Leadership #reliability
  • • Fintech Devs Slack
  • • On Deck Fintech + NY Fintech Innovation Lab
  • • USENIX SREcon attendees with fintech badge
#3Indie devtool startups (pre-Series A)
Fit 72
medium priority
Early-stage devtools · 5–40 employees
Developer infrastructure
$5k–$25k / year

Why this ICP

  • “Free-tier limits are calibrated to cover the first 12 months of a pre-seed devtool team — friction-free top of funnel.”
  • “OSS collector plugin doubles as the install path and the marketing surface in one repo.”
  • “Founders in this segment already live on HN and Dev Twitter — distribution is cheap and measurable.”

Buyer persona

Role: Founding Engineer

Seniority: Founder / Founding eng

Other decision makers:

  • • Founder / CEO
  • • Founding engineer

Buying triggers

  • •First paying customer in the last 30 days.
  • •First production incident or 'site is down' tweet from a customer.
  • •Show HN post about shipping a v1 or first paid tier.
  • •Closed a pre-seed round in the last 60 days.

Pain points

  • •Can't justify a full observability suite, but can't fly blind either.
  • •Every minute spent grepping logs is a minute not building.

Goals

  • •Stand up just-enough error visibility in an afternoon.
  • •Spend < $300/mo until they have real load.

Market & sales

Addressable: ~22,000 indie devtool startups globally with a live production deployment

Sales cycle: Same-day self-serve install; ~14 days from install to first paid upgrade

Tech stack

TypeScript
Next.js
Postgres
Vercel / Fly.io
Better Stack / Sentry free tier

Where they hang out

  • • Hacker News (Show HN, Ask HN)
  • • Dev Twitter / X founder networks
  • • Indie Hackers
  • • OpenTelemetry community Slack

Go-to-market plan

ContextGeo: North America, EUStage: Seed → Series ATeam: 6 (2 GTM, 4 eng)Target: $1.2M ARR in 12 monthsBudget: $18k / month all-inLang: English

Motion summary

hybrid
North star: Weekly active connected services (per workspace)

Product-led core motion with sales-assist on mid-market deals. Self-serve free tier captures the OTel community; one AE handles inbound trials over $20k ARR potential and runs targeted outbound to platform leads at the Top-50 warm-account list.

Funnel model — Mid-market SaaS platform teams in NA/EU

1.

Website visitors

Target: 8,000

OTel content + Show HN posts + community traffic.

2.

Free signups

Conv: 4%Target: 320

Email-only signup, no card.

3.

Connected workspaces (1+ service)

Conv: 55%Target: 176
4.

Qualified for paid (20+ services or > free quota)

Conv: 18%Target: 32
5.

Paid conversions

Conv: 35%Target: 11

8,000 visitors → 320 signups (4%) → 176 connected (55%) → 32 qualified (18%) → 11 paid (35%). At a $1,200 average monthly contract value that's ~$13,200 new MRR / month, ~$158k new ARR/quarter steady state by month 6.

90-day rollout

Foundation
Days 1–30
· Founder + 1 eng

Goals

  • •Self-serve onboarding under 10 minutes from signup to first connected service.
  • •5 paying design partners signed via warm intro.
  • •OTel collector plugin published with install docs.

Actions

  • →Ship in-product onboarding checklist + Slack notification install.
  • →Run 12 design-partner interviews; convert 5 to paid annual.
  • →Publish OSS collector plugin + 2 deep-dive blog posts.
Validate
Days 31–60
· Founder + first AE

Goals

  • •Launch publicly on HN + Product Hunt; hit top 5 on launch day.
  • •First fintech reference customer contracted (annual).
  • •Outbound sequence to Top-50 warm accounts live.

Actions

  • →Coordinate HN + PH launch; pre-line 20 community comments.
  • →Hire AE; ramp outbound to 80 touches / week on Top-50 list.
  • →Stand up usage-triggered upgrade emails (5+ services connected).
Scale
Days 61–90
· AE + first marketer

Goals

  • •25 paying workspaces total, $30k MRR run rate.
  • •2 case studies published (1 SaaS, 1 fintech).
  • •1 enterprise pilot in flight with security review started.

Actions

  • →Hire content marketer; ship a weekly OTel deep-dive.
  • →Run a SREcon sponsored talk + booth conversion list.
  • →Roll out SOC 2 Type I attestation in time for enterprise pilot.

Channel mix & budget

Total monthly: $18,000

35%

Developer content + OTel community

Our buyers live in the OpenTelemetry Slack and read deep-dive blog posts. Owned content compounds and seeds outbound talk tracks.

→ 120 signups / month and 35% of paid pipeline by month 3.

25%

Outbound to Top-50 warm accounts

Mid-market platform teams rarely self-serve all the way to a $30k contract. One AE running multi-channel outbound on the Top-50 list closes the gap.

→ 6 qualified meetings / week and 4 closed-won / quarter.

20%

Conference sponsorship (SREcon, KubeCon)

Two anchor events per quarter put the founder in front of the exact persona and produce a measurable booth-scan list to follow up on.

→ 300 booth scans → 40 meetings → 6 paid / event.

15%

Product Hunt + HN launches

Episodic awareness spikes that disproportionately convert OSS-curious devs. Cheap relative to paid ads in this segment.

→ 1,500 signups in the launch week; 8% activate to connected workspace.

5%

Targeted LinkedIn ads (warm-account match)

Small always-on budget retargeting the Top-50 warm-account list to keep us top-of-mind around outbound touches.

→ Lift on outbound reply rate from 8% → 12%.

Paid acquisition is intentionally < 10%. Spend follows where qualified buyers actually pay attention, not where it's easiest to spend.

Team & tooling

Hires

Day 45
Account Executive (mid-market) — Convert inbound trials > $20k ARR potential and run Top-50 outbound.
Day 75
Content marketer (developer-focused) — Sustain weekly OTel deep-dives and own the developer blog.

Tools

CRM: Attio · $348

$29/seat × 12 once AE + founder + ops onboarded.

Sales engagement: Apollo + Smartlead · $220

Lighter than Outreach; fine for one AE.

Customer comms: Plain · $95

Shared inbox + Slack-connect for design partners.

Product analytics: PostHog (self-host) · $0

Cheap at our scale; reuse OTel infra.

Marketing site: Astro + Fathom · $15

Privacy-friendly analytics for the dev audience.

Total tooling: $678

Pricing & packaging — tiered SaaS with usage-based caps

Free$0

Solo devs and pre-seed teams kicking the tires.

  • • Up to 1M spans / month
  • • 3 connected services
  • • 7-day retention
  • • Community Slack support
Team$99 / mo

Growing platform teams who've outgrown free-tier limits.

  • • Up to 25M spans / month
  • • Unlimited services
  • • 30-day retention
  • • SSO + audit log
  • • Email support
Business$499 / mo

Mid-market reliability orgs with regulator-adjacent workloads.

  • • Up to 250M spans / month
  • • Custom retention
  • • SOC 2 Type I
  • • Slack-connect support
  • • Quarterly reliability review
EnterpriseCustom

Regulated industries (fintech, healthtech) needing data residency + DPA.

  • • Unlimited spans
  • • Data residency (US / EU)
  • • SOC 2 Type II + ISO 27001
  • • Dedicated CSM
  • • 99.95% SLA

Free → Team is the highest-leverage upgrade trigger. Watch span-volume curve closely; if median upgrade lands at 8M not 1M, raise the free cap and reprice Team upward.

Experiments backlog

Adding an in-product Slack-install step at signup will lift week-1 activation by ≥ 15 pp.

Test: A/B test the onboarding checklist: variant A includes Slack-connect as step 2, variant B leaves it for week 2.

Success: Week-1 activated workspaces (1+ service + 1+ Slack notification fired) · 3wk

An OSS collector plugin will produce ≥ 30% of new free-tier signups within 60 days.

Test: Publish plugin, instrument the install command to attribute signups; measure share of new signups citing the plugin route.

Success: Attributed signup share · 8wk

Outbound sequences anchored on the buyer's most recent payment-rail launch (FedNow / RTP) will hit ≥ 12% reply rate vs. our 6% baseline.

Test: AE runs two parallel 50-account sequences for 4 weeks; one trigger-anchored, one generic value-prop.

Success: Reply rate (positive + neutral) · 4wk

Publishing 'noisy alert' anti-pattern teardowns weekly will 2x organic signups vs. the current monthly cadence.

Test: Ship one teardown per week for 8 weeks; compare attributed signups vs. the prior 8-week monthly baseline.

Success: Attributed organic signups · 8wk

KPI dashboard

weekly

New free signups

320 / month by M3

weekly

Week-1 activation rate

≥ 55% of signups connected

monthly

Free → Paid conversion

≥ 6% at 60 days

monthly

New MRR

$13k / month by M6

quarterly

Net revenue retention

≥ 110% by M9

quarterly

CAC payback (mid-market)

< 14 months

Risks & kill criteria

OpenTelemetry adoption stalls and prospects stay on proprietary agents longer than planned.

Mitigation: Ship a first-party agent in parallel with the OTel-native path; let customers start on whichever feels lower-risk and migrate within a quarter.

Kill if: If < 40% of paid customers are OTel-native by M9, repositioning may need to lead with the agent.

Sentry or Datadog ships a 'revenue-ranked alerts' feature that closes the wedge.

Mitigation: Stay focused on OTel-native depth and the fintech compliance angle they're slow to ship. Lock in 2+ multi-year fintech contracts before incumbents respond.

Kill if: If two top-3 incumbents ship credible revenue-ranking inside 6 months AND we lose > 30% of inbound to them, repositioning is mandatory.

First AE hire doesn't reach payback within 6 months.

Mitigation: 30/60/90 ramp plan with explicit pipeline-gen and closed-won gates at each checkpoint; reassign to BDR motion if Q1 close-rate < 15%.

Kill if: Cut the role at M6 if generated pipeline < 3× target salary and run inbound-only for one more quarter.

Want a playbook like this for your product?

One brief in, a full ICP + GTM playbook out — in about 90 seconds. First one is free, no card.