Ops Service Intake, Capacity & Rollout
A single front door for any team proposing to move work into Ops. Captures scope, AI-scores level of effort, schedules the rollout, and forecasts team capacity across the next quarter or year so we can set realistic launch dates and gate work until it's truly ready.
Submit Intake
Requesting team fills out the structured intake form. Auto-scores LOE and flags gaps.
Start a new intake →AI-Ranked Approval
Claude scores the queue by strategic value × urgency × capacity fit × risk. Ops Lead approves, schedules the rollout, and calendar milestones auto-create.
Open approval queue →Capacity Forecast
Week-by-week utilization across the team. Approved rollouts feed in automatically. Flags overload before it happens.
View capacity dashboard →Roadmap Builder
Claude sequences unscheduled intakes into the next quarter / 6mo / year against current capacity. Defers what won't fit. Recommends hires only when math forces it.
Build roadmap →Post-Rollout Survey
30 / 60 / 90-day check-ins from Ops + requesters. Drives confidence scoring and continuous improvement.
Capture feedback →Stakeholders
Manage who gets notified on intake, approval, revision, and decline events — keyed by category and tier.
Manage stakeholders →How LOE tiers work
Each intake is AI-sized into one of four tiers. The tier drives the required approver, the steady-state hours forecast, and the default rollout phase durations.
End-to-end flow
- Requester submits → LOE engine computes tier + estimated hours.
- Claude ranks the queue → priority score with rationale across 4 dimensions.
- Ops Lead approves → rollout plan auto-suggested from tier, kickoff/build/pilot/GA + 30/60/90 retros created in Google Calendar with Meet links.
- Capacity engine → projects week-by-week team utilization, flags overload.
- Roadmap generator → Claude sequences unscheduled backlog into the horizon, defers what won't fit, recommends hires only if forced.
- 30/60/90 survey → measures actual vs. forecast, feeds calibration back into the LOE model.