How to run a small architecture studio in India (without burning out)

Rohan finished the Working Drawings package for a residential project in Pune at 9pm on a Tuesday. He was proud of the work. Then he sat down to raise the invoice and spent the next 90 minutes hunting for the client's GSTIN, recalculating the cumulative fee balance in Excel, and trying to remember whether the previous invoice had been for Stage 3 or Stage 4.

By 10:30pm, the invoice was sent. By 10:31pm, he was answering a WhatsApp message from another client asking for a project update.

Rohan runs a 7-person studio in Pune. He is, by most measures, a successful architect. He is also, by his own admission, the studio's accountant, HR manager, project coordinator, and operations team — all rolled into one.

If you're reading this, you probably recognise that story. Running a small architecture studio in India means doing extraordinary design work and managing everything that surrounds it. This guide is about the second part.

Most guides cover how to start a firm: COA registration, business structure, marketing. That's useful for year one. This is for what comes after — the five operational areas every principal of a small Indian architecture studio needs to manage, and how to build systems around them so the work doesn't depend entirely on your memory.

The principal architect trap: why operations keep eating your design time

What "running a studio" actually means for a 3–15 person firm

In a 50-person corporate practice, different people handle finance, HR, project management, and client relationships. In a 6-person studio in Jaipur, one person handles all of it. Usually the principal.

The operational load typically includes:

• Generating phase-wise invoices and tracking outstanding payments
• Processing monthly payroll and generating payslips for 4–12 team members
• Managing attendance and leave
• Tracking which team members are allocated to which projects and whether anyone is overloaded
• Monitoring project-level profitability across 3–6 active jobs
• Maintaining client records, GSTIN details, and billing information
• Coordinating task assignments and following up on deliverables

Most principals spend 10–15 hours a week on these tasks. That's 10–15 hours not spent on design.

This is not a management failure. It's a structural reality of small-firm practice. The question is whether you're managing it with systems or with willpower.

When the Excel–WhatsApp–Tally stack stops working

The tools most small Indian studios rely on are not bad tools. Excel is a capable spreadsheet. Tally handles accounting well. WhatsApp is how Indian professionals communicate.

The problem is that none of them were designed to answer the question: "How is my studio doing right now?"

• Excel records what you enter. It doesn't update when a phase changes status or a payment comes in unless you update it manually. Manual updates slip.
• Tally tracks transactions after they happen. It tells you what was invoiced and received — not what's currently at risk or why a project's margin is shrinking.
• WhatsApp contains the actual operational context of the studio. But it's chronological, unsearchable, and completely dependent on everyone being online to interpret it.

At 3–4 people, a sharp principal can hold everything in their head. At 6–8, the context load starts breaking things. Deliverables slip because someone didn't see the message. Invoices are delayed because the billing sheet wasn't updated. A team member ends up on four projects simultaneously because no one had a clear view of total workload.

The problem isn't the tools. It's that the studio has grown past the point where these tools can give you an accurate picture of what's happening.

The five operational areas every small Indian architecture studio needs to manage

1. Project and phase tracking

The COA's 7 project stages give Indian architecture firms a natural framework for tracking progress: Concept Design, Preliminary Design, Approvals, Working Drawings, Tender, Construction, and Completion. Most studios already think in these terms. The gap is that this thinking rarely lives anywhere structured.

A basic project tracking system answers three questions for every active project:

1. Which phase is the project currently in?
2. What deliverables are outstanding for this phase?
3. Are we running ahead of or behind the original schedule?

The weekly project review habit is the simplest implementation. Thirty minutes, every Monday, working through each active project one by one. Not a meeting — a check-in with the data. The purpose is to catch slippage before it compounds.

A project kickoff checklist at the start of every new project, before design begins, makes this review much faster. When scope is documented and phases are defined from day one, weekly tracking becomes a 5-minute check rather than a 30-minute reconstruction.

2. Billing and invoicing

Billing delays are the single most common cash-flow problem in small Indian studios. The work gets done. The invoice is delayed by days, then weeks, because the principal is occupied with the next project.

The fix is a billing trigger: a rule that invoices go out within 3 working days of phase completion, every time, without exception. Not "when I remember." Within 3 days.

The trigger has two effects. First, it creates a regular payment rhythm clients come to expect. Second, it forces engagement with the billing numbers at the natural moment when project data is freshest.

When generating a GST invoice for architectural services, every invoice must include:

• Your firm's GSTIN and the client's GSTIN (if they're GST-registered)
• Place of supply (determines CGST/SGST vs. IGST split)
• SAC code 998311 for standard architectural services
• Taxable amount, CGST at 9%, SGST at 9%, total
• Cumulative fee billed to date (for phase-wise contracts)

If your current process involves assembling this from different places every time you invoice, that's where the 90-minute invoicing sessions come from.

3. Team allocation and utilisation

Priya runs a 9-person studio in Ahmedabad. Earlier this year, she agreed to take on a new commercial project because the pipeline looked manageable. Two weeks in, two of her best team members were each working on three projects simultaneously. Neither had flagged it. She found out when both projects started slipping deliverables in the same week.

This is the overallocation trap. It happens in almost every small studio that grows past 6–7 people without a structured allocation view.

The solution is not a complex resource management tool. It's a simple visual: for every project, which team members are assigned and at what approximate percentage of their time? With this view, the answer to "can we take a new project?" moves from a gut feel to a 2-minute check.

Utilisation tracking also catches something else: the team members who are consistently underallocated. In a small studio, underutilised capacity is as expensive as overloaded capacity — just less visible.

4. Payroll and attendance

For most principals of small studios, payroll is a monthly event that arrives unexpectedly. Attendance hasn't been tracked consistently. Leave balances aren't clear. The salary calculation takes 2–3 hours because it's being assembled from scratch.

Treating payroll as a system rather than an event starts with one habit: attendance tracked in real time, not reconstructed at month end.

With current attendance data, monthly payroll becomes a 20–30 minute process:

1. Review attendance and approved leave for the period
2. Calculate net days worked for any variable-pay team members
3. Generate payslips reflecting the current period
4. Transfer salaries and file payslips

This sounds obvious. In practice, the variance in how long payroll takes is almost entirely explained by whether attendance was tracked as it happened or assembled from memory. Team members also reference payslips for loan applications, visa documentation, and rental agreements — a studio that generates clean payslips consistently builds trust at zero additional cost.

5. Financial health visibility

Ravi runs a 6-person studio in Kochi. He completed a residential project last year — a ₹22L job that took 16 months. When he sat down with his CA after the final invoice was cleared, the project had generated a net margin of around 12%. He'd been expecting closer to 30%.

The margin had eroded across three areas: scope additions absorbed without variation orders, Working Drawings that ran 40% over the estimated hours, and a 4-month delay in the final site supervision invoice that pushed the receivable into the next financial year.

None of this was visible during the project. By the time Ravi knew, the project was over.

The financial health question for every active project is simple: what is the project's current implied margin, based on fees received versus direct costs incurred to date? Five projects should each have a live number.

When that number starts diverging from the expected margin, it triggers a conversation: Is there scope that hasn't been billed? Are hours running over the phase budget? Is an invoice outstanding past 60 days? These conversations, held during the project, are recoverable. The same conversations, held after the project closes, are an autopsy.

The five numbers to review every Monday:

1. Total outstanding invoices across all active projects
2. Invoices overdue beyond 30 days (by project)
3. Implied margin for each active project
4. Projects where phase completion hasn't triggered an invoice yet
5. Next invoice due date for each project

This review takes 10–15 minutes. It prevents the margin surprises Ravi experienced.

Building a weekly rhythm that keeps the studio running

Systems without a rhythm don't hold. Here's the minimum operational calendar for a small studio principal:

None of these are large time investments individually. The principal who runs on instinct spends far more time on each because they're reactive rather than scheduled.

What to systematise first

If you're currently running on Excel, WhatsApp, and memory, it's tempting to fix everything at once. Don't. Fix these three things in order:

First: Get billing on a trigger. Decide today that every phase completion results in an invoice within 3 working days. This single habit has the highest ROI of any operational change a small studio can make. Cash flow improves. The billing process becomes predictable. Outstanding balances shrink.

Second: Start logging time by project. Even a basic weekly log — just project name and hours worked — changes how you understand your margins. Research from Monograph found that firms tracking hours by phase run ~10% more projects on schedule, because they catch overruns before they compound. You need enough data to see whether a project is consuming more time than the fee justifies.

Third: Track outstanding invoices in one place. A single view of every invoice raised, its status (sent / partially paid / paid), and how many days since it was raised. This takes 10 minutes to set up. It prevents the common pattern of a studio reaching quarter-end and discovering ₹8–12L in receivables that haven't been followed up.

You don't need a perfect system before you start. Billing trigger, time logging, outstanding tracker. In that order. Everything else comes later.

How to run a small architecture studio without depending on your memory

The test of a well-run small studio is simple: if you took a week off without access to your phone, would the studio continue to function?

Not perfectly. But would the team be able to deliver work, respond to clients, and process a routine invoice without you as the intermediary?

For most principals of small Indian architecture studios today, the answer is no. The studio's operations live in one place: the principal's memory.

Getting to "yes" is not about hiring an office manager or buying enterprise software. It's about building the five systems above, establishing the weekly rhythm, and consistently externalising the operational context so the team can work without bottlenecking through the principal.

ArchiEase is designed to be that system for small Indian studios — projects mapped to COA stages, GST-compliant invoicing, team allocation and timesheets, payslip generation, and a financial health dashboard that shows the five Monday-morning numbers at a glance. The free pilot is set up with your actual projects, not a demo dataset.

But the framework in this article works regardless of what tool you use. The studio that runs without burning out the principal is the one where operations are a system, not a memory.