You don't need a full team. You need the right two people and the right tools.

There is a comforting belief that building serious software requires a serious number of people. A project manager, a designer, a few developers, a tester, someone to run it all. It looks impressive on a slide, and it feels safe, because surely more people means more gets done.

For most business software, it does not. Small and senior quietly beats big and busy, and it is worth understanding why, because it changes what you should be paying for.

The maths nobody likes

Here is the uncomfortable arithmetic. When you add people to a team, you do not just add their work, you add everyone's need to stay in sync with them. Two people need to keep one conversation aligned. Ten people need to keep dozens aligned, and that alignment is real, expensive work that produces nothing a customer will ever see.

Past a certain point, adding people slows a project down. The team spends more of its day in meetings about the work than doing the work. You have bought more hands and less progress, which is a strange thing to pay for.

Why senior changes everything

An experienced builder is not simply a faster version of a junior one. They are a different thing, because most of the value is in the decisions, not the typing. They know which path is a dead end before walking down it. They recognise the trap that a less experienced person only discovers by falling into it. They ask the awkward question early, when it is cheap, instead of late, when it is a crisis.

Put two of those people together, give them modern tools, and they get more done, and done better, than a large team where the senior time is spread thin over a lot of people learning on your budget.

Where the tools come in

This is the part that has genuinely changed. Modern tools, AI among them, take the repetitive work that used to justify a big team and shrink it. The mechanical typing that once needed several pairs of hands now needs far fewer. So the case for a large team, which was always partly about sheer volume of routine work, has largely dissolved.

What is left is the part that never scaled well anyway: judgement. And judgement does not come from more people, it comes from better ones.

What this means for you

The practical takeaway is not that teams are bad. It is that you should be suspicious of size for its own sake. A big team is not proof of seriousness, it is sometimes just proof of overhead, and you are the one paying for it.

For most things a growing business needs to build, the right shape is small, senior and well equipped: a couple of people who genuinely know what they are doing, talking constantly, using tools that remove the drudgery. Fewer hands, more thought, and a great deal less of your money spent on people keeping each other in the loop.

Do not ask how many people are on it. Ask how good they are, and whether they have what they need. That is the question that actually predicts the result.