All posts

Topic

Running an Integration in Production

Building an integration got cheap. Keeping it alive, trusted and reversible did not.

Most integration advice stops at launch day. This cluster is for everything after it: tokens that expire per customer forever, webhooks that arrive twice, fields the other side renames without warning, the partner outage that lands in your inbox, attribution numbers that don't match, and how to package your own API so the next partner doesn't have to learn its quirks by breaking.

GuideNovember 4, 2026

Partner Attribution for SaaS: When Your Numbers and Theirs Don't Match

Your dashboard says 40 partner signups and theirs says 12, and neither is lying. How to set up partner attribution both sides trust, and why retention matters more than conversion.

Read more
PlaybookOctober 31, 2026

How to Package Your API for Integration Partners

Stop letting every partner learn your API by breaking it. Package it once: a verified spec, an auth guide, documented webhook behaviour, a test kit, a change log with notice, and written support and exit terms.

Read more
GuideOctober 21, 2026

OAuth Token Refresh for Multi-Tenant Integrations

Every customer who connects a partner gives you a separate grant to keep alive forever. Refresh early, one refresh per tenant at a time, save rotated tokens first, check the tenant on every call, and fail cleanly.

Read more
EssayOctober 17, 2026

SaaS Integration Maintenance: Why Integrations Break After Launch

Building an integration got cheap. Maintaining, coordinating, trusting and undoing one did not, and those four costs decide whether it is still alive a year later.

Read more
GuideOctober 14, 2026

How to Handle Duplicate Webhooks: The Replay Test

Webhooks arrive twice, late and out of order. A processed-events table, version-guarded upserts, unsigned webhooks treated as a nudge to re-read, and the one test that proves your handler is safe.

Read more
GuideOctober 8, 2026

7 Common SaaS Integration Problems (and How to Fix Each)

Building the integration got cheap; maintaining, coordinating, trusting and undoing it did not. The seven problems founders who built one actually hit, from token refresh to attribution disputes, and the fix for each.

Read more