Advisory Service

SOP's & Internal Controls

Processes your team will actually follow, because they helped write them.

What This Is

Turning tribal knowledge into a process anyone can follow

Most businesses run on knowledge that lives in one or two people's heads. That works until it doesn't — a key person leaves, the team scales, or an audit finding shows the same gap you've been quietly living with for years.

We document how the process actually runs, build in the controls that catch errors early, and make sure it's something your team will use — not a binder that sits on a shelf.

Typical Engagement
4–8 weeks per process
Best Fit For
Scaling teams, post-audit findings
Delivery Mode
Workshops + documentation
Reports To
Operations & finance leadership
A binder that sits on a shelf isn't a control. A process your team actually follows is. — What we optimise for over paperwork
Is This You?

What changes once processes are actually documented

Without documented SOPs

  • Processes that exist only in one person's head
  • New hires learning “how we do things” by trial and error
  • The same mistake happening in a different department every quarter
  • No clear owner when something falls through the cracks

With documented SOPs

  • Documented, versioned SOPs anyone on the team can follow
  • New hires productive faster, with a clear process to reference
  • Controls that catch errors before they repeat elsewhere
  • A named owner and clear escalation path for every process
Where We Help

Four things we build into every engagement

Process documentation

Turning how things actually get done into clear, followable SOPs.

Internal control design

Building the checks and approval points that catch errors before they become losses.

Segregation of duties

Structuring who does what, so no single person can execute and cover up an error.

Policy & delegation framework

Setting authority limits and approval matrices that match how the business actually runs.

How We Engage

Four phases, built with your team

We write these with the people who'll actually use them, not for them.

01

Observe

Watch how the process actually runs today, not how it's assumed to run.

02

Document

Write clear, followable SOPs the team helped shape.

03

Control

Build in the checks and approval points that catch errors early.

04

Embed

Train the team and check back in to make sure it sticks.

Common Questions

Frequently asked questions

Do you write SOPs for the whole company or specific processes?

Usually specific processes, prioritised by risk — we can extend to whole-company coverage over time as priorities allow.

Will this slow my team down with bureaucracy?

That's exactly what we design against — the goal is practical, minimal controls that catch real risk, not red tape for its own sake.

Can this follow up on our internal or statutory audit findings?

Yes, this is one of the most common reasons clients bring us in — turning an audit finding into a fixed process.

How long until SOPs are in place?

Typically 4 to 8 weeks per process area, depending on complexity and how many stakeholders are involved.

Do you help train the team on the new SOPs?

Yes — the “Embed” phase specifically covers training and follow-up, not just handing over documentation.

Tired of the same mistake happening twice?

Tell us which process, and we'll start with where it actually breaks down.

Get in Touch
← Back to

Advisory Service

See all advisory offerings — business advisory, startup consulting, valuation, M&A and project finance.