Digital Transformation Consulting
You already know something is not working. Maybe the same task gets redone every month, maybe getting one number takes three days, maybe competitors have started using things you have not. But asked what to fix first, you cannot say — not because you do not understand your business, but because from the inside, the step that costs the most time is usually the one you are most used to.
We review how your business actually runs, find where the real bottleneck is, and hand you a staged roadmap with a clear order of priority — including what we think you should not do yet.
The cost of not knowing is not stagnation — it is spending in the wrong place. Two versions are common. One: software gets bought and nobody uses it, because it solved something other than the real bottleneck. Two: the decision keeps getting deferred until it cannot be, by which point there are fewer options and they cost more. Neither is caused by a lack of budget. Both are caused by having no basis on which to put things in order.
The root cause is that problems and symptoms get treated as the same thing. “Orders keep going wrong” is a symptom; the problem underneath might be that one record is typed in three places. Buy solutions for symptoms and you accumulate tools that do not talk to each other. Buy solutions for problems and you get a path you can keep walking. Telling them apart does not take more technical knowledge — it takes someone walking the process from the outside.
How the work runs
Walk the process
From an enquiry arriving to the money landing: every handover, every re-entry, every wait for someone to reply gets written down. We do not ask what system you want. We ask how it works today.
Find the real bottleneck
The bottleneck is rarely where the complaints are. It is usually somewhere nobody complains about, because it has always been that way. We name which step genuinely limits growth and which is merely annoying.
Neutral technology options
Off-the-shelf, custom build, or change the process and touch no technology at all. The cost, the ceiling and the future price of each, laid side by side — including “off-the-shelf covers this”, which is an answer that earns us nothing.
A staged roadmap
A document with an order in it: what comes first, why that, what you will be able to verify once it is done, and what to leave alone for now. You can take it to any developer. It does not have to be us.
What changes for the business
- A process map you can read
- How your business runs today, drawn once. Clients often say this alone was worth it, because it is the first time the team sees the whole shape.
- A priority order, not a wish list
- Not a list of things that could be done, but an order — this first, because the rest depends on it.
- What not to do yet, in writing
- The roadmap has a section for what is not worth doing now, and what would have to be true before it is.
- A scope you can take to other quotes
- Specific enough that another developer can quote against it and you can compare like with like. We do not win work by being the only one who understands the scope.
What's included
- Business Process Review
- Transformation Discovery Session
- Website & Systems AuditA concrete list of things to fix, not a report
- Technology ConsultationNeutral advice, including advising you not to buy something
Ongoing
Ongoing: periodic roadmap reviews, re-prioritised as the business changes.
This one is quoted individually
Website packages publish a floor because their scope is bounded. This does not, because the range is too wide for a figure to mean anything — a number in the middle deters the small project and over-promises on the large one. A free diagnostic settles the scope first, and the quotation follows from it.
See the published package prices, and why this is not one of themWhen this isn't the right thing yet
Not yet: committing to a large system. Encoding a process into software before it is standardised means writing the confusion into the code.
Common questions
- Do I have to hire you after the diagnostic?
- No. The roadmap is written to be specific enough to take elsewhere — that is the point of it. Some people think that is a strange way to run a business. A plan only we can interpret would be a risk to you, not a value.
- We are small. Is a diagnostic worth it?
- If the problem is “not enough customers”, a diagnostic is not the right spend and we will say so. If the problem is “things started going wrong once orders grew”, being small is an advantage: the process is still cheap to change.
- How much of our time does it take?
- A few conversations, plus a look at the spreadsheets and systems you actually use. The time-consuming part is our analysis, not your preparation. A diagnostic that requires your team to prepare extensively is a consultant outsourcing the work to the client.
- How is this different from the free diagnostic?
- The free diagnostic on this site is six questions and three minutes, and it tells you roughly which stage you are at. This is walking your actual process, looking at your actual data, and producing a roadmap someone can execute. The first helps you decide whether to talk. This is the work.