What Does a Software Consultant Do?

“What does a software consultant do?” is the search people type when they know they need help, but they don't want another developer who only asks “what should I build next?”

Short answer: a software consultant translates a business problem into a technical path — and is willing to tell you not to take that path yet.

Longer answer below. This is how I actually work at Rewod, not a textbook definition.

The Job, Without the Fog

In a typical engagement I am answering five questions:

1. What problem is this software supposed to remove?
2. Who is the first real user — not “everyone”?
3. What must version one do, and what must it refuse to do?
4. How should the system be structured so it can grow without a rewrite?
5. Should we write code now, later, or not at all?

If those answers are already obvious to your team, you may not need me. If they are not, hiring developers will not make them obvious. That is when to hire a software consultant.

What the Work Looks Like

What You Walk Away With

You should be able to hand the output to another engineer and they can start without calling you every hour. That usually means:

• A scoped MVP (and a list of what is out).
• A simple architecture diagram and stack recommendation with reasons.
• Risks: where this product will break if you get sloppy.
• A recommended next hire or next build step.

That package is the product of software consulting. Development is optional after that.

What a Software Consultant Does Not Do (Unless You Hire Them To)

• Sit in your Slack all year as an extra pair of hands with no decisions.
• Pretend a 40-feature wishlist is an MVP. See founders build too much.
• Choose microservices because it sounds senior.
• Take equity by default. I don't. You keep the company.

If you want the thing built after the blueprint, that is a technical partnership. Same person is possible. Different contract. Different expectation.

How to Hire One Without Getting Theatre

Ask these on the first call:

• What would you refuse to build for me right now — and why?
• What does “done” look like for consulting, before any code?
• Will you still be here if we need the product shipped, or is this advice-only?
• How do you explain architecture to a non-technical founder?

If they jump to a tech stack in the first five minutes, they are selling implementation. If they jump to your customer and your workflow, they are consulting.

Compare options in consultant vs agency vs freelancer if you are still mixing the three.

I consult from Port Harcourt with founders and companies in the US, UK, Canada, and Nigeria. If the first call shows you don't need me, I'll say that. If you need a blueprint, that's the work.