Work waits at handoffs between people or teams
Services / Business Analysis & Process Improvement
Understand the problem before you change it.
We find out how the work really flows, where it gets stuck and why, then design practical improvements with the people who do the work. The result is a set of deliverables you own, whatever you decide to do next.
Paid engagement · quoted after an initial discussion. The snapshot and the initial discussion are free.
The problem
When work gets harder than it should be.
Most operational friction doesn’t come from one broken tool. It builds up across people, steps and systems:
The same information is captured more than once
Systems don't share information, so people bridge the gap by hand
Nobody can easily see the status of work or the numbers
Similar cases are decided differently depending on who handles them
It is unclear who owns a step, or who can approve a change
Buying software before understanding the cause often moves the problem rather than solving it.
What we do
Established business analysis practice, applied to your operation.
Our approach draws on widely used business analysis practice, as described in guides such as BABOK: stakeholder engagement, elicitation, requirements analysis and solution evaluation.
Stakeholder interviews and workshops
We speak with the people who do, manage and depend on the work, so the picture isn't one person's view.
Current-state (as-is) process mapping
We map how the work actually flows today, including handoffs, exceptions and workarounds, using BPMN-style notation where it helps.
Requirements elicitation and validation
We draw out what a better process must do, and check those requirements with the people who will rely on them.
Root-cause and opportunity assessment
We look for the causes behind the symptoms, and size the opportunities against the evidence available.
Future-state (to-be) recommendations
We design how the work could flow, with clear ownership, controls and points where people stay in charge.
Solution options and prioritisation
We compare process, training, conventional software, integration and AI options, including doing less, and prioritise them.
Indicative implementation roadmap
We set out a sensible sequence of changes, dependencies and decisions, so you can act on the findings.
How an engagement works
Scoped in writing, validated with your people.
Agree the scope
We agree the problem, the questions to answer, the people to involve, the deliverables, assumptions, exclusions and fee in a written proposal before work or payment starts.
Stakeholder discovery
Interviews and workshops with the people involved, at a pace that fits their work.
Evidence gathering
Walk-throughs of real examples, documents, system screens and any figures you already hold.
Validation
We play back what we found to the people involved and correct it before drawing conclusions.
Prioritised recommendations
Options, trade-offs, risks and dependencies, with a recommended sequence.
Documentation and handover
Deliverables in formats your team can use, reviewed with you and formally accepted.
What you receive
Tangible deliverables, scaled to the engagement.
An engagement might include some or all of the following. We agree which are useful at the start, so a small engagement isn’t padded with paperwork.
- Stakeholder and process inventory
- Validated current-state (as-is) process maps
- Issues and evidence register
- Business requirements
- Future-state (to-be) process design
- Prioritised improvement opportunities
- Solution options, with trade-offs
- Risks, dependencies and assumptions
- Success measures to track after any change
- Indicative implementation roadmap
Reported, hypothesised, verified.
Every finding is labelled for what it is: something a person reported, a hypothesis still to be tested, or a finding verified against evidence or validated with the people involved. You can see how confident to be in each conclusion.
Yours to keep.
The paid engagement stands on its own. You keep and can use the agreed deliverables even if you choose another implementer, or decide not to implement anything.
Next step
Two ways to start.
Start with the free snapshot
Describe one operational problem in a few minutes and get a preliminary view on screen, including whether business analysis looks worthwhile. No email needed to see it.
Get your free snapshotAlready have a clear brief?
If you know the area you want analysed, ask for an initial discussion. It is free, and if an engagement makes sense you receive a written proposal to accept or decline.
Request a discovery discussionOr WhatsApp Justin →Questions
Frequently asked
Does every project need business analysis?
No. When a need is clear and bounded, such as connecting two systems with well-understood inputs and outputs, we can scope it directly on a free technical scoping call. Training enquiries never need it. Business analysis is for problems that are unclear, span several teams or systems, or carry real operational risk.
Will you always recommend AI or a build?
No. Recommendations follow the evidence. The outcome may be a process change, clearer ownership, training, conventional software, an integration, an AI system, or a decision to leave things as they are. A discovery engagement does not commit you to anything further.
How is an engagement scoped and priced?
It is a paid engagement, quoted by scoped proposal. After an initial discussion, which is free, we write a proposal that sets out the scope, the people and processes involved, the deliverables, assumptions, dependencies, exclusions, timing and fee. Nothing is chargeable until you accept it in writing. The size of an engagement depends on the problem, so there is no standard package or published rate.
What do we receive, and do we own it?
You receive the deliverables agreed in the proposal, reviewed with your stakeholders and provided in usable formats. They are yours to keep and use, including with another implementer if you prefer. Not every engagement needs every artifact or a particular formal notation; we agree what is useful up front.
How do you treat what people tell you?
We keep reported observations and hypotheses separate from findings we have verified with evidence or validated with the people involved, and we label which is which in the deliverables.
Is the free snapshot the same thing?
No. The Business Opportunity Snapshot is a short, self-service, preliminary view based only on what you report. It is a useful starting point, not a business analysis.
See how discovery fits with builds and training on our pricing page.
Have a process that isn't working?
Start with a free Business Opportunity Snapshot. It takes a few minutes and suggests a proportionate next step.
Get your free Business Opportunity Snapshot