Design a hosted pricing and adoption validation experiment #100

Working hypothesis

Free individual use can lower adoption friction; paid teams may value shared projects, permissions/review, managed operation and support. Treat feature boundaries and prices as testable proposals, not shipped entitlements.

Deliverable

Outline first-user interviews, a simple willingness-to-pay experiment, operating/support cost estimates and a retention dashboard specification. Measure first connected agent, first useful recall, repeat weekly projects and cross-harness handoffs; stars remain a secondary reach metric.

Acceptance

• Concrete experiment, success/stop criteria and a revenue scenario with labelled assumptions.
• Candidate free/paid boundaries do not make data export or basic ownership unexpectedly hostage.
• Billing, analytics collection and outreach are not activated by the design task.

Dependencies

Coordinate with release-model memo under #78; concept work can proceed now.