{
  "$type": "site.standard.document",
  "bskyPostRef": {
    "cid": "bafyreihrnmp5jxtqpwj6ikswx2tco5uykcvufrirhfye26nfza3j4mhrti",
    "uri": "at://did:plc:25rdn5elo5izoxrmtis34zuk/app.bsky.feed.post/3mohlvop34va2"
  },
  "coverImage": {
    "$type": "blob",
    "ref": {
      "$link": "bafkreiecx7jx42jesh57irm2eie3xe3ohmypnbcl52luwlxslonpgaeizm"
    },
    "mimeType": "image/webp",
    "size": 152928
  },
  "path": "/velobasex/the-boring-80-nobody-warns-you-about-when-an-ai-demo-becomes-a-real-product-3dnm",
  "publishedAt": "2026-06-17T04:55:33.000Z",
  "site": "https://dev.to",
  "tags": [
    "ai",
    "product",
    "saas",
    "softwareengineering",
    "Velobase Harness"
  ],
  "textContent": "This month the front page filled up with AI agents going off the rails — one reportedly ran its operator's bill into the ground, another tore through a Linux box unsupervised. Funny, until it's your credits and your customers. We learned that lesson the slower, more expensive way.\n\nOur team shipped an AI demo in a weekend. Turning it into something people could actually pay for took the next four months, and almost none of that time went into the AI part.\n\nThat gap surprised us more than it should have. The model call was maybe 30 lines. Everything around it — getting paid, knowing who to thank for a signup, stopping one script from burning $400 of credits overnight — was the real product. Below is what we got wrong on the way there, in roughly the order it hurt.\n\n##  Pitfall 1: \"We'll just add Stripe later\"\n\nLater is a lie. The moment you charge for AI usage, billing stops being a checkout button and becomes a metering problem.\n\nA flat $20/month subscription is easy. The trouble starts when usage is the cost. A heavy user can run you negative on a plan a light user is wildly overpaying for. So you end up needing both: a subscription _and_ a usage meter that counts tokens (or images, or minutes) and reconciles them against credits the customer actually has left.\n\nWhat we underestimated was the bookkeeping. Every generation has to decrement a balance, that decrement has to survive a crash mid-request, and the customer needs a dashboard that agrees with what Stripe charged them — to the cent — or you get support tickets you can't answer. We rebuilt this twice. The second time we finally separated \"what the model did\" (an event) from \"what we charged\" (a ledger entry), and the bugs stopped.\n\nIf you take one thing from this post: **model the usage event and the billing entry as two different things from day one.** Collapsing them feels simpler and costs you a weekend later.\n\n##  Pitfall 2: Free credits are a free lunch — for abusers\n\nWe gave new signups some free credits so people could try the thing without a card. Reasonable. Within a week someone had scripted a few hundred throwaway accounts and was draining the free tier in a loop.\n\nThere's no single fix. What actually worked was a stack of cheap, boring checks layered together:\n\n  * Rate limits per account and per IP (Redis, sliding window).\n  * A CAPTCHA on signup — we used Turnstile, but anything that adds friction for bots helps.\n  * Blocking disposable email domains at signup.\n  * Small signup signals (is this account an hour old with 200 generations?) feeding a guest quota.\n  * And the unglamorous one: **credit clawbacks** , so when you do catch fraud after the fact, you can actually take the credits back instead of eating the loss.\n\n\n\nNone of these is clever. The lesson was that abuse control isn't a feature you build once — it's a posture. You assume the free tier will be attacked and you make abuse slightly more annoying than it's worth.\n\n##  Pitfall 3: You will not know which channel actually works\n\nWe spent money on a few channels and had no idea which one produced paying customers. Client-side analytics told us about pageviews. It told us nothing trustworthy about _purchases_ , because ad blockers and the gap between \"clicked an ad on Monday\" and \"paid on Thursday\" quietly destroy attribution.\n\nThe thing that fixed it was moving attribution server-side: stamp the acquisition source when the account is created, carry it through, and fire the conversion from the backend when money actually changes hands — including the offline-conversion uploads back to Google Ads and the pixel events platforms expect. Suddenly \"this campaign cost $X and produced Y paying users\" was a sentence we could finish.\n\nIf you're running any paid acquisition for an AI product, do the server-side version early. The client-side numbers feel fine right up until you try to make a budget decision with them.\n\n##  Pitfall 4: An affiliate program is an accounting system wearing a marketing hat\n\nThis one humbled us. \"Let people refer others for a cut\" sounds like a referral link and a counter. It is not.\n\nThe instant real money is owed to real people, you're running double-entry accounting whether you meant to or not. A referred customer asks for a refund — now you have to claw back the commission you already credited the affiliate. Someone wants to cash out (in our case people asked for USDT). Promo codes stack in ways you didn't intend. Get any of this slightly wrong and you're not shipping a bug, you owe someone the wrong amount of money.\n\nWe ended up treating the whole thing as a proper ledger — every credit and clawback is a balanced entry — because that's the only way the numbers stay defensible when an affiliate disputes their payout.\n\n##  Pitfall 5: The \"rest of the backend\" is a second full-time job\n\nAuth. Background workers for anything slower than a request (we used BullMQ on Redis). Lifecycle email so trials don't silently lapse. An admin panel so you can actually look at a customer when they email you. Then Docker, then Kubernetes, then CI/CD so a deploy isn't a held breath.\n\nEach of these is a known, solved problem. The cost isn't difficulty — it's _count_. There are a dozen of them, none is the thing you set out to build, and together they're where the months go.\n\n##  So what did we do about it\n\nWe kept ripping these pieces out of one product and into something reusable, and eventually it became its own open-source project: Velobase Harness — MIT licensed, Next.js 15 / React 19 / tRPC / Prisma / Postgres, with the usage billing, server-side attribution, affiliate ledger, anti-abuse stack, workers, and deploy config already wired together. It's the scaffolding we wish we'd had before pitfall 1.\n\nWe're not going to pretend it's the only way to do this — plenty of people would (and do) assemble these from separate services, and that's a legitimate choice. We just got tired of rebuilding the same plumbing for every AI idea.\n\nWhat we're actually curious about, and the reason we wrote this down: **for those of you who've taken an AI product past the demo — which of these bit you hardest?** And did you build the billing/abuse/attribution layer yourself, reach for something off-the-shelf, or just... not, and hope? We're collecting war stories and genuinely want to hear how other people drew the line.",
  "title": "The boring 80% nobody warns you about when an AI demo becomes a real product"
}