01 / 09
scroll or ↑↓ · hover the tags for detail
SEATFROG  ·  CONFIDENTIAL — LEADERSHIP ONLY

Seatfrog AI
Operations.

Phased Q3 delivery.

9 JULY 2026DIRK 9 PAGES · 3 MINUTES · 2 DECISIONS AT THE END
02 / WHY

One closed intelligence layer on everything Seatfrog knows.

Queryable by any person or agent we authorise. Served to no external LLM. Portable across model providers — if tokens spike or a vendor dies, we move.

03 / THE COMPONENTS

What it's composed of.

C1Agent-ready surfaces Every company system reachable by agents through a standard gateway, with access controlled per person, per system, per action. IN FLIGHT
C2Semantic layer The warehouse labelled, so answers are only trusted where the data is documented — with a catalogue tracking owner, tier and PII for every table, and an agent keeping the labels honest. TO BUILD
C3Orchestration standard A standardised way to build agentic workflows — deep enough for engineers, simple enough for everyone else to build their own. IN FLIGHT
C4Governance & evals Human sign-off where it matters, and automatic quality testing — running two agent approaches against each other and scoring which performed better, the way marketing A/B tests campaigns. IN FLIGHT
C5Interfaces Ask in Slack, in Claude, in the Intelligence product, or over the partner API — the answer comes from the same place. LIVE
04 / INFORMATION SURFACES

Where the information lives.

A surface is anywhere company information sits — the warehouse, Slack, the support desk, the codebase. Each one has to be wired up before agents can use it. These are the ones that matter, and where each stands.

Snowflake + CortexThe data warehouse. Powers the TOC chatbot today; internal access is still narrow.IN FLIGHT
AWS telemetryProduction logs, alarms and service data — the raw material for investigation agents.LIVE
Rail industry dataFares, timetables, reservations, routeing — the Brain, queryable by people and agents.LIVE
GitHubAll source code. Bots raise and review PRs daily; a person merges every one.LIVE
Zendesk45k customer tickets a year. Agents read everything; replies stay human-confirmed.LIVE
LinearDelivery reality — every ticket, project and comment, queryable for analysis.LIVE
SlackWhere decisions actually happen. Bots post today; the archive needs a company home.IN FLIGHT
AmplitudeProduct analytics. The connector works; the event data itself can't be trusted yet.TO BUILD
…and ~30 moreBraze, Notion, Drive, RudderStack, Embrace, app reviews — catalogued the same way.CATALOGUED
05 / MEASUREMENT

How we measure it.

Every agent logs what it did and the time it saved into one analytics store, at the moment it does the work. The same method applies to every workflow we deploy, so usage, outcomes and cost are queryable at any point — the readout comes from the data, not from anyone's impression of how it's going.

Time saved per engineer, per month
NOW16.5 h
per-task benchmarks × logged usage · q2
PR lead time
NOW−77%
since claude-native delivery · github timestamps
Alerts investigated to root cause and ticketed, without a person
NOW40 in week one
investigations-bot
Refunds processed automatically
NOW188 · £7k in a day
emr crash day · darwin engine
Sessions, turns per session, and a did-the-user-get-value score for every Ask Intelligence chat
NOW40 turns, one session
value score lands with the eval harness · chat log
Agent diagnoses fixed at PR level — next, fixed with no person at all
NOW3 of 40 in flight
investigations-bot · linear
06 / COMPOUNDING

The compounding effect of incremental progress.

Each shipped step becomes infrastructure for the next, so the value we're getting at each step compounds. Avoiding a big bang release is the clear choice.

seatfrog-mcp Built so engineers could investigate production. Now run by customer support, the helpdesk bot, and the investigations bot. REUSED
The Brain Built to answer operator questions. Now behind the TOC chatbot, pricing analysis, and a government policy briefing. REUSED
The skills loop Every Claude session can propose improvements to the shared tooling — 17 accepted this week, each reviewed by Charlie before merge. GROWING
07 / THE WAREHOUSE

Most of the warehouse isn't usable by agents yet.

Tables the agent account is allowed to query23%
Core reporting models with written descriptions36%
Staging models with written descriptions13%

An agent can only use a table if it has been granted access and the table says what its columns mean. Without that, the AI guesses — which is why Ben only trusts answers that come from the documented part. Phase 1 grants the access and writes the descriptions for the data that matters most. From then on, an agent checks that every new source lands labelled and accessible, so coverage keeps climbing as the warehouse grows instead of decaying. Two more fixes ride along: one login pattern so agents can run on a schedule in the cloud rather than on laptops, and moving the systems that currently sit on personal machines into company ownership.

08 / THE PLAN

Q3, in three phases.

01 Get the data in shape
Write descriptions and grant access for the most-used warehouse data. Connect the remaining systems — Amplitude, Embrace, Notion, Drive. One login pattern so agents run unattended in the cloud.
WEEKS 1–4
02 Standardised builds
One standard platform for building agent workflows, so marketing, ops and CS build their own rather than queueing on engineering — CrewAI trial running now. Written rules for what agents may do without a person.
OVERLAPPING
03 First deployments
The alert-investigation bot's fix loop (already running) · the CS helpdesk agent (in flight) · an automated QA process for the growth team · pricing automation for revenue management · experiment analysis, built directly with Aaron — the multiple-validations-a-week capability he's asked us for. The product decision companion is what the ask-anything interface becomes as coverage grows.
EACH STARTS WHEN THE DATA (01) AND PLATFORM (02) IT DEPENDS ON ARE READY
FROM WEEK 4
09 / DECISIONS

Two decisions.

DECISION 01
Charlie
Confirm the secondment. I action it Monday.
DECISION 02
Leadership comms
Proposal: Olu and Sophie get the operational bits Monday. The full plan lands at your return walkthrough.