Services
Assess. Deploy. Operate.
Three stages, priced and scoped separately. You can stop after any one of them, and the work you've paid for stays useful if you do.
Assess
A short, fixed-fee engagement that answers one question: what can actually be built here, given where your data is allowed to go?
- What we do
- Map your data boundaries and the rules that set them. Identify which systems hold the value and how they can be reached. Interview the people who will review the design, so their requirements are inputs rather than surprises.
- What you get
- A written architecture recommendation, a deployment topology, a list of the integrations worth building first, and an effort estimate for each.
- How it ends
- With a document you own. If you take it to another firm, or build it yourself, it still works — we'd rather be judged on whether the thinking was any good.
- Shape
- Fixed scope, fixed fee, no dependency on what comes next.
Deploy
Building the thing and getting it into service, in the topology the assessment settled on.
- Where it runs
- Your hardware, your cloud account, or an isolated host. Local inference where data can't leave; a hosted API where your policy permits one.
- Integrations
- Connections to your internal databases, APIs and file shares, using outbound-only tunnels so no inbound firewall change is needed. Tools exposed to the agent over the Model Context Protocol.
- Surfaces
- Command line, desktop, mobile, and an end-to-end encrypted chat surface — whichever your people will actually open.
- Handover
- Runbooks, configuration under your version control, and a walkthrough with whoever will operate it.
Operate
Optional. Some clients take the handover and run it themselves; others would rather it stayed someone's job.
- Keeping it current
- Version upgrades, model changes, and provider switches — including moving between local and hosted inference as your policy changes.
- Measuring changes
- We define acceptance tests for your use cases and re-run them on every change, so a regression is caught by us rather than reported by your staff.
- Records
- Session and tool-call history is persisted on your infrastructure, where your own retention and review processes apply to it.
- Contact
- A named person who knows your deployment, not a queue.
Finish
Start with the boundary, not the model.
An Assess engagement is fixed scope and fixed fee, and ends with a written architecture you own — whether or not you continue with us.