Number of Seats/Users: RevenueCat offers discounts based on the number of users or seats. A higher volume typically leads to a better discount structure, especially for enterprise-level usage.

Commitment to a Long-Term Contract: Discounts are often provided to companies that commit to using the service for a longer period (e.g., 1-year or 3-year contracts). A longer commitment shows RevenueCat that the company is serious and willing to invest in the platform long-term.

No Active Discounts: Companies that are not already receiving other active discounts may have a better chance of qualifying for additional discounts from RevenueCat. RevenueCat reserves discounts for new customers or those not currently under promotional pricing.

Volume or Usage Commitment: RevenueCat offers discounts if you agree to a minimum amount of usage or transaction volume. This could be based on data storage, transactions, or other metrics tied to how much you will use the platform.

Enterprise-Level Negotiation: Companies that qualify as “enterprise” due to their size or complexity (e.g., having large teams, multiple departments, or geographical presence) may be eligible for additional discounts from RevenueCat. Such companies are often in a position to negotiate for better pricing.

Early Renewal or Prepayment: RevenueCat often offers discounts if you renew early or prepay for the entire contract period. This is a common approach to securing a lower price.

Here at Spendbase our internal data shows that RevenueCat is seen as a big time‑saver for teams building in‑app subscriptions, but it comes with cost and analytics caveats that matter once revenue scales.

Overall sentiment
Most Spendbase clients describe RevenueCat as “essential” or a “no‑brainer” during early and mid stages. The value shows up mainly in:

• No need to build/maintain a subscription backend
• Fast cross‑platform integration (iOS, Android, Flutter, React Native, Stripe)
• Strong documentation and quick setup guides
• Helpful for support workflows (single source of truth for purchases)

What Spendbase clients like most
Our internal data highlights recurring positives:

• Developer efficiency
• “Months of work saved” is a common theme.
• Stable integration: once implemented, teams rarely touch it.
• Free/low tier value
• Free up to a certain MRR is viewed as very founder‑friendly.
• Tooling and UX
• Dashboards and charts are used daily for:
  • Tracking trials and conversions
  • Validating impact of new releases
  • Managing entitlements across stores

Where pain points appear

As a discount specialist, these are the areas we see driving future cost and risk:

• Pricing model
• Percentage‑of‑revenue feels great when revenue is low, but:
  • Becomes “expensive” once apps hit ~$20–30k MRR
  • Some teams consider building in‑house at scale

• Desire for:

  • Better pricing for certain countries
  • More features on cheaper plans (webhooks, integrations, richer dashboard)

• Analytics & reporting

• Churn and cancellation reporting sometimes off vs internal numbers
• Revenue charts:
  • Don’t always handle VAT correctly (inflated take‑home)
  • Default to USD, ignoring FX on purchase day

• Charts can feel slow or a bit dated in UI

• Reliability & support

• Most mention responsive, friendly support.
• A minority report:
  • Multi‑day response times (4–10 days)
  • Outages and Android integration issues
  • Frustration with forum‑based help

• Some webhook/event delays affect internal sync logic.

• Usability & concepts

• Entitlements / Offerings / Products naming is initially confusing.
• Smaller issues: sandbox delays, restore‑purchase edge cases, missing SSL pinning.

What this means from a Spendbase perspective
– RevenueCat is highly cost‑effective for:
– Early‑stage and indie teams
– Companies without backend expertise
– As revenue grows, we typically recommend:
– Modeling RevenueCat fees vs a phased in‑house build
– Double‑checking its analytics against store and finance data
– Negotiating or revisiting plan tiers before costs creep up.