Everything in self-serve, plus a scientist who runs it with you. A Forward-Deployed Scientist is a builder who embeds in your team and works in your production environment, not an advisor, not a consultant writing decks. They run the improvement loop with you until a metric moves, then hand it back so your team runs it.
How the work happens
System Knowledge: In weeks 1–2 your scientist builds knowledge-book v0 with you, ingesting the tribal knowledge that lives in your team’s heads.
Agent Studio: Your scientist formulates hypotheses, generates multiple approaches, and tests them in parallel. You see the plan before anything ships.
The 8-week loop (single metric)
Two metrics (e.g. pricing and recommendation) extend the same loop, typically 12 weeks.
How the handback works
Your team doesn’t watch from the sidelines. Across the engagement they move from observers → co-builders → operators: shadowing the first tests, then driving them with your scientist alongside, then running the loop on their own. You’re left with the moved metric and the people and playbook to keep moving it.
What we ask of you
Self-sufficiency is real work, not a switch we flip on the last day. It needs you to name the people who’ll own the loop and give them time on it during the engagement.
This is bounded, not a services contract
The engagement is time-boxed and self-liquidating. It sits on the Pavo platform - reusable primitives, not bespoke code only we can maintain - so when we leave, nothing breaks. A healthy engagement needs less of us over time, not more.
What stays yours
The same isolation as self-serve - a per-client service account, your code and data never leaving your setup - plus a self-sufficient team at the end.
How to start
One conversation to find the problem worth solving. Book a demo, no procurement gauntlet to begin.
