Handoff
What you actually walk away with.
Every artifact we deliver when an engagement ships. Code in your repo from day one, prompts and configs you can edit, observability you can read, an eval suite that survives us leaving, and a runbook your on-call doesn't curse.
Six artifacts you get
Code in your repo
Every commit lives in your GitHub / GitLab from week one. Branch protections, PR templates, CI configs — all yours. No private mirror, no 'we'll send the tarball.'
Prompts, configs, agent definitions
Every system prompt, every agent config, every eval case in version-controlled YAML/JSON inside your repo. Editable by your team without us.
Observability dashboards
Langfuse instance configured in your account, with the dashboards we used during the build. You see what we saw — daily ops becomes weekly review.
Eval suite + replay infrastructure
20+ seeded cases, CI integration that fails merges on regressions, weekly replay job already scheduled. Named owner on your side.
Runbook + on-call playbook
Written runbook for the agent: how to deploy, how to roll back, how to investigate a bad output, how to retrain. The thing your on-call wishes they had.
Knowledge-transfer session
Two 90-minute working sessions with your team — one for engineers (architecture + ops), one for the business owner (eval review + drift signals). Recorded.
What's transferred to you
- All source code, prompts, and configs — assigned in writing on engagement close
- All API keys, infrastructure accounts, observability accounts — provisioned in your name from day one
- All fine-tuned models (if any) — hosted on your account or exported as weights
- All datasets we created during the engagement — yours, with provenance documented
- All eval suite cases including the ones derived from production — yours
What we keep
- The right to reference the engagement in our portfolio (with your sign-off on what's public vs. anonymized)
- Generic patterns we developed that don't contain your IP
- Aggregate metrics for our internal benchmarks (anonymized)
What happens after handoff
Three patterns. Pick the one that fits your team — we don't push.
Hands-off
You take it from here. We're available by email if something breaks, but no ongoing commitment.
Hourly retainer
Paid as you use it. We respond within a business day for triage, longer for bigger work. Easy to ramp up or down.
Monthly Retainer
Dedicated team allocation for ongoing tuning, new agent additions, eval coverage as the product evolves. Most of our flagship clients renew here.
Want to see what handoff looks like?
We'll share a sanitized handoff packet from a past engagement on request — runbook structure, eval suite layout, the works.
