Dynamics 365 vs Zoho One for 50 Users: A 3-Year Cost Model and the Monthly Billing Catches

What belongs in a 3-year CRM cost model for 50 users?

Licences are the line everybody compares and rarely the line that decides the outcome. Over three years the implementation, the changes you will want after go live and the time your own people spend administering the system often matter as much, and the exit cost is the line nobody writes down until they need it. Use the same categories for both suites so the comparison is like for like. We do not quote prices from Microsoft, Zoho or Solzet here: list prices change, discounts depend on your agreement, and a model built on someone else's numbers will not survive your finance review.

How do you fill in the 3-year worksheet from public list prices?

Copy the table into a spreadsheet, one column per suite and one per year, and fill each line from a named source. For licences, take each vendor's current public list price for the editions you would actually buy, multiply by the number of people in each role and by twelve months, and record the date you read the price. Replace list prices with quoted prices only when you have a written quote. For implementation, use proposals scoped to the same requirements for both suites, not a vendor's average.

Keep three rules. Every line has a source and a date. Year two and year three include headcount growth and the change budget, not just year one repeated. And the totals are shown both as a three-year sum and as cash per quarter, because the second is what decides whether the plan is affordable.

How does licensing by role change the Dynamics 365 number?

Dynamics 365 is priced per person according to what that person does, so the 50-user figure is really a role count. Sellers and service agents who work in the system all day need a full licence for their app. Someone who uses two Dynamics 365 apps may need a base licence and an attach licence rather than two full ones. People who mostly read records, approve or update a few tables may qualify for a lighter licence type, but only within the use rights Microsoft publishes, and relabelling full users as light users is a compliance risk that surfaces at true-up.

We do not restate the licence types or how to sort people into them: our Dynamics 365 licensing cost and renewal guide covers Per App and Per User licensing, attach licences, Team Members and rightsizing. For the 3-year model, list your 50 people by role, assign each the licence type you believe they need, and have the assumption confirmed in writing by Microsoft or your Cloud Solution Provider before the number goes into a budget.

How does Zoho One licensing work for a company with 50 CRM users?

Zoho One is a bundle of Zoho applications sold per employee. In its standard model Zoho has asked customers to license every employee in the organisation rather than only the people who will use the apps, and it has also offered a flexible-user model that licenses only named users at a different per-user rate. That makes the headcount you license, not the CRM user count, the main driver. A company with 50 CRM users and a much larger total workforce can find the all-employee model costs more than expected; a company where nearly everyone uses the CRM may find it compares well.

Check Zoho's current terms before you model it: which pricing models are offered, whether contractors and part-time staff count as employees, whether billing is monthly or annual and how that changes the rate, what happens when headcount rises or falls during a term, and what each bundled app includes at your edition. Zoho changes its packaging like every SaaS vendor, so take the answer from Zoho or its published terms, dated, rather than from a comparison article. Solzet does not implement or resell Zoho, so we describe the model only to help you put the right number in the worksheet.

What are the catches with monthly billing under Microsoft NCE?

Under Microsoft's New Commerce Experience the term and the billing frequency are two different choices, and confusing them is the most common monthly-billing mistake. The term is how long you commit: monthly, annual, and for some products longer. The billing frequency is how often you pay: an annual term can usually be paid monthly. Paying monthly on an annual term does not give you the right to reduce seats monthly.

• Monthly term: a higher price per seat than the equivalent annual term, in exchange for the ability to reduce seats at each monthly renewal. It suits seasonal or uncertain headcount, not the stable core.
• Annual term: the lower rate is fixed for the term, but seats can generally be added and not removed until the renewal date. Over-buying in month one is paid for over the whole year.
• Cancellation window: cancelling or reducing a new or renewed subscription is allowed only within a short period after the term starts, after which the commitment stands. Confirm the current window with Microsoft or your CSP; our renewal guide covers how to work within it.
• Automatic renewal: subscriptions renew at the quantity you hold unless you change them before the term ends, so a forgotten date renews every seat that drifted in.
• Price changes: an annual term protects the rate during the term; a monthly term can move with Microsoft price changes at each renewal. Model year two and three on that basis.
• Buying channel: whether you buy direct or through a partner affects invoicing, payment terms and who manages renewals, which our licensing procurement guide explains, including what a partner earns.

What lock-in and exit costs should the third year include?

Lock-in is not only contractual. Both suites hold your data in their own schema, both encourage you to build workflows, scripts and integrations on their platform, and every one of those has to be rebuilt if you leave. Put an exit reserve in the model even if you never intend to use it, because it changes which option is genuinely cheaper and it is the number your board will ask about if the vendor raises prices at renewal.

• Contract lock-in: annual or longer commitments, renewal dates and notice periods. Align end dates so you have one decision point rather than several.
• Data lock-in: can you export every table, attachment and audit history in a usable format, and how long does a full export take at your volume?
• Build lock-in: Dynamics 365 plugins, Power Automate flows and model-driven apps, or Zoho custom functions and cross-app workflows. Count them, because each is a rebuild item.
• Skills lock-in: the people who know how your system is configured, and whether that knowledge is written down.
• Bundle lock-in: if several departments come to depend on bundled apps, leaving the CRM means replacing all of them at once.

When does a custom CRM avoid per-user cost altogether?

A custom CRM has no per-user licence: you pay for the build, hosting and support, and adding the fifty-first or the five-hundredth user does not change the bill. That matters when many people need light access, when headcount is growing fast, or when an all-employee bundle would charge for staff who never open the CRM. It does not make a custom CRM automatically cheaper. It replaces subscription cost with build cost and with the obligation to own, host and maintain the system for its whole life.

We do not repeat the build-versus-license decision here. Our custom CRM versus licensed CRM decision guide sets out when building beats licensing and when it does not, and the custom CRM development page compares the cost factors over time. In the worksheet, add a third column for a custom build: build cost in year one, hosting and support in every year, a change budget, and zero licences.

What is a cash-flow-safe way to pilot before committing for three years?

The safest path spends the least committed money before the model has been tested against reality. A pilot that proves adoption and data quality for one team is worth more than a discount on a commitment for everyone.

• Pilot one team and one process, for example a single sales team on lead to opportunity, with real data and a fixed end date.
• On Dynamics 365, use a Microsoft trial for evaluation, then license the pilot users on a monthly term so you can reduce them if the pilot stops. Move the stable core to an annual term only after the pilot proves the role mix.
• On Zoho One, check whether a trial or the flexible-user model is available for a pilot group before you commit the whole workforce, and confirm how a later switch between models works.
• For a custom CRM, scope a first release around the single process that matters most, so the build is phased and each release is paid for as it is delivered.
• Measure the same things in any pilot: daily active users, records created, data quality issues found and support requests raised. Feed the measured numbers back into the worksheet.
• Make the go or no-go decision before any cancellation window or annual renewal date, not after it.

How does Solzet help, and what do we not do?

We recommend the right solution - whether that's Microsoft Dynamics 365, Power Platform, or a custom-built CRM. Some businesses need the Microsoft ecosystem. Others need full control without licensing. We deliver both.

In practice that means we implement Dynamics 365 Customer Engagement (Sales, Customer Service, Field Service and Customer Insights) and the Power Platform around it, and we build custom CRM systems on React, Node.js, PostgreSQL and .NET when Microsoft licensing does not fit. We do not implement or resell Zoho, and we do not resell Microsoft licences, so we have no margin in either suite’s seats. Our senior consultants and full-stack developers, with 8+ years of CRM delivery and working remotely from Yerevan, Armenia, can review your worksheet, scope the Dynamics 365 or custom CRM implementation lines, migrate data from Zoho if you leave it, and tell you plainly when Zoho One looks like the better fit for your shape of business.