Notes on tech partnerships, revenue, and relationships.
Page 10 of 18
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 →
Turning marketplace installs into pipeline
An independent guide to marketplace attribution. How to track installs to opportunities and revenue, connect activation to expansion, and build a model that tells you which installs are worth more.
Read →
Driving installs after launch: the first 90 days
An independent playbook for the first 90 days after a marketplace launch. How to seed real installs, earn early reviews, drive activation, and turn the first customers into the flywheel's first turn.
Read →
Integration acceptance criteria: defining done for partner builds
How to write integration acceptance criteria for B2B SaaS: what done means, the edge cases teams forget, and a reusable criteria checklist for partner builds.
Read →