Is it the system, the people, or the process?

You know there is a problem. The numbers don't match, sites operate differently, and you are getting five different answers for why something went wrong. I find out what is actually broken, prove it, and fix it.

Let's find the root cause

Do any of these sound familiar?

"I don't know if my numbers are even true anymore."

Payroll, attendance, or production figures are inconsistent across sites. Nobody can say with confidence which numbers are real.

"Every time I ask why, I get five different answers."

No single source of truth between sites or managers. Decisions are being made on guesses because the root cause is hidden.

"I'm paying for a system I'm not even using properly."

You bought software expecting it to fix things. It hasn't. You suspect it's not the software's fault, but you need a neutral party to confirm.

"Site A does it differently than Site B."

Site-to-site drift with no visibility. You only find out processes are completely out of sync when something finally blows up.

My Diagnostic Method

I don't guess. Before any changes are made, we run a strict diagnostic process to isolate the actual failure point.

1

Define the Symptom

What is actually being experienced on the ground, in plain English?

2

Build the Hypothesis

Is this a System error (bug, misconfiguration), a People error (training gap, workaround), or a Process error (workflow gap between departments)?

3

Run the Test

Pull the raw logs. Sit with staff during a shift change. Watch the actual process happen live to gather hard evidence.

4

Confirm the Cause & Fix

State exactly what broke. Implement the fix through retraining, process redesign, or directing system changes. Follow up to ensure it held.

Beyond the Diagnosis

The Three Fixes

Diagnosis is only half the battle. Once we prove whether the failure lies in the process, the system, or the people, I provide the exact execution path to fix it permanently.

1. Consulting

The Process Fix. The core service. Re-architecting broken workflows, eliminating site-to-site drift, and providing ongoing diagnostic oversight so problems are caught before they burn.

2. Custom Systems

The System Fix. When off-the-shelf software is the actual bottleneck. I scope, build, and deploy lean, custom internal tools that do exactly what your operation needs—with zero bloat.

3. Coaching

The People Fix. When the tool is right but the execution is wrong. I work directly with your managers and staff to close training gaps, align leadership, and build habits that stick.

Who I Work With

I specialize in working with mid-size, multi-site operations (100–1,000 employees). This is where complexity exists—multiple systems, multiple locations, site-to-site drift—but the company is still agile enough that a single, sharp diagnostic partner is the most effective solution.

Manufacturing Garment & Textile Timber & Forestry Logistics & Distribution Agri-Processing

Diagnostic Retainer Partnership

Don't wait for a crisis. I act as your on-call diagnostic partner, watching your systems and processes, so problems are caught in week one, not month three.

Continuous Watch Retainer

Starting at R10,000 / month

  • Monthly Health Check: A standing review across sites/systems to catch drift before it becomes a fire.
  • Executive Summary Note: Monthly one-pager detailing what was reviewed, what is solid, and what is starting to wobble.
  • Priority Response: When things break, response within 24-48 hours. I already know your setup, so we don't start cold.
  • Ongoing Diagnostics: Symptom → Hypothesis → Test → Cause → Fix support, flexed across the month as needed.

*Defined large projects, custom system development, and extensive on-site travel are scoped and quoted separately.

Let's clarify the problem.

Are you currently dealing with a system problem, a people problem, or are you not sure yet? Pick a time below for a diagnostic call.

Or if you prefer to write first, email me directly.

INTERNAL REFERENCE ONLY. Do not share this view with clients.

Master Strategy & Notes Document

1. Target Market Strategy (The "Goldilocks" Zone)

Small (10-100 employees)

One site, standard process problems. Problems are usually genuinely simple. One person, one location. "Why isn't this working" is often obvious inside a day.

Verdict: Reject.

Not enough complexity to justify R10-20k/month recurring — you'd solve it once and there's nothing left to retain you for.

Medium (100-1000 employees)

R500k–7M revenue. Multi-site + multiple systems creates genuine recurring diagnostic need (something's always slightly out of sync across sites).

Verdict: Ideal Target.

Company is still small enough that one sharp outsourced person, not a team, is a completely credible answer.

Large (1000+ employees)

Revenue 7M-50M. Real complexity, but at that scale they usually need a team on the ground, not one outsourced person on call.

Verdict: Reject.

You'd get pulled into full-time-equivalent hours fast, which breaks the "outsourced, not embedded" model you specifically want.

Specific Target Industries

Physical, multi-site operations running attendance/payroll/production systems where site-to-site inconsistency is the actual disease. (Matches existing client relationships like the timber group exactly).

  • Manufacturing
  • Garment / Textile
  • Timber / Forestry processing
  • Logistics / Distribution
  • Agri-processing

2. The Specific Problems We Solve at Mid-Market Size

  1. Site Drift: Site A does something differently from Site B and nobody's tracking it.
  2. Siloed Systems: Multiple systems (attendance, payroll, maybe a separate production/ERP tool) not talking to each other, and nobody owns reconciling them.
  3. Paper vs Reality: A process exists on paper but isn't actually followed, and leadership doesn't know it's not followed.
  4. Misdiagnosis: Training gaps that look like system failures until someone actually goes and watches people work.

3. Retainer Logic (How to pitch the "Quiet Month")

The core argument: You're not selling "fixing this month's fire." You're selling reduced time-to-detection and reduced time-to-correct-diagnosis, continuously.

"This is the same logic as a fractional CFO, a retained lawyer, or a security monitoring contract — none of those get cancelled in a quiet month, because quiet doesn't mean valueless, it means nothing burned because someone was watching."

How to concretely earn it in a slow month:

  • Monthly health check — a short standing review (30-60 min) across their sites/systems: anything drifting, any early signal of the people/process/system split showing up before it's a full fire.
  • A one-page monthly note — what you looked at, what's fine, what's starting to wobble.
  • Priority access — when something does break, you already know their systems and history, so you're not starting cold; that speed is what they're actually buying.

Pitch Script:

"You're not paying me for problems — you're paying so problems get caught in week one instead of month three, and so when you do call, I already know your setup."

4. Client Pain Hierarchy (Highest to Lowest)

Use this to qualify. Lead with 5 or 6, try to dig down to 1-4 to close the deal.

1. "I don't know if my numbers are even true anymore." (Existential)

Inconsistent payroll/attendance. High exposure. Highest willingness to pay.

2. "Every time I ask why, I get five different answers." (Trust)

No single source of truth. Decisions made on guesses. High willingness to pay for truth.

3. "I'm paying for a system I'm not using properly." (Sunk Cost)

Software didn't fix the issue. Need neutral confirmation it's not the software.

4. "Site A does it differently than Site B." (Drift)

Only find out during a crisis. Strong retainer material, ongoing issue.

5. "Managers keep asking for the same reports/changes." (Annoyance)

Lower perceived cost, but easy conversation entry point. Usually masks #2 and #4.

6. "I know there's waste somewhere." (Vague)

Lowest urgency. Use as an opener, not a pitch.

5. Scope Boundaries

SAY YES TO (In Scope)
  • Diagnosing system vs people vs process
  • Directing a fix and staying until it holds
  • Training, process redesign, coordinating a dev
  • A defined project block, quoted upfront
SAY NO TO (Quote Separately/Reject)
  • Building or coding a new system yourself
  • Open-ended "just keep fixing whatever" with no check-in
  • Becoming default IT for ad hoc requests (scope creep)
  • Unlimited daily availability for flat fee

6. The 6-Step Diagnostic Template

Use on every engagement to show method, not improvisation.

1. Symptom: What they experience (in their words).
2. Hypothesis: Consider 3 buckets (System, People, Process).
3. Test: Specific actions to confirm the bucket (logs, observation).
4. Confirmed Cause: What the test showed (no guessing).
5. Fix + Owner: Who does it? (You advise, dev builds, staff executes).
6. Confirm It Held: Check back later. (This creates retainer value).