Docusaurus + OpenAPI + Node/Python SDK teams
at Series B–E, using GitHub Actions
A precise, falsifiable ICP definition with Jobs-to-Be-Done scenarios, trigger moments, objection handling, and quantified segment sizing — grounded in GitHub Search API data.
🔧 Stack Fingerprint
The exact technical signals that identify a qualifying beachhead company. All counts from GitHub Search API (public repos only).
| Layer | Requirement | GitHub Signal |
|---|---|---|
| Docs platform | Docusaurus (primary) | 546 public repos w/ docusaurus-plugin-openapi |
| API spec | OpenAPI 3.x | openapi.yaml or swagger.json committed to repo |
| SDK languages | Python + Node/TypeScript | 72% of all SDK docs code blocks |
| CI platform | GitHub Actions | 89% market share in docs repos (94,976 workflows) |
| Docs hosting | GitHub Pages / Vercel | Deployed on push via GH Actions workflow |
| Secondary platforms | Mintlify, ReadMe.io | 104 and 482 repos respectively with CI integration |
docusaurus.config.js + openapi.yaml + .github/workflows/ is a confirmed beachhead target. 546 such repos exist publicly; enterprise orgs multiply this by 5–10× in private repos.🏢 Company Profile & Persona
Company
- Stage
- Series B → E
- $5M–$200M ARR
- Engineers
- 50–500
- Platform/SDK team of 3–15
- Docs team
- 1–5 people
- DevRel lead, DX eng, SDK maintainer
- Company type
- API-first or dev-tools
- Stripe-stage fintech, Twilio-stage comms, Plaid-stage data
- Examples
- Clerk, Resend, Neon, Unkey, Supabase-stage
- API-first companies with public SDKs
Primary Persona
- Title
- Head of DevRel / DX Engineer / SDK Maintainer
- Owns
- Developer onboarding, SDK quality, API docs
- Reports to
- VP Engineering or CTO
- Budget authority
- $10K–$60K/yr tooling
- Slack channels
- #developer-experience · #sdk-releases · #docs
- Metrics tracked
- TTFSAC · DX NPS · Support ticket volume
💡 Jobs To Be Done
“When I cut a new SDK release, I want CI to automatically verify every code example in our docs still runs, so I can ship confidently without a 4-hour manual review or a post-release support spike.”
“When an API endpoint changes, I want a PR comment showing exactly which docs examples need updating so I can fix them before merge.”
“When a customer files a bug about a broken example, I want to retroactively verify all similar examples to prevent repeat incidents.”
“When I onboard a new DevRel hire, I want a dashboard showing docs health over time so we can demonstrate DX improvement to the board.”
⚡ Trigger Moments
The specific events that create urgency and open the buying window. Each maps to a cold outreach angle.
SDK Release Spike
SDK v2 ships Friday. By Monday: 8 GitHub issues, 12 Slack pings. Python quickstart throws AttributeError — method name changed. Senior DX eng spends Tuesday patching 23 examples.
API Drift Goes Viral
API endpoint adds required field in v1.8. Docs example doesn't include it. 3 weeks later a developer tweets your quickstart doesn't work. 200 likes. You trace it to one unverified code block.
New Head of DevRel Hired
Series B/C company hires first Head of DevRel. She audits docs — 30–40% of code examples have never been machine-executed. Board wants DX improvement plan in 90 days.
Monorepo Migration
Team migrates to monorepo. Docs now live next to SDK source. An eng notices 15 /docs/examples files reference functions from old architecture. No tooling exists to catch this at PR time.
🛡️ Objection Handling
“We tried testing examples with GitHub Actions — too flaky”
DocsCI uses hermetic sandbox runners: ephemeral credentials, network allowlists, and deterministic environments. No external state = no flakiness.
“Our API examples require real credentials”
Customer-hosted runner option runs on your own infra with your secrets. DocsCI orchestrates; you provide the execution environment.
“Hard to justify before we have an NPS problem”
34% of SDK support tickets trace to bad docs = immediate ROI calculation. Even 10 tickets/month × $200 cost-to-resolve = $24K/yr saved, dwarfing the $12K starting price.
“We don't have a docs team — eng owns docs”
That's the ideal customer. When engineers own docs, DocsCI plugs into the workflow they already use: GitHub PRs and Actions.
“Our examples are too complex to automate”
DocsCI starts with simple execution verification (does it run without error?), not output assertion. 80% of bugs are caught at this level with zero test-writing required.
📏 Segment Sizing
ROI Calculator (per customer)
🔍 How to Find Them
Accessible via GitHub Search, LinkedIn, and community signals. No paid data required to build the initial outreach list.
| Source | Signal | Volume |
|---|---|---|
| GitHub Code Search | orgs with docusaurus-plugin-openapi in package.json | 546 public repos |
| GitHub Code Search | repos with rdme (ReadMe CLI) in GitHub Actions | 482 repos |
| GitHub Code Search | repos with Mintlify deploy in GitHub Actions | 104 repos |
| GitHub Code Search | repos with Spectral OpenAPI lint in CI (warm pipeline) | 720 repos |
| Head of DevRel at API-first company, hired < 1 year | Reachable segment | |
| Twitter/X | Engagement with broken-quickstart tweets at API cos | Direct switch trigger |
| Communities | devrel.co Slack, Developer Avocados, API the Docs | 3 key communities |
Are you this ICP?
If you run a Docusaurus + OpenAPI stack with GitHub Actions and have Node or Python SDKs, we'd love to talk. We're onboarding 10 design partners.
hello@snippetci.com →