agent-market-definition

The qcontrol dashboard (qdash, http://localhost:3030/) has been built by following the technology as it develops. We're now ready to align the product to specific personas and look for market fit. Market-analyst is the long-term home for this work (call pipeline, ICP data), but it holds proxy-era analysis and there are no relevant agent-monitoring calls yet — so this starts as hypothesis-first persona work in design.

A defensible set of persona hypotheses grounded in what the product actually is today, with explicit assumptions to validate as agent-monitoring calls arrive. "Done" looks like: persona one-pagers, a chosen first motion (mid-market security console vs. discovery wedge), and demo paths per persona feeding back into design positioning and bob-wire concepts.

• qcontrol/crates/qdash/ui/app/pages/ — the 17-page product surface being analyzed (read-only input)
• cycles/c55.agent-market-definition/ — analysis artifacts
• market-analyst/inbox/ + briefs/ — QControl-as-Signal docs and Cam's dashboard directives, to reconcile against
• Downstream: design positioning, bob-wire persona-specific concepts

• Page × persona analysis (page-persona-analysis.md, 2026-07-24): read all 17 qdash pages, mapped them against 11 general personas across small/mid/enterprise orgs. Headline: the product as built is a mid-market security engineer's console — the only persona with a complete detect → triage → decide → prove loop. Enterprise gaps are exactly the "projected" feature list (SIEM, SSO/SCIM, enforcement, evidence packs); the small-org story is shadow-AI discovery + cost, already fully live.
• Framed the discovery wedge as a candidate land motion: shadow-AI inventory ("what AI is actually running here?") is persona-universal, requires no workflow adoption, demos itself on first run, and expands naturally into the security console (which is also the mid-market → enterprise path). Trade-off: don't let the wedge define the category or the price — position the platform, land with discovery.

• First motion: mid-market security (matches the build) or discovery wedge (fastest to sell)?
• Is enforcement near-term roadmap or is "world-class dry run" the product for a few quarters? (Control vs. visibility-tool positioning.)
• Mid-market buyer: security, IT, or engineering leadership?
• Do proxy-era personas from market-analyst carry over, or is AI-agent governance a fresh buyer profile?