Build the fair before you invite the crowd
Serial starter giving web novels a voice in the reader's browser
Andrei's launch sequence inverts the usual order: first a gamified Discord, characters acting as masters of ceremonies, a Sparkles gift for joining funded by Modal's 30 dollars of monthly free credits, challenges and events on a calendar, and only then Reddit promotion, with ads as a distant maybe. The logic is that acquisition without retention infrastructure is a leaky bucket: a launch spike that lands on a product with no community evaporates, while the same spike landing in a running fair leaves behind a nucleus of evangelists who feel like early citizens. The fair also costs almost nothing, free credits, performed characters, a founder doing voices, which fits a pre-revenue budget. Before spending on reach, build the place where arrivals stay, give the first ones a gift and a role, and let the community be running, warm, and slightly theatrical before the first stranger walks in.
Related advice
Partner with the small platforms first and take the receipts to the big ones
Andrei wants official relationships with the web novel platforms, but Wattpad is owned by a very large East Asian corporation, and a solo founder with an unlaunched extension does not get that meeting. So the sequence starts lower: the smaller platforms, still counting users in the millions, share the same reader-retention problem, answer their own email, and can say yes without a committee. One legitimate integration there produces the assets the big conversation requires, engagement numbers, an accessibility story, authors who vouch for it, receipts instead of promises. He has already assembled the stakeholder list on LinkedIn and drafted the outreach before launch, because partnerships have lead times just like sales. Treat platform partnerships like fundraising: get quick yeses from those who can afford to give them, convert the yeses into evidence, and climb the ladder with proof in hand instead of cold-emailing the summit first.
Know whether you are a starter, and stop designing companies for a finisher
Andrei's resume looks fragmented, Java to C# to Ruby on Rails, four years teaching at the Politehnica, an abandoned PhD, an outsourcing firm, a fantasy novel, until you apply his own reframe: he is a starter, energized by taking projects from zero to first results and drained by the long steady middle. Instead of fighting that, he now designs for it, picking products that can reach a self-sustaining state quickly and planning early for automation and helpers to carry the marathon stretch. The standard startup script quietly assumes a finisher, someone who wants to run the same company for fifteen years, and a starter who signs up for that script abandons it at year two and calls himself undisciplined. Temperament is an input to company design just like market size. Figure out which kind of founder you are from the evidence of your own history, then choose the product shape, exit points, and delegation plan that fit the person who will actually be running it.
Build inside the platform instead of pulling its readers away
The existing text-to-speech tools all make the same move: extract the story from the platform and play it in their own app. That works until you notice whose lunch it eats, because web novel platforms live on ads, comments, and community, and a tool that siphons readers off the page is a traffic devourer they have every incentive to fight, in court if necessary. Naramine is an extension precisely so it can stay on the page: it reads the chapter where it is published, follows the pagination, and leaves every pageview, comment, and vote where the platform can count it. That shape is what lets Andrei position it as an accessibility layer platforms could tolerate or even endorse, rather than a parasite they must kill. When your product feeds on someone else's content, the architecture is also the legal strategy: pick the shape that adds to the host's metrics instead of draining them, and you convert a future plaintiff into a future partner.
Make the first audio chunk tiny so playback starts before the file exists
A chapter of a web novel runs around ten thousand characters, and synthesizing all of it before playing would mean a long silent spinner. Naramine instead generates a very small first chunk so the play button responds within seconds, then produces progressively larger chunks until the pipeline reaches normal flow, pre-buffering ahead of the listener and preprocessing the next chapter in the background before the current one ends. Minutes of compute still happen, but they hide behind consumption time the listener was going to spend anyway. This is the streaming insight applied to generative products: what users feel is latency to first value, not total processing time, and the two can be decoupled almost completely. Whatever your product generates, slice the work so the first slice is nearly free, ship it the moment it exists, and let the rest of the job run behind the experience instead of in front of it.
