The essentials in 30 seconds
- Four questions break duos: who accesses what, who talks to the client, who approves a quote or a change order, and what happens to the history when the person leaves.
- A four-role grid is enough: owner, administrator, collaborator, reader. Anything irreversible, or that reaches the client or a third party, belongs to the administrator.
- Everyone sees the whole workspace. "Responsible for a project" is a tracking label, never a wall; the client only sees what is meant for them.
- One human = one account. Shared logins destroy traceability and put you in breach of GDPR on your clients' data.
- The right tool is not the one with the most features: it is the one where a single file carries the project, the estimate and the client portal, with internal notes the client will never see.
The moment the studio grows to two
Three set-ups come up again and again in interior design studios. The occasional freelancer, brought in for a survey, construction drawings or a large site, who needs access to one or two projects, not the whole business. The intern or apprentice, who learns by doing and is given site reports, material research, a first estimate, all under review. The partner or permanent collaborator, who runs their own projects and must be able to speak to clients on your behalf.
In all three cases the change is the same: until now the studio worked because you knew everything. The prospect list in your head, the client history in your inbox, prices in your spreadsheet, the schedule on your phone. With two people, that way of working does not lower quality, it makes it random: the information exists, but nobody knows who has it.
The usual answer is to share a Drive and open a WhatsApp group. That solves file access and nothing else. The four questions below stay open, and they are where duos crack.
The four questions that break duos
1. Who has access to what?
A project file holds very different things: drawings and specifications everyone must see; the estimate and contractor bids, which reveal your margins and prices; the client's contact details and personal documents; your internal notes. A shared Drive gives all or nothing. The question is not "can I trust this person?" but "do they need this information to do their job?". GDPR asks it in the same terms: access to a client's data is justified by a purpose, not by good faith.
2. Who talks to the client, and what do they see of internal exchanges?
An interior design client has one point of contact, sometimes two. They must never stumble upon your internal hesitations: "the plumber's quote looks inflated", "we forgot the ventilation in the estimate", "the client changes their mind every week". In a WhatsApp group or an email thread, the line between internal and client is one wrong recipient away. The right tool makes the mistake impossible by design: team notes have no path to the client.
3. Who approves a quote, a change order, an invoice?
Sending an estimate to the client commits the studio. Publishing a change order alters an amount the client has approved. Issuing an invoice is an accounting act. These three acts are irreversible or reach a third party: they cannot be open to everyone by default. But if every send goes through you, you become the bottleneck the hire was meant to remove. The answer is a clear line between preparing and committing: the collaborator prepares everything, the administrator commits.
4. What happens to the history when the person leaves?
A freelancer finishes the assignment, an intern completes the year, a partner moves on. If their exchanges with the client, their site reports and their estimate versions lived on their personal account, Drive or phone, they leave with them. The question to ask on day one, not on the last day: will everything this person produces stay in the studio's file, under my control, the day I remove their access?
A simple role grid: owner, administrator, collaborator, reader
Four levels are enough for a studio of two to five. The principle separating them fits in one sentence: anything irreversible, or that reaches the client or a third party, belongs to the administrator. Everything else is open to the collaborator.
| Action | Owner | Administrator | Collaborator | Reader |
|---|---|---|---|---|
| See projects, documents, schedules, prospects | Yes | Yes | Yes | Yes |
| Create and edit an estimate, a site report, a task | Yes | Yes | Yes | No |
| Exchange with the client in their portal | Yes | Yes | Yes | No |
| Send a quote to the client, publish a change order | Yes | Yes | No | No |
| Invoice, close a project, delete a document | Yes | Yes | No | No |
| Invite or remove a member, change a role | Yes | Yes | No | No |
| Subscription, studio settings, branding | Yes | No | No | No |
The reader is useful more often than you would think: an accountant who needs to see projects and amounts without touching anything, a future partner discovering the studio, a coordination partner on a site. The collaborator is the default role for a freelancer or an intern. The administrator is for a partner, or a senior collaborator you trust with projects end to end.
Five golden rules
- Everyone sees the whole workspace. Restricting visibility project by project looks careful; in practice it creates blind spots and double entry. Confidentiality is owed to the client and third parties, not between members of the studio.
- "Responsible" is not a wall. Naming a responsible person per project tells everyone who follows up, who chases, who answers. It is a steering label, not an access restriction.
- Internal notes never leave. Team tasks, comments, doubts about a bid: they live in a space the client cannot reach, by design rather than by discipline.
- One human = one account. Sharing a login removes traceability (who changed this price?), breaks revocation (removing one person means changing everyone's password) and puts you in breach on your clients' data.
- The owner answers for their members. Towards your clients, you are the one granting access to their data. A confidentiality clause in the collaborator's contract and a written exit policy are the minimum.
The tools, compared on what matters as a team
The question is not "which tool has the most features" but "which one answers the four questions above without me having to think about it". Four families present themselves.
| Criterion | Drive + messaging | Generic suite (boards, kanban) | Practice management tool | Trade tool with roles |
|---|---|---|---|---|
| Distinct roles (prepare / commit) | No | Partial (editor / viewer) | Often a single level | Yes, four levels |
| Internal notes invisible to the client | By discipline | By discipline | Varies | By design |
| One file: project + estimate + client portal | No, scattered files | No, production happens elsewhere | Project and site, estimating sometimes | Yes |
| Revoking a member in one action | Folder by folder | Yes | Yes | Yes, with an activity log |
| Cost as a team | None | Per user | Per user, often high | Per seat, tiered or included by plan |
| Breaks at | The first message sent to the wrong recipient | The first week without discipline | The first estimate outside the tool | A need for advanced simultaneous co-editing |
Drive and messaging cost nothing and are enough for a freelancer on a short assignment, provided you accept that the internal / client line rests on everyone's attention. Generic suites structure the follow-up but leave production (estimate, quote, client portal) elsewhere, so the file stays scattered. Practice management tools cover the project and the site, most often with a single access level. The trade tool with roles is the only one answering the four questions inside the same file; its limit is simultaneous co-editing of a single document, rarely needed in a studio of three.
The onboarding checklist for a collaborator
Before day one: a confidentiality and client-data clause in their contract or agreement; a named account created with the right role; the projects they will be responsible for identified.
Day one: show them the prepare / commit line (they prepare the estimate, the administrator sends it); show them where internal notes live and why they have no path to the client; agree who answers the client and within what delay.
Week one: review together their first site report and their first estimate before sending; check they work inside the studio's file and not on their own machine.
Departure day: remove access before the last coffee; check that sharing links opened during the assignment are regenerated; make sure their client exchanges stayed in the file. All of it takes ten minutes if the tool was chosen for it.
And Nodal in all this?
Nodal applies this grid as is. A studio is a single workspace; the owner invites members by email and gives each one of the four roles. Every member sees the whole workspace; one or more responsible people are named per project, as a label. Team tasks and comments are invisible to the client by design: they do not exist in their portal. Favourite tradespeople are shared by the studio; reviews stay signed by the person. One honest note on Studio mood boards: they are edited by one person at a time, with a visible lock and the option to take over; simultaneous co-editing is not on the agenda for a studio of three. Per-seat terms are on the pricing page.