A written quote, testing on your own data, and a system you own.
Four steps from the first conversation to a system running for your firm. At each one you know exactly what you have committed, starting with nothing at all.
Six promises that go into every job.
A written quote before any work starts
After the review you get a written quote with an estimated price and timeline. The final price is agreed in a signed agreement, and a change of scope is priced and agreed before work on it starts.You watch it work before it goes live
On your own files, your own portal and your own exceptions, with you watching. Payment terms are set out in your signed agreement.You own what we build
The hardware, the code, the configuration and the data are yours, and accounts are opened in your name from the start.It runs on hardware and accounts in your name
The machines and the accounts are registered to you from the start. A care plan buys somebody watching it, and it is optional.Every agent action is logged
What the agent did, on which screen and when, is written down, so you can see exactly what happened on any record.A person can take over at any moment
One click hands control to a person and locks the agent out until it is handed back. Anything that touches money or a filing has a human check step built in.
Review, price, watch it work, run it.
The order below is the order things happen in, with what you have committed at each point.
- 01
The free AI review
Thirty minutes on a screen share. You show us the work that takes your team's time, and you leave with a written page on what to automate first.
What you have committed at this pointNothing. The review is free, it is thirty minutes, and you keep the written page.
- 02
A written quote
A written quote with an estimated price and timeline. If the scope changes, the change is priced and agreed before work on it starts.
What you have committed at this pointNothing yet. Reading the quote or saying no costs nothing.
- 03
Watch it work on your own data
Your files, your portal, your real exceptions. You watch it do the job before it goes live.
What you have committed at this pointWhat your signed agreement sets out. If it does not work on your own data, you see that before it goes live, and you keep the written findings.
- 04
Own it, and we keep it running
Builds use accounts in your name, and you own the code and the data. A care plan is optional, and the system keeps working if you ever stop.
What you have committed at this pointWhat your signed agreement sets out. What you have for it is a system you own, on hardware and accounts in your name.
These go in the quote, word for word.
Published here so you can read them before you speak to anybody, and so nothing in a quote is a surprise.
The first review is free
A thirty minute conversation about one task or one question. Neither side is committed to anything by it.Prices and timelines are estimates until signed
Starting prices on this site, quotes and anything said in a conversation are estimates. The final price, scope, timeline and payment terms are the ones in the agreement both sides sign.Payment follows the signed agreement
Work starts once the agreement is signed and any deposit it names is paid. Deposits are not refundable once work has started. Unless the agreement says otherwise, invoices are due within fourteen days.Changes to the scope are priced separately
Anything outside the signed scope, including changes you ask for and changes caused by your software or vendors, is quoted and agreed before work on it starts.Hardware is its own line
Where a machine is part of the job it is quoted separately. It becomes yours once it is paid for in full, and it is your responsibility once it is delivered.Care plans are optional
Monthly, with thirty days notice from either side. Without a care plan, any help after handover is quoted and billed when you ask for it.A quote expires after ten days
Costs move. A quote that has expired can be requoted.
How we handle the things that change.
Software lives in a changing office. These are the moments that come up, and what happens in each one.
Proving it on your own data
The process is built around this moment. You watch the system run against your own files, portal and exceptions before it goes live. If it does not do the job, you see that before anything goes live, and you keep the written findings.When a vendor moves a button
Software driven through the screen needs adjusting when the screen changes. On a care plan, we fix the screens as part of the plan. Without one, the fix is quoted when you ask, and the system tells you it has paused rather than filing something wrong.When a machine fails
The configuration is documented and reproducible, so a replacement is a rebuild rather than a rediscovery. Hardware is under its manufacturer warranty in your name, and we help you through the claim and the swap.When the scope changes
A change in what you are asking for is priced and agreed before work on it starts. You never open an invoice with a number you have not already seen.When you want to stop
Either side can end a project in writing. You pay for the work done and the costs committed up to that point, deposits are not refunded, and once that is paid you keep what was produced. The details are in your signed agreement and our terms.
What you own, and what a care plan adds.
What you own
- The machine, where one is part of the job. It is your asset, bought in your name.
- The code and the configuration written for you, with the documentation of how it was set up.
- The accounts: carrier accounts, domains, model downloads and any third party service, opened in your name from the start.
- Your data, which stays on a system you control throughout.
Without a care plan
The model, the agent and your documents are on a system you control, on hardware and accounts in your name. There is no licence server and no seat count.
What a care plan adds is somebody watching it: screens fixed when a vendor changes them, models updated, and exceptions caught early. A firm can take the plan for as long as it wants and then run the system itself, and we hand over everything it needs to do that.
Your data stays on systems you control.
On an in office install, the model runs on a machine you own, on your network. Customer conversations, documents and screen contents stay on that machine. There is no third party processor to add to a vendor list, no training on your data by somebody else, and no question about where a record was copied to. Where a firm prefers the cloud, the same setup runs in its own cloud account, under its own controls.
The controls are specific and written down: role based access on the private AI, a log of every action an agent takes, a human check step on any workflow that touches money or a filing, and administrator credentials held by you. Remote support is a session you start and can end, never a permanent way in.
We give you a written description of the architecture, the access controls, the audit log and where every piece of data sits, which is usually what a security questionnaire, an assessor or an insurer is asking for. We do not hold an audit certification ourselves, so if a contract requires one, raise it on the first call and we will work out together what your auditor needs.
Tell us what is taking your team's time.
Thirty minutes with an engineer, free. You leave with a written page on what to automate first, and a written quote if you want us to build it.