Notes on tech partnerships, revenue, and relationships.
Page 4 of 12
MCP tools, resources, and prompts: what to expose first
The three MCP primitives, how they differ, and how to pick the first customer job and a small, safe surface for a SaaS MCP server.
Read →
API changelog and versioning strategy for partners
Versioning schemes, changelog discipline, and a deprecation policy that external partners can plan around, so integrations keep working while the API evolves.
Read →
SDKs: build, generate, or skip?
When an SDK is worth the cost for partner developer experience, when to generate from OpenAPI, when to hand-build, and which languages to ship first.
Read →
How to run a beta partner program for a new integration
How to run an integration beta program for B2B SaaS: recruiting the right beta partners, running feedback loops, and the exit criteria that gate GA.
Read →
Integration QA: a test checklist for partner builds
An integration testing checklist for B2B SaaS: functional, auth, error, edge, and load tests for partner builds, plus a reusable QA checklist you can apply.
Read →
The first partner call: an agenda that qualifies fast
A first partner call agenda for B2B SaaS: a discovery structure, the qualifying questions that separate real fit from polite interest, and next-step discipline that keeps momentum.
Read →
The partnership one-pager that gets a meeting
A partnership one-pager for B2B SaaS: what to include, the shared-customer hook that earns a meeting, what good looks like versus generic, and a copyable template.
Read →
How to define your ideal technology partner (partner ICP)
A partner ICP for B2B SaaS. The dimensions that define a great technology partner, how to score fit against them, and the anti-patterns that waste a quarter.
Read →
How to source technology partners: inbound, outbound, customer-led
How to source technology partners for B2B SaaS. The three sourcing channels, how to mine customer requests for signal, and how to run outreach that gets replies.
Read →