Blog

What breaks between signup and the first invoice

Explainers and guides on proving the revenue path works, written from what the runner sees on real apps. One post a week, no roundups.

RSS feed
A magic-link signup travels five hops: the form, your server, the email provider, the inbox and the link that opens a session.MAGIC-LINK SIGNUP · FIVE HOPS1Form2Your server3Email provider4Inbox5Link opensEvery hop can fail without an error in your logs.Only a real inbox, and a real click, proves the whole chain.

Guide9 min read

How to test a magic-link signup flow end to end

A magic-link signup has five hops and fails silently at each one. Here is where it breaks, how to test it by hand, in CI, and on production after every deploy.

Read the post →
An uptime check pings the homepage and gets 200. A revenue-path check walks signup, welcome email, checkout and paid access, and finds checkout broken.UPTIME CHECKGET https://app.example.com/200 OK · 87 ms · every 30 s“Everything is up.”The homepage answered. Nothing else was asked.REVENUE-PATH CHECKSign up1.8 sWelcome email4 sCheckoutPOST /api/checkout → 500Paid accessnot reached“Checkout broke on deploy a41f9c2.”

Explainer8 min read

Synthetic monitoring vs uptime checks: what each one actually proves

An uptime check proves your homepage answers. Synthetic monitoring proves a browser could finish a task. Neither proves a customer could sign up and pay, unless you point it at that path.

Read the post →