Who Is Actually Building Your Software?
2026-07-21Here is a question almost nobody asks during a pitch, and it is the one I would ask first.
The people sitting across from me right now, are they the people who will actually build this?
Watch what happens when you ask it. You will get a lot of words about the team, the process, the bench. What you will rarely get is a simple yes, because in most of this industry the honest answer is no. You met the closers. You will be working with somebody else.
This is not a scandal. It is the standard operating model of professional services, and it has a name. The pyramid.
Here is how it works. A firm keeps a small number of expensive senior people at the top and a wide base of junior people underneath. The seniors win the work and oversee it. The juniors do most of the actual production. And the ratio between those layers is not an accident of who happened to be available. It is a dial. Inside these firms, the tiers of the pyramid are deliberately scrutinized and adjusted to extract more margin from the client, and the adjustments are often explained as upskilling the team when the reality is closer to the opposite (https://www.linkedin.com/pulse/avoiding-staffing-pyramids-large-firms-david-mackay).
Read that again. There is a lever in the room, and pulling it makes them more money and makes your team less experienced.
Now, I want to be careful here, because I have real affection for junior developers. Everyone was one. I was terrible at plenty of things once, and somebody let me learn. That is not the objection.
The objection is who is paying for the education.
In the pyramid, the classroom is your project. And the cost lands on you twice. First in the work itself, since concentrating production in the hands of people with one to three years of experience rather than seven to ten fundamentally changes the nature of what comes out, and creates quality risk that has to be caught later by rushed oversight instead of being built in from the start (https://northpathstrategies.org/2025/07/17/why-diamond-shaped-teams-outperform-the-old-pyramid-the-future-of-management-consulting/). And second in the seniors you thought you were buying, because those senior people end up spending significant time bringing juniors up to the point of being productive, which pulls them away from the actual job they were staffed to do (https://www.linkedin.com/pulse/avoiding-staffing-pyramids-large-firms-david-mackay).
So you pay for expertise and you receive supervision of inexperience. Those are not the same product.
This is exactly why our bench at Cause of a Kind is senior, in house, and onshore, with no pyramid underneath it. The people you meet are the people who build. Nobody is learning your business on your budget. When you describe a problem, the person hearing it has already seen four versions of it and can tell you which one you actually have. That is not a staffing preference. It is the entire product.
I will be honest about the tradeoff, because there is a real one.
We cannot be the cheapest, and we cannot scale by simply adding bodies. A pyramid can absorb a huge project next week by hiring a layer of juniors. We cannot. Our growth is limited by how fast we can find people we would actually put in front of you, which is slow, and occasionally frustrating, and it means we say no more often than a bigger shop would. We accepted that ceiling on purpose, because the alternative is quietly diluting the only thing we sell.
Here is the wisdom, and it goes far past software.
When you buy expertise, find out where it physically sits. Not in the logo, not in the case studies, not in the two impressive people who showed up to win you over. Ask who will be in the room on a random Wednesday in month four, when the interesting part is over and the hard part has started. Every professional services relationship eventually gets decided by that person, and most buyers never once ask their name.
The question is not whether the firm has great people. Almost all of them do. The question is whether their model puts those great people anywhere near your work.
If you have ever felt that strange drift on a project, where the energy and insight of the early conversations somehow never showed up in the delivery, you were not imagining it.
You did not get a different project.
You got a different tier.
