Intelligence & Operations

Business systems and process improvement.

Improve the workflows and tools behind your products and services, structuring lead management, delivery, reporting, and team handoffs around how your business actually operates.

The problem

Work that depends on the owner’s memory

Leads sit in inboxes, handoffs happen by message, and reports are assembled by hand. The business runs because a few people remember how, and the owner is pulled into every exception.

You might recognize:

  • Delivery, handoffs, and follow-up rely on constant intervention.
  • Tools were added one at a time and do not fit together.
  • Reports take hours to assemble and are not trusted.
  • New staff learn the process by asking around.

Intended outcome

Clearer ownership and more consistent execution, with a process your team can run without you in every step.

What is included

The scope of the work.

  • Current workflow mapping

    How work actually moves today, from first inquiry through delivery and follow-up.

  • Bottleneck analysis

    Where work waits, is repeated, or depends on one person.

  • Requirements

    What lead management, delivery, and reporting need to do, written before any tool is chosen.

  • Tool setup

    Selected CRM or work-management setup, and integrations where they are in scope.

  • Reporting

    The few numbers the owner needs, defined and produced consistently.

  • SOPs and training

    Written procedures and team training so the process holds after handover.

Deliverables

What you receive.

These are the documents and working files you keep. For each one: what it is, what it looks like, and what it does for the business. The layouts shown are illustrative and use a fictional business. No client material is shown.

Process maps

Also called workflow diagrams

What it is
Step-by-step diagrams of how work really moves through your business today, from first inquiry to delivery and follow-up, with the delays marked.
What it looks like
A row of steps joined by arrows, with the steps where work waits or depends on one person highlighted.
What it does for the business
Shows where time and effort are lost, so fixes go to the actual bottleneck instead of the loudest complaint.

Business requirements

Also called a requirements document

What it is
A plain-language list of what your lead management, delivery, and reporting must do, written before any tool is chosen.
What it looks like
A table: each requirement, why it matters, and whether it is a must or a should.
What it does for the business
Lets you choose or set up a CRM or work-management tool against your real needs, so you pay for what your process requires, not for the best demo.

Standard operating procedures (SOPs)

Also called written work instructions

What it is
Written, step-by-step instructions for the tasks your team repeats, so each one is done the same way each time.
What it looks like
One task per page: its purpose, who does it, numbered steps, and what done looks like.
What it does for the business
New staff learn from a page instead of by asking around, and the process holds when you are not in every step.

Also delivered

Built or set up for you, rather than handed over as a document.

  • Selected CRM or work-management setupYour chosen tool set up to the requirements above.
  • Integrations, if scopedConnections between your tools, where they are in scope, so information is entered once.
  • Team trainingYour team taught to run the new process.

How the work proceeds

Four steps, each ending in a decision.

Every engagement follows the same six-stage process, applied to this service.

  1. Map the current workflow

    Follow real work through the business and interview the people who do it.

  2. Find the bottleneck

    Choose the constraint whose removal is most valuable and feasible.

  3. Implement the smallest fix

    Configure the process and tools for that constraint, with owners named.

  4. Measure and hand over

    Check the change works, then document it and train the team to run it.

Read the full process

Illustrative example

Inquiries tracked in someone’s inbox

Illustrative example, not a client result

Inquiries arrive by phone, email, and a web form and are tracked in one person’s inbox. The map shows where leads wait. Requirements define stages, owners, and reminders. Setup follows in a CRM, with an SOP and a short training session so the routine survives staff changes.

Scope and boundaries

What this covers

  • Software and workflows: lead management, delivery tracking, reporting, and handoffs.
  • Physical IT infrastructure, such as hardware and network installation, is outside this scope.
  • Which platforms are set up, and any custom development or ongoing support, are agreed per project.

Related experience

Where this shows up in my work.

FAQ

Scope questions.

Which tools do you use?

Tool choice follows the requirements. I would rather write down what the process needs first than start from a favorite product. Supported platforms are agreed per project.

Do you build custom software?

Custom engineering responsibilities are agreed per project. Many improvements need configuration and clear procedures rather than new software.

Can my team run it without you?

That is the goal. Handover includes documentation, an access inventory, training, and named owners for each part of the process.

Make the way your business runs less dependent on you.

Start with a free, 20-minute introductory call to talk through your business, the challenge, and what a sensible next step looks like.

Book a Free 20-Minute Call (opens in a new tab)