The hard questions, answered plainly.

A defined engagement with fixed deliverables: a Diagnostic, a Design, an Install, or ongoing Operate & Improve support. Each is scoped and quoted separately, so you commit one stage at a time.

We interview leadership and key staff, watch how important work actually happens, review your tools and reports, and score all 30 cells of the Operating Grid. You receive a report, a scorecard, current-state maps of priority processes and a prioritised roadmap.

Yes, where the Diagnostic shows they are needed. Process maps and the RACI come from Design. SOPs, policies, templates, dashboards and training come from Install. We don't produce documents for the sake of it; each one must be used in daily work.

Yes, in Install. We buy mature products first, integrate systems that must connect, and build only where a real gap remains. We are not tied to any software vendor.

A Diagnostic typically takes 2–4 weeks, Design 3–6 weeks and Install 6–16 weeks depending on scope. We confirm timelines in each proposal.

Each stage is a fixed fee quoted after the Grid Session, based on the size of the business and the scope agreed. The Grid Session itself carries no charge.

A named sponsor, access to people and records, timely decisions and staff time for workshops and training. Change needs leadership involvement; we can't install it around you.

You keep the Client Operating Manual, the SOP library, configured systems, dashboards and a management rhythm your team already runs. Operate & Improve is available but optional.

The Operating Grid is scored before and after. You also agree the KPIs that matter in Design, and those are tracked on the dashboards we install.

Then you have a tool. The question is whether the business around it is designed: owners, rules, approvals and reviews. Most ERP frustration comes from processes that were never defined, not from the software.

Your accountant handles the Money function well. The Grid covers five others, and the processes that feed finance start in Market, Customer and Delivery.

They probably do, today. The test is whether a new hire, a second branch or your absence for a month changes that. If knowledge lives in people, it leaves with them.

Below about ten people, informal works. From there, complexity grows faster than headcount. The Grid Session will tell you honestly if it's too early.

Start with the Grid Session, then a Diagnostic, which is fixed-fee and tells you what the problems cost before you commit to more.

If your processes are already clear, an implementer is the right choice. If not, the software will copy the confusion. The Diagnostic shows which situation you are in.

You need what documentation does: work done the same way by different people. We keep documents short and only write the ones people will use.

Then the Grid Session will confirm it quickly. The usual sign is whether it works without you.

Your offer is unique. How you win customers, deliver, collect cash and make decisions follows patterns the Grid is designed to map.

Automation copies whatever process it is given. We design the process first, then automate the parts that are stable.

Because software without owners, rules and reviews gets bought and then abandoned. We install the software as part of the system, not instead of it.

So that you only pay to fix what matters, in the right order, and have a baseline to measure against.

The Diagnostic estimates where time, cash and control are being lost, and the scorecard gives a before-and-after measure. We won't promise returns we can't evidence.