When Hub launched it was four acts — Builder, Planner, Operator, Designer — the arc from an idea to a live business with a public face. Over the last few weeks that spine grew a body. Hub is now a company operating system: a library of focused modules organised into eight plain-English categories, where you switch on exactly the surface you need and the rest stays out of your way.
Every module lives under one of eight headings, named the way a freelancer thinks rather than the way software is usually filed: Communicate (the emails and replies you'd rather not write), Money (late fees, rate cards, cashflow, expenses, revenue), Clients (deal rooms, dossiers, portals, a simple pipeline), Insights (digests, trends, board reports), Build (proposals, agreements, intake forms, a document vault), Comply (consent, retention, an IP register, an incident log), Publish (a public changelog, roadmap, media kit, content queue) and Admin (decisions, people, runbooks). You don't learn a taxonomy — you find the thing where you'd look for it.
A module is a small, self-contained surface. A solo designer might run three of them; a five-person studio might run fifteen. Nothing you don't enable shows up in your sidebar, and nothing you enable demands a setup project — most modules are useful the moment you open them, because Hub already knows your business profile, your clients, and your work. The point of a company OS isn't more features. It's that the features you already pay for stop hiding from you.
A cluster of the newest modules — consent records, payment proofs, client notices, sign-off collection, an AI-usage log, a purpose register and a retention planner — do something the others don't: every meaningful action they take mints a receipt anyone can verify publicly, no account required. That's the difference between a tool that says it kept a record and a tool that can prove it did. We wrote that up separately.
A company OS earns the name when the operator stops asking "which app was that in?" and starts asking "what do I need to decide today?"
The four acts still hold — Build, Plan, Run, Ship is the spine the modules hang off. What changed is that the gaps between the acts filled in. The next stretch is less about adding modules and more about the seams between them: the moment a paid invoice updates your runway, the moment a signed agreement opens a client portal, the moment a missed deadline writes itself into the decision journal. The modules exist. Now they start talking to each other.