ZeroKTFor delivery leaders at IT services firms
Your engineers rotate. The engagement's context stays.
A session belongs to a client engagement, not to a person. The night shift hands it to the morning shift with the reasoning intact. When an engineer leaves, the engagement keeps their context. Nothing ever crosses between clients.
Walled by engagement
Each client account is isolated. Nothing crosses, and from inside one you can't confirm another exists.
Deletion per engagement
Deleting an engagement removes its files, memory and schedules. Export and a deletion certificate are in build.NEXT
Bring your own keys
BYOK on every tier. Your model spend stays on your accounts.
No training on your data
Your engagements never train a model. Ours or anyone else's.
Two ways context dies
The handoff
It's 2am IST. An engineer is four hours into a production issue with the agent. Three theories ruled out, one lead still open. Shift ends. The GMT team picks it up from a one-line status in Slack and starts over — including the three theories that were already ruled out.
The departure
A senior engineer resigns after two years on one client account. You get a two-week KT window and a folder of documents covering the part that was easy to write down. The half that mattered — why that integration is fragile, which client contact escalates, what was tried in 2023 and failed — leaves with them.
Same problem twice. The work happened inside one person's private window.
Isolation
Every client account is walled.
An IT services firm doesn't have one knowledge pool. It has five to sixty, each under an MSA with a confidentiality clause. ZeroKT walls every engagement — nothing crosses, and from inside one account you can't confirm another exists. When a contract ends, the engagement is archived and purged; portable export and a deletion certificate are in build.
Nothing from Northwind exists inside Contoso. Not the files, not the memory, not the fact that Northwind is a client.
Engagements
Searching in Northwind Trading
3 results
worker-7 retry backoff is sensitive to deploy timing
memory · from session #4821
Session #4821 · payment retries
closed 02:41 · 3 participants
runbook-payments-v4.md
knowledge base · indexed 12 Aug
Memory
The memory builds itself from the work.
Every other AI knowledge tool is upload-first — someone has to feed it, and keep feeding it. ZeroKT is work-first. When a session closes it's summarised and its facts extracted, and that becomes the searchable memory for that client account. Uploads still work for seeding. They just aren't the point.
The next person asks a question and gets an answer from work that already happened.
Sessions
Memory · Northwind Trading
Select a session to see what it contributed.
- worker-7 retry backoff is sensitive to deploy timingfrom session #4821
- Client escalation contact: R. Menon, ops leadfrom session #3712
- Staging does not mirror prod retry configfrom session #3390
Knowledge handover
When someone leaves, their context stays.
Mark an engineer as departing and ZeroKT builds a knowledge fingerprint from their actual session history. Their successor can query everything they ever worked on. Answers come from their sessions and documents. This isn't them.
The successor starts from 142 sessions instead of a two-week window.
The payment retry path assumes staging mirrors prod retry config. It doesn't. Two incidents have come from a deploy changing backoff without staging catching it.
Answers come from their sessions and documents. This isn't them.
Works where your delivery teams already work
Each connection is per-user. The agent acts as you, in your chats and in the work it runs on a schedule.
Connect your tools
Connected today
LIVEGoogle covers Gmail, Calendar, Drive and Sheets.
Next, for Microsoft shops
NEXTMost firms we're building for run on Microsoft. That's why it's next.
In Slack, the agent reads along silently and answers when you @mention it. It asks before doing anything sensitive.
What's live, what's next
We'd rather show you the line than blur it.
- LIVEPrivate workspace — 1:1 chat with the agent, file and image attach, full searchable history
- LIVEClient engagements — a shared space per client account, seedable from an uploaded folder, walled by default
- LIVETeam chat and Slack — @mention the agent to bring it in; it reads along silently otherwise, and asks before sensitive actions
- LIVEKnowledge base — full-text search inside documents, live processing status, cited as reference material
- LIVEMemory — auto-fills from conversation, readable and editable, full version history with restore
- LIVEScheduled tasks — set up conversationally, every run logged and viewable
- LIVEModel and effort picker — admin-approved model list, thinking effort from auto to max
- LIVEIntegrations — GitHub, Slack, Google, Notion, Linear, Dropbox, X
- NEXTSession handoff — explicit ownership, takeover events, reasoning trail inherited by whoever joins
- NEXT“Where this stands” — an auto-generated brief for anyone joining a session late
- NEXTKnowledge handover — query a departing engineer's accumulated context, drawn from their sessions and documents
- NEXTCertified deletion — archive, export, purge, ending in a content-free certificate you can hand a client
- NEXTDelivery agents — weekly client status report, escalation summary grounded in real session data
- NEXTMicrosoft-native — Teams, Outlook, SharePoint, plus Jira and Azure DevOps
Built for firms that run their own delivery
IT and engineering services firms, 50 to 2,000 people. Managed services, AMS, dedicated pods. Teams spanning IST, GMT and EST. Five to sixty concurrent client accounts, most of them running longer than a year. Attrition you've stopped calling temporary.
50–2,000
people
5–60
client accounts
12+ month
engagements
IST · GMT · EST
time zones
If your engineers work inside your clients' systems — their Jira, their Teams — there's nothing here to wall or accumulate. Staff augmentation isn't the fit.
If your organisation has large teams and knowledge that keeps getting stuck in silos, it works the same way for you.
Questions
Join the waitlist
Not a services firm yourself?
Most people reading this know someone who runs delivery. An introduction is worth more to us than a signup.