Skip to content
Partners

Why build client sites on ebitex

Client work is judged on the day it launches and every month after. These are the reasons partners build on ebitex: how the money works, what the client ends up with, and what it is like to build on.

The commercial case

A revenue share on clients you bring

When a client takes ownership you are attributed for the first 12 months and earn 20% of what they pay, from a monthly statement. It is recorded at the moment of hand-over, so it cannot change under you.

One suite on every plan

Content, Forms, Assets, Data and Audience share one login and one bill, and every plan covers the whole suite. What a plan buys is scale: limits, people and environments. Your client is not assembling five vendors.

Nothing is deleted when a plan changes

Moving a client to a smaller plan never deletes anything. It only stops them creating more than the plan allows, so right-sizing the subscription later is safe.

Build for free, bill when it is real

A sandbox costs the client nothing while you work. They pay when they take ownership, which is when the site is something they have already seen working.

The client owns it

The account, the billing and the content are the client’s from hand-over. You stay on as the Agency role for as long as they want you to, and they can end it at any time. That is a better conversation to have than a hosting contract.

Pricing you can show a client

The plans and their limits are public and rendered live on the Pricing page, so what you quote and what the client later sees on their Billing page are the same numbers.

The developer experience

A starter kit you can outgrow

Ready-made Contracts, Templates, themes and a demo experience, plus a React renderer you can override one section at a time and eject entirely. Nothing links it back to ebitex afterwards.

Typed SDKs and content as code

A JavaScript Content SDK, Forms and Data SDKs, and a .NET Content SDK. Generate types from your content model, and keep the model itself in your repository and apply it like a migration.

An MCP server for agents

Point an AI agent at a client’s content with a key you mint and scope yourself, and let it model, write and publish. Management keys need the Pro plan or above.

Browser-safe keys

A delivery key limited to the origins a site runs on can be shipped in a page, so a static front end needs no server of yours. Server-side keys stay server-side.

Localization and personalization built in

Languages, a locale hierarchy per site, and audience-specific content are part of the platform on every plan, not something you bolt on for the client who asks.

Real separation of environments

On plans that include more than one environment: staging and live content, promotion between them, and roles scoped per environment, so a client’s editors cannot publish by accident while you work on the next change.

From an empty organization to a deployed client site with the starter kit, in under two minutes.

A fair comparison

Questions worth asking any platform

Whatever you are weighing ebitex against, these are the questions that decide whether a platform is good for client work. Here are our answers.

Questionebitex
Can I build before the client pays?Yes. A free sandbox per client, time-boxed and capped, with real Content, Forms, Assets, Data and Audience.
What happens at go-live?The client takes ownership of the same organization. Nothing is exported, imported or rebuilt.
Who owns the account and the billing afterwards?The client. You keep an Agency role they control.
Do I earn anything once it is live?Yes: 20% of what the client pays for the first 12 months, recorded at hand-over, paid from a monthly statement.
Can the client change their own content?Yes. Edit, then publish, in the browser. The live site changes with no deploy and no message to you.
How fast can I show something real?The starter kit and its React renderer put a working site on screen in under half an hour.
Am I locked in?The Delivery API is plain HTTP, the SDKs are published packages, the content model can live in your repository, and the starter kit’s renderer can be ejected into your project.
Support

Help that does not need a call

The developer site documents every public API and SDK, the help center covers each app for the people who use it, and the public samples repository has complete working sites, including one built on the starter kit. The starter kit’s own guide goes from an empty organization to a rendered page.

Partners enrol by talking to us, and that conversation is where questions about your first client get answered.

Fit

What ebitex is not

ebitex is a content platform for people who build sites, not a drag-and-drop page builder or a theme marketplace. You, or the starter kit, supply the front end. If the client’s requirement is to design pages freehand with no developer involved, another tool will suit them better. If you want a model, an API and editors your client can use without you, this is built for it.

Ready to talk about your first client?

Enrolment is by ebitex. Tell us what you build and for whom.