A customer experience that fits the operation you already run.
Rehost can build and operate the customer-facing app and website around your approved services, locations, booking flow, memberships, rewards, and content. The scope states which existing systems stay, which integrations are feasible, and which regulated-data requirements need separate review.
Settle the operating questions before comparing feature lists.
These are the decisions that determine whether a managed customer app and website will simplify the operation or add another layer to maintain.
01
Do we have to replace our booking or practice software?
No. Replacement is a scope decision, not a default.
The current booking, payment, membership, or clinical system can remain the system of record when its API, vendor terms, and workflow support the approved customer experience. If replacement is proposed, migration, validation, parallel running, and ownership responsibilities must be written down first.
Confirm in the scope
Current system of record
Available API and vendor permissions
Migration and validation owner
Fallback if an integration is unavailable
02
Can one experience serve more than one location?
Yes, when location rules and data boundaries are defined before build.
A shared app can present location-specific services, hours, staff, availability, memberships, and content. The scope must say which information is shared, which is location-specific, and who approves changes. It should not assume that every third-party system exposes the same multi-location controls.
Confirm in the scope
Shared versus location-specific services
Location selection and permissions
Membership and reward rules
Reporting and approval responsibility
03
What changes when a wellness operation handles regulated data?
Data classification and contract requirements come before feature design.
Rehost does not assume that a med-spa or wellness project is inside or outside a specific regulatory regime. The discovery process identifies the data collected, the systems that store it, who can access it, and which agreements or controls are required. Clinical records should not be pulled into a customer app simply because an integration exists.
Confirm in the scope
Data types and intended use
System of record and access roles
Required agreements and vendors
Retention, export, and incident responsibilities
04
What can staff stop administering?
Rehost can own the customer-facing publishing and software work named in the plan.
The team can request approved content, service, location, campaign, and interface changes through the agreed channel instead of maintaining another site or app console. Staff still own the operational decisions, approvals, schedules, clinical work, payments, and internal records assigned to them.
Confirm in the scope
Included change types
Approval owner
Response and release targets
Work that remains with staff
05
How will we know whether it helps?
Choose operational and conversion measures before launch, then keep them attributable.
A useful plan names the actions that matter, such as booking starts, completed requests, membership interest, repeat visits, or qualified leads. Analytics and advertising connections require consent, account access, and stable event names. Rehost does not promise a result that the organization cannot measure from a reliable source.
Confirm in the scope
Primary customer action
Source system for the outcome
Consent and account ownership
Review cadence and decision threshold
Keep customer experience and systems of record distinct.
A managed app can simplify what clients see without forcing every internal tool into a replacement project.
Rehost can scope and operate
Branded app and responsive website
Location, service, content, membership, and reward interfaces
Approved integrations and customer notifications
Hosting, monitoring, analytics, and included publishing work
Usually retained or separately approved
Booking, payment, payroll, or clinical systems that remain the record of truth
Vendor subscriptions and API access not included in the Rehost plan
Clinical judgment, regulated records, staffing, and service delivery
Account, export, license, handoff, and end-of-service terms named in the agreement
Published US starting point
$950
USD per month for Business, up to 2,000 monthly active users
The published Business tiers are $950, $1,500, and $2,500 per month by monthly active users. The proposal confirms locations, integrations, third-party costs, compliance work, and the launch target.
Rehost publishes attributable client statements for a nail salon and med spa. The records explain what each statement supports and hold back independent metrics pending customer sign-off.
Questions beauty and wellness operators ask first.
Direct answers about systems, locations, pricing, regulated data, and evidence.
Does Rehost replace Vagaro, Boulevard, Mindbody, or our EMR?
Not automatically. The current system can stay as the record of truth while Rehost operates the approved customer-facing experience. Replacement or migration is proposed only after API access, vendor terms, data requirements, and operational risk are reviewed.
Can one app support salons, spas, or studios at several locations?
Yes, if the scope defines shared and location-specific services, staff, availability, memberships, content, permissions, and reporting. Integration capability still depends on each existing vendor and account.
Is Rehost HIPAA compliant?
A public page cannot answer that for every project. The scope must identify the data, workflows, vendors, access roles, and required agreements. Rehost does not treat clinical or regulated data as ordinary marketing data.
How much does Rehost cost for a beauty or wellness group?
Published US Business pricing starts at $950 per month for up to 2,000 monthly active users, then $1,500 up to 10,000 and $2,500 up to 50,000. Locations, integrations, third-party costs, regulated-data work, and transition terms are confirmed in the proposal.
How fast can a salon or med-spa app launch?
The target depends on approved scope, integrations, source content, account access, data review, and approval speed. Rehost puts the launch target in the proposal after those inputs are known.
What customer results can Rehost prove publicly?
Rehost currently publishes attributable statements from Vintage Nail Bar and Lumia Med Spa. Their evidence pages explain what each statement supports. Independent savings, hours, and before-and-after metrics remain pending customer sign-off.
Who owns the content, data, code, and design?
Customers retain the content and data they submit. Rehost owns its service software, code, and designs unless a signed customer agreement states otherwise. Accounts, licenses, exports, handoff, notice, and service-end terms follow that agreement.
Map the customer experience before choosing what to replace.
Bring the current booking, payment, membership, website, and reporting setup. We will identify what can stay, what Rehost can operate, and what needs written validation.