How We Work

Method is what makes advice repeatable. The three phases below are how every NextGen Services engagement runs, regardless of size — the difference between a two-week review and a year-long programme is depth, not discipline. Each phase has defined outputs, a fixed rhythm of communication, and a clear answer to the question every owner is entitled to ask: what am I getting for my money this month?

Phase 1 — Discover

Discovery is where we earn the right to advise. We sit with the people who do the work, watch the systems being used, and trace real examples end to end — a job, an order, a report — from trigger to completion. We collect the numbers that describe the current state: cycle times, error and rework rates, hours consumed, and the cost of the workarounds. Discovery typically runs one to three weeks and closes with a findings session in which we present the map, the measures and the problems, ranked by cost and risk. If the findings reveal that our services are not the right answer, we say so at this point.

• What you see: a current-state process map, a measured problem list, and an honest assessment of what is worth fixing first.
• What we need: access to your team, your systems, and a handful of real examples to trace.

Phase 2 — Design & Advise

Design turns findings into a plan you can execute with confidence. For each problem worth solving we define the target state, the options (including the "do nothing" option, costed), the recommended path, and the risks with their mitigations. Recommendations are presented with their trade-offs visible — cost, disruption, timing — because trade-offs are the owner's decision, not ours. The phase ends with a written proposal: scope, sequence, fees, and the measures by which the result will be judged.

• What you see: a target-state design, costed options with trade-offs, and a fixed-scope proposal with success measures agreed up front.
• What we need: your decisions — which options to pursue, in which order, and your appetite for change over the coming quarters.

Phase 3 — Deliver & Support

Delivery is disciplined, staged and measured. Work is sequenced so early stages build evidence and confidence for later ones; every change is piloted before full rollout; documentation is written as we go, not reconstructed at the end; and your team is trained before anything new goes live, not after complaints. A stabilisation period follows each significant change, during which we measure adoption and performance against the Phase 2 baseline. The engagement closes with a written handover pack — the artefacts, credentials register, runbooks and reporting rhythm your business needs to run without us.

• What you see: working changes, adopted by your team, with before-and-after measures and a complete handover pack.
• What we need: a nominated champion on your side, and protected time for the staff whose work changes.

Communication rhythm

Every engagement runs on a fixed communication cycle agreed at the start: typically a short written progress note each week or fortnight — what was done, what is next, what we need from you — and a scheduled call or meeting where decisions are made. Ad hoc questions are answered within one business day. You should never have to ask us for a status update; if you do, that is our failure, and we treat it as one.

A note on price and pace

We price engagements by phase, so you only commit to the next phase when the previous one has earned your confidence. Discovery is the smallest commitment and frequently pays for itself in clarity alone. There is no obligation to continue into Design or Delivery — though most clients do, because the plan is theirs, not ours.

The tools behind the method

Clients often ask what software we use, and the honest answer is: the least necessary. Our working kit is deliberately plain — office documents for maps and reports, shared boards for project tracking, your own systems for anything that touches your data. We avoid imposing proprietary platforms on engagements because the artefacts should outlive the tooling and remain editable by your team. Where an engagement justifies something more structured — a reporting pipeline, an integration build — the tooling is chosen in Phase 2 with the same rigour as any other recommendation, and it is documented in the handover pack like everything else. The method is the asset; the tools are just where it lives this year.

When priorities change mid-engagement

Businesses are living things, and priorities move — a big order lands, a key person leaves, a supplier fails. Our phases are designed to absorb that rather than resent it. Because work is priced and sequenced in stages, pausing at a stage boundary is clean: the findings and artefacts to date remain usable, and the plan can be revised without penalty. Mid-stage changes are handled through an explicit scope conversation — what moves out, what moves in, what it does to the timeline — agreed in writing before we proceed. What we never do is quietly drift: a project that ends up somewhere its proposal never mentioned is a failure of our discipline, and we would rather have the awkward conversation early than the apologetic one late.

Frequently asked questions