March 2026
Where we are on our go-live programs, a live Edge demo, how Kai is changing the way we work, and what AI means for Kaptio.
KTM Spotlight — Private & Confidential
Go-Lives
Our go-live programs are under pressure. We've had slips across the portfolio, and the leadership team is now in daily support mode to ensure no further slips occur.
Our Response
Monitoring how program scope is evolving day by day
Understanding throughput and identifying blockers early
Supporting teams in making the right trade-offs for go-live
Adjusting cadence to accommodate and prevent further slips
New Tooling
Unified Jira fields — Program, Go-Live Scope, and Scope Status — so every team looks at the same data. This is how we drive the daily check-ins.
Why this matters: Further slips are very costly — for us and our customers. Jon, Unnur, Nick, and Ragnar are in daily delivery support.
Program Scorecard — Live Data
Target
May 5
Backup: May 19
Scope Triage
100% triaged
Remaining
28
of 34
18% done
Velocity
13/wk
Avg done (8 weeks)
2/wk reopened
Active Work
Upcoming Releases
C14-END-3
Mar 16 · 1 wk left
Done
C15-MID-1
Mar 23 · 2 wks left
Tight
21 remainingC15-END-1
Apr 20 · 6 wks left
Past cutoff
Reality Check: Mid-case forecast Mar 30 at 12/wk · 5 days past stable release target
The Mission
We're here to support, not to second-guess. The teams have delivered remarkable things on incredibly demanding programs.
Edge Platform
Tomas will walk us through the latest Edge capabilities.
TG
Tomas Gudmundsson
~5 minutes
Kai
From commercial to engineering to services — Kai is an active member of the team, answering questions, writing code, building proposals, and learning from every interaction.
By the Numbers
893
Total mentions
910
Interactions logged
271
Last 7 days
81%
Resolution rate
301
Deep investigations
198
Quick answers
149
Content plans created
Weekly Volume Growth
W1
W2
W3
W4
W5
Now
Bjarki + Kai wrote and iterated a playbook over days. Executed the first site-license-to-named-users migration — years in the making. Clear path to solving overage for all customers. Kai also researched bulk API assignment for 800+ user orgs.
Bryn asked Kai to assess the Newmarket RFP. Kai built an RFP tool, loaded 10 historical RFPs, scored 5 categories, delivered "Conditional Go" with 8 validations. More rigorous than Notion AI on key risks.
Greg posted edit requests for the Viking China proposal deck. Kai applied every change, pushed live to spotlight.kaptio.com. Rebecca and Greg confirmed.
Services & Implementation
Tomas shared a Notion draft. Kai created a full scoping file: 13 assumptions, 14 open questions, 7 outcomes — live on enablement.kaptio.com within minutes. Every gap marked "missing context."
Scoping tool now generates Statements of Work from structured data + reference SOWs. Outcomes, delivery plans, RACI, workshops, commercial estimates — all synthesized.
Kai queried the Bunnik DEV1 org via SFDX, verified cleanup of deprecated packages (15 removed), PNR data (162 child records gone), package departures reduced from 609 to 219.
Engineering & Product
Stephen traced production errors through triggers, API registry, payment versions. Kai found the root cause and walked him through resolution.
Caine drafted responses to Intrepid. Kai code-checked margin config, rounding, promotions. Corrected specifics. Ready-to-send.
Explained Hawaii → Iceland release transition to Grace. Bridging release management knowledge across the team.
Sam couldn't save adjustments on inactive passengers. Kai dug through LWC code and found the exact custom permission dependency.
Kai's Brain
20 facts/user
Who you are, what you care about
30-day decisions
Channel topics and team decisions
"Things I've been told"
Attributed, with confidence scores
Quiet Sunday
"Quiet day — no requests came through. Enjoying the silence."
— Kai, End of Day, Sunday March 8
In Their Words
"What sorcery is this.. Kai, where have you been all my Kaptio life"
— Bjarki, after the license migration
"It was great talking to Kai. I don't quite think we're friends just yet, but give it time I'm sure we will be."
— Nick Flew, after the January onsite
"I had a request from Kai's second in command (Ragnar)..."
— Nick Flew, to the release management group
"Well done Ragnar, Bjarki and Kai, best of friends"
— Tracy Sharp
Live from Kai's Memory
Ragnar
193 interactions · 20 stored facts
Thinks in systems. Builds tools to solve problems rather than managing around them.
Constantly preparing board talking points, investor updates, strategy content.
Workflow: proposal, approval, implementation. Sequential thinker.
Flags things for human review when confidence is low. Practices what he preaches.
Analyzes competitor pricing at midnight.
Unnur
16 interactions · 20 stored facts
Excited about building with Kai. Her first project with him was a presentation she iterated on in rounds.
Gives detailed feedback. 10 points on one presentation alone.
Prefers not to share specific numbers externally. Saves detailed metrics for QBRs.
Wants to be notified when things are published.
Has experienced repeated deployment failures. Keeps going.
Rowan
7 interactions · 11 stored facts
Values human insight over AI capabilities for strategic work.
Appreciates when Kai is honest about limitations.
Deep in promotions, pricing discrepancies, cruise booking flows.
Responsible for approving enablement guide content.
Healthy skeptic. Exactly the kind of person who makes AI better.
Want to see yours? Ask him: @Kai what do you know about me?
queried live from production db
AI at Kaptio
AI is changing our industry and our company. We need to talk about it openly — what it means, how we feel about it, and how we shape it intentionally.
What We're Hearing
"I feel secure in my role"
Dropped to the 6th lowest scoring question company-wide in February — up from 22nd place. The trend started in Engineering in January.
Source: Officevibe, February 2026
This is real and we need to address it. AI is not going away — but the answer isn't silence, it's intentional design of how we work with it.
The Frame
We are building AI teammates and new ways of working that have AI embedded into reaching an outcome. This is not about technical training — it's about behavioral change and designing how humans and AI work together.
"Organizations that succeed will not be those that automate the fastest, but those that channel efficiency into reinvestment, fueling new forms of value creation."
— Deloitte Human Capital Trends 2026
AI Values
Share prompts, patterns, artifacts. Use Kai for cross-role knowledge. Be clear when AI helped.
Treat prompts and templates as iterated products. Run small experiments, publish learnings.
Humans stay accountable for decisions and customer impact. Verify before shipping. Escalate when confidence is low.
Model curiosity. Help others build confidence. Reinforce quality gates as enablement, not red tape.
New — AI Practice Library
We've launched a practice library where anyone can contribute the prompts, patterns, and lessons they've learned working with AI. 9 practices live today, organized by our four values.
Prompt
Use @Kai in Slack to surface existing knowledge before spending time searching manually.
Pattern
Version them, test them, refine them, share what you learn.
Checklist
A checklist for validating AI content, code, and analysis before it reaches customers.
enablement.kaptio.com/practices
We'll share this on #team-kaptio today.
How We Work with Kai
Kai will never have DMs with our team. He lives in open channels because that's where the whole team benefits. The context locked in private DMs is invisible to Kai — and to your other teammates too.
When we move conversations into open channels, Kai becomes a better teammate — and so do the humans. Stop siloing information in private DMs.
Contribute a practice
Say @Kai save this as a practice in any Slack channel.
Coming Next
End-of-March KTM — Ian and Janet will present how we're evolving Services. Not just program updates. A new way of thinking about what we deliver.
"Measure outcomes, not activity."
Stop tracking tickets closed and process steps completed. Start tracking: customer problem resolved, time-to-resolution, and did they come back with the same issue.
The Direction
The question isn't whether AI changes Kaptio — it's whether we shape that change intentionally. That's what we're doing.
How does this land? Questions, reactions, concerns — let's talk.