Deployment Framework | Market Horizon
The Market Horizon deployment framework: a five-phase engineering plan from scoping to production to expansion, with clear SLAs, approval queues, and customer responsibilities.
How We Ship
Deployment Framework
Market Horizon deployments are run as engineering projects, not as transformation programs. The framework below is the same one we use across every engagement, from a single use case to a portfolio of 24.
Phase 1 — Scoping (Week 0)
- One working session with the operating team. We map the workflow, the systems it touches, and the decisions it makes.
- We size the engagement honestly. If it does not fit, we say so on the call.
- Output: a written scope, an SLA target, a data-handling plan, and a price.
Phase 2 — Build (Weeks 1–3)
- Data-source integrations and read-only ingestion stood up first. We do not touch systems of record before that.
- Agent personas configured against the customer's actual rules, escalation paths, and tone of voice.
- Operator console deployed. Approval queues, audit trail, and dashboards are live from day one.
Phase 3 — Shadow run (Weeks 3–5)
- Agents run alongside the human team and produce recommendations, not actions.
- We measure accuracy, throughput, and exception rate against the existing baseline.
- Rule book is tightened with the operating team before any write-back is enabled.
Phase 4 — Production (Weeks 5–8)
- Write-back enabled, starting with the lowest-risk action classes and expanding by the rule book.
- 168-hour continuous operation window with on-call coverage from the Market Horizon team.
- SLA reviews weekly for the first month, then monthly. Cost and throughput are reported transparently.
Phase 5 — Expansion (Quarter 2 onward)
- Additional use-case categories added under the same scope-of-work framework.
- Cross-agent orchestration introduced where workflows overlap.
- Customer's operating team is now running the workforce. Market Horizon is on retainer for engineering, not headcount replacement.
What we expect from the customer
- A named operating sponsor with authority to approve scope and rule changes.
- Read access to the relevant systems in week 1.
- One operating analyst available for working sessions across weeks 1 through 5.
For questions about a specific deployment, email hello@markethorizon.com.