Four ways to add a premium website product
The realistic options for a hosting, domain or naming business: honest trade-offs, and where lazysite Studio fits.
A provider adding a website product is really choosing a commercial model; the technology follows from it. Four models cover the realistic choices: reselling a hosted whitelabel SaaS, building on a headless CMS with a custom frontend, extending WordPress with AI plugins, or adopting lazysite Studio. Each is a legitimate choice for some businesses.
This page describes the four in turn, then compares them against the nine criteria that tend to decide the matter: ownership, margin, compliance, AI cost, data location, delivery capability, time to revenue, customer experience, and exit. It assumes you have seen the Studio landing page and are now evaluating seriously.
Option 1: reselling a whitelabel SaaS
The mature, fast-to-market option, with Duda as the reference and 10Web, Site.pro and others in the same pattern. You sign an agency agreement with the platform vendor, sell the product under your own brand, pay the vendor a monthly fee per site, and set your own retail price above it.
Its strengths are real: the fastest time to revenue of the four, the lowest technical burden, a polished editor your customers can use themselves, mature multi-site management, and strong vendor certifications: Duda's ISO 27001 is genuine reassurance for regulated customers.
The trade-offs are commercial. The per-site platform fee grows with your site count, shrinking your margin exactly when the product succeeds. Customer data sits on the vendor's infrastructure, on the vendor's terms. The AI features are the ones the vendor chose to build, at the price the vendor chose to set. Leaving means rebuilding every site on another platform.
Option 2: a headless CMS with a custom frontend
The developer path: Sanity, Directus or Strapi as the content backend, with a frontend built on top in Next.js or Astro. This is the most flexible option and the most technically demanding.
It offers maximum architectural freedom, a modern stack and, with Directus or Strapi self-hosted, full ownership of code and data. AI integration is strong and improving.
The trade-offs follow from the same freedom. It needs a substantial initial build and permanent developer capacity. Each customer's site is bespoke work, which is hard to package as a fixed-price, fixed-turnaround product. Design and copywriting remain your problem, and the compliance evidence is whatever you assemble yourself.
Option 3: WordPress plus AI plugins
The incumbent, and the realistic default for many providers today. Your customers already know it, the theme and plugin catalogue is effectively infinite, it is cheap and fast to start, the support talent pool is deep, and every AI vendor is building a WordPress plugin.
The problems grow with scale. Maintenance effort rises faster than the number of sites under management, and the plugin ecosystem is a real security exposure: most WordPress incidents originate in plugins. AI capability arrives plugin by plugin, each with its own pricing and behaviour, and the compliance picture changes with every plugin update on every site you host.
Option 4: lazysite Studio
A productised website service delivered by Open Digital, running on the lazysite open-source engine, sold by partners at agency prices under their own brand.
The provider owns the whole stack: code, data location, infrastructure and the customer relationship. AI runs only when a customer asks for a change, so its cost follows the number of edits and stays predictable as the site count grows. Design and copywriting are delivered by Open Digital from a guided questionnaire, so the product works without designers on staff. Sites are plain files with a full version history, and a CRA-aligned attestation package is available from Open Digital as a separately priced product: the only option of the four where such a package can be bought at all.
The trade-offs deserve equal weight. Studio is a young product. The visual editing experience works and is improving, and it currently trails Duda's level of polish. The ecosystem is deliberately small: themes come from a curated library, and extensions sit close to the core and are audited at each release, instead of filling a marketplace of thousands. Self-hosting assumes infrastructure you already run, or a hosting partner. And the engine is written in Perl: a deliberate, stable choice, and one that some technical evaluators will pause on.
The fifth path: a design agency partnership
One more route deserves naming, because it is arguably Studio's closest true competitor: referring customers to a traditional design agency, or white-labelling an agency relationship. A good agency delivers genuinely bespoke work, often deeper than any productised service can reach. The difficulty is that it cannot be put on a rate card: delivery time and quality vary by project, prices are negotiated per job, the agency's capacity caps how much you can sell, and referral fees are one-off rather than recurring. Studio occupies precisely that gap: agency-quality output, productised into fixed tiers, fixed prices and fixed turnaround, with a recurring hosting and care fee attached.
At a glance
| Criterion | SaaS whitelabel | Headless CMS | WordPress + AI | lazysite Studio |
|---|---|---|---|---|
| Ownership | Provider rents the brand surface and workflow; platform stays with the vendor | Provider owns the code; may self-host (Directus, Strapi) | Provider owns the install; inherits the plugin ecosystem | Provider owns code, data, infrastructure and the customer relationship |
| Margin, per site | Fixed retail minus a recurring upstream per-site fee | Set by the provider; depends on bespoke delivery cost | Set by the provider; depends on plugin costs and build time | Wholesale margin fixed by Studio tier |
| Margin, recurring | Platform fee scales with the site count | Hosting and support only | Hosting plus plugin licences | Hosting and care fee, with no upstream per-site fee |
| CRA compliance | Inherited from the vendor's own certifications | Provider-owned, or per-vendor for hosted backends | Provider owns the full stack burden, shifting with every plugin update | CRA-aligned attestation package available from Open Digital (separately priced) |
| AI cost model | Inference varies by feature; runs on vendor terms | Per integration, provider-built | Per plugin, uncoordinated | Runs only at the point of change |
| Data location | Vendor infrastructure | Provider choice | Provider choice | Provider choice |
| Delivery capability needed | Vendor provides the editor; design is the customer's job | Developer capacity to build and maintain | WordPress skill in-house or contracted | Open Digital delivers design and copy |
| Time to first revenue | Weeks | Months | Weeks | Days once installed |
| Exit and portability | Migrate away by rebuilding on another platform | Standard content export; frontend is bespoke | Site content exports; plugin behaviour has to be rebuilt | Files leave as-is, fully portable |
A fair comparison of realistic options. Cells describe what each option genuinely offers, judged on its own terms.
The margin economics, compared
Take a worked example and name the assumptions: a provider selling fifty premium sites over two years, at a retail build price near Studio's Gold tier (£3,200), with a hosting-and-care fee near £65 a month.
On the whitelabel SaaS route, the vendor's per-site fee (commonly £10 to £30 a month, varying by platform and volume) comes out of that recurring fee before your margin. At fifty sites that is roughly £6,000 to £18,000 a year paid to the vendor, and the amount grows with every site sold. The build margin is yours; the recurring margin is shared for as long as the site exists.
On the WordPress route the vendor fee is replaced by plugin licences (typically £5 to £30 a month per site across page-builder, AI and security plugins) and, more significantly, by maintenance hours that grow with the number of sites. The economics work at small scale and worsen quietly as the fleet grows. The headless route reverses the shape: modest recurring costs, but tens of developer-days of bespoke build per customer, which is a service business rather than a product line.
Studio's model keeps both sides with the provider. The wholesale build price fixes your margin on each site sold, and the hosting and care fee has no per-site deduction: at fifty sites the recurring fee is yours in full, against infrastructure you already operate. The exact wholesale rate card is in the partner pack; the shape of the deal is already clear from here.
Compliance and the Cyber Resilience Act
The CRA phases in through 2026 and 2027, and its practical effect on a hosting business is documentary: providers will increasingly need to hold evidence of their upstream vendors' security obligations; who patches what, on what timeline, with what disclosure process.
The four options handle this differently. A SaaS vendor's certifications cover the vendor's platform, and your own obligations as a provider remain yours to evidence. The open-source routes, headless and WordPress, leave the full documentary burden with you, spread across every component and plugin in the stack. For lazysite, Open Digital sells commercial providers a CRA-aligned attestation package as a separately priced subscription: documentation from the vendor of record, bought as a product. Among the four options it is the only place such a package exists to buy.
Where Studio does not win
If your customers demand a drag-and-drop visual editor at Duda's level of polish today, or your offering depends on a marketplace of thousands of ready-made extensions, Studio is the wrong choice for now: both are roadmap positions, and this page will say so plainly when they change. Providers whose whole value is self-serve editing are better served by the SaaS route today.
Where Studio fits
Studio suits providers who want to own the stack, sell a genuinely different product, keep AI costs predictable, and buy their compliance documentation from the vendor of record rather than assembling it themselves. If that sounds like your business, the Studio landing page shows the packaging and pricing; and if you would rather see it applied to your own company first, the proof-site offer puts a live site in front of you within 48 hours.