Six things, and every one of them is yours
Most of what is sold as automation is one product with a settings page, and every buyer gets the same one. This is the opposite trade: we build against your business and hand over a system you own outright – your data, your models, your agents, working to rules you wrote.
Your knowledge base
Every quotation, job file, document, message and decision your business has produced, read into one memory you can question in a sentence. What did we charge for this spec last year? Which jobs hit a municipal delay over ten days?
It answers from your data or says it does not know. An answer without a source is a defect.
Your data store
A schema built for your business, holding your catalogue, rates, jobs and documents – in an account registered in your name, with an audit log on every write.
Five-part export on request and on exit.
Your own models
The model runs in your tenancy or on your own hardware, and your data is never training material for anyone. A small local model classifies a message; a larger one drafts a quote.
For work that cannot leave the building, the whole path stays inside it.
Your agents
Named for the roles you already have – your estimator, your compliance clerk, your service planner. Each is built against how that job is done where you work, with its own access and limits.
You name them. Every one drafts; none of them sends.
Wherever you already work
WhatsApp for the people who live on it, email where email is the record, the console for the office and your voice for the site visit. One system underneath.
Your existing accounts and numbers. Nothing new to log into.
Your controls
Approval before anything leaves. Role-based access so a branch sees its own board. An audit log of who approved what and when. Acceptance tests written into the agreement.
Money movement and regulatory filing stay with a person by design.
The engineering
A demo is easy. A system that a lender audits, an insurer relies on and a board signs off is a different discipline. If your CIO reads one section, it should be this one.
Answers grounded in your corpus, with the source attached
Quotations, contracts, drawings, certificates and correspondence indexed so every answer carries the document it came from. Where it cannot ground an answer, it says so.
A test set built from your own work, run on every change
Each stage is scored against real examples from your business with a key you agreed. When a model or prompt changes, the same set runs again, so quality is measured rather than asserted.
The right model for each job, and the choice is a setting
A small local model to classify, a larger one to draft, a specialised one to read a drawing. Swapping any of them is configuration, not a rebuild.
Your cloud tenancy, your VPC or your own racks
Where the work cannot leave the building, none of it does – models, index and logs included. Otherwise it still runs in an account with your name on it.
Inside the systems you already run
ERP, CMMS, CAFM, document management, monitoring portals, the ledger, the client portal. Read where a read is enough; write only where a write is authorised, logged and reversible.
Every action attributable, every output traceable
Who approved what and when, which model produced which draft and what it read. Role-based access per site and branch, and an audit trail a lender can follow.
Designed for the day it is wrong
Confidence thresholds that route to a person instead of guessing, drafts that flag what they could not establish, and nothing that degrades silently.
Built so you could run it without us
Architecture, schema, configuration and access list handed over as a matter of course. A system only one supplier can operate is a liability priced as an asset.
What we can build first
These are not plans or tiers. Which one comes first is decided by your answers, and nothing you build first is a dead end – the knowledge base your estimator needs is the one your service desk reads two years later.
An operations agent
Reads every enquiry on every channel, drafts the replies, runs the job board and puts one brief in front of you each morning.
A quoting engine on your own history
Years of your quotations read into a priced catalogue, then quotes drafted from a dictated site visit in the same format every time.
Generated compliance
Certificates, as-builts, commissioning records, operating manuals and the regulator submission, built from the job file.
A knowledge base over everything
Quotes, jobs, contracts and decisions in one memory that answers in a sentence with the document it came from.
Monitoring and fleet reporting
Assets, sites or plants read every morning across whatever portals they live in, with an alert when something moved.
Billing and reconciliation
Production or completion read into a monthly bill in your accounting package, with retention diarised.
A private deployment
The models, the data and the logs inside your own infrastructure, for work that cannot go anywhere else.
Multi-branch and franchise
Each branch with its own board, catalogue and rules, so head office sees all of them and none sees the others.
Start with the seven questions.
Eight minutes. Rank where the week goes, describe a bad one and give four rough numbers. You keep the map whether or not we ever work together.