ClickUp is one app. We did not want one app.

ClickUp jams every job into one window. Notion jams every job into a page tree. Jira jams every job into an issue tracker. We built five apps and one organisation.

Agencies outgrow ClickUp for a boring reason. You can configure anything. You still do not have a client, an invoice, or a wiki that knows the project — unless you build it out of custom fields and automations. Notion has the same trick with databases. Jira has the same trick with plugins. I got tired of tricks.

A timer should not look like a wiki. A teammate console should not look like a kanban column. ClickUp forbids that kind of drift by stuffing everything into one settings page. We allow the products to drift in craft. We forbid them to drift in organisation: one person, one seat, one client directory, one bill.

The seams that are not glue code

• Invite once in ShellStack. Tick Tides, TurtleTime, Kraken, Shelly. Restrict workspaces if a contractor should not see every client.
• Home opens an app already signed in. Each app keeps its own session. They are not interchangeable on purpose.
• Time is one shared record. The board writes it. The timer invoices it. Nobody syncs two timesheets.
• The customer is one shared record. Each app can hide a client where it should not appear.
• Shelly writes only through the agent inbox and an approval. Destructive actions wait for a person. Team chat can show the card.
• The Kraken editor is live and shared. Permissions stay with your workspace. Attachments are stored privately, not on a public gallery.
• App connections are linked to a workspace. A code event can become a task. A meeting can draft time. The rule still passes each app’s permissions.

How the five apps actually talk

They do not sync copies. They share records, and they call into one another.

• Identity: one account, one sign-in. Open an app already signed in; the app switcher jumps between siblings without a fourth invite.
• Directory: one client list and one workspace. Boards, projects, pages and crews all point at the same records. A client can be hidden from an app that should not see it.
• Time: one shared hour record. The board writes it, the timer invoices it, and Shelly can start or stop a timer with the same task on the card.
• Knowledge: documents keep their own permissions. The board and the timer search linked documents. Shelly only reaches documents its sponsor may see.
• Teammate: ShellHub is the home for crews. The sidebar is the same teammate inside the timer (it knows which app and page you are on), with first-party tools for the board, the timer and the wiki. Writes land in the agent inbox or wait for approval.
• Outside world: one app connection, three uses — workspace rules, Shelly’s search and actions, and research citations. Keys stay on the server.
• Research: Kraken research and Shelly’s web answers run through one private research service. The browser never touches a search engine or a scraper directly.

The cost is real. Five URLs. A Home to launch from. ClickUp will win the demo where someone says “wait, docs are already here?” We will lose that demo. I am fine with it.

A suite is a decision about what is allowed to drift apart.

Use this shape when collapsing work into one surface is the actual risk.