A subscription looks like a product with a repeat button. Operationally it is a promise that has to survive a failed card, an expired mobile wallet, a plan change, a partial payment and a customer who cancels twice. The platform fee is the visible cost. The recovery workload is the one that grows.
This guide builds a cost model for subscription operations in Bangladesh, with a calculator you can fill in before choosing a platform. It avoids fixed figures: the answer depends on how many renewals fail and how much recovery you automate.
Six cost centres, not one
- Catalogue and pricing logic. Plans, intervals, trials, coupons, proration, upgrades, pauses and grandfathering rules for existing customers.
- Billing engine. Renewal scheduling, invoice generation, tax treatment, retries and the record of what was charged and why.
- Collection. Gateway or mobile wallet integration, tokenisation, payment links, manual confirmation and failed-payment follow-up.
- Entitlement. The rule that decides what a customer can access, and the job that suspends or restores it when payment state changes.
- Finance operations. Reconciliation against gateway and wallet statements, refunds, adjustments, revenue reporting and VAT documentation.
- Support and change. Customer questions about charges, plan changes, cancellations, and the releases that keep the whole chain accurate.
A proposal covering only the billing engine leaves the rest to your team; those hours belong in the budget.
The annual cost formula
Annual cost = build effort + platform and gateway charges + recovery workload + finance reconciliation + support + change requests + internal time
Platform and gateway charges are usually a mix of subscription, percentage and per-transaction amounts; ask for the full schedule, including who bears refunds and failed attempts. Recovery workload should be measured in minutes per failed renewal multiplied by the expected number of failures, because that is where subscription economics quietly turn.
Internal time includes the person checking the wallet statement, the agent answering a duplicate charge and the manager approving a refund. None of it appears on a software invoice.
A calculator with nine inputs
Score each input from 1 (simple) to 5 (complex). The total indicates the shape of the operating model, not a price.
- Plan count: one monthly plan scores 1; several tiers, annual options and add-ons score 5.
- Billing intervals: monthly only scores 1; monthly, quarterly and annual with different renewal dates score 5.
- Payment methods: one gateway scores 1; cards, mobile wallets, bank transfer and cash at a branch score 5.
- Proration and changes: no mid-cycle changes scores 1; upgrades, downgrades, pauses and credits score 5.
- Trials and offers: none scores 1; trials, coupons, referral credits and win-back offers score 5.
- Subscriber base: a few hundred scores 1; tens of thousands with seasonal churn score 5.
- Recovery process: one retry scores 1; a multi-step dunning sequence with manual calls scores 5.
- Invoicing and tax: a simple receipt scores 1; VAT invoices, buyer references and audit exports score 5.
- Integration count: standalone scores 1; accounting, CRM, access control and support desk score 5.
Read the total in bands:
- 9–16: a focused build around one gateway and one renewal rhythm, with a manual recovery list.
- 17–25: a configured platform plus integration and a documented dunning process.
- 26–34: a custom or heavily integrated operations layer with reconciliation and entitlement testing.
- 35–45: a finance-grade subscription operation with multiple channels, audit evidence and a support model.
Where cost grows after launch
Failed renewals. Every failure creates a decision: retry, remind, suspend or call. Automating easy cases is inexpensive; ambiguous ones are not.
Manual wallet confirmation. Where recurring collection is unavailable or not approved for the merchant, the business sends a reminder and matches the reference by hand. That work scales with subscribers, not revenue.
Price changes and grandfathering. Existing customers on old terms need exceptions, and exceptions need a record. A simple pricing change can become a month of support questions.
Entitlement drift. A customer pays but cannot log in, or cancels and keeps access. Both cost money and trust, and both need scheduled reconciliation rather than a spot check.
Refunds and chargebacks. Each one touches finance, support and the billing record. The process needs an owner and a response target.
Bangladesh-specific lines
- Recurring collection depends on the gateway and the merchant agreement; many businesses still renew by reminder link or manual confirmation.
- Mobile wallet statements need a matching routine by reference, amount and date, especially when customers pay from another person's number.
- Card payments add authentication steps and disputes, which affect both support load and reconciliation.
- Bangla receipts, VAT invoices and bilingual plan descriptions are part of the build, not a translation afterthought.
- Some customers prefer cash or an agent at a branch, so the subscription record must accept an offline payment without breaking the renewal schedule.
- Dollar-denominated tools are billed to a card, which adds a finance approval step and exchange-rate questions.
Budget worksheet
| Cost line | One-off | Recurring | Owner | Evidence |
|---|---|---|---|---|
| Plan and pricing design | Workshop and rules | Review each quarter | Commercial lead | Approved plan matrix |
| Billing and gateway setup | Integration | Transaction charges | Finance | Gateway schedule |
| Dunning and recovery | Sequence design | Agent hours | Support lead | Recovery log |
| Entitlement testing | Test cases | Per release | Product owner | Access test results |
| Reconciliation | Mapping | Daily or weekly hours | Finance | Variance report |
| Customer support | Macros and training | Tickets per month | Support lead | Ticket reasons |
| Change requests | — | Reserve | Product owner | Release log |
Questions that change the number
- What happens on the third failed renewal, and who decides to suspend access?
- Can a customer pause rather than cancel, and how is the pause period billed?
- How is a mid-cycle upgrade prorated, and how is the credit shown on the receipt?
- Which payment methods support automatic recurring collection for our merchant profile?
- How are refunds and chargebacks recorded against the original invoice?
- Can we export the full billing history, plan changes and consent records if we leave?
- Who reconciles gateway and wallet statements today, and how long does it take?
- What is the monthly cost of the support queue after launch, not just the build?
A 90-day plan
Weeks 1–2: document plans, renewal rules, tax treatment and the current manual workarounds. Output: a plan matrix and a reconciliation map.
Weeks 3–4: choose the gateway and billing approach, confirm merchant capabilities and agree the failure policy. Output: signed integration design.
Weeks 5–8: build the catalogue, renewal job, receipts and entitlement rules. Output: a working flow in staging.
Weeks 9–10: test failed payments, partial payments, upgrades, pauses, cancellations and refunds. Output: acceptance record per scenario.
Weeks 11–12: migrate a pilot cohort, run billing in parallel with the old method and publish the support macro set. Output: reconciled first cycle.
Metrics to review monthly
Involuntary churn, recovery rate after a failed payment, entitlement errors, reconciliation variance, refunds as a share of collected revenue and support tickets per hundred subscribers. Review the reasons, not only numbers.
Where this fits in our work
Subscription operations are delivered through Commerce Systems, with payment reconciliation covering the matching routine. The pricing page explains how build, integration and monthly care are separated. For the operating models behind these choices, read the comparison of subscription operations models.
Sources
- Stripe, Billing documentation, accessed 17 November 2026.
- Shopify, Subscription APIs for purchase options, accessed 17 November 2026.
- Recurly, Product documentation, accessed 17 November 2026.
- IFRS Foundation, IFRS 15 Revenue from Contracts with Customers, accessed 17 November 2026.
- PCI Security Standards Council, PCI DSS resources, accessed 17 November 2026.
Responses (0)
No comments yet. Add the first one below.
Leave a response
Your email address will not be published. Required fields are marked *.