Custom development
You set the requirements, the system follows
First we sort out whether it is configuration, a common industry need, or truly custom — the first two cost you nothing extra. For real development, feasibility, timeline and price are all on the table before any work starts.
When custom work pays off
Four cases where changing the system beats changing your habits
Your rules do not match the common practice
Shift patterns, commission splits, deposits, comps — these rules took years to settle and changing them means changing people. Bending the system is easier than retraining twenty therapists.
The report head office wants does not exist
Group-specific KPIs, cross-store comparisons, how cost and margin are split — standard reports cannot produce them, and exporting to Excel puts you back where you started.
Equipment you already own needs to connect
Access control, lockers, barriers, wristband readers, self-service kiosks, or the finance, OA and group membership systems you already run. Without integration everything gets keyed in twice.
Your group has its own governance rules
How many approval levels, who can see which numbers, what a document must look like — the things written in your policy only count once they live in the system.
First, which kind is it
The vast majority of requests need no custom work
Anything configuration can solve, or that the whole industry needs, is not custom work — only a small number of specific needs call for separate development. The first thing we do with any request is help you tell which kind it is.
Kind one
Configuration solves it
The switch is already in the system, it just was not found or was set wrong. A consultant sets it up remotely.
No charge
Kind two
Common industry needs
Features most of your peers need, or that follow common industry practice, are not custom work. We put them on the product roadmap, build and release them, and tell you which version to expect.
Not custom · Scheduled release
Kind three
Extension of existing features
Rules only your business uses: one more field, one more calculation, one more column on a report, one more line on a document — built on top of what exists.
Priced by effort
Kind four
A project of its own
A new module, a new integration, a complete flow across clients. Full cycle: plan, quote, contract, acceptance.
Priced per plan
We tell you which kind it is and why — what already exists, what is common to the industry, what needs building just for you. We do not dress up a settings change as development work, nor charge a common need as custom work.
How we work
Five steps from first conversation to go-live
Step 1
One-on-one requirement talk
A consultant and a product person both listen. You describe how it works today, where it breaks and what you want instead; we pin down the boundary between what must change and what is just habit. You get written notes to confirm.
Step 2
Feasibility assessment
Whether it fits the current architecture, whether it touches settlement and reconciliation, which clients are affected. If it cannot or should not be built, we say so and offer an alternative.
Step 3
Plan and quote
The plan states what gets built, how acceptance is judged and when it ships; the quote covers all of it at once. Both arrive together, and the contract only follows your approval.
Step 4
Build and integration
Progress against milestones, with a usable build for you to try partway through, so nothing is discovered to be misunderstood at the very end.
Step 5
Go-live and acceptance
A trial run in your store first; full rollout once the numbers reconcile. Acceptance is exactly the criteria written in the plan, nothing vaguer.
After go-live
Upgraded with the main release
Custom parts enter our release maintenance, so upgrades never leave them behind and nothing has to be rebuilt each time.
Cost and payment
You can see where the number comes from
There is no fixed price list — the same sentence of requirement can mean five times the work depending on depth. So we pin the requirement down far enough to estimate, then give you a number that holds.
Priced by development effort
Once the requirement is confirmed we estimate the actual work involved, not how important the feature feels to you.
One quote, all in
Everything in the plan is inside the quote. If it turns out harder than we expected, that is our estimate to answer for, not a surcharge.
Paid in stages
On signing, on acceptance, and after it has run stably in production. Exact split is written into the contract.
Changes priced separately
Anything added midway gets its own estimate for time and cost, so it does not eat into the agreed go-live date.
Within two business days of the first conversation you get our classification; if development is needed, the plan and the quote come with it.
Where we draw the line
Some custom work we turn down
Saying what we will not build is more useful than listing what we can — it saves finding out halfway through that we are pointed the wrong way.
Anything that muddies the books
Bypassing reconciliation, editing settled records, making money hard to trace — we do not build these. Being able to audit the money matters far more than saving a click.
Anything outside store operations
E-commerce, social, short video and the like have nothing to do with running a foot spa or bathhouse. We would not do them well, so we do not take them on.
Anything that trades away settlement accuracy
Changes touching the commission and settlement engine get an impact assessment first. If the only way to build it is to give up correctness, we will say no and propose an alternative.
Anything agreed only verbally
What gets built and how acceptance is judged goes into the plan in writing. Whatever is not in the plan is not part of the delivery — that protects both sides.
Common areas
What people usually customise
Reports and data definitions
Your group's own daily figures, cross-store comparisons, how cost and margin are split, the one summary the boss actually reads.
Commission and settlement rules
Unusual splits, cross-store sharing, performance tied to shift patterns, mentor and apprentice arrangements.
Receipt and document templates
Header, fields, QR codes, multi-copy printing — matching the paper your store already uses.
Hardware integration
Access control, lockers, barriers, wristband readers and kiosks, so opening a tab and spending stay on one chain.
Third-party system integration
Finance, OA, group membership, redemption on outside platforms — entered once, present on both sides.
Member mini program and campaigns
Home layout, campaign mechanics, your own top-up and voucher schemes, in your own brand.
Ownership and upkeep
Who owns it, who maintains it
The custom feature is yours to use
Scope of use goes into the contract: which stores, which legal entities. In writing, not on trust.
If it turns out common, it joins the standard product
If your custom feature later proves useful across the industry, we merge it into the standard version and maintain it — you no longer carry the upgrade cost for it alone.
Your data stays yours
Operational data can be exported at any time. Product source code belongs to our standard product and is not delivered separately; raise it before signing if you need otherwise.
What people ask about custom work
- It depends on the kind: configuration is same-day; a common industry need ships with the product roadmap, and the assessment tells you which version to expect; an extension of existing features is usually one to two weeks; a standalone project follows the milestones in its plan, and the assessment gives you firm dates. We do not answer with "as soon as we can".
Tell us what you need solved
Describe how it works today, where it breaks down and what you want instead. The more specific, the more we can tell you in the first conversation instead of going back and forth.
Not sure whether you even need custom work? Call us — a consultant can first check whether configuration already covers it.