Small team, senior work: how AI reshapes the org chart.
The traditional answer to more work is more people. That answer is now wrong more often than it is right.
The old shape of a software company was a pyramid. A few senior people made decisions, and a wide base of junior people turned those decisions into code. The pyramid existed because implementation was the expensive, slow part, and the only way to get more of it was to hire.
That constraint has genuinely moved. Which means the shape built around it should move too.
What changed
The work that used to justify a wide base — boilerplate, wiring, the fourth variation of a form — is the work AI is best at. What it is not good at is deciding what should be built, noticing that a requirement contradicts one agreed three weeks ago, or carrying responsibility for an outcome.
AI compressed the base of the pyramid. It did not touch the top.
So the useful org chart is no longer a pyramid. It is closer to a flat, cross-functional pod: a small number of people who can each hold a whole problem, with machine leverage underneath all of them.
How that works here
We run eight disciplines in-house — backend, frontend, mobile, DevOps, product analysis, operations, marketing, and HR — with a team far smaller than that list would traditionally require. That is only possible because of two things, and the second one matters more.
- Leverage: every person is amplified on the execution half of their job, so the ratio of judgement to typing goes up.
- Range: we hire people who are comfortable owning a problem end to end rather than a slice of it, because a small team cannot afford handoffs.
The honest trade-off
This model has a real cost, and it is worth naming. A pyramid trains juniors — that is what the base was for. A pod does not, automatically. If the whole industry flattens without thinking about it, we collectively stop producing the senior people the model depends on.
We do not have a complete answer to that. What we have is a deliberate one: we keep a generalist seat open for someone early in their career, working across real products rather than on a training track, close enough to the decisions to see how they get made. It is not a solution to the industry's problem. It is us not pretending the problem is not there.
What it means for a client
Mostly this: the person you talk to is the person doing the work. There is no layer between the conversation and the commit, and nothing gets lost translating between them. For a company our size that is not a marketing position — it is just what is structurally true, and it is the main reason to work with a team like this instead of a larger one.