- Home
- Trail Map
The paid assessment
Find the workflow that is costing more than it should.
A Trail Map is a paid diagnostic. ProcessScout examines how the work actually moves through your business, sizes the friction and documents what should change. You get a written deliverable you can act on, whether or not you ever buy BetterWrk software.
- Paid engagement
- Written deliverable
- Yours to keep
The problem a Trail Map addresses
Somewhere in your operation, a workflow is quietly expensive.
Someone re-types the same information into two systems. An approval waits three days for a person who would have said yes in ten seconds. A spreadsheet holds a process that four departments depend on. Month end takes a week because the data has to be reassembled before it can be trusted.
Everyone can name the symptom. Almost nobody can put a number on it, which is why it never gets fixed.
What it examines
The work, not the org chart.
We follow a small number of real end-to-end workflows through whatever systems they currently touch — including the ones nobody calls a system.
The path of a record
Where a customer, employee, agreement or invoice is created, copied, re-typed and reconciled between the moment it appears and the moment it is finished with.
The handoffs
Every point where work moves between people, teams or systems. This is where almost all operational cost hides.
The exceptions
What happens when the case is not standard. Most software is judged on the happy path; most businesses live in the exceptions.
The approvals
Who has to say yes, how long they take, and whether the control is genuinely reducing risk or just adding delay.
The spreadsheets
The ones that became load-bearing. What they hold, who maintains them and what breaks when that person is on leave.
The software you have
What each system is actually used for, what you are paying for and not using, and where two products are doing the same job badly.
Evidence
Findings you can check, not opinions you have to trust.
Every statement in a Trail Map is tied to something we observed. If you disagree with a finding, you can open the evidence behind it and argue with the evidence.
This is the difference between a consultant’s report and a diagnostic. One is an informed opinion. The other is a record.
- Screen recordings of the work being done, by the people who do it.
- Documents and artefacts — the templates, spreadsheets and forms the process actually runs on.
- Connected systems, where you grant access, for the events that show timing and volume.
- Interviews with the people who know where the bodies are buried.
- Operational snapshots of volumes, cycle times and exception rates.
On the recordings
Recordings are of work, scoped to the workflow being examined, with the participants' knowledge. Sensitive fields are masked. This is a diagnostic, not a monitoring exercise.
What you receive
A written picture of the work, and what to do about it.
01
The workflow as it actually runs
Documented end to end, including the steps that are not in anyone’s process documentation because they were invented to work around something.
02
Where it breaks, and what that costs
Each point of friction, with the evidence behind it and an estimate of what it is costing in time, delay, rework or cash.
03
What should change, in priority order
Separated honestly into what is a process problem, what is a training problem, what is a configuration problem and what genuinely needs different software.
04
What the right environment looks like
If software is part of the answer, which parts of BetterWrk would earn their place first, what they would replace and what they would integrate with.
If the answer is “do not buy our software”
That is a legitimate outcome and we will write it down. A Trail Map that tells you to fix a process and keep your existing systems has still paid for itself.
Practicalities
Who takes part, how long it takes.
- Duration
- Typically two weeks from access being granted to the deliverable being presented.
- Price
- A fixed price, shown and paid at checkout before any work starts. No proposal cycle, no day-rate estimate that grows.
- Executive sponsor
- One person who can decide the scope and act on the findings. Usually the COO, Operations Director or Finance Director.
- Process owners
- The two or three people who genuinely know how the chosen workflow runs, including the workarounds.
- The people doing the work
- A handful of users, for recordings and short contextual questions. Their time commitment is small and their input is the most valuable part.
- IT contact
- Someone who can grant read access to the relevant systems, where you choose to include them.
- Credit
- Where a Trail Map leads to a launch, its value is credited against the launch scope. Ask before you buy if this matters to your approval process.
Questions
Before you buy.
No. It is a paid engagement with a defined deliverable, and you keep the deliverable regardless of what you decide afterwards. We charge for it precisely so that it does not have to be a sales call.
Most leaders can name the symptom. Far fewer can put a defensible number on it, or separate the process problem from the software problem. If we confirm what you already believed, you now have the evidence to fund fixing it.
Deliberately light. We observe the work rather than pulling people into workshops. Expect a scoping session, short interviews, some recorded work and one presentation of the findings.
This is worth taking seriously, and how you introduce it matters. The scope is a workflow, not a person; recordings are made with the participants' knowledge; sensitive fields are masked; and the output is about process design. We will help you brief the team honestly.
Then do not. A Trail Map is scoped as a diagnostic, not a procurement step. Plenty of its findings are process and configuration changes you can make in the software you already own.
Start where the evidence is.
Two weeks, a fixed price and a written picture of the workflow that is costing more than it should.