Skip to content

Review the $9.99 Lifetime Pro price from real proceeds and conversion data #20

Description

@lightcloud00

Outcome

Keep or change the Lifetime Pro reference price using observed customer value, conversion, proceeds, refunds, and support feedback—not guesswork or fake urgency.

Entry gate

Run after at least 30 days live and 25 purchases. If 25 purchases are not reached, wait until day 90 and explicitly record that the sample is small.

Plan

  • Capture localized price points, downloads, paying users, purchases, estimated proceeds, download-to-paid conversion, refund rate, and territory mix.
  • Review paywall support feedback and reasons users value or decline Pro where voluntarily provided.
  • Compare actual proceeds per download against the documented scenario model.
  • Decide: hold $9.99, test one alternative price, or improve value/message first.
  • If testing a price, define start/end dates and avoid overlapping paywall/product-page changes.
  • Preserve the decision and App Store Connect readback.

Guardrails

  • The app always displays StoreKit displayPrice; never hard-code a live localized price.
  • No countdown, crossed-out fake discount, subscription conversion, or data deletion pressure.
  • Sales are not proceeds; record taxes, commission, refunds, and exchange-rate caveats.

Acceptance

  • A signed-off price decision links exact provider metrics and date range.
  • Any price mutation receives explicit owner approval and public readback.

Plan: https://github.com/lightcloud00/parknudge/blob/main/Docs/REVENUE-ROADMAP.md


Scope / non-scope

Only the work and evidence already described in this issue are in scope. Merge, deployment, provider or store mutation, spend, billing, customer contact, device acceptance, indexing, and release remain separate gates unless this issue explicitly includes them and fresh proof is recorded.

Dependencies

No unresolved dependency is explicitly stated in the current body. If implementation exposes one, record its stable roadmap ID here before dependent work starts.

Evidence and closure

Close only from exact current-source evidence plus the applicable independent readback. Keep local, GitHub/CI, provider, deployment, device, store, commerce, indexing, traffic, and revenue evidence distinct; one does not imply another.

Owner / lane

The repository delivery lane owns ordinary implementation and verification. The operator owns only actions explicitly marked as operator-only or protected.

Resolution plan

  • Verified: 2026-08-25T05:34:22Z against main@04a6cd5e808720983471ee9595fd40bc94e1f0fe (commit time 2026-08-25T00:53:29Z).
  • Source basis: Original issue body, all 0 comment(s), current default-branch tree, disposition-appropriate source-path checks, and referenced pull-request states.
  • Disposition: Operator or external gate - execute only the bounded proof steps and stop at protected actions.
  • Outcome: Keep or change the Lifetime Pro reference price using observed customer value, conversion, proceeds, refunds, and support feedback—not guesswork or fake urgency.

Current evidence and corrected premise

The issue remains open and requires the resolution steps below.
All 0 issue comment(s) were read. There are no comments.

Resolution steps

  1. Refresh the authoritative external state and bind it to the exact account, app, build, deployment, or provider identity.
  2. Reconcile that readback with the issue-authored work below and identify the smallest remaining action.
  3. Prepare the protected action, rollback, and failure receipt without exposing credentials or inferring authority.
  4. Stop for the required operator decision or action, then execute it once through the owning workflow.
  5. Validate the official readback and map it to every acceptance item before closure.

Grounded issue-authored detail

Scope / non-scope

Only the work and evidence already described in this issue are in scope. Merge, deployment, provider or store mutation, spend, billing, customer contact, device acceptance, indexing, and release remain separate gates unless this issue explicitly includes them and fresh proof is recorded.

Tests and acceptance

Acceptance

  • A signed-off price decision links exact provider metrics and date range.
  • Any price mutation receives explicit owner approval and public readback.

Plan: https://github.com/lightcloud00/parknudge/blob/main/Docs/REVENUE-ROADMAP.md


Dependencies and stop gates

Dependencies

No unresolved dependency is explicitly stated in the current body. If implementation exposes one, record its stable roadmap ID here before dependent work starts.

  • Do not close this issue until every acceptance item is mapped to exact merged-head evidence.

Next AI first action

Only the work and evidence already described in this issue are in scope. Merge, deployment, provider or store mutation, spend, billing, customer contact, device acceptance, indexing, and release remain separate gates unless this issue explicitly includes them and fresh proof is recorded.

Metadata

Metadata

Assignees

No one assigned

    Labels

    area: commerceStoreKit, App Store Connect, and purchase acceptancearea: productNaming, legal, positioning, and product decisionsneeds-operatorRequires a named operator-only actionpriority:p1Important next milestone workreadiness:blocked-externalBlocked by a vendor or external gaterevenue:r2Multiple gates remain before revenuetype: experimentHypothesis with a metric and stop rule

    Projects

    No projects

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions