What we build
Three ways we put AI to work
Pick a service, then try the example to see what changes for your team.
Workflow automationRoutine work runs on its own.
We take one repeated workflow and make it run inside the systems you already use. People only see the exceptions, with what they need to decide.
What we build
- Reading orders, invoices and forms from email and PDF
- Checks against your stock, pricing and account rules
- Exception queues that hand each case to the right person
Best when the same work is retyped, checked or chased every day.
Start with an assessment →Emailed orders into the ERP
Illustrative example. Switch to Before, then come back and approve the held order.
Read and checked against stock, pricing and account rulesRetyped by three people between other work
Order inbox5
- HSHarbour SupplyPO 4471, 12 lines ReadUnread
- CPCedar PlumbingPO 0932, 4 lines ReadUnread
- LELakeshore ElectricPO 7718, 9 lines ReadUnread
- PTPrairie ToolsPO 2206, 3 lines ReadUnread
- BBBayview BuildersPO 5150, 6 lines ReadUnread
ERP sales ordersLiveBy hand
- Harbour SupplySO-20481SO-20481 CheckedTyped by hand, 14 min
- Cedar PlumbingSO-20482SO-20482 CheckedTyped by hand, 9 min
- Lakeshore ElectricSO-20483Qty 100 keyed as 1000 CheckedEntry error
- Prairie ToolsUnknown SKU BRK-22ONot entered yet Approved by youBeing typed
- Bayview BuildersSO-20484Not entered yet CheckedStill in the inbox
Retyped by hand
0 of 55 of 5
Waiting on a person
15
Entry errors
01
AI operating systemOne connected view of the business.
We connect the systems you already run, so knowledge is easy to find, work moves between systems, and leaders see problems early.
What we build
- Connections between your ERP, CRM, inboxes and spreadsheets
- Answers to everyday questions, drawn from your own records
- One live view of the numbers leaders check every week
Best when answers live in people’s heads and reports are rebuilt by hand.
See it in the system map →The numbers leaders check every Monday
Illustrative example. Connect or disconnect a system and watch the view change.
Connected sources 4 of 4
Leadership viewMonday 8:00
Orders this week
412Up 6% on last weekRebuilt by hand from the ERP, about an hour each weekQuotes waiting
183 older than two daysRebuilt by hand from the CRM, about an hour each weekEmails unanswered
7Oldest is 3 hoursRebuilt by hand from the shared inbox, about an hour each weekStock at risk
5 SKUsBelow reorder pointRebuilt by hand from spreadsheets, about an hour each weekSources connected
4 of 4
Numbers built by hand
0 of 4
Age of the numbers
Live
Operating model redesignRoles rebuilt around the change.
New technology changes who does what. We redesign the roles, handoffs and routines so the gains show up in your numbers.
What we build
- A clear owner for every automated and manual step
- Fallbacks for when something does not work
- A review rhythm, so workarounds do not creep back
Best when a new system went live but the work did not change with it.
Start with an assessment →The order workflow: who owns what
Illustrative example. Switch to Before, then assign an owner to each step.
Steps with an owner
4 of 4
Fallbacks agreed
4 of 4
Workarounds
Unlikely
Included every time
What every engagement includes
Whichever service you choose, these come with it.
Assessment first
A real option not to build. We only build what the evidence supports.Building starts from a demo, before anyone checks it is worth it.
One accountable owner
One person runs scope, specialists, testing and communication.You coordinate the developer, the software vendor and your IT.
Your systems stay
We build into the ERP, CRM, inboxes and spreadsheets you already run.A new platform your team has to learn and move to.
Protected for up to 36 months
Adoption Protection, 12 months of Reliability Care, then a conditional Performance Guarantee.Support ends at go-live. After that, fixes are billed by the hour.
How the Assurance worksHonest measurement
Net usable capacity after residual effort, not theoretical hours.Hours saved on paper that never show up in the numbers.
Change management built in
Training on the work that changed, clear fallbacks and an early review, so people actually use it.A training video at launch, then people drift back to the old way.
People decide the exceptions
Routine steps run on their own. Anything unusual goes to a person.Edge cases break the flow, and nobody notices until a customer does.
Done is agreed in writing
Acceptance criteria set before work starts, so everyone knows what finished means.Scope drifts, and finished becomes a matter of opinion.
How it runs
Four steps, one accountable owner
Assess
Starts with a fit callWe pick one repeated workflow, measure it honestly and recommend build or no-build. Sometimes the right answer is to simplify, buy or wait.
You get
- The decision, with the reasoning written down
- A business case measured at four levels, down to net capacity
- Scope, responsibilities and acceptance criteria
Who is involved
Delivery ownerYour process owner
Build
Scope set in the assessmentOne accountable owner scopes, builds and tests the workflow inside the systems you already run, bringing in specialists only where they are needed.
You get
- The workflow, built into your existing systems
- Testing on real examples, including the awkward exceptions
- Sign-off against the acceptance criteria
Who is involved
Delivery ownerSpecialistsYour process owner
Adopt
First 90 days after go-liveWe train people on the work that changed, watch how it is used and fix friction quickly, so the team keeps the new way instead of drifting back.
You get
- Training on the steps that changed
- Clear fallbacks for when something goes wrong
- An early review of how adoption is going
Who is involved
Delivery ownerYour teamYour process owner
Protect
Up to 36 monthsReliability Care keeps the workflow working for 12 months. After that, a conditional Performance Guarantee covers up to 24 more months.
You get
- Monitoring, fixes and adjustments as your business changes
- Regular reviews of how the workflow is performing
- A written guarantee with clear conditions
Who is involved
Delivery ownerYour process owner
By team
Where the first workflow usually comes from
Pick your team, then a workflow, to see what would run on its own and what still reaches a person.
Typical first workflows
Starts when
A supplier invoice arrives
Runs on its own
Matched to the purchase order and receipt, line by line
A person sees
Only the mismatches, with the difference highlighted
Starts when
An invoice passes its due date
Runs on its own
Reminders go out on your schedule and replies are logged
A person sees
Disputes and accounts over their limit
Starts when
The month closes
Runs on its own
Reconciliations and checklists prepared from each system
A person sees
The items that need judgement, ready to sign off
Usually starts with
Workflow automationTypical first workflows
Starts when
A customer asks for a quote
Runs on its own
Stock, price and account terms checked, and a draft built
A person sees
The draft, ready to send or adjust
Starts when
A quote goes below margin
Runs on its own
Sent to the right approver with the context attached
A person sees
One approve or decline, with the history
Starts when
A call, email or order happens
Runs on its own
Activity and next steps logged against the account
A person sees
The accounts that have gone quiet
Usually starts with
Workflow automationTypical first workflows
Starts when
An order arrives by email or PDF
Runs on its own
Read, checked and entered in the ERP
A person sees
Only the orders with a problem
Starts when
An order line is short
Runs on its own
Alternatives and dates checked, and the customer told
A person sees
Substitutions that need approval
Starts when
An order ships
Runs on its own
Tracking sent and the order status updated
A person sees
Late or failed deliveries
Usually starts with
Workflow automationTypical first workflows
Starts when
A customer asks where their order is
Runs on its own
Status pulled from the ERP and carrier, and a reply drafted
A person sees
Questions the system cannot answer
Starts when
A return request arrives
Runs on its own
Checked against your policy and the original order
A person sees
Returns outside the policy
Starts when
A case comes in
Runs on its own
Sorted by type, account and urgency
A person sees
Their own queue, already in priority order
Usually starts with
AI operating systemTypical first workflows
Starts when
Reporting day comes round
Runs on its own
Figures pulled from each system and assembled
A person sees
A finished report to review
Starts when
Something needs approval
Runs on its own
Sent to the right person, with a deadline and reminders
A person sees
One place to approve, with the history
Starts when
A document arrives
Runs on its own
Read, named and filed against the right record
A person sees
The documents it could not match
Usually starts with
AI operating systemNot sure which service you need?
You do not have to know. The assessment starts with one workflow and tells you what is worth building.