Your platform already holds each business's services, team, hours and booking links. Here is how that becomes a website under your brand: what your platform provides, what we run, and what stays yours.
No website team to hire, no builder to maintain, no hosting to run. Your engineers expose one endpoint and sign one token, and we help set up both, on staging first.
Serve each business's details in one documented format. We read it server to server, and your data token never reaches a browser, a published site or a database row.
{
"business": {
"id": "biz_4821",
"name": "Juniper & Rose"
},
"services": [{ "name": "Balayage" }],
"bookingUrl": "https://book.acme.example"
}When a merchant clicks Website, your platform signs a short token and sends their browser to the builder. They arrive signed in, with no sign-up form and no second password.
{
"sub": "usr_91f2c",
"business_id": "biz_4821",
"role": "owner",
"exp": 1790673330
}Short illustrative examples. We share the full data format and sign-in contract with your engineers during setup. Acme Booking and Juniper & Rose Hair Studio are fictional.
The builder runs as your product. Merchants sign in on your domain, see your logo and colors, and change their sites without ever meeting Unshift.
Your platform already knows each business: what it offers, who works there, when it is open and where to book. Its website starts from exactly that, and stays in step with it.
The first time a merchant opens the builder, their site is created from a template for their kind of business, with their own details in place. No copy is invented, and a section with no data is left out.
Services, prices, team, locations and opening hours come from your platform, so a change there shows on the site within minutes, without anyone editing it twice. Everything else, including every word the merchant writes, is theirs to change.
Every Book button on the site opens your booking flow.
Add a Website button to your dashboard. It signs the merchant in to the builder, so there is no separate account to create and no second password to forget.
Switch off public sign-up and the builder has no sign-up form. Merchants arrive from your dashboard, already signed in.
Your token says who is signing in and in which role, so the business owner and the staff you let in edit the same site.
Admins of your deployment (your own support staff, and ours only where you agree to it) can sign in as a merchant to help with their site. Each time needs a reason, and it is recorded before the session starts.
HeadingLived-in color
Easy, wearable cuts on Haywood Road. Walk-in consultations on Saturdays.
Book an appointmentMerchants click any word on the page to change it, swap a photo, add a page and publish. A new headline or a holiday notice does not become a ticket for your support team.
A merchant can connect their own domain, with SSL handled for them, or keep an address on yours.
Your builder runs on a database project of your own, which we run for you in a region agreed with you, or which sits in your own account on request, so merchant accounts and sites are never stored alongside anyone else's. Form submissions from their sites are not stored in any database: each one is emailed to the business through our mail service, or sent to a webhook or a tool the business connects.
Sites are served from a global edge network, on hosting we run, with SSL on every address and on every domain a merchant connects.
Page titles, descriptions, social previews, sitemaps and structured data on every site.
Exporting a site as code is an option we switch on or off for each partner, so you decide whether merchants can take their site elsewhere.
How we keep partner data apart is on our security page. The data processing agreement for partners comes with the pilot agreement, and our list of subprocessors is public.
45 minutes with your product and engineering leads on your platform, your merchants and the data you hold. Then a private demo under your brand, and a pilot proposal in writing.
We set up your builder with your brand, your domain and a database project of your own. Your engineers add the data endpoint and the Website button on staging, and we run acceptance checks on two or three test merchants before anyone real signs in.
20 to 100 of your businesses, chosen with you. A fixed fee and a set period, agreed up front, with a success metric written into the contract and reviewed weekly with your product owner.
Every merchant, on terms agreed before the pilot started. Same stack, nothing rebuilt.
A small team. Your product owner works directly with the engineers who built it, in a shared channel, with replies in business hours during the pilot. We say what is built, what is planned and what is not, and we put it in writing.
A platform fee, plus a fee per live site: published sites, never accounts or drafts. You decide what merchants pay, or bundle the website into a plan. Figures come in a proposal after a first call.
Something else? Write to sales@unshift.ai
Software platforms whose customers are small businesses, starting with booking software for salons, barbers and spas. If your platform serves another kind of business, tell us about it.
Leave your details and we will reply by email to set up a working session with your product and engineering leads. Or book a call straight into our calendar.