LiveSubscription platformPayments · Entitlements

Subscription Model Infrastructure for Recurring Revenue

We moved Waqtly from a one-time hardware sale to a subscription model. Each plan is linked to a Welcome Code, payment is set up in the Remote app with Stripe, and each tablet reads its access level from the CRM, with a cached copy for offline use.

Waqtly tablet showing the QR handover screen, next to the Remote app's Welcome Code and Stripe payment screens
The challenge

The high one-time price limited sales.

Waqtly was sold as a single, high-priced purchase. This limited who could buy it, ended the customer relationship at checkout, and gave no recurring revenue to pay for new content, prayer-time sources and software updates.

The approach

We redesigned the pricing model and the systems behind it.

We designed the plans, the activation flow and the entitlement logic together, so the store, the tablet, the Remote app, Stripe and the back office all use the same access rules.

The outcome

The subscription model is live, existing owners were not affected, and revenue is now recurring.

Two plans are on sale in the store, devices activate with a Welcome Code, payment is handled in the app through Stripe, every device sold before launch kept full access with no action from its owner, and new customers are buyers who pay monthly.

Buy-once versus always-on

Dimension
One-time purchase
Subscription
Upfront price
High, single payment
Low, monthly
Market reach
Premium buyers only
Broadens the market
Relationship
Ends at purchase
Ongoing service
Updates
Manual and one-off
Continuous
Revenue
One-time
Recurring (MRR)

Model: Two plans, selected at checkout.

The customer orders a tablet with a plan. The plan is linked to the Welcome Code, so nothing has to be chosen during setup. There are four store SKUs, Nano and Plus with either plan, and each SKU has its own code pool.

Subscription

Default
€99

one-time, then €7.99/month after the included months

  • 6 months of full access included
  • Payment method added in the Remote app, and it can be skipped
  • Cancel anytime from the app
  • Azan always stays free

Lifetime access

€250

one-time, no subscription

  • Every feature, no expiry date
  • No payment step at activation
  • No billing events, no renewal emails
  • Suitable for gifts and family purchases

Original access

Free

for every device sold before launch

  • Pre-flagged as grandfathered in the CRM
  • Always gets full access from the CRM
  • No registration, no new account
  • No changes for existing owners at launch

How it works from the order to activated tablet.

Five systems are involved, and the CRM is the source of truth. Shopify only handles the order. The subscription is created during onboarding in the Remote app, with payment through Stripe.

What we built: Twelve components of the subscription system.

These components cover the tablet, the Remote app, the CRM service and the back office, and were released together.

01 · Codes

Welcome Code system

Each device ships with a pre-generated, easy-to-read code that holds its plan and model. Codes are stored in one pool per SKU and go through a fixed lifecycle. They are validated on the server and are not case-sensitive.

WQ-4KJ2-A
AvailableReservedActivated
02 · Orders

Order webhooks

When an order is placed, Shopify calls the CRM. The CRM verifies the signature, reads each line item by SKU, reserves one code per device and returns the codes for the confirmation email.

order-createdHMAC1 code / line item
Waqtly tablet asking the user to finish setup by scanning a QR code with the WaqtRemote app03 · Handover

Tablet-to-phone QR handover

The tablet completes its own onboarding, then shows a QR code and a backup setup code for the Remote app. The tablet only shows progress and unlocks; email and payment details are entered on the phone.

Remote app screen for adding a payment method through Stripe
04 · Payments

In-app payments with the Stripe SDK

The Remote app uses Stripe's mobile SDK. A SetupIntent saves the card without charging it, so billing starts only after the included months. The user can skip this step and add a card later. Card data never reaches our servers.

05 · Billing

Billing by webhook

Stripe runs the monthly billing. The CRM receives Stripe's webhooks, verifies each signature and updates the device record.

invoice.paid
mark active, set next billing date
invoice.payment_failed
notify the user, flag the payment
subscription.updated
sync plan and state
subscription.deleted
Azan only at next check-in
Tablet message saying a feature needs the subscription reactivated, while the Azan stays active06 · Entitlements

Feature gating with Azan always on

Each device has one access state. Locked features stay visible but faded; tapping one explains why and links to the Remote app. Azan, prayer times and the clock always work.

24 h07 · Resilience

Offline-first entitlements

The tablet checks in on launch and caches its entitlement for 24 hours (weekly for Lifetime and Original access). If the connection drops, the Azan keeps working.

Remote app Access and subscription screen showing plan, access, billing and payment for one device
08 · Remote app

Access & subscription in the app

The Remote app shows plan, access, billing and payment for each linked device, with flows to manage, cancel, reactivate and update payment.

Back office Welcome Codes table with code, pool, plan, status and order columns09 · Operations

Back office

An operations portal for orders, Welcome Code pools, devices, subscriptions, support search and an audit log, with manual overrides for support cases and pool-level alerts.

10 · Gifting

Activation for gifts

A code is linked to the order, not to the buyer. The person who activates the device with their own email becomes the account holder, and the included months start at activation, not at purchase.

11 · Email

Lifecycle emails

Order confirmations include a Welcome Code for each device, labelled by model. Reminders are sent before the included months end. Payment emails ask the user either to add a card or to update a card that failed.

12 · Continuity

Existing owners kept full access

Every device sold before launch was flagged as grandfathered in the CRM, so it gets full access without registration or a new account.

Device access states

The tablet reads its entitlement from the CRM. The CRM keeps each device's state in sync with Stripe through webhooks, and the tablet caches the result.

State
What the user gets
Check-in
How it ends
trial_active
All features for the included months
On launch, cached 24 h
Becomes active_recurring on the first successful charge
active_recurring
All features, billed monthly by Stripe
On launch, cached 24 h
If cancelled or unpaid, access ends at the end of the billing period
lifetime
All features, no expiry
Weekly
Never
grandfathered
All features, no expiry, no account needed
Weekly
Never
expired
Azan, prayer times and clock. Premium features stay visible but locked
On launch, renew from the Remote app
Full access returns when Stripe confirms payment
Interactive demo

See the subscription flow in action.

A live, embedded prototype of the customer subscribe-and-manage journey.

demo.attenddr.com/waqtly-subscription
Live now

Building a connected product?

We design and build the device interface, the app and the systems behind them.