sync on nov 4th with @RulaKhaled @ajay-sentry @katia-sentry

• high level details for private free plans
  • the team plan (as-is) will replace the experience of the free plan today (which is 1 user currently viewing pro)
    • v1: to replace with team plan
      • how about existing customers?
        • existing plans are grandfathered in, meaning the former free plans experience stay as-is
    • v2: team plan with upgrade options (fla)

next steps:

• eng discovery in v1 + designs audit on implications (quick wins for upgrade flow polish and/or any rollout needed) + ToDo is plans page
  • @RulaKhaled @ajay-sentry
• design discovery on v2
  • @Adal3n3

open questions:

• what are the metrics of success
• what is the plan for the for the former plan? is there a deprecation plan?
• release related
  • rollout communication
  • marketing pricing page / release alignment
  • docs updates, how/where do we want to handle communicate this
  • public API changes?
• does this affect the Sentry Free plan?

Re trials - it's worth considering if we want to allow trials from team to pro and build for that. Very soon, there will be a significant difference between the pro plan and the team plan in terms of features (project coverage, flake detection).

Note - Currently the system always assumes you'd want to trial pro from free --> meaning we fall back to the developer plan after a pro trial expires... this is hardcoded (see https://github.com/codecov/internal-issues/issues/1015)

Audit

• areas of concern:

  • when a trial is completed and then customer goes to private repo and sees loss of the features and/or does not see the features
    • v2 aims to mitigate this by having the levers of difference
  • adalene: question to product: why remove the features from team
    • aj: for team plan members we causing confusion today
    • most feedback is the loss of functionality

• plans page:

  • problem to solve: differentiate and make clear to user that for public they receive pro / private team plan pro
    • other is that user that pay for team are irritated about the team plan
    • alternative is improving the confirmation for the upgrades of the team plan

• plans > manage

• trials

  • IF trial is available, what are the upgrade levers we can show related to v1 (quick CTAs) v2 discovery longer term resolutions
    • consider

Here's the figma: https://www.figma.com/design/UdZNtpQdWrPgEyWxegm4ev/GH-2778?node-id=1-2

• The problem we are addressing is that when customers upgrade from the free developer plan to the team plan, they end up paying but losing features. This upset some customers because 1/ in their mental model, they don’t expect to pay for less features 2/they unaware that the team plan doesn’t have the features they have configured in free plan.
• The solution is to align with their expectations so when they upgrade from the new free plan they will not lose any features.
• What are we changing? We’re creating a new version of the free plan where private repos have the same features as the team plan, meaning they will only have patch coverage. This involves removing flags, components, CFF, and project coverage from the free plan.
• These changes will apply only to new customers; existing customers will retain the same experience they currently have.