Launch paid cloud suite experience

Problem

The Cloud Suite has no billing-aware product surfaces, account settings for plan management, or onboarding flows designed for paid users. The current experience assumes internal/free users and has no concept of subscription tiers, usage limits, payment methods, or upgrade prompts. Without these, launching a paid cloud offering is impossible — there is no way for customers to sign up, manage their subscription, or understand what they are paying for.

Context

• The hosted product currently assumes internal or free usage and does not yet present billing-aware onboarding, plan management, or account-state messaging for paid customers.
• Paid launch readiness depends on adjacent integrations work, but Cloud Suite still owns the user-facing surfaces where subscription state, upgrade/downgrade actions, and account expectations are explained.
• This task should define the hosted-product scope that makes a paid experience coherent before attempting to ship every monetization detail at once.

Possible Solutions

• A - Bolt billing state onto the existing internal-facing UX: fast, but likely confusing for real customers and support teams.
• B - Recommended: define and implement the minimum billing-aware hosted UX: cover onboarding, account settings, plan-state messaging, and failure/restriction behavior needed for a credible paid launch.
• C - Defer paid launch until every billing and self-serve path is fully mature: safest, but it may block the rollout longer than necessary.

Plan

1. Map the paid-user journey through signup, onboarding, active use, restriction states, and account management, highlighting where the current Cloud Suite UX is incomplete.
2. Define the minimum billing-aware surfaces the hosted product must support at launch and the behaviors it can explicitly defer to follow-up work.
3. Coordinate the product UX requirements with billing and integration tasks so account state, plan messaging, and support expectations stay consistent.
4. Write launch-readiness acceptance criteria and QA scenarios for paid flows, including downgrade, access restriction, and operator-support edge cases.

Implementation Progress

• Confirm scope and acceptance with milestone owner.

• Milestone readiness signal is updated.

• Track blockers and mitigation owner.

QA Exploration

• [ ] QA exploration completed (or N/A for non-UI tasks)

Review Feedback

• [ ] Review cleared