Custom builds
Your own processes, built into your portal.
Packaged software rarely fits every business. We give you AI-native tools, then build the rest around you: your CRM, processes, screens and controls. Every step can run on its own or wait for a person.
Custom build
Fleet amendments
2 of 4 on their own
- 1Read vehicle changes from emailRuns on its own
- 2Check each one against the cover scheduleRuns on its own
- 3Assign a handlerWaits for a person
- 4Approve the changeAlways a person
CRM
Pipelines, stages and approvals set up the way you sell, with your records imported from the spreadsheets you keep.
Processes
Fleet amendments, reconciliation, forecasting and claims, each step running on its own or waiting for a person.
Bespoke screens
Screens built around the job, like a fleet book, a claims queue or the month's control log.
Controls
Who sees and does what, by role, team or person, with the approvals and red lines you set.
People in the loop
You choose what runs on its own.
Start with a person approving every step. Switch steps to run on their own as you come to trust them, and back again at any time. Either way, each step is recorded in the audit trail.
- Runs on its own: the step happens as the work arrives
- Waits for a person: the step is prepared, then approved
- Always a person: payments, claim decisions and submissions to a regulator
Chat, routines and agents
Run it from wherever you work.
A build's actions are available in the portal's chat, routines and agents, with the same switches, and only to the people allowed to use them.
- In chat, ask what is waiting or have the next step prepared
- As a routine, run the month's reconciliation on a schedule
- With an agent, have new claims prepared for a handler
Custom skills and connectors
Skills for your work. Connectors to your systems.
We write skills with your team: the instructions, documents and examples each job needs. Connectors read from the systems you already run, from Microsoft 365 and Google Workspace to Acturis and FileMaker.
- Skills written with your team, from your own documents
- Shared by role, team or named person
- Connectors that read, with any change approved by a person
Consulting
Every build starts with the map.
Our operations review maps the work, scores each workflow and says in writing which ones are worth building. No build is priced before the hard part works on your own documents.
- Map the work, the rules and the systems behind it
- Score every workflow, including those not worth automating
- Build once the hard part is proven
Questions
What people ask.
Can we turn automation off?
Yes. Any step can go back to waiting for a person at any time. Payments, claim decisions and submissions to a regulator never run on their own.
Does a build replace our core system?
No. A build works alongside the systems you already run, reading from them and writing back only through steps you control.
Where does a build's data live?
In your portal's own database and storage, in the region you chose, under the same access rules and audit trail as everything else.
Tell us about the work you want built.
Book an operations review. We map the workflow, prove the hard part on your own documents, and then price the build.