Questions worth asking first.

Small and growing ones — where a single person often holds a critical process in their head, and where there is no internal team to hand a recommendation to.

Both, and that is the point. Most consulting stops at the recommendation and hands the hard part back. We write the software, wire up the integrations, and put it into production.

It depends on the work, which is why there is no rate card here. What we will do is give you a written scope — what we would do, in what order, and what it costs — before you commit to any of it. You will not get an open-ended bill.

A conversation about what is actually in the way. No deck, and no discovery phase that bills for three weeks before anything happens. If we are not the right people for the problem, we will tell you then rather than three months in.

Yes. It is documented and explained well enough that you can run it, change it, and hand it to someone else without calling us. An engagement that leaves you dependent on the consultant has not finished.

No. A lot of the work is making existing systems talk to each other, or filling the gap between what IT maintains and what the business actually needs. We would rather work alongside whoever is already there than replace them.

Then that is the answer, and it is a cheaper one than finding out later. Some problems are a process that needs changing, not software that needs writing.

Often, yes — an abandoned build, a system nobody understands any more, a process that broke when someone left. Tell us what state it is in and we will say honestly whether it is worth continuing or starting again.