Systems
Nobody wants a blank agent canvas and a year to fill it in.
That is what a generic platform sells you: an empty policy screen, a free trial, and the job of working out — usually during an audit — which actions an agent should never have been near. A system arrives with that argument already had. The agents, the workflows, the interfaces, the connectors and the rule table for one kind of business, on top of the limits the operating system enforces underneath.
Five multiple-choice questions. A person replies within one business hour.
The idea
A tenant, not a template.
Most vertical AI is a template pack: a folder of prompts, two integrations and a demo that goes well. Underneath it, the agent still has broad access, the limits still live in a system prompt, and the consequences are still entirely yours.
A system here is a tenant of the operating system. It brings the vocabulary of one industry — an order, a consent record, a matter, a work packet — and the rule table that industry already lives by. What sits underneath is unchanged and is not negotiable by the system on top: every action carries a risk tier, unattended agents are capped below anything irreversible, the irreversible waits for a named person, and every decision including every refusal is written down.
The practical effect is dull and valuable. The argument about what an agent is allowed to do happens once, at the operating-system layer, with your security and compliance people in the room. Every system after that inherits the answer.
Three words, used literally
None of the four below is Live, and we are not going to pretend otherwise.
Every system, module and capability on this site carries one of three labels. They are not marketing tiers. They are the difference between something we can show you this afternoon and something we would build with you — and reading the badge before the paragraph will save you a call.
- Live
- Running today. We can show it to you on a call.
- Preview
- Built and running — for one client or on part of the surface. Being packaged.
- Design partner
- Designed and reviewed, not yet built. We build it with the first customer.
The four
Find the bad day that is yours.
Commerce
PreviewEvery customer answered. Nothing said that you did not approve.
The question that cost you the sale arrived at twenty to midnight and was answered at nine. The assistant replies in seconds using wording you approved, captures the order, and hands anything it cannot answer to a person — rather than inventing a policy in your name.
- Approved answers sent verbatim, never model-written prose
- Orders, payment evidence and order status
- Human handoff with an attention queue and the context attached
Kivara
Design partnerPut AI agents to work without putting your licence at risk.
An assistant that answers a licensed question is not a support incident; it is a complaint with your licence number on it. The design puts a governed front door in front of the CRM you already run, and leaves the regulated act with the person who is allowed to perform it. Specified and reviewed across three model families, and not yet built.
- Enroll-Ready — the insurance and Medicare front door
- Front Door — virtual care intake, scheduling and escalation
- Clear-to-Close — lending document intake, later
Leadnix
PreviewFrom brief to campaign, with every claim checked before it ships.
A campaign tool that can publish can publish at three in the morning, and a claim nobody checked is the one the regulator reads back to you. A brief becomes governed copy, media and a launch packet; publishing and spending stop at a named person. Running inside our own company; no external customers yet.
- Brief to copy, media and launch packet
- Claims reviewed and approved before anything publishes
- Spending requires a person, every time
Forge
PreviewAutonomous development needs contracts, not vibes.
The agent wrote the change in four minutes and the tests are green, and nobody can say what is in the build. Goals become scoped work packets, agents build in isolation, a different model family attacks every change, and proof gates decide what is promoted. Live on our own governed software delivery; customer repositories are design-partner work.
- Scoped packets with owned paths, not a free-roaming agent
- An independent adversary on every change
- We build VertixOS this way, under the same gates
Blueprints
Four more that are drawn, and not built.
Each of these is a reviewed blueprint: the job, the rule table and the interfaces exist on paper and nowhere else. They are listed because knowing what we have thought about is useful to you, and because the first customer in each one decides what it becomes.
Legal Desk
Law firms
Design partnerThe intake problem first: the call nobody picked up, the enquiry that sat overnight, the matter opened by hand at the end of the week.
Front Desk
Clinics, trades and local services
Design partnerThe phone rings while everybody is busy with the person in front of them, and by the evening that enquiry belongs to somebody else.
Creator Back Office
Creators and small studios
Design partnerThe work between the idea and the post: drafts, pricing, cut-downs, and knowing what a month of it is allowed to cost.
Proposal Desk
Government contractors
Design partnerCapture and proposal work, where the deadline is fixed, the compliance matrix is the real document, and everything is late.
Design partner is not a waiting list and it is not a discount for beta software. It means we build the thing with you, against your rule table, and you are the first person it has to work for.
Straight answers
Before you pick one.
Pick the workflow that costs you the most.
Whichever system you end up with, the first step is the same: a measurement of your own operation — how long people wait, what repeats, what an agent could take and what it must never touch — which is yours to keep whether or not you buy anything else.
Five multiple-choice questions. A person replies within one business hour.
Autonomy where it is safe. A human where it is not.