Automating client onboarding

Update your website.Use a modern CMS.

How ScaleMind built SiteMaker — a multi-tenant publishing platform that turns any live website into a fully managed, editable site, verified pixel-for-pixel against the original. The site you are reading runs on it.

The problem

Most rebuilds quietly discardthe site you paid for.

A website rebuild usually means pouring your content into somebody else’s template. The design goes, the URLs move, and what comes back is an approximation of the thing you spent months getting right — defended on the grounds that the old site had to go somewhere.

SiteMaker starts from the opposite premise: the site you already have is the specification. We reproduce it as a real application, verify the reproduction against the original screenshot for screenshot, and hand you a CMS that speaks in your site’s own vocabulary rather than a builder’s.

What we built

A CMS that learns your site’s language.

Three ideas do most of the work. None of them require the platform to know anything about your site in advance.

It reads your site, not a template

Every site publishes a catalogue of what it can render — its own templates, sections and blocks. The CMS reflects that back as an editing interface in your vocabulary, and knows nothing about your site until your site says so.

Onboarding starts with a URL

Paste an address. A headless browser captures every page, a classification pass maps what it finds, and the result is rebuilt as a real application with your content already in it.

Editing and publishing never collide

Every site runs two deployments at once: a private preview where you draft, and the live site pinned to published content. Publishing is deliberate, and it never interrupts whoever is editing.

How it works

From a URL to a site you can edit.

The whole pipeline runs in an afternoon, and every stage leaves evidence you can inspect.

  1. 01

    Paste the URL

    We crawl the site, capture every page at full fidelity, and keep those captures as the reference of record.

  2. 02

    Rebuild

    Each page is reconstructed as a server-rendered React application and its content imported into the CMS as an editable page tree.

  3. 03

    Verify

    Rebuilt pages are diffed against the original captures, pixel for pixel, at desktop and mobile widths. Nothing counts as done until the diff is clean.

  4. 04

    Edit and publish

    Edit in place in the browser, preview instantly, publish when you are ready. Your site, your domain, your assets.

Proof

The page you are reading is...the product demonstrating itself.

This site was reproduced from its own live original, imported as a tenant, and is served from the CMS it advertises — same pipeline, same verification, no exception made for the vendor. ScaleMind’s own site moved the same way, off a website builder and its proprietary CMS, without losing a pixel.

Underneath: a Python API, server-rendered React on every tenant, MySQL, and infrastructure — hostnames, certificates, services — provisioned automatically per site.

Next step

Point it at a site,SiteMaker does the rest.

Send us a URL and we will show you the same site running on SiteMaker — with the diff to prove it is the same site.

Tell us about your project

Most of this form stays hidden. Answer a question and only the ones that follow from it appear, so it is shorter than it looks.

The people on your side
Is anyone else involved?
Your website today
Do you have a website already?
What would you like us to build?
Pick the closest one
Hosting and address

Every site runs in two places at once. A private Preview you edit against, and the public site your visitors see. Publishing never interrupts editing.

Who hosts the public site?
Editing, extras and launch
What else do you need?

Leave it blank if there is no fixed date.

No date yet
Anything else

A band is enough. It tells us which of the routes above is realistic.