Each one started as a client engagement that turned out to be the same problem three times. We built it once properly, and now we sell it and operate it — with the tracing, evaluation and guardrails every system we ship carries.
Nothing here was built speculatively. Every line reached production for a named client before it became a product.
Product lines, client engagements and the two tools we built for ourselves. Filter by domain — every one of them is running somewhere today.
Payroll, attendance and appraisals on one tenant-isolated platform, with an agent that answers policy questions from the handbook and routes the exceptions to a named person.
Ask about this buildProduct discovery, order status and returns resolved against the live catalogue and order system, with anything it cannot confirm handed to a human.
Ask about this buildIntake, quoting and dispatch run against live engineer availability, with ETAs the customer can watch and the exceptions raised to a dispatcher as they happen.
Ask about this buildAdaptive coursework and auto-marked assessment, with a tutor agent that answers only from material the institution actually owns.
Ask about this buildA supervised agent watching carrier, weather and customs feeds, rebooking inside a per-lane authority limit and escalating the rest with an action already drafted.
Ask about this buildHybrid retrieval across 1.2M internal documents with citation enforced at generation time — cleared by compliance for regulatory submissions.
Ask about this buildDocument intelligence across KYC packs and corporate structures, confidence-gated per field, running entirely inside the client estate.
Ask about this buildRetrieval rebuilt against the current protocol set, with anything the index cannot ground routed to a clinician with the source attached.
Ask about this buildOur internal evaluation harness. Task-specific suites run against client data on every build, and a regression against the agreed baseline blocks the deploy.
Ask about this buildThe tracing console behind the retention promise — retrieval, tool calls and responses, kept and searchable long after anyone remembers the incident.
Ask about this buildShowing 10 of 10. Client systems appear with permission — the ones that do not are the reason this list is shorter than our invoice history.
A product line here does not exist until all six are true of it. None of them is an enterprise tier and none of them is billed separately.
Each tool call, retrieval and model response is recorded with the inputs that produced it. Eleven months later there is still an answer to "why did it do that".
Task-specific, running on your data rather than a public benchmark. Nothing reaches your users without beating the baseline it was signed off against.
Automated actions carry a threshold and an authority limit. Below it, work routes to a named human with the uncertain field already highlighted.
Our tenancy, your cloud account, or on-premise where the data cannot leave. The same product, with the boundary drawn where your security team wants it.
Code you own outright, with the architecture written down and the tests that prove it. Several clients take full ownership after the first quarter.
The people who built it carry the pager for it. Support is not a separate contract with a different team behind it.
The rule is deliberately slow, and it is the reason there are four of these rather than fourteen.
Every line here started as a scoped engagement that reached production and stayed there. Nothing in this portfolio was built speculatively against a market we imagined.
Production, not a pilot
One client is a project and two is a coincidence. When a third arrives with the same problem, the shape is real and it is worth building once properly instead of three times badly.
Three, then we build
It becomes a product only when we are willing to run it — tracing, evals, upgrades and the pager. If we would not operate it, we will not sell it.
Ours to keep running
Five things that are true of every product in this portfolio, stated before you ask a procurement team to find them in a contract.
You own the code
Documented and tested, handed over in full. Taking it in-house later is a decision, not a negotiation.
Fixed scope, fixed number
Each delivery phase is priced up front. No hourly billing, and no change request without a written estimate first.
Deployment is your choice
Our tenancy, your cloud account or on-premise. The price moves; the product does not.
Your data is not training data
Zero retention at the API level, and no model is tuned on your content without a separate written agreement.
Monthly operations, scaled to traffic
Tracing, drift alerts, upgrades and on-call. Cancellable, and the handover pack is already written when you do.
None of these fits?
Then it is an engagement, not a product — which is how all four of these started. Bring the process and we will tell you straight whether it is worth building.
Bring one process you think an agent could run. We'll tell you straight whether it's worth building — and what it would cost if it is.
