Skip to content
AppDues
Log in
Contact salesSign up

The Tapping Solution App: Moving Off a Custom Subscription System

The Tapping Solution App is a wellness product built around guided Tapping (Emotional Freedom Techniques, or EFT) meditations.

Its team replaced a four-year-old custom subscription system with a managed platform and reported fewer access failures, more trustworthy event data, and lower backend engineering load. This page explains the problems, the decision, and the reported results, and gives teams a checklist for judging a similar move.

The two core problems: access and data

A custom-coded subscription management system served the app for its first four years. As it aged, two categories of problems emerged.

Access failures. A small but persistent set of edge cases meant some purchasers were not granted premium access immediately upon purchase. Even a low rate of these cases created urgency because the customer experience was unacceptable.

Data-quality failures. The team could not fully trust subscription-related events and attributes. Without confidence in that data, the marketing and analytics stack, including Braze and Amplitude, could not be used reliably. Benchmarks were hard to establish and data-driven campaigns were hard to run. The team also described a timing problem: getting the right data often depended on the app being opened on the user's device again after a subscription event, which left room for incorrect data and weakened targeted messaging. Backend developer hours were spent troubleshooting individual data issues.

The build-vs-buy decision

The team considered three options: a managed subscription platform, a competing platform, or having their backend engineer update or rebuild the custom solution. They ruled out the competitor because the chosen platform stood out as the leader in the space. They also weighed the risk of concentrating the rebuilt system in one engineer's hands: if that person was busy, work would wait, and if that person left, no one else would understand the system as well. A managed platform with an entire team behind it felt safer.

This is a useful decision frame for other teams. The question is not only which option has the lowest initial cost, but who carries the operational risk when access breaks or data is wrong.

What the migration involved

After choosing the platform, the team worked with the vendor's customer success team through the migration. They described responsive communication, a shared Slack channel, weekly status calls, and help tracking down answers. The migration was described as intimidating at first but ultimately a smart move.

Reported results

The team reports four outcomes after the migration:

  • Backend engineering hours: engineering hours billed to their development agency fell by over 50% because entitlement-granting and data issues no longer required troubleshooting.
  • Winback campaigns: with event data they could trust, they launched winback campaigns via Braze in Q1 2023. They report winning back an average of 3.6% of users through offers they now feel confident sending. Their top-performing winback segment reached 7.35% for canceled Android subscriptions (not trial lapses).
  • Benchmarks: using platform events in Amplitude, they could measure subscription metrics for the first time with confidence and plan quarterly progress reviews.
  • Access edge cases: the team reports no regular occurrence of users who start a subscription not being granted premium access immediately.

ConfigureTargetTest

A checklist for judging a similar migration

Before replacing a custom subscription system, ask:

  1. Are access failures rare but real? Track how often a purchase does not immediately unlock premium access. A small rate can still be a serious customer-experience problem.
  2. Can you trust your subscription events? Check whether event data depends on the app being reopened after a purchase. If it does, your targeting and benchmarks may be unreliable.
  3. Who carries the operational risk? If one engineer owns the custom system, what happens when that person is unavailable or leaves?
  4. What does the migration team look like? Ask about communication channels, status calls, and who answers questions during the transition.
  5. What will you measure after migration? Define the access, data-quality, and campaign metrics you will review, and how often.

Access failures vs. data-quality failures

These two problems look similar but need different fixes.

  • Access failure: a purchaser pays but does not receive premium access immediately. The symptom is visible to the customer and creates urgency.
  • Data-quality failure: subscription events or attributes are missing, late, or wrong. The symptom is invisible to the customer but damages targeting, benchmarks, and campaign confidence.

A migration can address both, but the team should track them separately so a fix for one is not mistaken for a fix for the other.

Frequently asked questions

What problems did The Tapping Solution App have with its custom subscription system?

The team described two core issues: a small but persistent number of edge cases where purchasers were not granted premium access immediately, and data-quality problems that made subscription events and attributes untrustworthy. The data problems affected marketing and analytics tools including Braze and Amplitude and consumed backend developer time.

Why did the team choose a managed platform over rebuilding the custom system?

They considered a managed platform, a competitor, and a custom rebuild. They ruled out the competitor because the chosen platform stood out as the leader. They were concerned that a rebuild would put everything in one engineer's hands, creating risk if that person was busy or left. A managed platform with a full team behind it felt safer.

What results did the team report after migrating?

They reported a reduction of over 50% in backend engineering hours billed to their development agency, an average winback rate of 3.6% with a top Android segment at 7.35%, the ability to establish reliable subscription benchmarks in Amplitude, and no regular occurrence of new subscribers failing to get premium access immediately.

When were the winback campaigns launched?

The team launched winback campaigns via Braze in Q1 2023, after gaining confidence in their event data.