We come to your place, and watch the work
Before we design anything, we spend time where the work happens. On the floor, at the counter, in the yard, beside the person doing the job. Most software fails because nobody did this.
- Businesses who know something is slow but not exactly what
- Companies about to spend heavily on software and wanting a second opinion first
- Operations where the real process differs from the documented one, which is most
- Leadership teams who cannot get a straight answer about what to build first
What you get
Process observation
We follow real work end to end and record every handoff, wait, re-key and workaround. The workarounds are the most valuable thing we find.
Conversations at every level
The person entering the data usually knows exactly what is wrong. They are rarely in the requirements meeting, so we go to them.
Quantify the pain
Time per transaction, error and rework rates, and the cost of delay, so priorities are argued with numbers instead of seniority.
Systems and data audit
What exists, what talks to what, where the spreadsheets bridge the gaps, and what condition the data is really in.
Options with trade-offs
Usually three: minimum intervention, the sensible middle, and the full build. Each costed, with what you give up in each.
A plan you own
A written report and roadmap that is yours to keep, take to your board, or hand to another supplier.
The engagement, step by step
6 stages. Something usable at the end of each one.
- Stage 01
Scoping call
Free. We work out whether a visit is warranted, which sites and which processes, and who we need access to.
- Stage 02
On-site week
One to five days depending on scale. Observation, shadowing, interviews, and photographs of the actual forms and screens in use.
- Stage 03
Analysis
Process maps, a quantified pain list, a systems and data assessment, and a gap analysis against off-the-shelf options.
- Stage 04
Options workshop
We present three costed routes and argue them with your team, including the option of building nothing.
- Stage 05
Report and roadmap
A written deliverable with phasing, dependencies, risks and indicative costs, in language your finance team can read.
- Stage 06
Decide
Build with us, build with someone else, or fix the process without software. All three are legitimate outcomes.
What lands in your hands
- 01Current-state process maps
- 02Quantified pain and opportunity list
- 03Systems inventory and integration map
- 04Data quality assessment
- 05Three costed options with trade-offs
- 06Phased roadmap with dependencies and risks
- 07Indicative budget and timeline
- 08Everything delivered as editable files you keep
Tools we reach for
On-site Discovery: common questions
Let's find out whether we are the right fit.
A first call is with an engineer, not a salesperson. Bring the problem; we will tell you honestly what we think.