One login, one bill and one place where the day starts: that is what the satellite ecosystem turned into. At launch it was one app per pain, with invoicing here, negotiation there, polite replies somewhere else and privacy docs in a fourth tab, each with its own dashboard, its own login flow and its own marketing site. The architecture was tidy. The user experience was a tab graveyard.
Most of it was collapsed over the last month, and the pricing was settled the same week: one Hub plan ladder, plus a single named standalone for miniterms. The architectural decision and the pricing decision are the same decision viewed from two angles: the user wants one bill and one place to look. Anything else is the company's convenience pretending to be the user's.
HelpMeNegotiate, Politeno, and Minireplies are now Hub-native modules. They have marketing domains — helpmenegotiate.app, politeno.app, minireplies.com — but the workspace is one tab in app.dekimu.com. Five-minute tools that someone uses once a week didn't earn their own dashboard; they earned a fast path from the Decision Inbox to the right scenario. InvoiceUp and miniterms kept their standalone surfaces because they're daily-use working tools — invoicing for the owner, legal documents for the lawyer or accountant who reads them. The line is narrow on purpose.
One login. One bill. One place where the day starts. The Hub's Decision Inbox aggregates the things that need a human — late invoices, expiring contracts, document drift, an email that needs answering. From the inbox, you fall into the right tool: a polite-firm reply, a rate-conversation draft, a legal-document refresh, a runway check. The point isn't that the modules are powerful in isolation. The point is that they're one click from the moment of pain.
We tried to ship six apps. We finally figured out we were shipping one workspace with six interesting corners.
We over-built infrastructure for products that hadn't earned the weight. Politeno had auth flows. HelpMeNegotiate had its own dashboard shell. Minireplies almost got the same treatment before we caught ourselves. A cleanup pass swept hundreds of lines of orphan modules out of the satellites, code that existed because we'd published a separate-app posture before we'd validated separate-app demand. That lesson is written down now: the default for any future tool is Hub-native, and an exception has to be argued for in writing first.
InvoiceUp and miniterms keep their standalone homes because they're daily-use working tools. Everything else now defaults Hub-native. The next two products on the runway both ship as Hub modules from day one: no separate dashboards, no separate logins, no fifth bill. The marketing domains stay; they're great front doors. They just don't have to pretend to be products.
This post was drafted by an AI system from Dekimu's public engineering record and published with automated checks, without per-post human editing.
← Back to blog