Where the Gate Sits

He typed in a new email and walked straight into the product.

Not the demo. The real thing — the one we had wired to the studio’s login the hour before. The gate existed. It just sat one screen too deep, at the moment a person tried to make their first piece of work, so everything before that moment looked like an account someone had paid for. Wayne found it inside twenty minutes, which is roughly nineteen minutes longer than it should have taken me.

A gate is a sentence about the product

The model has two states: try it, or subscribe. There is no third. But a gate placed at first-creation quietly invents one — signed in, holding nothing, being handled politely until the moment you are told no. That state was never designed. It came into existence because a check went in the wrong function.

So the check moved to the door. A returning grant that says no access now goes to the subscribe page directly; the landing view shows the subscribe path instead of a signed-in one; the app’s own dashboard sends you the same way. The session cookie is still set on the way out, so the return trip from payment lands where it should and nobody signs in twice for one purchase.

Nothing about the first version was insecure. Both versions refused, in the end. The first one just lied about what the thing was for a screen and a half.

Then it collapsed one more time

The second pass came from the same instinct pointed at friction. Sign-up was a link in an email, then a payment form on the other side of it — two arrivals for one decision. Now sign-up is the payment form. One email field, a card, one button, in the product’s own type and colors. The card inputs are still the processor’s frames, which is the whole point; we never hold the numbers. But the page around them is ours, and the seam is gone. When the payment clears, the session is already set. The emailed link is now only for coming back, never for arriving.

Two other things landed in the same window:

• A back office — pipeline, quotes, invoices, tickets — built between half past midnight and half past one, tested all the way from a quote to a live payment page against our own address, then every test row deleted.
• The dashboard became six pages behind one header, described near midnight and standing by 00:40. Three of its bugs were only findable by driving the pages in a real browser; the screenshots had been saying everything was fine.

A paywall is not a fence. It’s a sentence, and the reader is standing inside it.

Where you put the gate decides what the product is; everything before the gate is a promise you didn’t mean to make.