The Quietly Brilliant Project Stack for Studios Under Ten People

There's a particular kind of software fatigue that hits small studios. You signed up for the tool everyone said would change your life, then another one, then a workflow add on, then a Notion template that looked beautiful on Twitter. Now you've got six tabs open, none of them being used properly, and the team is back to running things in a group chat.

The truth is: small studios don't need more tools. They need fewer, used better.

Here's a stack that holds up for teams of two to ten without becoming a second job.

The principle: one source of truth per layer

Most studio chaos comes from the same problem. Project info lives in five places. Updates get scattered. Files drift. Someone working from the wrong version. The fix is structural: pick one tool per layer, and make it the only place that thing lives.

You only need four layers:

Project tracking. Where the work lives. What's due, who's on it, what's next. Communication. How the team talks to each other. File storage. Where the work actually sits. Client facing work. What the client sees, signs, and approves.

That's it. Anything else is decoration.

The stack

For project tracking: Linear, Asana, or Notion. Linear if you lean technical or work with developers. Asana if you want grown up task management without the engineering bias. Notion if you want a malleable system you can shape to your studio's actual rhythm. Pick one. Make it the only place tasks live. The team should not be able to do their job without opening it.

For communication: Slack, plus one rule. The rule is: decisions don't live in DMs. If something matters, it gets posted in a channel where the relevant people can see it. DMs are for "are you in the office today," not "we're going with option B."

For file storage: Google Drive or Dropbox, organised on purpose. The tool doesn't matter as much as the folder structure. One folder per client. Inside that, one folder per project. Inside that, a tight subfolder structure (working files, exports, references, archive). Set it up once. Defend it.

For client work: this is where Rally lives. Proposals, scopes, sign offs, all in one shareable link. The point is that everything client facing has a single home. No "did I send you the latest PDF" emails. No version control confusion. The client opens one link and sees the current state of things.

What to cut

A lot of studios are running:

• A project management tool
• A separate tasks tool
• A separate notes tool
• A separate docs tool
• A separate client portal
• Three different chat apps depending on the client

Every overlap is a place for things to fall through. Audit your stack honestly. Anywhere two tools do the same job, kill one.

A note on shiny new things

The design world is great at making software look beautiful. That doesn't make it the right tool for you. Before signing up for the new platform everyone's talking about, ask: does this replace something I'm using, or add to it? If it adds, it has to earn its keep, and most don't.

The best stack is the one your team uses without thinking about it.