A small digital product should be small enough to finish and specific enough to sell. Most of the work is deciding what to leave out.
Problem
My first three products all failed the same way: I built the interesting part and left the boring part unfinished. A calculator that works but has no delivery mechanism is not a product, it is a demo.
My System
Every small product ships with six pieces, and none of them are optional:
- The tool. The thing that does the job. Usually one page, no accounts.
- A landing page. One promise, one screenshot, one price.
- Payment. A hosted checkout; I do not build payment flows.
- Delivery. Automated, immediate, and tested with a real card before launch.
- A short guide. Half a page on how to get value in five minutes.
- An update path. A changelog and a version number, even if it is v1.0.
Tools
- Static HTML, CSS and vanilla JS for the tool itself.
- Hugo for the landing page and documentation.
- Cloudflare Pages for hosting, which costs nothing until volume arrives.
- Stripe or Lemon Squeezy for checkout and delivery.
Workflow
Idea → one-page brief → working prototype in a day → pricing decision → checkout and delivery → launch note → six-week review.
The six-week review is the part people skip. It is where I decide whether to keep the product alive. Twice the answer has been no, and both times that was the right call.
Why It Works
Shipping small keeps the maintenance burden measurable. A single-page static tool can be left alone for a year and still work. Anything with a server cannot.
Limitations
This approach does not scale past a certain point. Once a product needs collaboration, history or syncing, the static-first assumption breaks and a backend becomes unavoidable. At that point it is a different project with a different budget.
