Taking a bilingual booking platform to production, and keeping it there

The challenge: an owner-operated business running on software that does not fit it

A studio business runs on bookings, memberships and payments, and most reach a point where the off-the-shelf tool covers perhaps three quarters of what they do. The remaining quarter is handled manually, by the owner, in the evening.

Bilingual operation makes it worse: a platform that handles two languages as an afterthought produces a customer experience that is fluent in one and awkward in the other, and the awkward one is usually where the growth is.

The approach: build it, then stay responsible for it

ASE designed and delivered a bilingual booking platform with subscription payments, membership management and owner analytics. The analytics were treated as part of the product rather than a later addition, because an owner-operated business needs to see what is happening without commissioning a report.

The platform was taken to production and is live. Management consulting continues alongside it on expansion and certification, which is the part that separates a delivered system from a system that keeps earning.

Subscription payments were the part that had to be right first. Recurring billing is where a small business either gains predictable revenue or acquires a monthly reconciliation problem, and the difference is decided by how the edge cases are handled: a failed charge, a mid-term change, a cancellation. Those were specified before the interface was designed.

European rules make that specification narrower than it first appears. The strong-customer-authentication exemption for a recurring series applies only where the amount and the payee are both the same each time. A studio charging a fixed monthly membership sits inside it; the moment the model includes a class pack, an add-on or a no-show fee, the charge amount varies and the transaction falls outside that exemption, so it has to run as a merchant-initiated transaction instead. That is a decision about how the mandate is set up at sign-up, not something that can be corrected at the point of the first failed charge.

The results: in production, and still supported

The platform has been live since 2026, carrying bookings, subscription payments and membership management, with owner analytics in the same product.

The engagement did not end at go-live. That is the intended shape: the studio has a system in production and an ongoing line back to the people who built it, rather than a handover and a support address.