Buy, Build, or Configure CRM: Which Path to Choose

This article isn’t about which CRM is “the best.” It’s about how not to lose a year and a six-figure budget on a path you don’t actually need. We’ll break down three scenarios: buying a ready-made vertical CRM, building one from scratch, or configuring a horizontal platform to fit your business. For each — real numbers, common mistakes, and signals that show which route is yours.

The material is built on dozens of CRM implementation projects in Ukrainian and international companies — from online education and e-commerce to B2B consulting and manufacturing.

When a leader asks “which CRM should we pick?” they think they’re asking about software. In reality, they’re deciding how their sales team will operate for the next 5–7 years.

The platform sets the discipline. Discipline drives conversion. Conversion drives revenue. If you start with a system that your sales team sabotages by the third month, no amount of training will fix it. That’s why getting it wrong here costs heavily — not in money, but in lost revenue and time.

You have three options:
1. Buy a vertical CRM — software tailored to one industry: car dealerships, clinics, real estate agencies, logistics, fitness clubs. Industry-specific processes and terms are already built in.
2. Build a CRM from scratch — assemble a development team or hire a contractor and write a system around your own processes. Total control and total responsibility.
3. Configure a horizontal CRM — take a universal platform (Pipedrive, Kommo, HubSpot, Salesforce, Zoho) and adapt its pipelines, fields, automations, and integrations to your business.

The difference between these paths isn’t 20% — it’s 5–10x in budget and six to twelve months in launch timeline. Each one saves a business in one situation and buries the project in another.

Here’s a side-by-side comparison:

Now let’s break down each path.

The problem. A leader sees an ad for “CRM for medical centers” or “CRM for real estate agencies” and thinks: “great, this is built for us, everything’s ready.” They buy it, roll it out — and four months later discover that the system can’t calculate partner commissions, doesn’t play well with local telephony, and won’t export data in the format their accounting needs.

The cause. Vertical CRMs shine where industry processes are standardized. If 95% of barbershops handle bookings the same way, an industry-specific product will serve them perfectly. But the moment your business model deviates from the typical one — hybrid B2B + B2C, non-standard lead sources, complex pricing logic, multi-brand structure — those industry templates start getting in the way. What seemed like a plus yesterday (“everything’s already built for us”) becomes a cage tomorrow (“we can’t change anything”).

The second cause is market size. Vertical CRMs have a narrow customer base, which means smaller development budgets compared to horizontal leaders. The interface often lags 5–7 years behind, the mobile app is weak, and the API is limited. When you need to connect a new communication channel or an unusual messenger, you’ll wait for the vendor to add support — or you’ll wait forever.

The third issue is lock-in. Migrating away from a niche CRM is hard. Data structures are non-standard, export modules are poor, and there are almost no integrators familiar with the system. Three years in, you’ll find yourself dependent on a single vendor, and any price hike on their side becomes your problem.

The solution. A vertical CRM makes sense only when three conditions are met simultaneously:

1. Your industry is genuinely specific — medicine, law, logistics, finance, construction — and regulated such that general-purpose software can’t cover the requirements (medical records, licensing registries, industry-specific reporting).
2. You’re willing to work within the limits set by the vendor: adapt your processes to the product, not the other way around.
3. There’s an established leader in your niche with clear case studies, reviews, and a developed partner ecosystem.

If even one of these doesn’t hold, look toward a horizontal platform.

From our practice: over the last three years, out of every project where the client initially wanted a vertical CRM, we kept it in only a handful of cases — a clinic and a logistics company. Everyone else, after a process audit, chose a horizontal platform with configuration.

After a detailed review, the “industry specifics” turned out to be 2–3 custom fields and one integration, not the entire operating structure.

The problem. “We’ll build our own — it’ll be cheaper in the long run, and we’ll get exactly what we want.” We hear this from IT company owners and entrepreneurs who already have developers on their team. Eight months later, the MVP isn’t launched, the team is burned out, investors are asking uncomfortable questions, and the sales team is still living in Google Sheets for the third year running.

The cause. A custom CRM is not a three-month project. It’s the operating system of your company that you’ll be supporting forever. Let’s honestly count what’s behind “let’s just build it ourselves”:

• The team. Minimum viable composition: product manager, designer, 2–3 developers (front, back), QA engineer, DevOps. That’s $15–25k per month in salaries on most European markets, more in North America.
• Time to the first useful version. 6–12 months. Throughout all of it, you’re not running sales through your CRM — you’re “about to start.”
• Backlog. When the product launches, you’ll have a list of 200+ improvements your sales team will request immediately. Each one is hours of development and testing.
• Technical debt. Within 2–3 years, parts of the code become legacy. Refactoring is a separate budget that nobody plans for.
• Key developer turnover. When the engineer who wrote the core of the system leaves, the next person spends months getting up to speed. Every rotation does the same.
• Security and reliability. Backups, monitoring, attack protection, fault tolerance, GDPR compliance — all on you.
• Integration updates. APIs for Telegram, Instagram, telephony, and email change regularly. Every change is work for your team.

In horizontal CRMs, all of this is already included in the license price. A vendor like Pipedrive or HubSpot has hundreds of engineers. Your team will have 3–5, and they’ll never catch up with the vendor’s pace.

The solution. Building a CRM from scratch is rarely justified. In our experience, it’s less than 1% of inquiries. Specifically: when a company has a product based on proprietary data or algorithms that can’t be replicated in a standard CRM.

For example:

• a marketplace with complex multi-sided economics and proprietary matching logic;
• a fintech service with regulatory requirements that no off-the-shelf solution covers;
• a product company where the CRM itself is part of the core product, not a supporting system.

In every other case, custom development is buying an expensive illusion of control — control over things that can be configured in a week on a ready-made platform.

The advice we give IT team owners: if your developers are sitting idle, put them on integrations and automations around an existing CRM. You’ll see business results in a month, not “the release at the end of the year.”

The problem. Many people think that “configuring a ready-made CRM” means registering, adding users, and getting to work. It doesn’t work that way. A CRM without designed pipelines, fields, access rights, and automations is just a pretty notebook — one your sales team stops opening within a month.

The cause. Between “we bought a license” and “our sales team runs on the CRM like clockwork” lies 80–150 hours of work on system architecture. This scope is rarely understood at the start — which is why so many DIY implementations fail.

What a proper configuration includes:

• mapping and formalizing sales department processes (often the first time they’ve been written down at all);
• designing pipelines — usually 3–7 in parallel: new clients, repeat sales, reactivation, partner channel, tenders, upsells;
• setting up required fields and validations so a manager can’t move a deal forward without proper qualification;
• automations: stage transitions, task creation, notifications, reminders, deadlines;
• integrations with telephony (RingCentral, Aircall, Twilio), messengers, your website, ad platforms, accounting, warehouse management;
• reports and role-based dashboards — for the manager, sales lead, and owner;
• importing historical data and cleaning duplicates;
• training the team and reinforcing discipline through clear regulations.

That scope of work closes in 4–8 weeks — versus 6–18 months for a from-scratch build.

The solution. A horizontal CRM is a construction set in which 80% of what you need is already there. The remaining 20% comes through configuration, widgets, and integrations. The platforms we use most often:

Pipedrive — for classic B2B sales with deals, long cycles, and a transparent pipeline. Great for agencies, IT companies, wholesalers, project-based businesses, and B2B services. Strengths: visual pipeline, flexible reporting, well-designed access controls.

Kommo CRM — when your main lead channels are messengers (Instagram, WhatsApp, Telegram, Viber). Ideal for online schools, info-products, local services, and small B2C. Strengths: built-in messenger integrations and chat center.

For e-commerce and retail, we also work with platforms that connect directly to marketplaces, fulfillment, shipping, receipts, and fiscalization. The choice depends on your region — what matters is that the CRM speaks to your local commerce stack out of the box.

Each of these CRMs covers 80% of the workload from day one. The rest is our job: configuring it for the specific business.

What’s important: configuration is not development. We don’t write code. We configure fields, pipelines, permissions, automations, and dashboards, and we connect integrations through ready-made modules or via services like Albato, Make, Zapier, and n8n. The result is fast, affordable, and maintainable.

A side benefit — horizontal platforms keep evolving. Every quarter, they ship new features that would otherwise need to be commissioned separately in a custom CRM. When Pipedrive added an AI assistant for deals in 2023, our clients got it for free.

Before committing to any CRM, answer seven questions honestly. This isn’t a theoretical quiz — it’s the map we use during client consultations.

Up to 7 — go with a horizontal CRM. More than 15 and radically different (marketplace + services + wholesale + franchise simultaneously) — consider a hybrid: a horizontal CRM plus a few custom modules.

If the business is “lead → request → negotiation → contract → payment → delivery,” a horizontal platform covers everything. If you run complex matching, exchange logic, in-deal auctions, or dynamic pricing per transaction — you need a custom layer on top.

Up to 5,000 active cards — any horizontal CRM handles it fine. Above 50,000+ — performance becomes a question, and you should look at enterprise platforms or build a custom data layer.

Under $20k — definitely a horizontal CRM configuration. $20–80k — configuration plus complex integrations, possibly some custom modules. $80k+ with a five-year horizon — a hybrid with custom modules becomes worth considering.

Up to 50 — any horizontal platform works. 50–300 — pick platforms with robust role management and analytics (Pipedrive Advanced/Professional, HubSpot Enterprise, Salesforce). 300+ — you need a dedicated CRM architect and usually a hybrid with custom modules.

If yes — a horizontal CRM speeds you up dramatically. If no — be ready to pay for development. Honestly, “the way we’ve always worked” is usually a set of old mistakes nobody wants to revisit. A CRM rollout is the best time to revisit them.

If you don’t have someone internally who understands the CRM and you’re commissioning custom development — the system will be a nightmare within a year. A horizontal platform with a contractor on retainer is more stable and cheaper to maintain.

After these seven questions, nine out of ten clients know exactly what they need. Most often, the answer is configuring a horizontal CRM with a 3–5 year growth horizon in mind.

To keep the checklist out of theory, here are three real situations from our practice — and the logic of choice in each.

The client came in saying, “We need our own CRM because Pipedrive can’t calculate ROMI for each deal.” The audit showed: in Pipedrive, this is handled with one custom field and an integration with ad platforms via Albato.
Implementation timeline — 5 weeks. Cost — around $4,000, including a year of licenses. If they’d gone the development route, it would have been 8 months and $80k+. They chose configuration.

Six months later, conversion from lead to deal went from 11% to 18% thanks to nurturing automations and mandatory qualification fields.

Here, a horizontal CRM didn’t fit. Reasons: integration with a medical information system through a specific protocol, regulatory requirements for storing patient records, scheduling logic tied to doctors and rooms. They chose a vertical CRM built for medical centers.

Implementation took 4 months. Custom development wasn’t even on the table — for a single clinic network, it’s economically irrational.

Here we actually advised against a horizontal CRM. The business model is built on a proprietary matching algorithm between providers and customers, with specific commission and settlement logic. The solution — custom development for the core product plus Pipedrive for the supplier-management team.

A hybrid architecture. A year in, the core product runs on the proprietary platform, while the supplier-side sales pipeline lives in the ready-made CRM. Splitting the functions saved roughly $200k on development by avoiding a complete from-scratch build.

The general rule we draw from dozens of projects like these: the type of business matters more than its size. A small marketplace startup needs a custom layer. A large agency with a hundred sales managers does perfectly well on Pipedrive with configuration.

Over the years, we’ve catalogued the same mistakes repeatedly. Each costs companies 2 to 12 months and tens of thousands of dollars. If you recognize yourself in any of them, it’s a signal to stop and reconsider.

In 95% of cases, this is an illusion. A business’s uniqueness lives in the team, product, and marketing. The sales process in B2B consulting looks the same in Kyiv as it does in Berlin: qualification → demo → proposal → negotiation → contract. Before commissioning development, audit your processes and map them against 2–3 horizontal CRMs. Nine times out of ten, the custom-build idea drops off on its own.

A cheap CRM that lacks the integrations or flexibility you need will turn into a migration project within 6–8 months. Migrating a CRM means a month of work, a risk of data loss, and serious team demotivation. Sales managers lose faith in the very idea of CRM. It’s better to pick a platform once with a 3–5 year horizon in mind.

Launching a CRM without documented business processes is the number-one reason rollouts fail. Before you buy a license, you need a process map of the sales department, defined pipelines, fields, qualification rules, and clear communication-channel quality standards. Otherwise, you’re paying for software your team won’t log into.

Trying to stuff 100% of the wishlist into the first release guarantees a six-month rollout. The right approach is implementation in 2–3 stages. Stage one: the basic sales process, conversion tracking, basic reports. Stage two: automations, complex pipelines, marketing integrations. Stage three: deep analytics, end-to-end sales analytics, customer segmentation.

They won’t. Or rather, they’ll figure it out their own way: within a month, deals will be tracked in three places simultaneously — the CRM, Excel, and people’s heads. A rollout isn’t just configuring the system. It includes sales department quality control, discipline, regular pipeline reviews, clear regulations, and consequences for ignoring them. Without that, the CRM turns into an expensive address book — and you end up dealing with the classic reasons CRM gets sabotaged.

If you’re rolling out a CRM to lock in your current chaos, you’re not buying a CRM — you’re building a monument to that chaos. Use the implementation moment to revisit your processes. That often delivers more impact than the CRM itself. On one of our B2B-services projects, reworking the lead qualification process lifted conversion from inquiry to deal from 8% to 17% — without replacing the CRM, just by reshaping the pipeline and required fields.

A CRM is a living system. Three to six months after launch, you need a review: which fields managers actually fill out, which they ignore, where automations get in the way, and where they save hours. Without regular tuning, even a flawlessly launched CRM degrades within a year.

Suppose you’ve read this article and realized you took the wrong turn: bought a too-narrow vertical CRM, commissioned development that won’t move, or you’re working in a horizontal platform without any configuration. What now?

“The vertical CRM doesn’t fit” scenario. If the system has been in use under a year and contains fewer than 5,000–6,000 cards, migrating to a horizontal platform is cheaper. Migration takes 2–6 weeks. If you have more data or the system has been in place for 2+ years, it’s usually cheaper to keep configuring with workarounds and integrations than to migrate everything.

“Custom development is stuck” scenario. Stop the project and run an honest audit. If you have no working version after 12 months, another “three months” won’t fix it. Freeze development, switch to a horizontal CRM with 6–8 weeks of configuration, and keep selling.

“We bought a CRM and it’s empty” scenario. This is the most common case. Audit processes and redesign the system architecture from scratch. Sales managers don’t sabotage a CRM out of spite — they don’t use it because it doesn’t make sense for their work. Make the CRM save them time instead of taking it.

If the decision is made — configure a horizontal CRM — gather these materials before signing a contract with a contractor.

It cuts project time by 30–40% and removes most of the back-and-forth.

1. Description of your current sales pipelines: lead channels, stages, who’s responsible at each stage.
2. List of roles in the sales department and their permissions: what the manager sees, what the team lead sees, what the owner sees.
3. List of systems the CRM must integrate with: telephony, messengers, website, ad platforms, accounting, warehouse, ERP.
4. Metrics you want to track: stage-by-stage conversion, average deal size, sales cycle length, loss reasons, channel efficiency.
5. Lead qualification rules and reasons for stage transitions.
6. List of tasks that currently eat time but can be automated: outreach, reminders, task assignments, reports.

These six points cover 80% of the questions a contractor will ask at the first meeting. The more detailed your answers, the faster and more accurate the configuration — and the higher the chance the rollout delivers results rather than turning into a six-month chat thread. For a deeper look at what each phase involves, see our breakdown of the stages of CRM system implementation.

After launch, the next phase is working with the database and customer retention. If you want to extract maximum value from accumulated data, plan ahead for segmentation, lifecycle marketing, and reactivation campaigns. A well-configured CRM makes these tasks dramatically easier because the data is already structured and segmented automatically. Many of our clients pair CRM rollout with strategies for increasing customer loyalty from day one.

One more important point: agree with your contractor on two consecutive support phases. The first is the first 30 days after launch, when small things get fixed and feedback is gathered from the team. The second is monthly support for 3–6 months, when the system gets tuned to actual deal flow. Companies that include this phase from the start hold CRM data quality at 85–90% card completeness on average. Without ongoing support, that number drops to 40–50% within six months — and at that point, no analytics work.

In 60 minutes, we’ll review your current sales processes, show where a CRM can lift conversion by 20–40%, and recommend whether you should configure a ready platform, migrate, or start with process consulting. No generic advice — only what fits your business.

Book a CRM implementation consultation → at form below.