Documents

Monthly snapshot of Output Systems' own numbers. As of Aug 1: MRR $8,200 (Selvam + Staff Chasers), pipeline weighted value $34,000, active paying clients 2, founding-partner slots open 3, monthly infrastructure spend ~$410, cash runway not disclosed in the demo view. Trailing 30 days: 4 discovery calls booked, 1 proposal out (Bridgeway), 2 wins (Bluewave retainer + Selvam expansion).

Working draft of the positioning statement using April Dunford's framework. Current version defines the target as fractional COOs and business advisors managing 3+ concurrent client engagements; the primary alternative as "ten browser tabs open at 8am"; the unique value as "one workspace where the day is already prioritized." The one-line pitch: "Command Center is the daily operating surface for advisors who run their clients like a business — not a Slack channel." Next revision after Sarah Whitfield discovery call.

The end-to-end sales motion Output Systems runs. Steps: (1) LinkedIn identifiable target list from Sales Navigator; (2) 4-touch outreach sequence via Meet Alfred; (3) reply -> Calendly for discovery; (4) discovery call script (5 questions, listen 80% of the time, never pitch); (5) same-day written recap email; (6) proposal within 48 hours if fit; (7) two follow-ups then archive. Conversion baseline: 12% first-touch to reply, 40% reply to discovery, 35% discovery to proposal, 45% proposal to close.

The original brief that scaffolded this app: a multi-client workspace built on Next.js 16 and Supabase, backed by a generic cc_records/cc_messages/cc_events schema, with a two-axis navigation model (context selector on top, module sidebar on left). Every module either drives from the generic tables or has a bespoke component. The brief calls out the three seeded clients, the 15 internal modules, the module registry pattern, and the deploy-to-Vercel + Supabase apply-all.sql workflow.

One-page reference for running a Level 10: Segue (5 min), Scorecard (5 min), Rock Review (5 min), Customer/Employee Headlines (5 min), To-do List (5 min), IDS — Identify, Discuss, Solve (60 min), Conclude with Cascading Messages, Rating, and Recap (5 min). Includes the modifications Output Systems makes: keep the meeting to 60 min for smaller teams, always time-box IDS to protect the last 5 min, and require every to-do to have a name and a date.

How an Output Systems engagement is structured: a 90-minute intake, a two-week diagnostic (org chart, scorecard baseline, top-10 issues list), a 6-month standard engagement with weekly L10s, monthly leadership syncs, and a quarterly Rocks reset. Includes pricing rails, cancellation terms, IP treatment, and the "ownership never transfers" boundary — Output Systems installs the operating system, the founder operates it.

The document Output Systems sends within 24 hours of contract signature. Contains: welcome letter, intake questionnaire (org chart, top 5 goals, top 5 fires, scorecard baseline questions), Loom video walkthrough link of the Command Center context they'll get, calendar invite for the first L10, and a shared drive folder link with editing permissions pre-set. Standardized in Q2.