Ask anyone in a small studio "who owns procurement follow-ups?" and watch what happens. Silence, then "we all kind of do it," which in practice means the owner does it at 11pm. Most Indian design studios under fifteen people run on an unspoken structure where everyone does everything, the founder does the most of everything, and responsibility is a fog that thickens exactly when something goes wrong. The fix isn't an org chart with fancy titles, it's role clarity: a written answer to "who owns what" for the fifteen or so recurring jobs every studio has. Let me map the actual roles a studio needs, how they evolve as you grow, and the ownership questions that matter more than any title.
Roles are bundles of ownership, not titles
Strip away the designations and every interior or architecture studio runs on the same recurring jobs: winning work, designing it, documenting it, buying for it, building it, billing it, and keeping the clients calm throughout. A "role" is just a named bundle of those jobs with one accountable person per bundle. In a three-person studio one human holds four bundles, and in a fifteen-person studio the bundles split across specialists, but the bundles themselves never change, which is why role clarity scales and titles don't.
Here's the map I'd draw for a typical growing studio:
| Role | Owns | Typically appears at |
|---|---|---|
| Principal / founder | Design direction, key client relationships, pricing, final approvals | Day one |
| Senior designer / project lead | A project's design quality and delivery, end to end | 3 to 5 people |
| Junior designer | Drawings, specs, boards to standard, under review | First hire, often |
| Site supervisor | Execution quality, snags, contractor coordination, daily site updates | When execution work grows |
| Procurement / operations | Vendor quotes, POs, deliveries, vendor payments | 5 to 8 people, often part-time before that |
| Accounts / finance | Invoicing, collections, expenses, GST and TDS hygiene | Part-time or outsourced early, in-house later |
| Client success (often the lead) | Updates, approvals, expectation management | Grows out of the lead role |
Two observations from watching studios run this map well. First, the highest-leverage separation is design from procurement, because they compete for the same hours and procurement always loses until a delivery fails. The person chasing vendor quotes at 6pm cannot also be detailing a staircase at 6pm, and when one person holds both, the studio silently pays in whichever currency it can least afford that week. I've written the full operational chain in how to run procurement from PO to delivery without chaos, and the first line of that fix is giving the chain one named owner.
Second, the founder's real role transition is from doing to approving. In a healthy structure the principal's name appears on approvals, pricing, and direction, and progressively disappears from production. If your name is still on "drawings" at ten people, the structure has a bug, and it's usually costing you the growth I described in how to scale an interior design studio.
The ownership questions that actually cause fights
Titles don't prevent conflicts, ambiguous edges do. These five edges cause most of the friction I see, so settle them in writing:
Who talks to the client? Everyone eventually, but one person owns the relationship per project, and every commitment (dates, changes, costs) routes through them. Clients exploit multi-channel studios ruthlessly, asking the junior for the freebie the lead refused.
Who can commit money? Define the rupee threshold above which a purchase needs the principal's sign-off, and below which the procurement owner just moves. No threshold means either everything waits for you or nothing does, and both are terrible.
Who approves what leaves the studio? Drawings, boards, quotes: each needs a named approver per project. "It went out unreviewed because I thought you'd checked it" is a structure failure, not a people failure.
Who owns the site relationship? The supervisor owns daily execution and the snag list, the lead owns design intent, and when the carpenter proposes a "small simplification," the escalation path between the two must be explicit, because that simplification is where design quality dies quietly.
Who chases money? Collections need one owner with a standing weekly review, because an invoice everyone can see and nobody owns ages to ninety days. Margin protection is mostly ownership, a point I've expanded in how to protect your margin on every design project.
Writing it down without bureaucracy
You don't need a fifty-page HR manual. One page per role: the bundle it owns, the decisions it can make alone, the decisions it escalates, and the standing meetings it speaks at. Then one studio-wide grid mapping the fifteen recurring jobs to names. Review it quarterly and whenever someone joins or leaves. The formal profession has long worked this way, architectural practice under the Council of Architecture framework defines stage-wise responsibilities precisely, and bodies like the Institute of Indian Interior Designers publish practice standards for interior design engagement scopes, and small studios can borrow the principle without the paperwork: responsibility is defined per stage, in writing, before the stage begins.
The one-page role definition
- The bundle: which recurring jobs this role owns, listed plainly
- Decides alone: the calls this role makes without asking
- Escalates: the calls that go up, and to whom
- Money authority: the threshold this role can commit without sign-off
- Speaks at: which standing meetings this role reports in
- Backup: who covers when this person is on leave, decided now, not during the leave
Freelancers and consultants slot into the same grid, with sharper edges: a freelance 3D visualiser or a contract site supervisor gets the same one-pager, plus IP and confidentiality terms, because informal external engagements are where both quality and ownership leak first. I've covered the specifics in managing freelancers in a studio.
Where the structure becomes real: in the system
Here's the catch with role clarity on paper: paper doesn't enforce anything. The role grid says the procurement owner raises POs and the principal approves above the threshold, but if POs are Word files sent over WhatsApp, the structure depends on everyone remembering it under pressure, and pressure is exactly when they won't. Structure becomes real when the workspace encodes it: purchase requests route to the named approver, quotes can't reach clients unreviewed, payment approvals wait for the person with money authority, site updates flow from the supervisor's phone into the project where the lead sees them, and the client sees exactly what's released to their portal, nothing else.
That's how Designa is built, roles map to what each person sees and can approve, the org-wide ledger shows the principal every rupee moving without asking anyone, and clients get their own branded portal with unlimited free client logins, so "who talks to the client" becomes structurally clean too. New joiners inherit the structure on day one instead of learning it by mistake, which connects directly to onboarding a new designer well: a legible studio teaches its own structure.
Start with the grid this week: fifteen recurring jobs down the left, names on the right, no shared cells. Where two names want the same cell, that's your next conversation, and where no name fits, that's your next hire or your next system. If you want the version where the grid enforces itself inside one connected workspace, at one flat founding price for the whole studio, billed in rupees, walk through it at demo.designa.work or see the founding offer at go.designa.work.
Frequently asked questions
What roles does a small interior design studio need?
Seven bundles cover most studios to fifteen people: principal, project lead, junior designer, site supervisor, procurement or operations, accounts, and client communication. In small teams one person holds several bundles, but each bundle needs exactly one accountable owner.
When should a studio hire a dedicated procurement person?
Usually around five to eight people, or earlier if execution-heavy projects dominate. The signal is design hours being eaten by vendor follow-ups, because design and procurement compete for the same time and procurement failures cost real money.
How do I stop everyone from talking to the client separately?
Name one relationship owner per project and route all commitments through them. Other team members can interact, but dates, costs, and scope changes come from one voice, ideally through a portal where communication is visible and recorded.
What is the founder's role supposed to become as the studio grows?
Direction, pricing, key relationships, and approvals, with production progressively delegated. If the founder is still producing drawings at ten people, the structure is limiting growth.
How do roles work with freelancers?
The same one-page definition applies, with added IP assignment and confidentiality terms. A freelancer with a defined bundle, money threshold, and escalation path behaves like part of the structure instead of a loose end.