Reselling managed EspoCRM to clients in 2026

TL;DR

• Small clients are priced out of per-seat CRMs. Salesforce Pro Suite runs $100 per user per month; HubSpot Sales Hub Professional is $100 per seat plus a $1,500 onboarding fee.

• EspoCRM is an open-source CRM under the AGPLv3 license. It has no per-seat fee, so a client's whole team works from one instance at a flat cost.

• The reseller model is one isolated EspoCRM per client. The wholesale cost is €9 per month per instance; agencies price the managed service at €40–80 per month.

• At 20 clients, that is €620–1,420 per month in recurring margin — and the cost stays €9 even as a client's team grows.

• Your product is the configuration and the single point of accountability, not the hosting. This post covers the math, the isolation model, what white-label actually requires, and where the gaps still are.

Why small agencies are productizing a CRM line in 2026

A client asks whether you can host their CRM too. The honest reason they ask: per-seat pricing has priced their team out. Salesforce starts at $25 per user per month and reaches $175 at the Enterprise tier. A managed open-source CRM turns that recurring client cost into recurring agency revenue.

The pattern repeats across web, marketing, and growth shops. You build a client's site, run their campaigns, and set up their tools. Then the CRM question lands.

Most small clients can't justify enterprise CRM pricing. Salesforce Pro Suite is $100 per user per month, billed annually. HubSpot Sales Hub Professional is $90 per seat annually, or $100 monthly, plus a one-time onboarding fee of $1,500. Even Pipedrive's Professional tier is €49 per user per month. For a five-person team, those numbers reach $500 a month before add-ons.

The squeeze got tighter in the last year. Salesforce raised list prices on its Enterprise and Unlimited tiers in 2025. Per-seat tools keep climbing while small clients' budgets stay flat. That widening gap is the opening an agency can productize.

The agency sees the opening. A managed CRM line is recurring revenue, it deepens the client relationship, and it fits work you already do. The objection is operational, not commercial. You don't want to run servers, field 2am outage calls, or become a hosting company by accident.

That objection is solvable. The rest of this post shows how the model works with EspoCRM, what the margin looks like, and where the honest limits are today.

The agency math

One isolated EspoCRM per client costs €9 per month wholesale. Agencies price the managed service at €40–80 per month, because the value is the setup and the ongoing management, not the server. At 20 clients, the recurring margin lands between €620 and €1,420 per month.

Start with the unit. A single managed EspoCRM instance is €9 per month — one app, one client, fully managed. You sell that inside a productized service priced at €40–80 per month, depending on how much configuration and support the client needs.

The margin per client is €31–71 per month. Twenty clients put recurring margin at €620–1,420 per month. Fifty clients put it past €1,500. The revenue compounds because it recurs, and churn on a working, configured CRM is low.

EspoCRM's license creates the structural advantage. It is released under the AGPLv3 and runs self-hosted, so it has no per-seat fee. A client's whole team works from one instance. When a client grows from five users to fifteen, a per-seat SaaS bill triples. Your cost stays €9. The client's value rises while your input cost holds flat.

The table below shows what a five-person client pays today, against a flat managed EspoCRM line.

SaaS list prices are 2026 figures in USD (Salesforce, HubSpot, Zoho) and EUR (Pipedrive), taken from each vendor's pricing page. The DANIAN wholesale cost and the agency retail range are in EUR.

Zoho is the cheapest mainstream option, and at five seats it still costs more than a flat managed EspoCRM line — with a bill that climbs as the team grows. The managed EspoCRM line stays flat and covers every user.

Run the same comparison annually and the gap widens. A ten-person client on Salesforce Enterprise pays around $21,000 a year. The same team on HubSpot Sales Hub Professional is roughly $10,800 plus onboarding. Zoho's Professional tier, the cheapest mainstream option, still runs about $2,760 a year for ten seats.

A managed EspoCRM line covers that ten-person team for one flat monthly fee. The seat count doesn't change your wholesale cost. It doesn't change the client's price either, unless they ask for more work. That is the structural advantage you're selling: a bill that holds steady while the client's headcount climbs.

A note on honesty, because it protects the relationship. The €40–80 price is not a markup on €9 of hosting. Framed that way, the client eventually feels overcharged. You're selling a configured CRM, ongoing changes, and one person to call when something is wrong. The €9 is a cost input, the way a hosting bill is a cost input for the site you already manage.

See managed EspoCRM at €9/month.

Why one instance per client beats shared multi-tenancy

EspoCRM is single-tenant software. Running ten clients on one shared instance is fragile — one client's customization can break another's, and a load spike hits everyone. The clean model is one isolated instance per client, each in its own container with its own resources.

The temptation is to save money by putting several clients on one EspoCRM and separating them with roles. It doesn't hold up. EspoCRM stores one organization's configuration per instance. One client's custom fields, pipelines, and workflows are the same ones every other tenant sees. Change one and you risk changing all.

Isolation also matters for trust. Client data should never sit one permission mistake away from another client's sales team. Resource contention is real too — one client importing 200,000 contacts shouldn't slow every other client's CRM.

The model that works is one EspoCRM per client. At DANIAN, each app runs in its own hardened container with isolated networking and its own CPU, RAM, and storage allocation. One client's instance can't reach another's data. One client's load doesn't touch another's performance. The boundaries are real, and the backup and patching discipline is the same one we'd run if every app had its own machine.

You also choose the region per client, from 21 datacenter locations across six continents. Host a client's instance close to their users for lower latency. If a client needs their data in a specific region — an EU region, for example — you select that region for their instance.

Reliability is the reseller's reputation. One outage on a shared instance hits every client at once. An agency's name is on all of them. Per-client isolation contains that blast radius, so a problem on one instance stays on one instance.

Patching, monitoring, and backups run per instance. A fault is caught and fixed on its own instance, without spreading to the rest of your book.

Your real product is configuration, not hosting

EspoCRM is configured through its admin panel without code — custom fields, pipelines, workflows, and role-based dashboards. That configuration is the agency's product. The hosting underneath is a commodity; the CRM that fits a client's exact sales process is not.

A CRM is only useful when it matches how the client actually sells. That match is the work, and it's where an agency earns its retail price.

EspoCRM does this without developers. The Entity Manager adds custom entities, fields, and relationships from the admin panel. The Label Manager renames any term in the interface, so "Opportunity" becomes "Deal" or "Matter" to fit the client's language. Workflow and BPM tools automate follow-ups, assignments, and email triggers. Role-based dashboards let a sales rep and an owner see different views of the same data.

A standard setup for a new client usually means a clean pipeline with named stages, the lead sources that client uses, the handful of custom fields their process needs, a few email templates, and one reporting dashboard. Then comes the work that makes a CRM stick: importing the client's existing contacts and deals, mapping their pipeline stages, connecting their email, and training their team for an afternoon. None of that is hosting. All of it is billable, and all of it deepens the relationship.

Data migration is where a CRM project earns trust. A client switching from spreadsheets or an old tool arrives with messy data. Their contacts have duplicates, and their deals sit in inconsistent stages. Cleaning that, mapping it to the new pipeline, and importing it is skilled work.

That import is also the moment a client commits. Once their history lives in the CRM you built, switching away is painful. The configuration earns the retail price; the migration is what makes the relationship stick.

One detail makes this scale. EspoCRM stores your customizations in a separate directory, and a configuration built on one instance can be moved to another. Build a standard setup once — your default pipeline, your common fields, your reporting dashboards — and replicate it across clients. Each new client starts from your template, then gets tuned to their process. The first build is the investment; every client after is faster.

Setup is one-time; management is monthly, and that distinction matters for pricing. After launch, a client wants a new field or a changed pipeline stage. Next it's an extra automation or a new dashboard. Those small changes are the ongoing work that justifies a recurring fee.

The CRM is never finished, because the client's process keeps moving. That is why this is a managed service and not a one-time project fee.

The honest comparison: Salesforce's ecosystem and AppExchange are broader, with a deeper catalog of third-party add-ons. EspoCRM matches core CRM workflow — contacts, accounts, leads, opportunities, pipelines, automation, and email — at a fraction of the per-seat cost. For most small clients, core CRM done well is the whole job. EspoCRM's documentation covers the configuration options in depth.

What white-label requires, and what's here today

A full white-label reseller setup needs four things: a custom domain, a branded login and app, client billing pass-through, and a central control plane. Today, EspoCRM and DANIAN cover the first two cleanly. The last two are gaps, with the honest state and the workaround below.

White-label means the client sees your brand, or their own, and never the vendor underneath. Four pieces make that real. Two are solved today; two are not. Naming the gaps is the point — a reseller plan built on features that don't exist fails on the first client.

What works today:

• Custom domain per client. Each instance runs on a domain you choose — crm.clientname.com, for example. The DNS setup is handled for you; support performs the DNS edits during onboarding. The client never sees a shared hosting URL.

• Branded application. EspoCRM is built for white-label deployment. From the admin panel you set the logo, the application name, and the color theme; an extension changes the login background. The client logs into something that looks like their own CRM, not a generic product.

What isn't here yet:

• A central control plane. There is no single agency dashboard to provision and manage every client instance from one screen today. You manage instances individually, with support handling the changes that need a human. For an agency at five to twenty clients, that is workable. A central plane matters more at fifty-plus clients, and that is the point to revisit.

• Automated billing pass-through. There is no built-in pipeline that bills your clients on your behalf. You bill clients on your own system; the €9-per-instance wholesale cost is billed to you. For an agency that already invoices clients, this is a line item, not a blocker.

A formal partner tier — volume pricing, a commission structure, a partner dashboard — is a conversation rather than a published plan right now. If you're planning a CRM line at real volume, the next step is to see our Partner program.

You carry the €9-per-instance wholesale cost as an expense. It works the way hosting already does for the sites you manage. You invoice the client your retail price on your own schedule.

The margin is the difference between your retail price and that €9. It sits inside the managed service you already bill for, with no separate tooling required.

Add marketing automation and ERP when the client is ready

A managed CRM is the first line, not the last. Clients who want email campaigns and lead nurturing can add managed Mautic for marketing automation. Clients who need invoicing and inventory can add Dolibarr for ERP. Each is another €9-per-month managed instance and another retail line.

The CRM is the anchor. Once a client trusts it, the next tools are an easy conversation, and each one is another isolated instance you resell.

Marketing automation is the most common next step. Mautic is open-source marketing automation — email campaigns, drip sequences, lead scoring, and landing pages. It pairs with EspoCRM by design: the CRM holds the contacts and deals, Mautic runs the nurture. For a client who has outgrown a basic email tool, a managed Mautic line follows the same model as the CRM — €9 wholesale, your retail price for setup and management.

For clients who need more than CRM, Dolibarr covers ERP territory — invoicing, quotes, inventory, and accounting in one open-source suite. A services client running CRM and a product client needing stock and invoices can both sit on managed open-source instances you operate as a set.

The pattern is consolidation. Instead of stitching a client onto four separate SaaS subscriptions, you offer a managed open-source stack — CRM, automation, and ERP — each instance isolated, each at a flat price, each billed through you.

Pair it with managed Mautic for automation.

When this works, and when it doesn't

This model fits agencies with recurring client relationships, a standard CRM setup they can replicate, and clients priced out of per-seat SaaS. It doesn't fit one-off projects, clients who need Salesforce's ecosystem depth, or agencies that want a fully automated reseller portal today.

It works when:

• You have ongoing client relationships, not one-off projects. The model is recurring revenue, so it pays off where you retain clients for months or years.

• You can standardize. Build one strong EspoCRM configuration, replicate it, and your margin per client rises as setup time falls.

• Your clients are small-to-midsize and priced out of per-seat CRMs. The five-to-fifty-user client who balks at $100-per-seat pricing is the fit.

It doesn't work when:

• The client needs Salesforce's depth. If they depend on a specific AppExchange integration, advanced forecasting, or a large partner ecosystem, EspoCRM isn't a drop-in replacement, and forcing it serves no one.

• You want a turnkey reseller portal today. If your plan requires a central control plane and automated client billing on day one, the gaps above will frustrate you. Validate the model with a few clients first.

• You're chasing the lowest possible price. A client who would happily run their own server for €9 was never your client. Your buyer is paying for the configuration and the accountability.

FAQ

Is it legal to resell EspoCRM to clients?

Yes. EspoCRM is licensed under the AGPLv3, which permits commercial hosting and resale. You're selling your setup, configuration, and management — not the software itself, which stays open-source. The standard, unmodified instances you host already meet the license's source-availability terms.

Do I need to be technical to offer this?

No deep technical skill is required. EspoCRM is configured through its admin panel without code — fields, pipelines, workflows, and dashboards. The server, patching, and backups are run for you. Your work is configuring the CRM to each client's process and supporting the relationship.

What happens if a client's CRM breaks at 2am?

That is the part you're offloading. We patch, monitor, and back up every instance, with 24/7 chat and email where a named person replies. A failed update or an outage is ours to catch and fix. You keep the client relationship; you don't carry the on-call pager.

Can each client have their own domain and branding?

Yes. Each instance runs on a custom domain like crm.clientname.com, and the DNS setup is handled for you. Inside EspoCRM, you set the logo, application name, and color theme from the admin panel, so the client logs into something that looks like their own CRM.

How do I manage many client instances?

Today you manage instances individually, with support handling changes that need a human. There is no single agency control plane yet, which is workable at five to twenty clients. If you're planning a CRM line at larger volume, see the parner page.

What if a client adds users or outgrows the base plan?

EspoCRM has no per-seat fee, so adding users costs nothing in licensing. If an instance needs more CPU, memory, or storage, resources scale up — and we won't upgrade a client's resources or bill for it without your say-so. You scale the container, not the seat count.

How much can an agency charge clients for managed EspoCRM?

Most agencies price a managed EspoCRM line at €40–80 per month per client. The wholesale cost is €9 per instance, so the margin is €31–71 per client. You're charging for the configuration, the ongoing changes, and one point of contact. The €9 server cost is an input, not the product.

Is EspoCRM cheaper than Salesforce, HubSpot, or Zoho for a small client?

For a five-person team, yes. Salesforce Pro Suite runs $500 a month at that size. HubSpot Sales Hub Professional is $500 plus a one-time $1,500 onboarding fee. Even Zoho, the cheapest mainstream option, costs more than a flat managed EspoCRM line covering every user.

Why use managed hosting instead of running EspoCRM on my own server?

EspoCRM is free, but running it isn't. A server, updates, security patches, backups, and uptime monitoring are ongoing work. One outage on a server you run hits every client at once. Managed hosting turns that into a flat €9 per instance, so you sell setup and support.

How do I move a client's existing data into EspoCRM?

EspoCRM imports contacts, accounts, and deals from CSV files. A client moving off a spreadsheet or another CRM brings their full history along. The work is cleaning duplicates and mapping fields to the new pipeline. That clean import is often the moment a client commits to the switch.

What can I customize in EspoCRM without writing code?

A lot, all from the admin panel. You add custom fields, entities, and relationships, and rename any label in the interface. You build pipelines, set up workflow automation, and create role-based dashboards. The configuration that fits a client's exact sales process is the agency's real product.

Can EspoCRM be tailored to a specific industry?

Yes. Fields, entities, and labels in EspoCRM are all configurable. That lets you shape it for real estate, recruiting, legal, or any niche your clients serve. Build one industry template, replicate it across similar clients, and tune each one from that base.

Does EspoCRM have an API and integrations?

Yes. EspoCRM ships with a REST API, so it connects to other tools a client already uses. It supports inbound and outbound email, calendar sync, and webhook-style triggers through its workflow tools. For anything custom, a developer can build against the API.

Can EspoCRM handle email marketing, or do I need another tool?

EspoCRM handles one-to-one email well — sending from records, using templates, and automating follow-ups. For campaigns, drip sequences, and lead scoring, pair it with managed Mautic. The CRM holds the contacts and deals; Mautic runs the nurture. Each is a separate €9 managed instance.

Does EspoCRM support multiple languages and currencies?

Yes. EspoCRM ships in dozens of languages, and each user picks their own from their profile. It also handles multiple currencies, which matters for clients selling across borders. You set the defaults during configuration, and individual users adjust from there.

Can clients use EspoCRM on their phones?

Yes. The EspoCRM interface works in a mobile browser, and mobile apps cover day-to-day use. Clients can view records, log activity, and check the pipeline away from their desk. They sign in with the same account and see the same data as on desktop.

Can I fully white-label EspoCRM so clients never see the EspoCRM name?

Mostly. From the admin panel you set the logo, application name, color theme, and login background. The product looks like the client's own CRM at the surfaces they use daily. Some deeper references to the underlying software remain, so it isn't a total rebrand.

Who owns the client's data, and what happens if I stop reselling?

The client's data is theirs. EspoCRM stores everything in a standard database, and records and attachments export at any time. If you stop reselling, the data hands over cleanly to the client or another provider. There's no proprietary format locking it in.

How secure is each client's instance?

Each client runs in its own isolated container with its own networking. One client's instance can't reach another's data, and connections use HTTPS. Every instance is backed up and patched on its own. Isolation means a problem on one instance stays on that instance.

Are backups included for each client instance?

Yes. Every managed instance is backed up automatically, so a client's CRM data stays protected. If data is lost or corrupted, it restores from backup. You don't run backup scripts or manage storage — that's part of the managed service.

What to do this week

Pick one client to pilot, ideally a retained client who already pays for a per-seat CRM and feels the cost. The goal this week is a single working instance and one honest conversation about price, not a full product launch. One client is enough to test the whole model end to end.

Deploy one managed EspoCRM instance and configure a standard setup: a clean pipeline, the fields that client needs, and their contacts imported. Price it as a productized service — setup plus a monthly managed fee — not as hosting with a markup. Run it for a month, gather the client's feedback, and use that first build as the template for the next.

The model is sound in shape: recurring revenue, low churn on a working CRM, and a cost that holds flat as the client grows. The first client is the experiment. The tenth is a line of business.

See the partner program