Project Management
At some point in the life of every growing architecture or interior design firm in India, the principal hits a wall. Not a design wall - the design work is fine. The wall is something more operational, more invisible, and far more damaging to the business: they can no longer hold all their projects in their head at once.
There are eight projects running simultaneously. Three are in the design phase, two are under construction, two are at the approval stage, and one is almost at handover. Each client believes - correctly - that their project is important. Each expects timely responses, informed updates, and the sense that they are being given priority attention.
And the principal, who is the connective tissue for all eight, is fielding calls during site visits, responding to WhatsApp messages at midnight, and waking up at 3am trying to remember whether they got the budget sign-off from the Mehta project or just thought about asking for it.
This is not a capacity problem. The firm has enough people to do the design work. The actual bottleneck is communication capacity - and it's costing the firm in client satisfaction, in referrals, and in the mental health of its founder.
There is a widespread belief among architects that the hard part of scaling a firm is hiring good designers. This is only partly true. Hiring good designers helps you do more work. But it does nothing to solve the coordination problem between your firm and your clients.
Communication with clients doesn't scale automatically with your team. When you have two projects, you can personally manage all client communication. When you have eight projects, you cannot - and if you try, you either become the bottleneck or you start dropping things. Neither outcome is acceptable when you're managing projects worth ₹40 to ₹80 lakhs each.
The firms that successfully manage 8, 10, or 15 simultaneous projects in India are not operating on superior talent. They are operating on superior systems. Specifically, they have built systems that separate two things that most small firms treat as inseparable: the delivery of information and the perception of personal attention.
"Every client thinks they're your only client. Your job isn't to correct that impression - it's to build systems that make it feel true."
This is the core insight of multi-project management for architecture and design firms. Clients don't need to physically occupy your time - they need to feel that their project is being actively cared for. Those are different things, and systems can deliver the second one even when the first is impossible.
When a client feels they are not getting attention, they rarely attribute it to your firm being busy. They attribute it to a failure of professionalism, or worse, a sign that something is wrong with their project. This is how silences become crises.
The trigger for feeling deprioritised is almost always one of three things:
The client sent a message or asked a question and didn't receive a timely response. This doesn't mean same-day response to every message - it means that substantive questions about their project don't sit unanswered for three days while you're dealing with a crisis on another site. A simple acknowledgement - "I've noted this, will revert by Thursday" - changes the entire experience.
If a client has not heard from you in ten days, they start to wonder. Not because they expect daily contact, but because the silence creates uncertainty. In the absence of information, people fill the gap with their own fears. A quick site update or progress note - even a brief one - resets the uncertainty clock and reminds the client that their project is in motion.
Clients talk to each other. A client in Bandra whose friend is also working with your firm in Andheri will compare notes. If their friend received weekly updates and they haven't heard from you in two weeks, the disparity itself becomes a data point. The solution is not to manage every client identically - it's to have consistent minimum standards of communication that apply across all projects regardless of size or stage.
Building a multi-project management system for an architecture firm requires addressing four specific operational areas. Each one is a place where things fall through the cracks when you scale beyond what a single person can hold in their head.
You need to be able to see the current state of every active project from a single view - not by opening eight different files or tabs, and not by asking your team for a status update. A project health dashboard that shows stage, last client communication, pending approvals, and budget status gives you the situational awareness to prioritise your attention correctly.
Without this, you default to giving attention to whichever client made the most noise most recently - which is exactly backwards. The clients who most need attention are often the quietest, because they are waiting for something that has already fallen through the cracks.
Reactive communication - responding when clients reach out - is not a system. It's the absence of a system. A genuine multi-project communication system means you have a scheduled cadence for proactive updates on every active project, and it happens regardless of whether the client has asked.
For most architecture firms, a weekly site update during construction phase and a bi-weekly check-in during design phase is the minimum. This doesn't have to be long - a few photos, a brief note on what happened this week and what's coming next, and any decisions pending from the client. Ten minutes per project per week. At eight projects, that's eighty minutes. It's the most valuable eighty minutes you will spend.
In a multi-project firm, verbal approvals are a liability. When you're managing two projects, you remember what each client said. When you're managing eight, you don't - and neither does your team. The result is that decisions get re-made, or worse, they get made incorrectly based on someone's recollection of what was agreed.
Every approval - material selections, design changes, scope additions, contractor quotes, budget variations - needs to be documented as a formal record with a date and a clear statement of what was decided. Not as bureaucracy, but as infrastructure. This record protects you when disputes arise, and it reassures the client that their decisions are being acted on precisely as they were made.
A firm in Pune running ten concurrent projects introduced formal approval documentation for all their projects last year. Within three months, the number of "but I thought we agreed on..." conversations dropped dramatically. The time saved on dispute resolution alone more than covered the time spent on documentation.
One of the hardest parts of scaling a multi-project firm is transferring ownership of client communication to team members without losing quality or consistency. Principals often hold on to client communication because they've been burned before - a junior architect gave a client incorrect information, or forgot to follow up on something critical.
The solution is not to keep all communication with the principal. The solution is to give team members a structured framework that makes it hard to get it wrong. When there are clear templates for site updates, defined approval workflows, and a system that flags overdue communications, your team can own client communication with confidence - and the principal can focus on the work that actually requires their expertise.
"The principal's job in a well-run multi-project firm is to make decisions, not to be the communication department."
Let's be specific. Here is what a well-run multi-project week looks like for an architecture firm in Bangalore managing nine active projects:
Monday morning: the principal reviews a dashboard showing the status of all nine projects - which ones have pending client approvals, which ones haven't had a site update in more than seven days, which ones have budget variations that need client communication. This takes fifteen minutes and produces a clear priority list for the week.
During the week: project managers send structured site updates to each client in construction phase. These go out through a client portal, not WhatsApp, so there is a record. Clients who have pending approvals receive a clear notification with exactly what they need to decide and by when.
Friday: any unresolved approvals are flagged automatically. The principal reviews which ones are stalling a project and decides whether to follow up personally or delegate.
At no point does the principal need to remember what's happening on every project. The system holds that information. The principal's attention goes where it creates the most value - design decisions, client relationships, business development - not to remembering whether the tile approval for the Sharma residence has come through yet.
Most architecture firms in India underestimate what unstructured multi-project management actually costs them. The cost is not just the principal's time. It shows up in other ways:
There are specific signals that your current multi-project management approach is reaching its limits. Watch for these:
Any one of these is a signal. All five together means the system has already failed - you're just managing the consequences rather than addressing the cause.
The counterintuitive conclusion that most growing architecture firms eventually reach is this: they can take on more projects not by hiring more designers, but by building better client communication systems.
When clients feel informed and cared for without requiring reactive time from the principal, the principal's real capacity - their ability to think, design, and guide projects - is freed up. A principal who is spending two hours a day fielding "what's happening?" calls has two fewer hours for the work that grows the firm. Fix the communication system and you get those hours back - for every project, every week.
Architecture firms in Mumbai, Bangalore, Delhi, and Hyderabad that are successfully running 12 to 20 projects simultaneously are not exceptional firms with exceptional people. They are ordinary firms with excellent systems. That's the whole secret.
Archivault gives every project structured updates, formal approvals, and a client portal - so you can scale without the principal becoming the bottleneck.
Book a demo →