Custom development
Custom software development for wellness businesses
The standard Yujian Cloud plan covers the common operating workflows of wellness centers, TCM clinics, aromatherapy studios, and healing spaces. When your operation needs something beyond it — a specific workflow, an integration, a different deployment shape — that is custom development. We explain the process and its boundaries first; proposals and pricing come after.
How it works
Six steps from one workflow to item-by-item acceptance
01 · Requirement confirmation
Start with one real business workflow: the current state, where it gets stuck, and the outcome you need. Please do not include health records, client personal data, or sensitive documents.
02 · Scope assessment
We assess whether the standard plan can be configured to cover it, and whether the required integrations and third-party dependencies are feasible. Conclusions are stated plainly — we write down exactly what can be done.
03 · Demo and proposal
Coverage is demonstrated in a real system, not mocked up in slides. The proposal states what is included and what is not; capabilities marked as in testing or planned are verified against live demos.
04 · Itemized quote
Pricing itemizes the confirmed scope line by line, and the full cost structure is agreed before signing. Third-party accounts and usage costs are settled separately, never mixed in.
05 · Development
Work proceeds against the written, mutually confirmed schedule, with progress shared at key milestones. A schedule is only issued after scope confirmation — it is never estimated or promised before that point.
06 · Acceptance
Delivery is accepted item by item against the written feature list. Anything that misses the list does not count as delivered, and pre-acceptance status never represents production being live.
Stated up front
Beyond pricing, these boundaries come first
No unverified timelines
Before requirements and scope are assessed, no date is promised. The governing schedule is the written one issued after scope confirmation.
No medical features
We do not build disease diagnosis or treatment features. Related questionnaires are used only for non-diagnostic preference and self-assessment scenarios.
No unverified capabilities
Integrations and deployment options are feasibility-checked first. Capabilities marked as in testing or planned are verified against live system demos.
Third-party costs itemized
SMS, payment channels, and similar third-party accounts and usage costs are settled separately at actual usage, listed line by line at signing.
FAQ
Frequently asked questions
How is custom development different from the standard SaaS plan?
The standard Yujian Cloud plan is an annual subscription covering the common workflows of wellness centers, TCM clinics, and aromatherapy studios — membership, booking, checkout, and marketing — with the client-facing side running on WeChat Mini Programs (WeChat only). Custom development is for specific workflows, integrations, or deployment shapes the standard plan does not cover. It is scoped and quoted separately, and never bundled into the SaaS fee.
Do you commit to delivery timelines?
No. We do not commit to any timeline before requirements and scope are verified. A schedule is issued together with the quote, after scope assessment and proposal sign-off, and it is the written, mutually confirmed schedule that governs delivery. Before that point you get the process, not a date.
How is custom development priced?
The quote itemizes every piece of the confirmed scope, and the full cost structure is agreed before signing. Third-party accounts and usage costs — SMS, payment channels, and similar — are settled separately at actual usage and are never mixed into the development quote.
What kind of work do you decline?
We do not build medical diagnosis or treatment features. We do not take on requirements that violate WeChat platform rules or whose feasibility we cannot verify. Assessment conclusions are stated plainly: we write down exactly what can be done, and we say no to what cannot.
What is the first step when the standard plan does not cover a workflow?
Describe one real business workflow you need to improve, using the form on our contact page (please do not include health records or client personal data). We first assess fit: if the standard plan can be configured to solve it, we will not push custom work. If it genuinely cannot, the project moves into scope assessment and a demo-based proposal.
Start with one business workflow
Describe one real workflow you need to improve. We assess fit first: if the standard plan can solve it, we will not push custom work; if it genuinely cannot, you get a scope assessment and a demo-based proposal.