Pilots open · for delivery, sales and supply chain teams
Kokum gets decisions confirmed by everyone before the call ends, finds the right owner and warns you early if work is likely to slip.
Free 30 minute call. You keep the written plan, whether or not you go ahead.
Kokum is in design partner pilots. On your first call we’ll show you exactly what’s live for your workflow.
Sound familiar?
Say it once. Kokum makes sure it happens.
No retyping notes into a tracker. No second call to confirm. No status meeting to ask what changed. No context lost when work changes hands.
The film
Six short chapters from one fictional go live. Choose one to start the film there, or watch it all.
Chapter 1 · 0:00
On the call Decisions confirmed by everyone, before the call ends.
Chapter 2 · 0:19
Crossed out, not deleted The old date keeps its source. The new one is current.
Chapter 3 · 0:24
Scores Slip risk on every promise, with reasons.
Chapter 4 · 0:33
Agents Agents check with each other, then with you.
Chapter 5 · 0:54
Every team and every fix Connect another team, and less falls between you.
Chapter 6 · 1:04
No double work No second call. No retyping. No status meeting.
On the call
When Kokum hears a decision, it shows you the exact line. One click asks everyone to confirm it before the call ends. It listens only with everyone’s consent.
Heard at 34:12. Confirmed by Priya, Marta and Dana at 34:41.
A passing maybe doesn’t become a task. Remarks with low confidence are logged as discussed, not decided.
Confirm each decision or mark it not decided. Select a decision to see the line it came from.
Marta · Halden IT · 33:48
Our identity team is moving us to Entra ID. SSO can’t finish before the 9th.
Dana · Engineer, Austin · 34:02
Then the 7th is off. Staging needs two clear days.
Priya · Engagement lead · 34:12
Let’s move go live to the 14th, if SSO passes staging by the 11th.
Arjun · Engineer, Pune · 34:26
I can take SSO from Friday. My morning is Dana’s evening.
Marta · Halden IT · 34:31
Works for us. I’ll let procurement know.
Dana · Engineer, Austin · 34:52
Maybe we skip the MFA test for now?
Priya · Engagement lead · 34:58
No. Keep it in.
Marta · Halden IT · 35:06
Can we book Wednesday at 8:30 for the next check in?
Heard a decision
Move go live to 14 Oct, if SSO passes staging by 11 Oct
“Let’s move go live to the 14th, if SSO passes staging by the 11th.”Priya · 34:12
Heard a decision
Skip the MFA test for now
Low confidence · countered at 34:58
“Maybe we skip the MFA test for now?”Dana · 34:52
Heard a decision
Book the next customer call for Wed 1 Oct, 08:30
“Can we book Wednesday at 8:30 for the next check in?”Marta · 35:06
Scores
Kokum scores every promise three ways: how likely it is to slip, who should own it, and how sure Kokum is of each fact. Every score shows its reasons.
For leaders, one list: every promise at risk, why, and who owns the fix.
Active go lives6At risk1
Fictional exampleHalden go live · 14 Oct
Pushing it up
Pulling it down
Learns from your own delivery history. Until there’s enough of it, Kokum says so instead of guessing. The band shows how sure it is.
Arjun M. · Pune
0.91strong match
Arjun M.0.91Pune · strong match
Dana R.0.48Austin · weak matchDana Austin17:30 CDTArjun Pune09:00 ISTGo live · 14 Oct
0.97high confidence
Figures come from a fictional example.
Agents
Kokum’s agents check with each other, draft work for you to approve, and answer questions wherever you already work. They only act within the permissions you set.
1A2A · agent to agent
The delivery agent asks the supply agent if Halden’s portal orders can still start the week of 19 Oct. The answer is checked against real capacity.
Can ask other agents · can’t change orders
In the example, the delivery agent asks: Portal orders from 19 Oct? The supply agent answers: Yes, capacity checked in ERP.
2A2H · agent to human
Herald drafts the update for Halden and sends it to Priya in Slack with Approve and Edit. Nothing reaches the customer until she says yes.
Can draft · can’t send to customers without approval
In the example, Herald’s update for Halden reads: Go live moves to 14 Oct, if SSO passes staging by 11 Oct. Approver: Priya S. Priya approves, then it is sent to Marta K.
3H2A · human to agent
Arjun asks “What changed overnight?” from Slack, Claude or ChatGPT. He gets the handoff, the failing tests and the decision behind them.
In plain words: Claude and ChatGPT connect to Kokum through MCP, an open standard that lets AI assistants use tools with your permission.
In the example, Arjun asks his assistant: What changed overnight? Kokum answers through MCP: Go live moved to 14 Oct. You own SSO. 2 of 14 tests failing. Dana’s notes attached.
Scout reads email and calls
Scribe joins your calls
Planner matches people and time zones
Verifier runs the tests
Herald drafts the updates
Which ones are live for you is confirmed before your pilot starts.
Trust
Kokum doesn’t ask for blind trust. Every fact links to its source and time, every score shows its reasons, and anything uncertain goes to a person first.
Open any fact to see where it came from: the call and the minute, the email, the system.
Low confidence items go to a person. A passing maybe doesn’t become a task.
Anything bound for a customer waits for approval from the person you choose.
Better with use
Start with one team and one workflow. Each team you connect and each fix you review adds to what Kokum knows.
One team
Every team, system or partner you connect adds what it knows, so less falls between you.
+ Sales
Connect sales: what was promised on the deal call is delivery’s scope on day one.
+ Supply
Connect supply: a late shipment shows every customer date it touches.
+ Halden IT
Invite your customer: Marta’s SSO date arrives as a fact, not a forwarded email.
Customers and partners see only what you choose to share.
The graph starts with one team: Priya, Dana and Arjun with five agents, and three open questions. Sales joins and answers the first: promised SSO in phase 1. Supply joins and answers the second: portal orders the week of 19 Oct. Halden IT joins, outside a line marked shared with permission, and answers the third: SSO ready on 9 Oct.
In plain words: this is a network effect. Each new team fills in what the others couldn’t see.
Your team stops solving the same problem twice. Reviewed fixes become patterns, and Kokum checks each one still fits before it’s reused.
01What happened, next to what was planned.
02A person reviews the fix.
03It’s saved as a pattern, with its source and version.
04It’s checked against the next customer before reuse.
Fictional example: Halden’s SSO setup started with 8 of 12 steps from a reviewed pattern.
Patterns stay inside your company. Nothing learns from a correction nobody reviewed.
Compare
AI note takers, chat assistants and project trackers each do part of the job. Kokum connects the parts and carries the work through to done.
| Outcome | Kokum | AI note takers | Chat assistants | Project trackers |
|---|---|---|---|---|
| Decisions confirmed by everyone | On the call, before anyone hangs up | Notes and a summary | Only if you ask | Someone types them in |
| Knows which fact is current | Source and time on every fact. Old ones crossed out. | Each meeting on its own | Whatever is in the chat | Last edit wins |
| Warns before something slips | Slip risk on every promise, with reasons | No | Only if you ask | Only with rules you build |
| Finds the right owner | By skill, capacity, access and time zone | Names in action items | No | You assign it |
| Moves work forward on its own | Agents coordinate and draft. You approve. | Sends the notes | When you prompt it | Rules you build |
| Works across teams and companies | One live record, customers and partners included | One meeting at a time | One chat at a time | One project at a time |
| Asks a person when unsure | Yes. Low confidence goes to a person. | No | Varies | Not applicable |
| Gets better with use | Reviewed fixes become patterns | Templates you set | Remembers your chats | No |
Based on how each category typically works today. Products vary, and many are great at their part. Keep the ones you like: Kokum works with your tracker and your chat tools.
Start with one workflow.
Get a pilot planUse cases
Kokum works the same way in every workflow. It hears the decision, keeps the facts current and makes sure the right person gets it done.
When a go live date moves
Every task, test and customer update that depends on it moves too, each with an owner.
When a deal closes
What sales promised becomes delivery’s scope on day one, with the call it came from. No second discovery call.
When a shipment slips
Kokum traces the orders and customer dates it touches, so new dates are promised with the full picture.
When an urgent ticket touches a renewal
It links the ticket, the account’s promises and the engineer on call, then drafts the customer update for approval.
When a statement of work is signed
It turns the SOW into scope, milestones, staffing and acceptance tests, so the team starts with a plan, not a meeting.
When a new partner signs
It plans certification, system access and first deal support across the partner’s time zones.
When a cutover weekend is planned
It sequences data loads, tests and rollback, with a named approver at every gate.
When a release date moves
It finds every customer, contract and enablement plan that depends on it, and tells each owner.
Don’t see yours? If a promise crosses a team, it probably fits.
Get a pilot planWe kept seeing the same thing. A good call. Everyone agrees. Then the date moves in an email nobody forwarded. The person who owned the next step goes offline for the night. And the customer hears about it before your team does.
Nobody did anything wrong. The promise just fell between people.
AI note takers made the notes better. They didn’t make the work happen. So we built Kokum for the part after “sounds good”: confirm the decision while everyone is still there, keep track of what’s true, and make sure the right person gets it done.
If there’s a promise your team keeps missing, we’d really like to hear about it.
Pilot
Tell us where work falls between teams. On a free 30 minute call we’ll scope one workflow, then write up the baseline, the measures and what’s live for you.
| Measure | Today’s baseline | During the pilot |
|---|---|---|
| Time to start | Measured in week 1 | Measured weekly |
| Rework | Measured in week 1 | Measured weekly |
| Handoff completeness | Measured in week 1 | Measured weekly |
| Decision accuracy | Measured in week 1 | Measured weekly |
Template. No results yet.
Kokum is in design partner pilots. On your first call we’ll show you exactly what’s live for your workflow.
No. Kokum drafts tickets in your tracker and works alongside your note taker. It adds what they don’t do: decisions confirmed on the call, current facts, the right owner and tracking to done.
Nothing counts until the people on the call confirm it. If it’s wrong, they correct it or mark it not decided, right there.
Every fact has a source and a time, and every score shows its reasons, so a wrong one is easy to spot and correct. Low confidence goes to a person, and nothing reaches a customer without approval.
You choose each source and what it can see, and everyone on a call is asked for consent. Agents act only within the permissions you set, and your security team gets a walkthrough before anything connects.
Your private notes stay private, and patterns stay inside your company. Nothing is shared across customers. Retention and deletion are agreed before your pilot starts.
Not really. Kokum works from your calls, email, Slack and tracker, and you can ask it questions from Claude or ChatGPT. Pilots start with one team and one workflow.
The scoping call is free, and you keep the written plan either way. Pilot terms are agreed on that call, before anything starts.
Kokum is in design partner pilots. On your first call we’ll show you exactly what’s live for your workflow. Connectors are confirmed for each pilot.
