Work out what is worth building first.

Finds where your operation loses time, money and certainty — then fixes the process before recommending any technology. Concretely: we watch how work actually moves (not how the org chart says it moves), map it end to end, locate the bottlenecks, duplicate entry, unclear ownership and dropped handoffs, score the fix candidates by effort against payback, and hand you a sequenced roadmap. Then — the part that separates us from report-writers — we implement the top items, whether that means a redesigned form, a clarified role, or targeted automation.

Order of operations. Automation executes a known fix: this workflow, made automatic. Consulting decides what should be fixed at all — because the most expensive mistake in operations is automating the wrong thing beautifully. Consulting engagements often end in automation, but they also legitimately end in a procedure change, a form, a role clarification, or the recommendation to change nothing yet. If you already know exactly which workflow hurts, skip straight to Process Automation; if you know something is wrong but not precisely what, this is the front door.

Small businesses often get the fastest payback, because one person’s lost hours are a visible fraction of everything. A five-person operation where quoting takes three touches and invoicing gets chased by the owner at 9pm has more recoverable capacity per head than most fifty-person firms. The engagement scales down honestly: a compact discovery, a shortlist of three fixes, implementation measured in days. What does not scale down is the discipline — small businesses deserve diagnosis before prescription too.

A representative list from real engagements: an intake form that captures complete information first time (killing the back-and-forth that consumed a day per job); an approval rule that let anyone qualified approve instead of one bottleneck inbox; a role clarification that ended two people each assuming the other chased invoices; a template that turned quoting from an hour to ten minutes; a decision NOT to buy the software a vendor was pitching. Technology showed up in fewer than half of those. The deliverable is a process that works; the means follow.

Discovery: we watch the work run and interview the people who do it — including the workarounds they have stopped noticing, which are usually the real process. Mapping: the flow drawn end to end with its exceptions, so disagreements surface on a diagram instead of on the floor. Scoring: every candidate fix rated by effort against payback on the matrix you can see on this page — so the build order stops being whoever argued loudest. Roadmap: what to do first, next, and deliberately not at all, with reasoning attached. Implementation: we build the top items rather than posting you a PDF and an invoice.

Less than the problem already does. Discovery is designed around your schedule: short observation windows during normal work, interviews of thirty to forty-five minutes per key person, batched so nobody loses a day. The people closest to the pain usually enjoy it — being asked “where does this go wrong” by someone empowered to fix it is a rare pleasure. After discovery, your involvement is decision points and reviews, not homework.

Effort against payback, scored the same way for every candidate — the two-by-two on this page is the actual instrument, not decoration. Quick wins (low effort, high payback) go first, not because they are glamorous but because they fund credibility and momentum for the bigger bets. Time sinks — high effort, low payback — get named and deliberately parked, which is often the roadmap’s most valuable line: the expensive idea everyone assumed was next, formally demoted with reasons.

The process maps (current and future state), the scored opportunity list, the sequenced roadmap with reasoning, and — because we implement — the top fixes actually working: the form live, the rule in place, the automation running, the procedure written. Plus the part that keeps it honest: before-and-after measurements on what we changed, so the engagement’s value is a number you can check rather than a feeling you are invited to have.

Because we sell implementation and resell nothing. No software commissions, no platform partnerships that bias the answer, and a public bias toward the cheapest fix that works — which is frequently a rule, a template or a role, not a purchase. Our matrix scores “change nothing yet” as a legitimate outcome. The economics align the same way: our reputation compounds on fixes that hold, not on licences you resent.

Then you hear it privately, framed as process, because it usually is process: unclear ownership, an approval structure that made one person the bottleneck, a role that grew by accretion until nobody could succeed in it. We name the structural cause and design around human dignity — the goal is work that flows, not a report that wounds. What we will not do is launder a hard truth into vagueness; you are paying precisely for the thing nobody internal can comfortably say.

Fixed for discovery and roadmap — sized by how many processes and people are in scope — then fixed per implementation item, so you can stop after the roadmap, after the quick wins, or never, at your discretion. The structure is deliberate: the diagnosis is priced to be an easy yes, and everything after it has to justify itself through the same effort-versus-payback lens we apply to your operations. You will never be surprised by an invoice, which in consulting is apparently a differentiator.

Both, matched to the work. Observation is best done where the work happens — for Victoria and Island businesses that means being physically present for discovery days; further afield we run structured remote observation (screen-shares for digital processes, guided video walkthroughs for physical ones), which works better than people expect. Mapping, scoring and implementation are location-independent. Plenty of engagements mix one on-site discovery visit with everything else remote, which keeps cost proportionate for smaller businesses.

Please do — that is success, not lost revenue. The instruments are deliberately transferable: the mapping notation is teachable in an afternoon, the effort-payback matrix is a whiteboard habit, and the roadmap format is yours to reuse. We leave the templates behind and will happily coach an internal owner. Businesses that internalise the discipline call us back for the gnarly cases and the builds, which is exactly the relationship we want.

Quick wins from the roadmap typically land within days of approval — that is what makes them quick wins. The full arc (discovery, roadmap, first implementations) usually completes inside a few weeks for a small business. And one honest expectation-set: some value arrives on day one, uninvoiced — the moment the map goes on the wall and three people see, for the first time, what the others actually do, something in the room usually gets fixed by conversation alone.