Pricing direction for the new product

The launch model is straightforward: Starter is the self-serve managed SaaS path, while Growth and Enterprise stay sales-assisted so integrations and deployment can be scoped intentionally.

Starter

Single internal app

Best for small teams that need a lightweight review loop without adding heavy runtime behavior.

  • Pinned visual comments
  • This Page and All Comments views
  • Reviewer and manager roles
  • Managed cloud persistence

Growth

Cross-functional teams

Best for teams that want structured workflows, integrations, and wider rollout across admin surfaces.

  • Everything in Starter
  • Jira connector options
  • On-demand screenshot attachments
  • Multiple workspaces or projects

Enterprise

Privacy-sensitive organizations

Best for companies that need self-hosting, deeper access controls, and enterprise rollout support.

  • Self-hosted or BYO-cloud path
  • Advanced access controls
  • Connector extensibility
  • Implementation support

Frequently asked questions

Will the widget stay lightweight on the host app?

Yes. Lightweight runtime is a core product constraint. The base widget is meant to stay small, framework-agnostic, and low-overhead, with heavier capabilities loaded only when needed.

Will screenshots be always on?

No. Screenshots are planned as an on-demand capability only. They should load only when a workflow explicitly needs them.

Will Jira be part of the core widget?

No. Jira is the first deep connector, but it should remain modular so the core runtime does not become connector-heavy.

Will there be a self-hosted option?

Yes. The packet explicitly calls for an enterprise self-hosted or BYO-cloud path while keeping the same public widget API.