Questions and answers.

A website builder that your platform offers to the businesses it serves, under your own brand. Each merchant's site starts filled in from your platform's data and stays in sync with it.

Software platforms whose customers are small businesses. We are starting with booking software for salons, barbers and spas.

Retention: a merchant whose website runs on your data has one more thing to lose by leaving. Revenue: a product line you price, sold as an add-on, in a bundle, or both. Reach: your data and booking links on every site, and every Book button leads back into your product. Effort: no website team to hire, because we run the builder, the templates, publishing, hosting and updates.

No. The builder carries your name, logo, colors, fonts and favicon on every screen, in light and dark mode, on a domain of your own, and every link back to Unshift can be switched off.

Public sign-up, Unshift billing, the template library, the AI assistant connector, every link back to Unshift, and code export.

From a Website button in your dashboard. They are signed in with no sign-up and no second password, and the first visit creates their site from a template for their kind of business.

Their services, prices, durations, team, locations, opening hours, booking links, name, description and logo, from your platform. No copy is invented, and a section with no data is left out.

They click any word to change it, swap photos, add pages and publish. The owner and the staff your platform lets in can edit the same site.

The site follows within minutes. Services, prices, team, locations and opening hours stay in sync with your platform, and words the merchant wrote stay as they wrote them.

In your product. Every Book button on a merchant's site opens your platform's booking flow.

Yes. A site gets an address on your platform's domain, or the merchant connects their own domain. Both are served with SSL.

Every site has page titles, descriptions, social previews, a sitemap and structured data.

Two things: a business data endpoint that our servers call, and a signed sign-in token for when a merchant clicks the Website button in your dashboard. We help you set up both, on staging first.

One documented format: business name, category, tagline, description, contact details, logo, locations with addresses and opening hours, services with category, duration and price, staff with role, bio and photo, booking links and photos.

No. The endpoint is called server to server, and the token never reaches a browser, a published site or a database row.

Your platform signs a JWT: HS256 with a shared secret, or RS256 or ES256 checked against keys you publish. It carries your user id, the business id, email, name and role (owner or staff), and it is single use and valid for at most two minutes.

No. Accounts are keyed by your platform's user ids, never matched by email.

Yes. Setup runs on staging first, with acceptance checks on two or three test merchants before anyone real signs in.

In a database project of your platform's own, which we run for you in a region agreed with you, or which sits in your own account on request. Merchant accounts and their sites live there, never alongside another platform's.

Run by us: the builder, the site API and hosting for your merchants' sites. Shared: the build service, image storage (in your own folder) and the sender for form emails. Sites are served from a global edge network with SSL.

No. Each submission goes to the business by email, or to a webhook or a tool the business connects, and none is stored in any database.

Yes, for support. Only admins of your deployment can: your own team, and ours only where you agree to it. Every sign-in is recorded with its reason before it starts.

SOC 2 is planned, not held.

Yes. A data processing agreement for partners comes with the pilot agreement, and our subprocessors are listed on the subprocessors page.

A platform fee, plus a fee per live site. A live site is a published one: accounts and drafts are not charged. Figures come in a proposal after a first call.

You decide. Sell the website as an add-on, bundle it into a plan, or both.

With setup on staging, then a paid pilot with 20 to 100 of your businesses, chosen with you. The pilot has a fixed fee and a set period, agreed up front, and a success metric in the contract that we review weekly with your product owner.

Rollout to every merchant, on terms agreed before the pilot starts. Same stack, nothing rebuilt.

A small team. Your product owner works directly with the engineers who built it, in a shared channel, with responses in business hours during the pilot. Your team supports merchants as it does today, and we support your team.

A 45-minute working session with your product and engineering leads, a private demo under your brand, and a pilot proposal in writing.

Yes. Your site keeps working.

As usual, at studio.unshift.ai.

Write to support@unshift.ai.