A CRM You Own Outright: When Building Beats Licensing, and When It Does Not

What is the decision rule between a licensed CRM and a CRM you own?

Start from the signals, not the products. Most buyers can place themselves in one column within a few minutes, and the ones who cannot usually have one unresolved question, such as a hosting rule or a group of light users, that decides it. If you land in the left column, the remaining question is which licensed platform, and the rest of this page covers that too.

How do Dynamics 365 Sales, Salesforce, HubSpot and a custom-built CRM compare?

The table compares the four options on the factors that decide the choice rather than on feature lists, which change every release. Feature sets, editions and prices move constantly on all three licensed products, so check the vendor pages for current detail. Solzet implements Dynamics 365 and builds custom CRM; we do not implement or resell Salesforce or HubSpot, and we say so because it colours any comparison we write.

What does owning a CRM outright actually mean?

With any licensed CRM you own your data and can export it, but you rent the software: the vendor sets the price at renewal, decides which features exist, retires the ones it no longer wants to support and runs the platform in its own cloud. For most organizations that is a fair trade, because the vendor also carries the security patching, the uptime and the roadmap.

Owning a CRM outright means the source code, the database, the documentation and the deployment configuration are yours by contract, and the system runs in your cloud account or on your own servers. Nobody can change what it costs to keep using it or switch off a feature you rely on. That matters most to organizations with hosting or data sovereignty rules, which is why it comes up so often in public sector work and in markets such as Armenia. How Solzet contracts ownership and which stack we build on is set out on the custom CRM development page.

What are the trade-offs of a custom CRM that nobody states?

A custom CRM is not a cheaper Dynamics 365. It swaps one set of obligations, licences and a vendor roadmap, for another. Before choosing it, be sure you are willing to carry these.

• No marketplace. On a licensed platform a missing capability is often an app you install. On a custom CRM it is a feature you specify, build, test and maintain.
• No out-of-the-box reporting. Every dashboard, report and export is designed and built. Plan reporting into the first release, or leadership will be back in spreadsheets.
• An owner for its whole life. Someone must be accountable for security updates, dependency upgrades, backups, monitoring and new requirements, every year the system runs.
• Documentation is not optional. A system only one developer understands is a liability. The data model, the API and the deployment need to be written down so any competent team could take over.
• Integrations are yours too. When an email, telephony or accounting system changes its API, your integration has to change with it.
• Time to value is longer for standard needs. If a platform already does what you need, configuring it is faster than building it.

When does per-user licensing scale badly against headcount?

Per-user pricing is fair when a modest number of people live in the CRM all day. It scales badly in a specific shape of organization: many people who each touch the system for one step, such as field staff logging a visit, branch employees raising a request, seasonal teams, or partners and suppliers who need a portal. Every one of them is a seat, or a lighter licence type with restrictions on what they may do, and the total grows with the business rather than with the value each user gets.

The honest comparison is total cost over several years, not the first invoice. We do not reproduce it here: the factor-by-factor table on the custom CRM development page, under "Custom CRM or Dynamics 365: which costs less over time?", is the one to use. For the licensing side, our Dynamics 365 licensing and procurement guide explains how licences are bought and sized.

Does an existing Microsoft 365 tenant change the answer?

Usually, yes, and in favour of Dynamics 365. Microsoft 365 does not include Dynamics 365 Sales licences, so it is not free, but it changes what you get for the licence: sellers track email and meetings from Outlook, work records inside Teams, analyse in Excel and Power BI, sign in with the accounts they already have, and use Copilot against the same data. HubSpot and Salesforce both integrate with Outlook and Teams, but the integration is a connection between two platforms rather than one platform.

Microsoft 365 also brings the Power Platform into view. Some requirements that look like a CRM are really one structured application, and depending on your plan and whether you need premium connectors or Dataverse, a Power Apps build may cover them without a full CRM. A Microsoft 365 tenant does not force the answer, though: a custom CRM can use Microsoft Entra ID for single sign-on and integrate with Outlook and Teams, it simply does not get that integration for free.

What can you do when the CRM budget is frozen?

A frozen budget rules out new licences, but it usually rules out a custom build too, because a build is a project with its own cost. Treat the freeze as time to make the eventual decision cheaper and safer rather than as a reason to switch.

• Fix what you already have. Many CRM complaints are data quality, process or adoption problems that travel with you to any new platform. Cleaning duplicates, agreeing pipeline stages and retiring unused fields costs time, not licences.
• Use what Microsoft 365 already includes, within its limits. Shared mailboxes, Teams channels, Lists and Excel can hold a disciplined pipeline for a while. Check what your specific plan includes before building anything on it.
• Know what a free or entry tier really covers. HubSpot offers free CRM tools, and they can carry a simple pipeline, but the capabilities that usually justified the project tend to sit in paid tiers.
• Write the requirements and the decision now. Map the process, the users by how much access they need, the integrations and any hosting rules. That document is what makes the next budget request specific and defensible.
• Plan a phased start for the next cycle. A licensed pilot for one team, or a first custom release scoped to the single process that matters most, spreads the cost and proves the value before the full commitment.
• Check whether the freeze is on operating or capital spend. Subscriptions and a build are often funded differently, which can change which option is fundable at all. Your finance team decides this, not the CRM vendor.

Which option fits a 45 person team?

Headcount alone does not decide it; what those 45 people do in the system does. Our comparison of Dynamics 365 with Pipedrive and HubSpot for small teams covers the lighter end honestly, including when a light CRM is the right buy. At 45 people the patterns we see are these.

• HubSpot fits when the work is mainly marketing and a straightforward sales pipeline, the team wants to be productive quickly, and nobody needs deep changes to the data model.
• Dynamics 365 Sales fits when the company already runs on Microsoft 365, sales has to share a customer record with service or field operations, or the process needs enforced rules, integrations and reporting across systems. See Dynamics 365 Sales implementation for what that involves.
• Salesforce fits when the organization already has Salesforce skills or ecosystem investments, or a specific AppExchange product is central to how it sells. We do not implement Salesforce, so take that line as a description, not a recommendation.
• A custom CRM fits when only part of the 45 are sellers and the rest need light access, when the core process is unusual, or when ownership and hosting are requirements rather than preferences.

Does a 45 person team need consultants at all?

Not always, and it depends more on the platform and the scope than on the size of the team. The line is the same one our guide to hiring a Dynamics 365 consultant or doing it yourself draws in detail: configuration a capable administrator can own, against data model design, migration, security and integration work that goes wrong quietly.

What does Solzet deliver, and what does it not?

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 our senior consultants and full-stack developers implement Dynamics 365 Customer Engagement, meaning Sales, Customer Service, Field Service and Customer Insights, build on the Power Platform, and build custom CRM systems on React, Node.js, PostgreSQL and .NET for organizations that need CRM without Microsoft licensing. We migrate data from HubSpot, Salesforce and spreadsheets into either. We do not implement or resell Salesforce or HubSpot, and we do not deliver Dynamics 365 Finance, Business Central or other ERP implementations. With 8+ years of CRM delivery from Yerevan, Armenia, a short discovery is usually enough to tell you which column you are in.