Business & LegalBill the person who gets the furnished room, not the shop that sold the sofa
Serial starter behind Naramine and cofounder of HausJam
One tempting HausJam model is to charge furniture sellers for placement in the catalog, or to fold the tool into the retailer's price so the consumer never sees a bill. The room, and the founders, preferred the opposite: the person arranging the apartment pays, because that is who receives the value and who will feel a credit pack as fair. Seller-pays sounds like distribution and behaves like a tax on the catalog. It also trains the retailer to treat your software as a marketing cost they will cut the first slow month. Consumer-pays keeps the incentive clean, five free pieces to try the magic, then credits or a project pack when the room is real. If you are building a tool that sits between a shop and a household, pick the side that cannot confuse your invoice with a listing fee.
Related advice
Andrei StatescuStore generated content in the user's browser, not on your servers
Every minute of audio Naramine generates is cached in IndexedDB on the listener's own machine, sometimes tens or hundreds of megabytes of it, with a clear-data control and a download option for the user. Andrei's servers never store the stories or the audio derived from them, and that decision does double duty. Economically, his storage bill is zero and stays zero as usage grows, which matters enormously for a solo founder with an 80 percent margin target. Legally, it keeps him a tool rather than a distributor: a service that hosts copies of authors' copyrighted stories, or audio derived from them, has built a library it must defend, while audio generated on demand and held only on the reader's device looks like the reader's own personal-use copy. When your product transforms content you do not own, ask where the transformed bytes live, because that answer decides both your infrastructure costs and which side of a copyright argument you are standing on.
Andrei StatescuRun the free tier on the user's hardware and sell the GPU as the upgrade
Naramine's Basic tier is the same open source engine as Premium, Kokoro, but executed as Kokoro JS in the listener's own browser, so every free user brings their own compute and Andrei's marginal cost for the entire free tier is zero. The limits of local execution, roughly 1.3x listening speed on a good laptop but stuttering below realtime on weak hardware, and English only, are exactly the pitch for Premium, which runs bigger models on Modal GPUs with two to three second cold starts, better voices, and more languages, at under a dollar per 50 chapters. The elegance is that the free tier demos the paid tier by being honest about its own ceiling: the user who feels the stutter understands precisely what the upgrade buys. If your workload can run client-side at acceptable quality, that is a free tier that cannot bankrupt you, with an upsell built out of physics instead of feature gates.
Andrei StatescuWhen usage comes in waves, sell a one-time gift instead of a subscription
Web novel readers binge: two weeks inside one story, a quiet month, then another binge. A monthly subscription taxes the quiet month, teaches users to cancel, and turns every resubscription into a fresh purchase decision. Andrei prices Naramine Premium as a roughly 10 dollar one-time purchase of Sparkles credits, about 20 per chapter, framed as a gift you give yourself, with costs behind it near a dollar fifty for an 80 percent margin. The one-time frame lowers the entry barrier, matches the wave shape of real usage, and eliminates dunning, churn dashboards, and the resentment of paying for silence. Subscriptions are the default because spreadsheets love them, not because users do. Look at your actual usage pattern first: if value arrives in bursts, credits that never expire align price with value, and the customer who returns after a quiet month arrives grateful instead of guilty.
Andrei StatescuPut the upgrade button inside the moment of friction
Naramine's free tier synthesizes speech on the listener's own hardware, and on weak laptops it drops below listening speed and stutters. The room's suggestion: detect that moment, processing under roughly 95 percent of playback speed, and surface a small in-context offer, "Too slow? Boost this chapter", that hands the stalled chapter to the paid GPU pipeline. This beats any pricing page because the user is experiencing the exact problem Premium solves at the second the offer appears; no abstract feature comparison is required. Two disciplines keep it honest: the free tier must remain genuinely usable, since a deliberately hobbled Basic reads as bait and poisons trust, and the copy must sound like help, boost, speed up, finish faster, never like a penalty for owning an old laptop. Map where your product's real friction lives and put the upgrade there, phrased as a favor. A pricing page asks users to imagine the pain; an in-context upsell arrives while they feel it.
Extracted from
Indie TM #14: One Photograph, Then the Furniture Moves