Deployment Sprint
Two weeks. One FDE. One real workflow.
One FDE, one real workflow, two weeks. You get a working deliverable and a production plan. If it's not worth it, you get a full refund and keep the code.
It is the lowest-risk way to find out what a Forward Deployed Engineer does inside your systems, before you commit to a pod or a white-label deployment.
What happens in two weeks
Week 1: Discover and Embed
We pick the workflow together and define done with a metric. Your FDE joins your Slack, your repo and your standups.
Week 2: Ship
The FDE builds the deliverable in your infrastructure and writes the production plan: what it takes to go live, what could break, what to do about it.
What you walk away with
A working deliverable, running on your systems.
A production plan: integrations, guardrails, evals and hand-off, with a timeline.
A fixed fee, agreed before we start.
Full refund if it's not worth it. You keep the code either way.
Questions we get
- What do you need from us?
- Access to the workflow, the data and the systems, and one person on your side who owns the metric.
- What if we're not convinced?
- Full refund. You keep the code and the production plan.
- Can the sprint turn into a pod?
- Yes. The production plan is the Discover phase of an AI Deployment Pod, already done.
Pick the workflow. We'll take it from there.