Built for Phase Two on Day One

What this means for you

Rover has a written two-phase audience and is designed for the second phase from day one. Phase one is a small dogfooding team running so1’s automation stack today. Phase two is external engineering teams within twelve months. The phase one design has to age into phase two without softening.

The pitch

Power users in the literal sense. They wrote the system, they read logs in their sleep, they sit next to a terminal and a GitHub tab. Their first impression must read as a serious instrument built by people who do this work, not as another SaaS to evaluate.

Who it’s for

The reviewer or contributor about to suggest a friendlier empty state, a tutorial overlay, or a hand-holding tooltip on a production screen.

Proof points

• Audience named in PRODUCT.md by phase, with twelve month horizon between them
• Job-to-be-done quoted verbatim: “act fast and stay oriented” on any given screen
• Context stated: desktop or tablet, often with a terminal, log viewer, or GitHub tab adjacent
• Anti-context stated: not 9-to-5, this surface is open during incidents and off-hours runs

quadrantChart
  title Rover readers, by depth and weight
  x-axis "Skim" --> "Deep read"
  y-axis "External" --> "Operator-first"
  quadrant-1 "Phase 1: internal operators"
  quadrant-2 "Future hires & dogfooders"
  quadrant-3 "Drive-by evaluators"
  quadrant-4 "Phase 2: external engineering teams"
  "Internal operator (now)": [0.93, 0.95]
  "External engineering team": [0.85, 0.4]
  "Skeptical buyer": [0.6, 0.3]
  "Future hire": [0.5, 0.75]