The process
All of it happens on-site, in your business, sitting with the people who do the work. Not over email. Not from a boardroom.
Evolves and rebalances as you scale
MAP · Step 1 of 6
We map your current process
We do not assume, we ask. We sit with your team and document how work actually moves today, where leads, jobs, and quotes really flow, and where the handoffs quietly slow everything down.
We do not assume, we ask. We sit with your team and document how work actually moves today, where leads, jobs, and quotes really flow, and where the handoffs quietly slow everything down.
The process loops. It evolves and rebalances as you scale.
You own everything
Your accounts, your keys, your systems, from day one.
No provider lock-in
We move to the model that best fits each job and its cost.
Evolves as you scale
A live register, rebalanced as your business grows.
Three things we build. Examples, not a menu.
The missed handoffs, the tools nobody mapped, the reporting that does not exist yet. Each of these had to clear the same test before we built it: would the return justify the spend? These did. Here is what it looks like when those problems get solved.
AI Usage Framework and Staff Training
Your business has AI tools, or staff are using ChatGPT on their own. Nobody knows what is safe to put in. Different people use the tools differently. Some avoid them entirely. You are paying for licences but getting inconsistent value.
We sit with each role and understand their actual work. We define what can and cannot go into AI tools for that specific role. We create approved prompt templates, written in plain language, tested on real tasks, specific to the job. Then we run hands-on training sessions where staff use the templates on their own work. Not a webinar. Not a slide deck. Actual practice with their actual tasks.
Everything goes through your team for approval before it is rolled out. The guidelines belong to you, not to us. When we leave, the team has a documented framework they can update as tools and policies change.
Your team does not need to figure out how to use AI properly on their own. We give them the guardrails and the templates for their specific role. When we leave, they keep getting better. Not worse.
One Process, Run Without the Manual Handoffs
A core business process runs across four to six tools with manual handoffs between each step. People copy data between systems. Things get missed, which means errors, rework, and waste. The owner has no real-time visibility into where things stand.
We map the entire process end-to-end, sitting with the people who actually do the work. We identify the manual handoff points. We automate the ones that should be automated and add human checkpoints where judgment matters. We connect the existing tools so data flows without manual re-entry. We build a live dashboard so the owner can see the state of every job without asking anyone.
Every automation has defined boundaries. The system handles the routine. It routes exceptions to the right person with full context. Nothing runs without oversight where oversight matters.
Then comes the handover. We document every workflow. We train the team to understand what was built and why. We run them through common changes and extensions so they can adjust the systems themselves. When we step back, the team does not just have a set of automations. They have a documented system they understand, can explain to new hires, and can extend without us.
Six months on, the systems run with fewer errors and less waste. If your team has the technical depth, they can maintain and extend them; if not, we stay available to keep operating and improving them as you grow. (Example, not a guarantee: a multi-site operator might point this at supplier ordering and rostering admin. Your real numbers come out of the Sprint, not a brochure.)
Tender Response Pipeline
A tender notification lands in the inbox. Someone reads the requirements, pulls content from past submissions, adapts template sections, chases input from three different people, formats everything to the evaluation criteria, and uploads it to the portal. That takes two to four days. The person assembling it works late. Some tenders get skipped because there is not enough time.
We sit with the team and map the tender process. The templates, the evaluation criteria formats, the submission requirements. Then we build a system that monitors for tender notifications, extracts the requirements and deadlines from the documents, pulls relevant content from the firm's template library and past winning submissions, and assembles a structured draft matched to the evaluation criteria. Placeholders flag where human input is needed.
The draft goes to a senior team member for review. They spend half a day refining and adding the judgment calls. Not three days assembling from scratch. Once approved, the system formats the submission and uploads it to the required portals.
The person who used to spend three days pulling a tender together now spends half a day making it better. They go home at a reasonable hour. The firm responds to more tenders without adding headcount.
Three examples, three different businesses. The thread is the same in all of them: we sit on-site, map how the work really moves, and build around what we find, then hand it over so you own it. No two builds are the same, even when the outcome is.
What Stays the Same Every Time
No matter which engagement you choose, these things are always true.
We build under your accounts. You hold the credentials.
We do not mark up tool costs. You pay providers directly.
We document everything we build.
We test every system against real failure cases before it touches live work.
If you stop working with us, your systems keep running.
What Changes with Scale
For an AI Opportunity Sprint, the process is tighter. We focus on one key workflow or team, identify the highest-value opportunities, implement one quick win, and deliver a clear roadmap. Most Sprints are complete within two to three weeks.
For an Embedded AI Partnership, the process is ongoing. We are on-site two days a week, wherever the work actually happens, continuously mapping workflows, building systems, training the team, and improving what is already running. The depth builds over time as we learn more about how the business operates.
For an Enterprise Partnership Program, the process expands across departments. We audit multiple workflows, design future-state processes, run formal approval gates, train staff by role, and include a 30-day stabilisation window after go-live. These engagements typically run three to five months.
The depth scales with the job. You own what we build, every time, at every size.
Want us to walk one of your workflows through these six steps?
Book a 30-minute call. We will not map your workflows from a slide deck. If it looks like a fit, we come on-site and do it properly. If it is not, we tell you straight.
Book a Strategy Call