Notes on tech partnerships, revenue, and relationships.
Page 1 of 12
Co-selling headless and API-first products with platform partners
An independent guide to co-selling headless and API-first products with platform partners. Why the motion fits, how the field actually sells, category examples only, and the enablement that makes it repeatable.
Read →Integration health metrics: errors, latency, and churn signals
Integration health metrics that predict churn: error rate, latency, sync gaps, and broken connections, plus how to set thresholds and alert before customers leave.
Read →Forecasting partner-sourced revenue
A simple model for forecasting partner-sourced revenue. Conversion assumptions, confidence bands, sourced vs influenced, and the mistakes that make the forecast a wish.
Read →Attribution models for co-sell and integrations
How to pick an attribution model for co-sell and integrations: first-touch, multi-touch, sourced, and influenced, without inflating pipeline.
Read →Setting partnership targets for seed to Series B
How to set partnership targets from seed to Series B: capacity math, stage-appropriate goals, and leading indicators you can steer by.
Read →Building a partnerships dashboard execs trust
How to build a partnerships dashboard executives will actually use. The few numbers they want, sourced vs influenced definitions that hold up, and a layout finance can trace.
Read →Integrations for the productivity ecosystem (Notion, Figma, and friends)
An independent overview of integrations across the productivity ecosystem. Patterns and opportunities in docs, design, chat, and tasks. Category examples only, not claimed partnerships.
Read →When to sunset a partnership: the data signals
When to sunset a technology partnership. Adoption flatline, API deprecation, and strategic drift, plus a clean-exit checklist so you leave without burning the relationship or the customers.
Read →Integration strategy for vertical SaaS (fintech, health, legal)
How integration strategy changes for vertical SaaS. Fintech, health, and legal each have different ecosystems, compliance costs, and first-build priorities. An independent guide, not a program document.
Read →