← All posts
Why one system

Why Spreadsheets Break at Five Projects

Why Spreadsheets Break at Five Projects: the honest math on what a scattered setup really costs an Indian studio, and what one connected system changes.

8 min read

Every studio I know started the same way, one project, one spreadsheet, and it worked. You had a tab for the budget, a tab for the furniture list, maybe a shared drive folder with the drawings, and it all held together because the whole business fit inside your head. Then you took a second project, and a third, and somewhere around the fifth concurrent job the whole thing quietly fell apart, and you could not even point to the day it happened. This post is for the studio owner or project lead who is running four or five jobs at once on Excel and Google Sheets and feeling the ground shift, and I want to show you the actual math of why five is so often the number where a spreadsheet setup breaks.

The spreadsheet works beautifully, right up until it doesn't

Let me be honest about why spreadsheets feel so good at the start, because pretending they are useless would insult your intelligence. A spreadsheet is free, it is flexible, everyone on the team already knows how to use one, and for a single project it genuinely is enough. You can see the whole job on one screen. The trouble is not the spreadsheet itself, the trouble is what happens when you multiply it, because a studio does not grow by making one project bigger, it grows by running more projects at the same time, and that multiplication is exactly what a flat file was never built to survive.

The math nobody runs before it hurts

Here is the part worth sitting with. A single home project is not one spreadsheet worth of information, it is roughly eight rooms, each with a furniture and finish list, each list going through three or four rounds of client revisions, each revision touching a quote, and each quote eventually needing an invoice. So one project is already dozens of moving cells that all have to agree with each other. Now run five of those at once.

Roughly how the moving parts multiply as you add projects
1 project30
2 projects60
3 projects90
4 projects120
5 projects150

Those numbers are illustrative, not a survey, but the shape is the whole point, the workload does not add up, it stacks, and every one of those cells is a place where the version on your laptop and the version in your site engineer's inbox can quietly disagree. When you had one project you could hold the discrepancies in your head. At five you cannot, and that is not a discipline failure, it is arithmetic.

Projects runningWhat a spreadsheet setup feels likeWhat actually breaks
1 to 2Calm, everything on one screenNothing yet
3Slightly busy, a few duplicate filesSmall version slips
4You start a "master" sheet to track the othersCross-references go stale
5 and upYou are managing the tracking, not the workSingle source of truth is gone

Version chaos and the "which file is right" tax

The first thing to actually break is truth. Someone downloads the furniture list to edit on the flight, someone else updates the shared copy, and now there are two, and neither is clearly the real one. Multiply that by five projects and you spend a genuinely painful chunk of every week just working out which number is current, which is a tax you pay in the most expensive hours you have. I wrote about this specific failure in the hidden admin tax on designers, because it is the leak that hides best, and it compounds fast once you cross into multiple concurrent jobs. The deeper version of this problem, tool sprawl, is what happens when you paper over the cracks by adding a chat app here and a separate quoting tool there, and I broke that down in how tool sprawl slows a design studio.

Where the money leaks, not just the time

Version chaos wastes hours, but the spreadsheet also leaks actual rupees, and this is the part owners underestimate. Procurement is the clearest example. When your purchase orders live in a separate sheet from your approved specs, it is easy for a PO to go out at last month's rate, or for a delivery to slip with nobody watching the date, and that gap between the quote the client approved and the money that actually left your account is pure lost margin. I laid out a clean way to run procurement from PO to delivery without chaos, and none of it works reliably on disconnected sheets. The other quiet leak is revisions, because when a client changes their mind and the change does not flow from the spec to the quote to the invoice, you eat the cost, which is exactly the trap I covered in how to stop losing money on revisions.

What breaks first, and in what order

If you want to know where you sit on this curve, watch for the failures in sequence, because they arrive in a fairly predictable order and each one is a warning about the next.

Signs your spreadsheet setup is already past five-project strain

  • You keep a spreadsheet whose only job is to track your other spreadsheets
  • Two people have edited two copies of the same list this week
  • A PO went out at the wrong rate and you found out at delivery
  • You cannot answer "what is the latest cost on that project" without opening four files
  • Month-end invoicing takes days because nothing carries over from the quote

If three or more of those are true, you are not disorganised, you have simply outgrown the tool, which is a good problem to have because it means the studio is actually working.

Why "just be more disciplined" misreads the problem

Every owner's first instinct is that this is a discipline problem, that if the team just named files properly and updated the master sheet religiously, it would hold. I believed that too, and it is wrong, because discipline scales in a straight line while the work scales combinatorially. You can ask five people to be careful, but you cannot ask them to manually keep 150 interdependent cells in sync across five projects while also designing, and expecting that is setting good people up to fail. The failure is structural, the tool stores loose files that have no obligation to agree, so the only thing holding them in agreement is human vigilance, and human vigilance is exactly the resource a busy studio has least of. Blaming the team for a spreadsheet's design is a bit like blaming the driver because the road had no lanes.

One connected system changes the unit of work

Here is the shift that actually fixes this, and it is not "a better spreadsheet". The reason five projects break a spreadsheet is that a spreadsheet stores information in files, and files multiply. A connected system stores the studio as one live structure, so a project is a project, its rooms and specs and quote and invoice are all the same record, and adding the fifth project does not add a fresh pile of files to reconcile, it just adds a project. That is the whole idea behind why one connected system beats five disconnected tools, and it is why I eventually stopped patching spreadsheets and built the thing properly.

This matters more in India than the global tools assume, because our studios run lean, we take on more concurrent projects per head, and our compliance and billing sit right on top of the design work rather than off in a separate finance department. Professional bodies like the Council of Architecture and the Institute of Indian Interior Designers have grown the profession fast, and a lot of that growth is small studios juggling many jobs at once, which is precisely the workload spreadsheets handle worst.

5
the project count where most spreadsheet setups quietly break
1
connected workspace instead of a folder full of files
0
double entry between an approved quote and a GST invoice

Frequently asked questions

Why do spreadsheets stop working when a studio grows?

Because a studio grows by running more projects at once, not by making one bigger, and a spreadsheet stores loose files that have no obligation to agree with each other. The interdependent data multiplies faster than any team can keep it in sync by hand.

How many projects can you run on Excel before it breaks?

There is no hard limit, but around five concurrent projects is where most studios feel it go, because that is where version chaos, stale cross-references and procurement slips outrun human vigilance.

Is Google Sheets better than Excel for a design studio?

Shared editing helps a little, but it does not fix the core issue, which is that files still multiply and nothing forces the specs, quote, procurement and invoice to stay connected. A connected workspace solves what neither spreadsheet can.

What replaces spreadsheets for an interior studio?

One connected system where leads, room-by-room specs, client approvals, quotes, GST invoices and procurement live in the same record, so adding a project adds a project rather than a new pile of files.

Spreadsheets are not the enemy, they are just the tool for a stage you have grown out of. The moment you are running five projects at once, the cost of keeping everything in flat files stops being convenience and starts being lost margin and lost weekends. If you want the wider comparison of what to move to, I keep it current in the best software for interior designers in India guide. Designa runs the whole studio in one connected workspace for one flat founding price for the whole studio, billed in rupees, with unlimited free client logins. Click through a real setup at demo.designa.work, and when the fifth project is straining your sheets, the founding offer is at go.designa.work.

Run your whole studio on Designa

One flat founding price for your whole team, every module included, with a 7 day money back guarantee. See exactly how it works, then get started today.