When Growth Outpaces the Spreadsheet

Every developer starts small. A handful of sites, a founding team who knows every project by name, and a shared spreadsheet that gets updated whenever someone remembers to do it. At 50 sites, this works fine. The person managing the portfolio can hold most of it in their head, and the spreadsheet is more of a shared notepad than a system of record.

The problem is that growth doesn’t ask permission. And what works cleanly at 50 sites starts to break down long before you reach 500.

At 50 sites: manageable, if fragile

With a portfolio this size, a small team can usually track site status, interconnection progress, and construction milestones through a mix of memory, email threads, and a spreadsheet that gets updated after the fact. It’s not elegant, but it’s survivable. If someone asks “where do things stand with Project 23,” there’s a good chance someone on the team just knows.

The fragility is easy to miss at this stage because it hasn’t caused a visible failure yet. The information exists, just not in a form that scales. It lives in one or two people’s heads, in scattered email threads, and in a spreadsheet that’s only as current as the last time someone remembered to open it.

Somewhere between 250 and 500 sites: the wheels start to wobble

This is where most developers we talk to say the cracks start to show. The team has grown, but not proportionally to the complexity of the portfolio. More projects are moving through site acquisition, interconnection, and construction simultaneously, and no single person can hold the full picture anymore.

The spreadsheet is now being updated by multiple people, on different cadences, with different levels of diligence. Version conflicts creep in. Someone updates a site’s status locally but forgets to push it to the shared file. A project manager assumes a milestone happened because it’s marked complete, when actually the mark was made three weeks before the milestone was even confirmed.

Meanwhile, the questions leadership asks get harder to answer quickly. “Which projects are behind on interconnection?” used to be something you could answer from memory. Now it requires someone spending an afternoon reconciling five different sources before they can say anything with confidence.

At 500+ sites: the old approach doesn’t just wobble, it fails

Past a certain point, the manual approach doesn’t just become inefficient. It becomes actively unreliable. The gap between what’s happening in the field and what’s reflected in your tracking system grows wide enough that decisions get made on outdated information. A capacity offer gets missed because nobody flagged the deadline in time. A construction crew shows up to a site missing a lease detail that was known internally but never made it into the file they were working from.

This is also the point where the cost of the old approach becomes visible in ways leadership can’t ignore. Not because someone finally built a better spreadsheet, but because the fundamental model, information scattered across people and files, stops being able to support a portfolio at this scale, no matter how disciplined the team is about updating it.

Why this isn’t a discipline problem

It’s tempting to treat this as a process failure: if the team were just better about updating the spreadsheet, this wouldn’t happen. But that framing misses what’s actually going on. No amount of individual diligence fixes a structural problem. A spreadsheet, however well maintained, is a single static snapshot updated by hand. It was never built to reflect the real-time state of a growing, multi-stage portfolio, and no team discipline changes that fact.

The fix isn’t better habits. It’s a system where site, project, and asset data live in one place that updates as work happens, not one that depends on someone remembering to type it in afterward.

What to watch for in your own portfolio

If your team is somewhere in that 250 to 500 range, or approaching it, a few signs tend to show up before the fully unmanageable stage does: leadership questions that used to get answered in a sentence now take an afternoon of reconciliation. Different people on the team have different answers to the same status question. And someone, usually without saying it out loud, has started keeping their own shadow tracker because they don’t fully trust the shared one anymore.

None of these are signs of a bad team. They’re signs of a system that was built for a smaller version of the business than the one you’re now running. It’s worth addressing before the gap between what’s tracked and what’s actually happening gets wide enough to cost you a project.


About Sitenna

Sitenna is the intelligent operations platform built to eliminate blind spots across modern infrastructure. By centralizing fragmented asset data and automating workflows from site acquisition through execution and management, Sitenna delivers the real-time visibility and control needed to keep projects on track. With Sitenna, infrastructure teams move faster, collaborate smarter, and scale confidently – turning complexity into clarity at every stage.

Contact us at sales@sitenna.com