The engagement

Most engagements begin with one conversation.

Within two weeks, you have a written plan with your name on it.

This page shows you exactly what it looks like to be a client. Not what we believe in. What happens, in what order, and what you get at each stage.

What actually happens

Week by week. No ambiguity.

Every phase has a defined output. Nothing runs without sign-off.

Week 1–2LISTEN

We listen before we recommend anything

First meeting: you. We want to understand your strategic priorities, the areas causing most pain, and what you have already tried. This takes about 90 minutes.

Second meeting: the people who actually do the work. A different conversation. Different answers. Both matter.

We are listening for patterns — the workarounds your team has normalised, the bottlenecks everyone navigates around, the one person who holds too much together.

In most engagements, the area we end up working on first is not the one named in the first meeting. It is usually adjacent — a process everyone works around, or a person carrying knowledge the business does not realise it depends on.

A written priority list with time estimates and a clear recommendation on where to start.
Week 3–4DESIGN

We design the first afferent together

What it handles. What it escalates. What it never touches without you.

Every connection is documented before it is built — what has access to what, what permissions are required, what the boundaries are. You see the map before we lay a single cable.

You review it. You change anything. You sign off in writing.

Nothing proceeds to the build stage without your written approval. This is not a formality — it is the foundation of the engagement.

A signed architecture document: scope, connections, permissions, escalation rules, and boundaries.
Week 5–6BUILD & RUN ALONGSIDE

It runs alongside your team first

The afferent is built and runs in observation mode. It does not take actions. It shows your team what it would have done.

Your team compares outputs to their own. They flag anything that needs tuning. We tune it.

This continues until it meets your requirements — not ours. Your team decides when it is ready.

The afferent earns its place. It does not replace your team — it proves itself to them first.

A tuned, validated afferent that your team has approved.
Week 7+ACTIVATE & EXPAND

You decide when to go live

One decision. Your call. When your team is satisfied, you activate.

Once it is running and proven, adding further afferents becomes easier — the connections are already in place, the access is already mapped.

Monthly review: what it handled, what it escalated, what needed tuning. Numbers, not words.

The second afferent is always easier than the first. The third is easier still. Each one builds on the foundations of the last.

Monthly operations summary. What ran, what escalated, what was learned.

The thing nobody else does

The problem is rarely the one you call it.

The MD says it is the reporting. We sit with the ops team and discover the reporting is fine — it is the data going in that is broken. One person manages the exceptions manually. They have been doing it for two years. Nobody knows how they do it.

That is where we start.

“We have never started an engagement and ended up where we expected.”

That is not a flaw in the process. It is the process working.

Is there a report that takes longer to build than to read?

Security & access

We come from cybersecurity operations. That shapes every connection we design.

Before building operational systems, we spent years inside enterprise security operations — assessing, hardening, and responding to incidents caused by exactly the kind of ungoverned access that gets businesses into trouble.

If you have an IT team, we work with them. If you have a security policy, we design to it.

Minimum necessary access

Afferents connect only to what they need for their specific task. Access is scoped, documented, and reviewable.

You see the map first

Every connection is documented before it is made. You approve the architecture before we build. No surprises.

Your data stays in your systems

We do not move, copy, or store your business data. Afferents operate inside your environment.

Personal data never reaches external processing

Customer names, financial details, and anything personally identifiable are anonymised before the system works with them. The intelligence operates on patterns. On output, your data is restored.

Full audit trail

Every action logged. Searchable. Exportable. Built for compliance from the ground up, not retrofitted.

On personal data

The tools your team may already be using — consumer-grade AI services on personal accounts — process whatever they are given. There is no anonymisation. If someone pastes a customer record or a contract summary, that data is in a third-party system. Under UK GDPR, the responsibility for that exposure does not sit with the employee who did it. It sits with you.

Our approach is different by design. Before any processing occurs, customer names, personal details, financial identifiers, and anything that could identify an individual are replaced with anonymous tokens. The system works on the structure and patterns of your data. On output, the real values are restored. Nothing identifiable is ever transmitted beyond your environment.

“Your customer data is anonymised before it moves. Not as a feature. As a rule.”

The current landscape of tools being connected to business systems without proper governance concerns us too. This is why our approach to access design and audit exists.

Your controls

You hold the controls. We operate inside your boundaries.

Every afferent can be paused or disabled from your portal. One click. Immediate effect.

One click

Pause any afferent instantly

One click in your portal. The underlying process reverts to your team immediately.

Always reversible

Nothing is irreversible

Changes that cannot be undone require explicit sign-off. Everything else can be rolled back.

Full visibility

Complete audit trail

Every action logged with timestamp, context, and outcome. Available from day one.

“If something goes wrong — and occasionally, something will — you will know what happened, why, and what to do about it.”

Does one person carry knowledge the business cannot afford to lose?

How it is managed

Written deliverables at every stage. No open-ended engagements.

Every phase has a defined duration and defined outputs. Nothing proceeds without sign-off. If something changes, we tell you before it costs you anything.

End of week 2

Priority plan

Written findings, recommended starting area, time estimates. Your approval required.

End of week 4

Architecture document

Full design: connections, permissions, escalation rules, boundaries. Signed by you.

End of week 6

Launch sign-off

Team-approved validation. Your decision to activate.

Monthly

Operations summary

What it handled. What it escalated. What it learned. Numbers for your board pack.

How decisions are made

Three tiers. You choose where each task sits.

Not all operational decisions carry the same weight. You classify each task. You can reclassify any time.

RUNS AUTOMATICALLY

Routine and low-risk

Repetitive tasks with deterministic outcomes. The afferent acts, logs it, and moves on.

Supplier chase emailsReport assemblyData reconciliation
RUNS AND REPORTS

Meaningful changes flagged

The afferent acts, but surfaces anything outside the expected range for your review.

Order exceptionsInvoice mismatchesNew data patterns
PROPOSES AND WAITS

Your sign-off required

The afferent prepares the recommendation and stops. Critical decisions stay with you.

Contract changesAccess provisioningPricing exceptions

What changes

The work does not disappear. It stops needing a person.

Real patterns from real engagements, anonymised.

Monday management report

Before

3 hours, one person, every Monday

After

Delivered at 07:00. Already in your inbox.

3 hrs → 0

Supplier chase

Before

40 minutes a day, inconsistent

After

Done hourly. Escalated only when needed.

40 min/day → 0

Month-end reconciliation

Before

Late nights for finance, every month

After

Pre-reconciled. Exceptions only.

4 late nights → 2 hours

The problem they didn’t come with

What they said

“We need better reporting.”

What we found

One person held all the context. The report was fine.

Discovery first. Always.

What would your ops manager do with eight extra hours a week?

The hire you haven’t made

You are not short of people. You are short of hours.

Every business we work with has capable people who spend a meaningful fraction of their time on work that should not require them. Not because they are inefficient. Because the systems around them were never built to absorb it.

An afferent does not replace a person. It takes the operational grind off the people you have — so they can do the work you actually hired them for.

“The ops manager who was spending 40 minutes a day chasing suppliers is now spending 40 minutes a day on the strategic supplier relationships that matter. Same person. Better work.”

The economics

Priced as an operational asset, not a consulting day rate.

Fixed-scope, fixed-fee. You know the cost before you commit. Once afferents are in place, expanding is significantly cheaper than building the first one.

THE MAP

Fixed fee. You own the output.

Discovery, priority analysis, and architecture design.

  • Two rounds of discovery meetings
  • Written priority plan with time estimates
  • Architecture document for the first afferent
  • Access and security review
  • No obligation to proceed

Most clients who complete The Map proceed to build. Not because they have to — because the plan makes the case.

BUILD & MANAGE

Fixed project fee + monthly retainer.

Build, activation, and ongoing management.

  • Build to approved specification
  • Parallel running and team validation
  • Activation on your sign-off
  • Monthly operations summary
  • Expansion at lower marginal cost

Monthly retainer covers tuning, expansion, and review. Cancel with 30 days notice.

“The second afferent costs less than the first. The third less than the second. The infrastructure is already in place.”

Not theoretical

We run our own operations on the same system.

The afferents described on this page are not hypothetical. We use them ourselves — for operations, reporting, and business management. We are not asking you to be an early adopter. We are showing you a system that works.

“We run the same workflows we deploy to clients. Every improvement we make for you, we have already proven on ourselves.”

Start here

When you are ready, the first step is a single conversation.

No deck. No sales process. A conversation about your business and whether this is the right fit. If it is not, we will tell you that too.

Book a conversation →

Typically a 45-minute call. No obligation beyond the conversation itself.