The five things to pin down first
1. Start and stop — What triggers the work, and what finished means for a customer, for finance, and for operations — not always the same. If finished is vague, the tool will be vague.
2. Handoffs with names — Who touches the same record next, in what system, and where it waits (inbox, queue, I will do it after lunch). A map with no owner is a wish list, not a spec. Tie this to clear ownership for system work before you are locked into a licence.
3. The system of record — One place that is truth for each fact you care about (customer, order, job, stock line). If two places both own the number, the new software will not fix it — you will re-key, sync badly, or fight in a spreadsheet. Our technical debt in ops article is the long-run bill when that is left unnamed.
4. Edge cases, not the demo — the top three Tuesdays that break the happy path: the credit, the return, the split job, the we always do a bit in WhatsApp step. The vendor will show a clean pipeline; you need a map that admits reality.
5. What good looks like in 90 days — not everything the brochure offers, but one or two measurable wins (time to respond, time to get paid, fewer re-keys). If you cannot name them, the procurement is a shopping trip, not a business case.
Book a free systems review and we can map a slice of the flow with you — it is a conversation, not a slide deck. Read our process page for how we like to work, and what we offer for a deeper process audit or build when the map says so. Teesside and the North East, and remote when the fit is right.
Happy path vs your real Tuesday
Demos are synthetic — a neat pipeline, a single currency, a user who never opens email mid-task. Your team lives in the exception queue: a partial ship, a pricing dispute, a customer who only speaks to Dave. If the map you sign off only covers the happy path, you will sign a spec that the go-live week will contradict.
Workshop rule: for each stage, add one sticky note: this is where it usually goes wrong — and another: where we work around the system today. If that second one is the same every time, the problem is often process and ownership first — see is custom software worth it? before you pay for a code-shaped bandage. For a quick build-or-buy pass, we also have twelve questions in an hour.
From map to a short RFP you can trust
A one-page process map and the five non-negotiables above are enough to shorten vendor sales cycles in your favour. You are not buying a category; you are buying a fit to these handoffs and this truth of data. A clear map means:
- You can demand a demo on your own edge case, not theirs — and walk away when the gap is fudged.
- You can list non-functional needs the room agrees on: integrations, who administers users, and exit (export, API, contract terms) before signature.
- You can separate must-have from phase two and stop phase two from becoming a surprise project team after go-live.
See what we offer for audits, builds, rescue when a previous buy went wrong, and ongoing system care once the right system is in flow. Book a systems review to draw the first slice of the map together.