# Go fully agentic, one value stream at a time

> Map a value stream, build its first agentic app with the people who run it in 2 to 4 days, put it on rails, then do the next one on the same platform.

Source: https://paddington.io/companies

For companies

# Go fully agentic, one value stream at a time.

Company-wide AI programmes stall because they start from tools. Start from the work instead. Pick a value stream, put agents on it with the people who run it, on infrastructure you own. Then do the next one, faster, on the same platform.

[Request beta access](/signup)

The board

## See the whole company, step by step.

Every value stream, every step, marked by how much of it agents do and whether they do it on rails. It is the plan, the progress report and the risk register in one view.

Value streams · Acme Insurance example

| Value stream | Intake | Triage | Decide | Act | Record |
| --- | --- | --- | --- | --- | --- |
| Claim to payout | on rails | on rails | agentic | agentic | assisted |
| Quote to bind | agentic | assisted | manual | manual | assisted |
| Issue to resolution | assisted | assisted | manual | assisted | manual |
| Procure to pay | manual | manual | manual | manual | assisted |
| Hire to onboard | manual | assisted | manual | manual | manual |

manual assisted: a person uses AI agentic: agents act, people approve on rails: agents act, rails decide

**5** value streams mapped

**4 of 5** steps agentic in claim to payout

**2** steps on rails

**Next** quote to bind

The method

## Four steps, then repeat.

The second stream costs less than the first: identity, data, policy and the portal are already there.

Step 1 · one week

#### Map

Walk the stream with the people who run it. Mark every step manual, assisted, agentic or on rails.

Step 2 · 2 to 4 days per app

#### Build with the team

A business applications engineer builds the first agentic app with the front-line team, on Kilter.

Step 3 · before it acts

#### Put it on rails

Airbender ARC decides every consequential action and keeps evidence of each decision.

Step 4 · then

#### Measure and move

Measure the stream's outcome, move the next step, then the next stream.

Shipped

## Two apps, built on Kilter.

Real applications built on Kilter. The payoff shows up twice: the application shrinks, and the parts you'd normally get wrong move into infrastructure you can read.

Healthcare · HIPAA

### A regulated publishing platform, built in 45 minutes

The compliance surface moved off the application and into infrastructure you can point an auditor at, so the app stayed tiny and the controls stayed provable.

-   Access control → Postgres row-level security (the database says no, not an if-statement)
-   Immutable 6-year audit trail → statement-level triggers the engine physically enforces
-   Author → clinical → compliance approval → a Temporal workflow that can't be sidestepped
-   Identity & PHI-handling agents → Ory principals, every action audited with provenance

Postgres RLS Temporal Ory TanStack Python agents

ITSM · ServiceNow replacement

### An agentic ITSM platform where the engine is the product

The lifecycle, the audit, and even the UI's safety moved into canonical primitives: one universal record, one mutation door, an AI-generated interface a dumb renderer paints from an allowlist.

-   Every lifecycle (incident, change, approval, SLA) → a durable Temporal workflow
-   One universal work\_item + one withMutation door → tx, audit, and outbox, atomic
-   Event-driven, not event-sourced → Postgres is truth, Kafka builds projections
-   AI-generated SDUI → a schema-validated, signal-allowlisted renderer that can't surprise

Temporal Kafka Postgres+pgvector Ory SigNoz bifrost LLM

Start with one stream

## Map a value stream with us.

One week with the people who run it. You leave with the board, the first app to build, and the steps to put on rails.

[Request beta access](/signup)