Service · Software development

Custom subscription management platform development.

A custom billing and subscription platform for organisations with recurring revenue: SaaS, telecom, energy, leasing, membership or streaming. We don't build a replacement for Stripe Billing or Chargebee where those off-the-shelf packages are sufficient. We build what's needed when pricing, industry rules or integration depth fall outside the standard.

∞

What a subscription management platform does.

A subscription management platform, also known as a billing platform or subscription management system, is the software that manages the lifecycle of a subscription: a prospect starting a trial, a customer converting, mid-term price and plan changes, periodic invoicing, payments, dunning for failed payments, any cancellation, and everything that follows in terms of retention and renewals. In the background runs the billing engine that calculates the right price for the right period in the right currency, with VAT and any discounts applied.

For many organisations, an off-the-shelf package such as Stripe Billing, Chargebee, Recurly, Maxio (Sage), Zuora or Salesforce Revenue Cloud is a perfectly good choice: these platforms have years of experience with SaaS flows and cover the vast majority of common use cases. We therefore explicitly do not replace these packages for standard recurring billing. We only build custom when pricing complexity, industry-specific rules, multi-entity requirements or compliance demands show that the off-the-shelf package causes more pain than it solves.

A related area we often help with is setting up the actual payment flow (Stripe, Mollie, Adyen, SEPA and iDEAL) as part of the broader platform. For organisations that want to connect their existing core systems to a new billing platform, this service ties in with our smart API integrations; for larger enterprise projects, see our enterprise software development page.

What sets custom billing apart from an off-the-shelf package.

Pricing engine
Volume tiers, add-ons, and regional and customer-specific discounts in a single model
Industry rules
Telecom CDRs, energy meter readings or lease mileage directly in the billing run
Deep integration
ERP, CRM, product platform and data warehouse in one chain
Customer portal
Branded self-service without white-label restrictions

Three types of subscription projects.

Which route suits you depends on whether you are extending an off-the-shelf package, building a complex billing engine from the ground up, or putting a platform layer in place for multi-entity groups with several product lines. The patterns below together cover the vast majority of the subscription management projects we get involved in.

Approach 01

Custom customer portal and integrations on top of an off-the-shelf package

Stripe Billing, Chargebee or Recurly enhanced with custom development

You already use a SaaS billing package, such as Stripe Billing, Chargebee, Recurly, Maxio or a similar solution, but the standard self-service portals don't meet your needs, or the integration with your ERP, CRM and product platform is incomplete. We build a branded customer portal in your own house style, connect it to the billing package via APIs, and set up two-way synchronisation with systems such as Exact, AFAS, HubSpot or Salesforce. The billing package remains the source of truth for subscriptions and invoicing; we build the layer around it that makes it work within your operations.

This route is the pragmatic choice for SaaS companies and B2B organisations that don't want to carry the complexity of their own billing engine, but do want to close the costly gap between the off-the-shelf package and their own business processes. For visualising MRR, ARR, churn and cohort analyses, we often build an adjacent dashboard; we describe that approach on our custom KPI dashboard page.

Branded customer portalStripe Billing APIChargebee / Recurly APIERP syncCRM integrationMRR / ARR dashboard
Approach 02

Custom billing engine for complex pricing

When off-the-shelf packages break down on pricing complexity

Volume tiers combined with add-ons, time-based scales, customer-specific discount rules, multi-currency with country-specific VAT, and pricing that depends on usage data recorded elsewhere in your system. Off-the-shelf packages break down here, not because they can't handle volume tiers, but because the combination of rules that is common in your market falls outside their model. We design a pricing engine that builds your business rules in explicitly: a transparent model that product management can maintain themselves, with an audit trail on every price change and pro rata calculations for mid-cycle changes that actually add up.

Next, we build the billing run that cycles periodically over active subscriptions, generates the invoices, processes payments via Stripe, Mollie, Adyen, SEPA direct debit or iDEAL, and handles the dunning flow with retries, email reminders and payment pages. The cancellation flow with retention prompts and the renewals logic for auto-renewal are part of the same chain, not separate modules that can't see each other's data. For customers who also want to integrate their order and delivery flow, this ties in with our custom order management system page.

Pricing engineVolume tiers + add-onsMulti-currency + VATBilling run + dunningStripe / Mollie / AdyenSEPA + iDEAL
Approach 03

Industry or enterprise platform for recurring revenue

Telecom, energy, leasing, insurance or multi-entity groups

For telecom providers with CDR records and bundle pricing rules, energy suppliers with meter readings and fixed-price contracts, leasing organisations with mileage corrections, insurers with premium collection, and groups with multiple product lines where subscriptions, leasing and maintenance run side by side, a SaaS package simply isn't enough. We build platform-layer billing for organisations like these: with carrier-grade volumes, an SOX-level audit trail, tax reporting per country and deep integrations with the operational core systems that the usage data comes from. For groups who also want to include their resource planning and ERP question, this ties in with our custom ERP system development page.

In projects like these, compliance is rarely an afterthought: SOX, GDPR, SSAE16/SOC, and cross-border VAT handling with OSS and IOSS schemes for EU deliveries. We build the controls in from the design stage, rather than bolting them onto a working system later. For organisations still at an early stage, we also say explicitly when custom software is overkill and a standard package would serve better. We do that check before we start, not once the first sprint is under way.

Telecom CDR billingEnergy meter readingsLease mileage correctionsMulti-entitySOX + SOC + GDPROSS / IOSS VAT

What you have at the end.

A production-ready subscription management platform, plus everything around it to manage it yourself or have us manage it.

Platform in production

Production, staging and development environments, in your cloud account or hosted by us.

Codebase + integration docs

Full source code, API documentation and integration guides under your control.

Admin guide

For your finance and operations team: plan management, billing run, dunning settings, audit export.

End-user training

Sessions for key users in finance, sales and support, plus video material for wider use.

Management (optional)

Monitoring, security patches, payment provider updates and ongoing development under contract.

When custom subscription management is the right choice.

Seven patterns where a standard package demonstrably hits its limits and the business case for custom billing becomes realistic.

Pricing

Complex pricing models

Volume tiers combined with add-ons, time-period scales, customer-specific discounts and multi-currency with the correct VAT per country. Standard packages support each element separately, but the combination often hits limits or leads to workarounds that make the system unmanageable.

Industry

Industry-specific billing rules

Telecom CDR records that are rated per call, energy meter readings taken monthly, lease agreements with mileage corrections, insurers with premium collection according to policy rules. These rules are rarely found in a SaaS package and need to live in your billing engine itself.

Group

Multi-entity and multi-product

Groups with SaaS subscriptions, lease agreements and maintenance contracts side by side, sometimes under different legal entities and with different tax regimes. Only a single platform serving all those product lines at once makes reporting and consolidation manageable.

Retention

Your own retention and expansion flows

Automated upsell prompts at usage thresholds, churn prediction based on behavioural signals, retention offers during the cancellation flow, win-back campaigns after cancellation. Standard packages have rudimentary versions of these. If you want to do something serious with them, you need your own flow.

Brand

Branded customer portal without white-label limits

Partners and customers see the billing environment as an expression of your brand. White-label portals from standard packages give a decent foundation, but they rarely follow your own design system and behaviour patterns. When brand requirements are higher, a custom portal layer always wins.

Integration

Deep integration with core systems

When billing needs to talk two ways with your ERP, CRM, product platform or data warehouse, and when changes to a subscription need to flow straight through to fulfilment, support tickets or operational dashboards, the standard API of a SaaS package often becomes the bottleneck. With your own platform, you stay in control.

Compliance

Strict audit and compliance requirements

SOX controls on revenue recognition, SSAE16/SOC reporting for enterprise customers, GDPR requirements around personal data in invoicing, and VAT handling for cross-border sales under the OSS and IOSS regimes. We build compliance in from the design stage, not later.

Scale

Carrier-grade volumes and latency requirements

Wholesale billing with millions of events per day, real-time usage-based rating, and batch runs that must complete within an overnight window. An infrastructure approach that scales with those volumes belongs in the platform from the design stage.

Not sure about a large project yet?

Test your idea first: a working prototype in 1 day

With OneDayBuild, we make your idea tangible in a single day for €1,150, so you know whether further development is worth the investment. Decide to go ahead with the full build? Then we deduct the cost in full.

View OneDayBuild →

How a subscription project works.

01Introduction→ 02Pricing model→ 03Build→ 04Live + management
Step 01

Introduction

What pricing model do you have, which systems need to integrate, and might a standard package already be enough?

Step 02

Pricing and data model

We define the plan catalogue, add-ons, discount rules and VAT rules explicitly, through workshops with finance, product management and sales ops.

Step 03

Building in sprints

Every sprint delivers a working build on staging. We build out the pricing engine, billing run, payments, customer portal and integrations incrementally.

Step 04

Live + management

Phased migration of existing subscriptions, dual running where needed, and ongoing management or handover to your IT team, depending on what fits.

The stack we work with.

For each project we choose what fits: vendor-neutral, and based on what your team already has experience with, which billing or payment providers are mature in your context, and which tax and compliance requirements apply. No religion about a single framework.

Billing platforms and engines
Stripe BillingChargebeeRecurlyMaxio (Sage)ZuoraSalesforce Rev CloudCustom engine
Payments and ERP/CRM
StripeMollieAdyenSEPA Direct DebitiDEALExactAFASHubSpotSalesforce
Frontend, backend and data
Next.jsReactNode.jsPythonGoPostgreSQLKafkaBigQuerySnowflake

Frequently asked questions.

What exactly is a subscription management platform?
A subscription management platform, also known as a billing platform or subscription management system, is the software that drives the lifecycle of a subscription: sign-up, trial-to-paid conversion, price changes, recurring invoicing, payments, dunning for failed payments, cancellation, renewals and the related customer communication. Under the hood sits a pricing engine that calculates the right price for the right period in the right currency, with discounts and VAT applied. At SaaS companies it is usually called a billing platform, in telecoms or energy people tend to speak of a rating and billing engine, and membership organisations talk about subscription management software. Under the hood, they largely do the same thing.
Do you replace Stripe Billing or Chargebee for our standard flows?
No, not if those packages cover your flows. Stripe Billing, Chargebee, Recurly, Maxio and similar solutions have been refined for years and handle the vast majority of standard SaaS billing cases well. We only build custom when pricing complexity, industry-specific rules, multi-entity requirements or integration needs demonstrably hit the limits of such a package. Often the right route turns out to be a hybrid: you keep the standard package as your billing source, and we build a branded customer portal and the deep integrations with your ERP, CRM and product platform around it. We prefer to do that check before we start, not once the first sprint is under way.
Can you support volume pricing, add-ons and customer-specific discounts at the same time?
Yes — it's one of the main reasons clients come to us for custom development. We design the pricing engine so that plan prices, volume tiers, add-ons, time-based tiers, customer-specific discount rules, regional pricing and short-run campaigns all sit in one explicit model. Product management can create new plans or rules themselves through an admin interface; finance can see, for every invoice, which rules and which changes were applied. Pro-rata calculations for mid-cycle upgrades or downgrades are built into the engine as standard, with an audit trail on every price change so everything stays reproducible.
How do you handle multi-currency and VAT for cross-border subscriptions?
Multi-currency appears in two places in the platform — in pricing (a plan can be issued in multiple currencies) and in billing (the invoice uses either a fixed exchange rate on the invoice date or an external FX feed). We handle VAT according to the rules that apply to your situation: the OSS scheme for cross-border B2C within the EU, the IOSS scheme for sales to consumers outside the EU where applicable, and reverse charge for B2B with a valid VAT number. We integrate with VAT validation services such as VIES and with tax providers such as Avalara or Vertex when the complexity justifies it — for most Dutch organisations, however, a custom VAT rule set is already sufficient.
What does a dunning flow for failed payments look like?
Dunning is the flow that kicks in when a payment fails — usually because of an expired credit card, insufficient funds or a SEPA reversal. We configure a series of retries at sensible intervals, followed by email communication in different tones: a friendly reminder, a second notification, a final warning before suspension. Customers can update their payment method via a payment page without having to go through support. If payment ultimately fails, automatic suspension or a downgrade follows, with an audit log on every step. For B2B segments where the finance relationship matters more than an automated retry, we can also route the dunning flow to your own account managers instead of the end customer — whichever behaviour suits your customer segment.
How do you connect the billing platform to your ERP, CRM and product platform?
Via APIs and — where needed — event streaming. A new or changed subscription triggers events that the relevant systems pick up: the ERP books the invoice and the revenue recognition, the CRM sees the upgrade or downgrade trigger for account management, and the product platform sets the right feature flags or access rights. For Dutch organisations this usually means Exact or AFAS on the ERP side and HubSpot or Salesforce on the CRM side. We work bidirectionally: a change in the CRM (for example, a sales discount) can also flow back to the billing platform. For clients who also want to feed their data warehouse and KPI reporting, we add an event stream to BigQuery, Snowflake or a comparable data warehouse.
What about audit trail, compliance and revenue recognition?
An audit trail isn't optional in a billing platform; it's a requirement. Every change to a plan, a subscription, a price or an invoice is logged immutably, with the user, timestamp, and original and new values. For SOX-relevant customers, we build in revenue recognition reporting in line with IFRS 15 or ASC 606, with an explicit waterfall from billed to recognised revenue per period. SSAE16 and SOC 2 reporting for enterprise customers is achievable through the same audit layer. We handle GDPR as standard: personal data in invoices is stored encrypted, with retention periods in line with tax legislation (seven years for the Dutch tax authority), and the right to be forgotten is handled through pseudonymisation rather than hard deletion, so the financial history stays intact.
What determines the cost of a subscription management platform?
The price depends heavily on scope and complexity. Three factors weigh the most. First: the complexity of the pricing model. A simple flat-rate subscription is fundamentally different from a telecom bundle with CDR records or an insurer with policy rules. Second: the number and depth of integrations. Integrations with ERP, CRM, payment providers, tax services and a data warehouse are each a scope of their own. Third: the compliance requirements. SOX controls, SSAE16 reporting, GDPR pseudonymisation and sector-specific regulations add work in every phase. We give an honest estimate after the pricing model phase; before that phase any figure is a guess, and we won't hold clients to it.
How long does a subscription management project take?
That depends on scope and starting point. An additional customer portal on an existing Stripe or Chargebee platform with a few integrations can be in production within a project of several sprints. A complete custom engine with pricing, billing run, payments, dunning, customer portal and the first set of integrations is a bigger project, usually delivered in phases: we get the first use case live relatively quickly, then keep building based on what the first customer group teaches us. Carrier-grade telecom or energy billing with millions of events a day and heavy compliance requirements is always a longer project. We give you an honest estimate after the pricing model phase; before that phase, any number is a guess.
Can we migrate existing subscriptions without interruption?
Yes, and in practice that is almost always a requirement. We work with a dual-running phase in which the new platform runs in parallel with the existing system: new sign-ups go straight onto the new platform, while we migrate existing subscriptions in phases, at a pace that fits the billing cycle. For customers with mid-month pro-rata issues, we build an explicit cutover per customer so that a duplicate or missed invoice can never occur. Reconciliation between old and new is a fixed part of the migration, not something we do afterwards once someone spots a problem.
What about ownership and lock-in?
You keep full ownership. The code, the database, the pricing rules and the integration configuration are in your name; we work in an environment that you manage or that we hand over at the end. Whichever billing platform or payment provider you choose, we make sure the application layer stays portable in principle: business logic isn't hidden in vendor-specific services, and we make any use of cloud- or provider-specific components explicit in the architecture docs so you know where a future migration would take work. Maintenance is always a service you can choose to take, never a dependency we lock you into.

Talk to us about your subscription management platform.

A no-obligation introductory call of half an hour. We listen to your pricing model, take a brief look at your current billing and payment stack, and give you direction you can use, even if it turns out that an off-the-shelf package is the better choice for now.

Edit content