Current-state process map
PDF + editable sourceHow work moves through your business today, with every handoff and every break marked.
Contents
- Lead to payment flow
- Handoff points
- Where records are re-typed
- Average wait at each stage
CRM consulting
Before anyone writes code, somebody has to map the mess
A paid discovery engagement that ends in a document, not a proposal. We interview your team, follow one lead from first touch to final payment, and write down exactly where it breaks.
Fixed fee · 5–8 working days · The document is yours to keep
Where your data lives on day one
WhatsApp groups
Three of them. Where leads actually arrive.
Leads_final_v7.xlsx
Owned by whoever opened it last.
Visitor register
Front desk. Carbon copy.
The old CRM
Nobody has logged in since March.
Hover to straighten. That is roughly the job.
Who we talk to
The person buying the CRM is rarely the person who has to use it
We interview every role that will touch the system. These are the questions we open with, and what each one tells us.
Founder / MD
“Which number do you check first thing in the morning?”
Tells us what the system has to surface above everything else.
Sales head
“Where do deals stall, and how long before you find out?”
Every delay here is a stage the CRM needs to make visible.
Field executive
“What do you enter twice because two systems need it?”
Duplicate entry is the fastest way to lose adoption.
Accounts
“What are you chasing people for at the end of every month?”
Usually a document or an approval that should be automatic.
Support
“What does a customer ask that you cannot answer quickly?”
Shows which records need to be joined together.
Ops / admin
“Which report do you rebuild by hand every week?”
That report becomes a scheduled job on day one.
Five to eight working days, start to document
01
Day 1–2
Interviews
Sessions with every role that will touch the system, on their desk, not in a boardroom.
02
Day 3
Trace one lead
We follow a single real enquiry end to end and note every place it is re-typed or waits.
03
Day 4
Data audit
What you hold today, how much is duplicated, and how much can survive a migration.
04
Day 5–6
Process map
Current state drawn out with the breaks marked, then reviewed with your team line by line.
05
Day 7–8
Recommendation
What to build, in what order, what to skip — and an honest build-or-buy call.
What you walk away with
Four documents, and not one of them is a sales deck
This is the entire output of the engagement. No slides, no vision statement — things you could hand to an engineer tomorrow.
Data audit
Spreadsheet + summaryEverything you hold today, scored on whether it can survive a migration intact.
Contents
- Sources and record counts
- Duplicate estimate
- Fields worth keeping
- What cannot be recovered
Scope recommendation
DocumentThe modules worth building, in the order that pays back fastest — and the ones to leave out.
Contents
- Phase one module list
- What to defer
- Integration requirements
- Role and permission matrix
Fixed-cost estimate
DocumentOne number for the build, with a written build-or-buy call — including when buying wins.
Contents
- Cost by phase
- Timeline with milestones
- Build vs buy comparison
- Ongoing running cost
The document is yours. Take it to another vendor if you want to.
Discovery is a separate engagement with its own fee, which means we are not writing it to justify a build. If the map says a ready-made product will serve you, it says that. If it says the work is worth doing but not with us, you have everything you need to brief someone else — the process map, the data audit and the scope, in a form any competent team can quote against.
How we price discovery
Start with the map, not the quote
Book a short call and we will tell you whether a full discovery engagement is worth it for your size and stage — or whether you can skip straight to scoping.
- Fixed fee, agreed before we start
- Five to eight working days
- Every document is yours to keep
- Fee credited against the build