Nearly every project kickoff starts the same way. Someone from the client team pulls up a business directory on their phone, reads what it says about Gensler, and announces: “Six thousand people. Offices all over the world. You can definitely handle this.”
I’ve nodded along to that script more times than I want to admit. I stopped nodding after three of my own projects came in late, over budget, or both—because I let a headcount number do the talking instead of looking at the team around the table.
Quick background: I’ve spent about ten years in project delivery for global architecture and design firms, the last seven with Gensler. I’ve worked on roughly forty projects, mostly workplace interiors, base buildings, and two office-to-residential conversions. Three of those projects went sideways. Not because the design was wrong. Because the gap between the firm’s public profile and the studio’s actual readiness was bigger than any of us admitted at kickoff.
The Gensler company size number isn’t wrong. It’s incomplete.
Search “gensler company size” and you’ll find numbers around 6,000 employees and more than 50 offices. Some directories say 5,500, some say 6,400. The exact number changes quarterly. Gensler has ranked at or near the top of industry size and revenue lists for most of the past decade, and the firm has made no secret of its scale.
That scale is real. But I’ve learned to see it as a limit rather than a feature.
Here’s why: a firm with thousands of people doesn’t work as one giant studio. It’s a network of smaller teams that share a name, a quality standard, and a research budget. The actual work on your project will be done by a relatively small group in one office. That group has its own workload, its own leaders, and its own specific experience. None of that appears in the Gensler company profile.
If the profile tells you the firm has experts in airports, healthcare, and digital experience, that’s true. It does not mean those experts are assigned to your building.
Where I tripped: trusting the brand instead of the bench
In September 2021, we won a feasibility and concept design package from an owner who wanted to convert a 1990s office building into rental housing. Good project, right client, genuinely interesting problem. The proposal included a senior architect who had led a well-known office-to-residential conversion in another city. He was the reason the client signed.
Three weeks before kickoff, I got the email I now dread: he had been shifted to a larger project that had just won approval. The handoff made sense from a business perspective. It didn’t help my client.
I backfilled the role with a very capable designer from our interiors studio. And this is the part I keep replaying: she was talented, but she had never taken an office building through the residential conversion code path. We underestimated the vertical riser capacity, missed a fire separation issue at the existing core, and only caught both after the owner’s peer reviewer flagged them.
The result: $95K in added surveys and redesign work, a $45K fee credit to keep the client relationship intact, and five weeks of delay. The senior architect I had originally promised did fly in for two four-hour workshops. Those eight hours saved the project. They were also eight hours too late to undo the problem.
This wasn’t a failure of design talent. It was a failure to match the profile to the people who were actually available. I oversold the firm’s size as if it meant “the right people will materialize when needed.” Sometimes they do. Sometimes they’re already on something else.
The hidden cost of a mismatched big-firm team
What bothers me most is that the real damage doesn’t show up on invoice totals.
In that 2021 case, the visible cost was around $140K. What didn’t show up: the client’s internal team spent two months managing our process instead of refining their business case. Their lender pushed the financing timeline out. They lost three weeks of leasing season. That’s the part that keeps me honest when someone searches for the Gensler company profile and assumes we’ll just handle it.
A large firm’s internal reviews and quality processes exist to catch errors. I still believe in them. But when the team is wrong for the assignment, those processes add coordination time instead of safety. You get more meetings, more layers of review, more project management overhead—and none of it compensates for the missing experience.
I have also watched this happen in the opposite direction. A small regional owner once asked us to help reposition an 80,000-square-foot office building. We could do it. We could also bring a global network of consultants, workplace strategists, and proprietary benchmarks nobody asked for. The project needed a county-specific permit path and a decision maker who lives within an hour of the site. We were not the most efficient option, and I told them so. A local firm, with twenty people and a decade of relationships in that building department, was almost certainly the better fit.
That’s not false modesty. It’s the difference between being a good architect and being the right architect.
How I check any firm’s true profile now
After the 2021 mess, I created a pre-kickoff checklist for our own teams. Now I give it to clients too, even when we’re the firm being evaluated. It’s saved us from at least two bad fits in the past two years (and saved me from two more awkward kickoff calls).
- Ask for the names and recent work of the exact team. Not the firm’s portfolio—the portfolio of the people who will be on your project. If the people aren’t named in the proposal, that’s a red flag.
- Ask how many active projects that team is carrying. Everyone says they’re busy. Dig one level deeper: how many projects are at the same stage as yours? A team running three parallel construction documents packages isn’t giving you their full attention.
- Ask which senior person stays with you from kickoff through construction. Design firms bring out their stars for the pitch. Confirm that the same person is accountable for delivery—and get the org chart in writing.
- Ask for references from that specific office, not from the firm’s global client list. Speak to someone whose project was done by the same studio, and ask: “What did the firm’s internal process add to your project? What did it take away?”
- Ask what they would not take on. If a firm claims everything is a great fit, you’re talking to a salesperson. A team that knows its limits is safer than one that says yes to anything.
I use these checks before committing our own staffing. The last question—the one about limits—has saved me the most money. A few years ago, driven by the need to win at all costs, I would have papered over this. Now, if the right team doesn’t exist, I’d rather say so early. It protects the client’s schedule and our reputation.
When does a firm like Gensler actually make sense?
If you hire a global firm, hire it for problems that benefit from being global: complex programs, multiple sites or countries, interdisciplinary planning, projects that need deep research benchmarks, or work with enough uncertainty that a large firm’s ability to absorb change matters.
If your project’s success depends on intimate local context and a person deeply embedded in a specific building department, the right answer might be ten people who live there. I don’t say this to turn work away. I say it because I’ve been on the receiving end of “we chose them because they were big and safe,” and I now know that “big and safe” isn’t a delivery plan.
So, yes, continue to look up the Gensler company profile and compare Gensler’s size with other firms. Let the profile get you to the table. But choose the team, not the logo. The logo won’t be in the room when the riser capacity comes back short and someone has to tell the lender.
My experience here comes from global projects and conversion work on the client side. I can’t speak to how this applies to a deeply local cultural project—if that’s what you’re doing, find local references, not a global profile. If your project spans markets and needs firepower, then large-firm scale helps. The trick is knowing which problem you are actually solving. That, I’ve learned the expensive way.
