The sale isn't done until the download works

There's a moment every maker walks right past. The payment goes through, the confirmation page loads, and it feels like the work is finished. It isn't. The buyer paid for a thing. Until that thing is in their hands and working, you haven't sold anything — you've taken money and made a promise to deliver.

The checkout is the middle of the sale, not the end. The end is the download that opens, the login that lets them in, the file that turns out to be the file they were promised. Everything past "payment succeeded" is the part the buyer actually paid for — and it's the part that's easiest to leave half-built, because the demo already felt complete the moment the money moved.

I've watched this play out in our own catalog. A store had a working checkout, a real product page, a price — everything that photographs well. What it did not have yet was the file the checkout was selling: the download asset didn't exist, and the delivery email was switched off, so a receipt would have gone out with nothing behind it. The payment path was the impressive-looking part. The fulfillment was the part nobody had finished. A buyer would have paid, and then sat staring at an inbox.

That's the failure mode of the last mile: it's invisible in every demo. You test the button, you watch the charge land, you see the success screen — and none of that touches the only question that matters to the customer, which is whether they can use what they just bought. Delivery lives on the far side of the payment, past where most testing quietly stops.

So the discipline is simple and a little humbling: buy your own product the way a stranger would, all the way through. Not to the confirmation page — to the thing. Click the download. Open the file. Log in with the account you just created. Read the email that's supposed to arrive, and check that it arrives at all. If any of that breaks, you don't have a product with a small bug. You have a promise you can't keep, and a refund already on its way.

Fulfillment is also where trust is won or lost, and it compounds in both directions. A clean handoff — the file opens, it's exactly what was described, the follow-up is actually useful — turns a first-time buyer into someone who'll open your next email. A broken one does the opposite, quietly, usually without a complaint. Most people don't write in to tell you their download was empty. They just don't come back.

None of this needs more infrastructure. It needs you to finish the half of the sale that happens after the money. Make the smallest complete thing — one product a stranger can pay for and actually receive, end to end — before you build the second one. A catalog of checkouts that don't deliver isn't a catalog. It's a list of apologies you haven't sent yet.

That's the bar we hold Prompt Garden to: you pay, and the prompts are yours right then, with nothing waiting on a file that isn't there. If you want the rest of how we think about shipping products that actually reach the person who bought them, the Loop newsletter is where that thinking lands.