What a software consultant actually does
Beyond the slide deck: where technical consulting earns its money, and when you do not need it.
Short answer
A software consultant helps you make expensive technical decisions correctly (architecture, scaling, build-versus-buy, and technology choice) and leaves you with a prioritised, actionable plan. You hire a consultant when the cost of choosing wrong is higher than the cost of the advice; you hire a developer when you already know what to build.
The decisions worth paying for
Most technical decisions are reversible and cheap. A few are neither: the data model, the core architecture, whether to rewrite, which platform you build on, and what you choose to own versus buy. Those are where outside judgement pays for itself.
What a good engagement produces
- A clear read on what is working and what is genuinely risky.
- A prioritised list of changes, in the order that matters.
- The trade-offs stated plainly, including what you give up.
- Something your team can start on the same week.
Consultant, contractor, or fractional CTO?
A consultant answers a bounded question and leaves you with a plan. A contractor executes work you have already scoped. A fractional CTO provides ongoing technical leadership (architecture, hiring, and delivery oversight) without a full-time hire. Founders without a senior technical partner often need the third even when they ask for the first.
When you do not need one
If you already know what to build and have people who can build it, you need delivery capacity, not advice. Bringing in a consultant to validate a decision your team has already made well is usually an expensive way to buy confidence.
Common questions
How long does a software consulting engagement take?
- A focused architecture or scaling review is typically one to three weeks. Ongoing fractional technical leadership runs monthly. If someone proposes a long engagement before understanding your problem, treat it as a warning sign.
What is technical due diligence?
- An assessment of a codebase, architecture, and team, usually for an investor or acquirer, reporting real risks and strengths in plain language, including how much it would cost to fix what is broken.
Can a consultant also build the software?
- Sometimes, and it can be an advantage when advice and delivery stay connected. The risk is advice that conveniently recommends more work; a good partner is explicit about when you do not need them.