The Sprint ships the system. Watch ships your roadmap.
Lighthouse Watch is the continuous service that turns the agent system you shipped into a roadmap engine. Every month, the gaps your system can't yet compose — the customer requests it routes to humans, the workflows it can't yet absorb — surface automatically. Watch turns those gaps into the +1 improvement we ship next month. Your roadmap stops being a guess and becomes what your own system tells you it needs.
Foundation-layer churn and pattern-library drift get covered as part of the baseline. The +1 is what makes Watch unique: one gap closed per month, scoped from what your system surfaced — not from a quarterly planning meeting.
Replaces the prior “Observatory Retainer” offering. Same lineage, productized.
Why Watch exists. Two things broke the optional-retainer model.
Foundation-layer churn. New foundation models drop every 8–12 weeks. Every release forces a decision: stay, swap, run side-by-side, or delete. Without a partner running that decision tree, the system Studio shipped becomes brittle within a quarter. The cost of not deciding is higher than the cost of deciding wrong.
Pattern-library drift. Every Sprint Studio runs extracts patterns into a shared library. Those patterns get sharper after each engagement. Without Watch, your system gets the v1 of every pattern and never benefits from the v2, v3, v4 that subsequent engagements produce. Watch is the channel that pumps those improvements back to you.
The strategic claim, plain: we don't sell you an agent. We sell you a system that tells you what to build next — and then we build it.
What every Watch month delivers. Four streams plus one.
Keep the floor under you.
- Model swap testing within 7 business days of any new release
- Eval suite re-run on the full agent fleet, monthly
- Prompt-drift detection against the original baseline
- Provider deprecation tracking — clean migration window, not a fire drill
Keep humans above the loop.
- Governance Runbook revisions tied to incidents and policy changes
- Acceptance-rate monitoring on every gated agent (target ≥80%)
- Reviewer UI feedback loop — what humans flag goes into the eval set
- Quarterly architecture review with your CMO/CTO sponsor
Each month, the system surfaces the gap. We ship the fix.
- The +1 is whatever your system asked for and couldn't yet deliver — a new pattern from the Studio library that absorbs the gap, or a workflow redesign that removes the friction
- Scoped jointly in the previous month's review — you always see the +1 coming
- Eval-gated before promotion. If it fails its eval, it doesn't ship.
- Failure case: we owe you the improvement next month, plus a call
The deliverable that lives in your inbox.
- Delivered the 1st of every month. Signed by the lead engineer
- 3–4 pages: model status, acceptance trends, evals, incidents, the +1 delivered, library updates available, next-month preview
- Always-on Slack channel with same-day SLA on critical, next-business-day standard
- Direct line to the lead engineer who shipped your Sprint — not a support tier
Three tiers. Standard is the default.
All tiers are monthly, billed in advance, against a single agent system shipped by Studio. Multi-system clients are quoted bespoke at roughly 1.7× per additional system.
- Stream A · Foundation maintenance
- Stream B · Governance & observability
- Stream D · Monthly health report
- No +1 improvement
- Standard SLA only
- Everything in Essentials
- Stream C · +1 improvement every month
- Quarterly architecture review
- Pattern-library updates flow in
- Standard SLA
- Everything in Standard
- 4 hrs/mo named-engineer advisory
- Priority response · 4-hour SLA on critical
- Emergency-hours bank (8 hrs/yr)
- Direct line, named engineer
Sprint + Watch bundle. One PO, one signature.
For clients who prefer a single purchase order at engagement start: a bundled price covers the Sprint plus the first 12 months of Watch · Standard. The discount is paid for by the term commitment — the bundle is non-cancellable for the first 6 months.
Sprint + Watch · Standard 12-mo
$290k flat — vs. $356k separately at the entry Sprint band of $68k + 12 × $24k. The bundle saves your team a budget cycle and locks in the engineer team across both phases.
What Watch is not. The perimeter that keeps the price honest.
Spelling out the absences matters. These are the scopes Watch deliberately doesn't cover — and the reason the price stays where it is.
Outside Watch scope
- Not new agent development. Building a brand-new agent or migrating a new workflow is a fresh Sprint, not a Watch deliverable. The +1 extends what already exists.
- Not unlimited advisory. The Pro tier caps advisory at 4 hrs/mo for a reason. Beyond that we propose a Beacon Workshop or a follow-on Sprint.
- Not breakdown insurance. If your data infrastructure breaks (CDP, warehouse, unified ID), that's outside the Watch perimeter. We diagnose and refer; we don't fix data plumbing as a Watch deliverable.
- Not a managed service. Your reviewers operate the agent. We keep the agent and the governance current. We don't replace your operators.
A typical Watch month. No surprises in the calendar.
| Week | Activity |
|---|---|
| Week 01 | Health report delivered. Standing review call (45 min, optional but encouraged). Last month's +1 confirmed delivered. This month's +1 confirmed in scope. |
| Week 02 | +1 improvement build. Eval suite expanded to cover the +1. |
| Week 03 | +1 ships behind gate. Reviewer feedback loop opens. Foundation-layer scan: any new model releases since last cycle? |
| Week 04 | +1 promoted (if eval passes). Governance Runbook updated if applicable. Next-month report drafted. Quarterly addition (every 3rd month): 90-min architecture review with your sponsor. |
SLA matrix. Severity drives response.
| Severity | Definition | Response | Resolution target |
|---|---|---|---|
| P0 · Critical | System down, evals failing across the board, governance breach | 4 hrs (Pro) / 1 business day (Std/Ess) | 24 hrs |
| P1 · High | Single agent failing, acceptance rate dropping, model deprecation imminent | 1 business day | 5 business days |
| P2 · Standard | Drift detected, runbook update needed, +1 scoping | Next monthly review | Within current cycle |
| P3 · Backlog | Nice-to-haves, future tier upgrades | Quarterly review | Quarterly review |
How a client starts on Watch. Two paths.
Path A · Sprint → Watch (default). Watch is offered in Week 8 of the Sprint, signed at closeout, and starts the day after handoff. About 70% of Sprint clients sign Watch · Standard within 30 days. There is no gap; the engineer who shipped your Sprint is the engineer who runs your Watch.
Path B · Inherited system. If you already shipped an agent system with another partner, Watch can adopt it after a 2-week assessment ($14k flat, credited toward the first month if you sign). The assessment determines whether the system is adoptable as-is or needs Sprint-level work first.
Want to see what your Watch month-one would look like?
We'll write a one-page Month-01 plan against your current agent system. Free, takes 30 minutes on a call. No obligation.