/P

/ process · 5 stages · ~12 weeks to prod

How we ship.
No pivots, no PoC graveyards.

AVG CYCLE · 0 WEEKS
SLIPPAGE · <0%
AGENTS.SHIPPED · 31 ◆AVG CYCLE · 12 WEEKS ◆SLIPPAGE · <4% ◆OPEN SLOTS · 1 / MONTH ◆ON-CALL P1 · < 15 MIN ◆DATA-RESIDENCY · EU ◆REPO-OWNED · YOUR ORG ◆ROLLBACK · 1-CLICK ◆AGENTS.SHIPPED · 31 ◆AVG CYCLE · 12 WEEKS ◆SLIPPAGE · <4% ◆OPEN SLOTS · 1 / MONTH ◆ON-CALL P1 · < 15 MIN ◆DATA-RESIDENCY · EU ◆REPO-OWNED · YOUR ORG ◆ROLLBACK · 1-CLICK ◆
/ the rail · click a step
01
1–2 weeks · Fixed · €12k

Discover

Sit with your team. Map data, pain, ROI. Walk out with a ranked use-case list.

We embed 2–3 of our people with your ops and engineering leads. We audit the data — what exists, what is usable, where the access lives. We sit in on actual work: support queues, trading desks, underwriting rooms. Then we write a 25-page artifact: ranked use-cases, ROI math, build-vs-buy per candidate, and a sequenced roadmap.

team
1 principal · 1 ML eng · 1 domain analyst
WHAT WE NEED FROM YOU
01Stakeholder access (ops, data, exec)
02Data catalog (if you have one)
032–3 shadowing sessions
DELIVERABLES
#01Ranked use-case list with ROI math
#02Data readiness audit
#0312-month roadmap
#04Build-vs-buy recommendation
#05Go / no-go decision memo
/ typical timeline

Week 1 to production.
One chart.

◀ swipe ▶
WEEK
01
02
03
04
05
06
07
08
09
10
11
12
13
14
01 · Discover
02 · Architect
03 · Build
04 · Integrate
05 · Operate
fixed scopebuild (T&M)ongoing retainer
/ how we actually work

Six rules
inside every stage.

01

Week 1 you see code

We do not spend a month on slides before writing anything. By end of week 1 you have a prototype running against real data.

02

Your repo, not ours

All code lives in your organization from day 1. We push to your branches and request your reviews.

03

Eval before prod

No agent goes live without a replayable eval harness and a named owner for the golden set.

04

Reversible cutover

Shadow → co-pilot → autonomous. Each step has a written go-back procedure.

05

One team, not two

Our engineers join your standups. Your engineers review our PRs. Integration is the product.

06

SLOs on paper

Latency, accuracy, kill-switch latency, cost-per-decision — all agreed and logged before build.

/ FAQ

Questions
we always get.

How fast can we start?
Typical discovery kicks off 2–3 weeks after a signed MSA. We keep one principal slot open each month for urgent engagements.
Do you work fixed-price?
Discovery, Architect, and Integrate are fixed-price. Build is T&M because scope genuinely changes. Operate is a monthly retainer.
Can we stop at any point?
Yes. Each stage is independently billable and terminable with 5 business days notice. You keep all code and artifacts regardless.
Who owns the models and code?
You do. Always. We license nothing to you — everything is in your repo under your license of choice. We reuse learnings, not assets.
Do you handle regulated industries?
Yes — SOC2 Type II, HIPAA, PCI-DSS, EU AI Act. Compliance lead joins from Architect onwards, not retrofitted at the end.
What if the model provider changes?
Every agent ships with at least one fallback provider and a model-abstraction layer. Switching is a config change, not a rewrite.
→

/ start at stage 01

Discovery opens
every month.

Fixed price, two weeks, no commitment to build. You walk out with a ranked list of what's worth doing and what isn't.

Book discovery 2 weeks · €12k hello@kiz8.com