Community solves a complete problem
A user should be able to reproduce one incident, find a credible supported contributor, and share redacted evidence without an expiry or deliberately unusable result.
No public Pro plan is available yet
The current paid design-partner programme uses founder-led onboarding and manual commercial validation. It is not the final Community or Pro offer, and no monthly or annual public pricing should be treated as settled until real paid tests are reviewed.
Packaging principles
Monetize recurring workflow, not measurement truth.
Accuracy is identical
Community and Pro must share the same trace schema, attribution truth, scoring rules, capability model, and essential findings.
Pro earns renewal
Recurring value should come from monitoring, longer history, compatible comparisons, reports, support, and professional multi-workflow operation.
Leading edition hypothesis
A useful free diagnosis; paid ongoing confidence.
| Workflow | Community candidate | Pro candidate |
|---|---|---|
| Capture | Manual page/workflow capture; Safe, Standard, and focused one-shot Deep where supported. | Controlled automatic sampling and saved monitored workflows. |
| Evidence | Interactive trace, capability report, span detail, and basic top measured opportunities. | Same measurement truth with recurring aggregation and workflow-specific context. |
| History | Bounded recent local history sufficient for one-off diagnosis. | Longer configurable history with route distributions and cohort controls. |
| Comparison | Single-trace evidence and a redacted export. | Compatible before/after cohorts, saved comparisons, and professional reports. |
| Support | Documentation and a public support channel. | Ticket support; priority routing only after measured support capacity exists. |
| Sites | No account required for the local Community workflow. | Active production-site licensing hypothesis; staging/local should not consume activations. |
Always shared
Measurement truth
- Supported spans mean the same thing in both editions.
- Unavailable capability remains unknown, not a better score.
- Essential diagnosis is not withheld from a Community trace.
- Redaction, storage health, and retention controls are not premium safety features.
- Licensing failure must not silently change local trace accuracy.
Validate before building
Open commercial questions
- Which recurring workflows cause professionals to pay and renew?
- Do reports materially affect agency conversion or retention?
- Which site-count ladder fits actual portfolios?
- What support response is sustainable?
- Should connected fleet services exist at all before multi-site demand is proven?
Provisional license-expiry principle
Expiration should leave already-installed local monitoring functionality running. Updates, support, and separately delivered connected services may stop. The final behavior must be documented and tested before public checkout.
What happens now
Design partners validate the boundary with real work.
The programme asks agencies and operators to bring a real slow dynamic workflow, complete a controlled diagnosis, and show which parts of monitoring, comparison, reporting, and support they actually use. The resulting paid behavior—not survey enthusiasm—will set the public offer.