DEV Community

Cover image for I killed my SaaS subscription 7 days after launch. Here's the math.
劉穎諺
劉穎諺

Posted on

I killed my SaaS subscription 7 days after launch. Here's the math.

Last week I launched UIPrompt, a visual component editor that writes exact prompts for AI coding tools. Product Hunt went fine. People said nice things. Signups: a handful. Paid conversions at $12/mo: zero.

I spent a few days blaming traffic. Traffic was part of it. But when I sat down and pretended to be my own customer, the pricing model fell apart on its own.

The usage curve is wrong for a subscription. You use UIPrompt hard for the two weeks you are building out a design system, then you ship, and you do not touch it until the next project. Paying monthly for a tool you use in bursts feels bad even at $12. Nobody churns politely; they just never subscribe.

What buyers actually wanted was an asset. The most-used feature request from launch feedback was "can I export the whole system". That is not a service. That is a file you own. Tailwind UI figured this out years ago: pay once, own the output forever.

So I rebuilt the model in three days:

  • One price: $39 launch (goes to $59). No renewals, ever.
  • Free tier got MORE generous: full playground without signup, free accounts keep 3 saved components.
  • The paid unlock is the thing that behaves like property: unlimited components plus an AI Design System Pack export. One zip: SKILL.md for Claude Code, .cursorrules for Cursor, AGENTS.md for everything else, tokens.css, and per-component specs with exact values and state diffs.

The pack is the part I am proudest of. I blind-tested it: a fresh AI session that had never seen my design got only the exported files and built a settings page. 34 of 34 specced properties matched. It invented zero colors. It derived the entire dark mode from two token values. That is what "your design system speaks AI" means in practice.

Some honest notes for anyone considering the same pivot:

  1. Killing a subscription you already wired up (Paddle, webhooks, trial emails, dunning) feels like burning work. It is actually deleting risk. My codebase lost 108 lines of trial machinery and gained one webhook case.
  2. Buy-once forces the free/paid line to be sharp. "Trial expires" is a deadline; "you hit 3 components and want the pack" is a decision. I prefer selling to people making decisions.
  3. The refund promise got simpler too: 14 days, no questions. There is no proration math when there is nothing recurring.

Maybe this fails too. My success bar is written down: 3 real purchases in 14 days of relaunch, or I move on to the next bet and leave UIPrompt in maintenance mode. Either way I will post the numbers.

Try the playground (no signup): https://uiprompt.co

Top comments (1)

Collapse
 
bhavin-allinonetools profile image
Bhavin Sheth

This is a solid example of pricing following user behavior, not the other way around. I've seen one-time purchases convert much better than subscriptions when usage naturally comes in bursts.