Business analysis and improvement

Find where the process breaks down before choosing new software.

We review the process with the people doing it, examine examples of delays or rework, and identify what needs to change. You receive findings, requirements, and a recommendation your team can use to decide what to do first.

Discuss an assessment

Sample assessment · Fictional records

From a finding to a testable requirement

F1
FINDING

7 of 12 requests arrived without an owner.

R1
REQUIREMENT

Assign matching requests automatically, using agreed routing rules.

ACCEPTANCE CHECK

An unmatched request stays in review and cannot move to estimating until an owner is assigned.

The check gives the team a specific behavior to verify before accepting a system.

Inspect the evidence and requirement

When to bring us in

When the problem is familiar but the answer is not

  • Everyone sees the friction, but disagrees about its cause.
  • You are choosing software before the requirements are clear.
  • There are too many improvement ideas and no agreed sequence.

Services

Investigate the problem and define the project

Process assessment

Follow the work as it happens, including the exceptions.

  • Interviews and walkthroughs
  • Inputs, handoffs, owners, and delays
  • A current-process map and issue register

Problem and root-cause analysis

Separate the visible symptom from the conditions creating it.

  • Review of representative examples
  • Competing explanations and evidence gaps
  • A focused statement of the problem to solve

Requirements and acceptance criteria

Define what a useful solution must do and how it will be checked.

  • User needs and business rules
  • Data, access, and integration requirements
  • Scope boundaries and acceptance examples

Software and option evaluation

Compare options against the needs of the business.

  • Existing-tool improvements versus replacement
  • Requirements-based evaluation criteria
  • Licensing, implementation, and support considerations

Prioritization and roadmaps

Sequence work around dependencies, effort, and expected value.

  • A prioritized improvement backlog
  • Assumptions behind effort and benefit estimates
  • Phased delivery and decision points

Implementation coordination

Track dependencies, review deliveries, and help the team accept the completed changes.

  • Workstream and dependency tracking
  • Review and acceptance coordination
  • Handover responsibilities and adoption planning

Example engagement

Find out why requests take too long to turn into quotes.

For a team considering new software because quote requests wait in shared inboxes and spreadsheets.

How we check the result

  • The people doing the work recognize the process and its exceptions.
  • Recommendations can be traced to observed problems.
  • The next decision, owner, and information needed are explicit.

Illustrative engagement. Your proposal defines the deliverables and exclusions.

Sample demonstration

Follow a delayed quote from evidence to requirements

Questions

Commissioning an assessment

Can we commission the assessment on its own?

Yes. The output can be a review, requirements document, recommendation, or roadmap that your team or another provider implements.

Do you need to know our industry already?

We start by understanding the process and its constraints with your team. Where decisions require specialist industry, legal, or regulatory expertise, that expertise needs to be part of the project.

Can you help evaluate competing software options?

Yes. We agree the requirements and evaluation criteria first, then compare the relevant options and identify what needs to be demonstrated or verified.

Will you recommend a build every time?

No. A change in ownership, a clearer rule, a better template, or configuration of an existing tool may address the problem.

Related services

Other help you may need

Which delay or recurring problem needs a closer look?

Tell us who it affects, what you have tried, and whether you are considering a change of software.

Discuss an assessment