Free first call
A 30-45 minute conversation about what you do and where you are stuck. I give you my first read and an honest answer on whether going further is worth it. No fee, no commitment.
Consulting · Service
Business process analysis and digitisation consulting
Most companies start from the wrong question: “what software do we need?” The right one is: which work actually eats time, what would digitising it return, and which parts should stay exactly as they are? I map your processes with you and show, in numbers, what is worth automating — even when the answer is “build nothing”.
- Category
- Consulting
- Typical timeline
- 1-2 weeks
- How I work
- Design + development from one person
What you get
What do you have
when this is done?
The list below isn't a marketing promise, it's the delivery list. It goes in the contract too.
- 01
A written figure for how many hours each task costs per month and what digitising it would return
- 02
A roadmap ordered by cost and benefit, so you know which process to tackle first
- 03
An explicit list of the work you should not pay to automate
- 04
A scoped requirements document you can use when collecting quotes
Scope
How the process
moves, step by step.
At every step I share plainly what has been completed and what comes next.
Process inventory
We map what actually fills your team's day, step by step: what passes from whom to whom, where each piece of data lives, which step is still done by hand. Built from talking to the people doing the work, not from assumption.
Cost and return calculation
For every repeating task I work out the monthly hours and what those hours cost you. That is where the payback period for automation comes from — and where I write it down when there isn't one.
Tooling decision
Not every problem needs custom software. If an off-the-shelf SaaS, a restructured spreadsheet or a connector like Zapier or Make covers it, I say so — at the cost of my own billable work. Custom development is only recommended where it is genuinely required.
Roadmap and report
Findings become a prioritised roadmap: what comes first, the estimated budget and duration band, and who owns each step. The report is yours and stays useful even if you continue with a different supplier.
Deliverables
Everything handed
over to you.
On a one-off project, the source code, design files and accounts are yours once it's complete, and you're under no obligation to keep working with me. If you continue with a monthly arrangement, the working copy stays with me so the code stays current, and you receive it in its latest state when the arrangement ends.
- A written and diagrammed map of current processes
- Monthly hour and cost table for repeating work
- Automation candidates ranked by payback period
- A reasoned list of what should not be digitised
- Prioritised roadmap: step, estimated budget band, estimated duration
- A scope document you can send out for quotes
- A 60-minute closing session where the report is walked through
Frequently asked
The questions
on your mind.
I moved the most common proposal-stage questions here; neither of us enjoys email ping-pong.
Is the first call really free?
Yes. We talk for 30-45 minutes, you describe what you do and where it jams, and I give you my first read. No invoice, no obligation to continue. If my answer is “you don't need to spend money on this”, that is what you will hear.
Do I have to commission the development from you afterwards?
No, and that rule is deliberate. The report is handed to you and you can use it to collect quotes elsewhere. The analysis fee is not tied to development — which is precisely why the report is free to say “don't build this”.
My company is small. Is this overkill?
Usually the opposite. In companies of 5-50 people the repeating work sits in nobody's job description, stays invisible, and is exactly where the time goes. Large-enterprise transformation programmes are not what I do; my scale is small and mid-sized businesses.
Our processes aren't written down anywhere. Does that matter?
No — that is the normal starting point. Writing them down is the first step of the job. I build the map by talking to the people who actually do the work, because the process a manager describes and the process on the floor are rarely the same, and the gap is where the finding lives.
Could the conclusion be “do nothing”?
It could, and sometimes it is. Automating a task that takes two hours a month usually never pays for itself. Recommending it would cost you money and earn me a short-term project; I don't make that trade.
Why build custom software when off-the-shelf tools exist?
Most of the time you shouldn't. If a ready-made product covers your case I will recommend it and tell you which one. Custom development makes sense when your logic doesn't fit packaged products, when per-seat licensing overtakes the build cost, or when your data must not leave your control.
How long does it take, and how much of my team's time does it need?
The report typically lands in 1-2 weeks. From your side it needs roughly one hour each with 2-4 people who do the work, plus access to any existing records. It does not require pausing your operations.
Related services
You might also
be interested in.
Most projects aren't one service, but a combination of several.
Next step
Let's talk about your project.
Write down what you want to build and we'll settle the scope, a realistic budget and the next step together. The first call is free.