Custom CRM vs HubSpot or Pipedrive: when to build your own, and why to configure first

Custom CRM vs HubSpot in one answer

Custom CRM vs HubSpot or Pipedrive usually comes down to one question: is the record your business runs on a sales deal? If it is, configure HubSpot or Pipedrive properly and don't build. If your work runs on something else, such as a job, a site, a case or a placement, build that part and keep the product for sales.

A CRM (customer relationship management system) is where a company keeps its contacts and the deals it is working on. This guide is for owners and operations leads at UK and EU firms of 10 to 200 people. You may be paying for HubSpot or Pipedrive and working around it every day. Or a developer has told you that a CRM of your own is quick to build now.

We build custom internal software for a living, and for a sales pipeline we'd still tell most firms to keep the product. This guide covers what to configure first, when building pays off, and what you take on when you build.

Comparing HubSpot and Pipedrive with a custom CRM

The options differ less in features than in who does the work: the vendor, your team, or a developer you hire.

The second row matters most. HubSpot lets you add record types of your own, which it calls custom objects, but only on Enterprise subscriptions. Pipedrive's help pages describe custom fields on its own record types: leads, deals, people, organisations, activities, products and projects. If your business runs on a record that isn't on that list, keep reading.

Configure first: what to try before you build

Many complaints about a CRM turn out to be setup problems. Nobody agreed what the fields mean. One pipeline does three jobs. Everyone can edit everything, and nobody decided who logs what.

Both products let you change a lot without writing code:

• Add your own fields, such as a contract end date, a site count or where the lead came from.
• Run a separate pipeline for each kind of sale, each with its own stages.
• Automate follow-ups and hand-offs with the rules your plan includes.
• Decide who sees what and who changes what. HubSpot sets view and edit rights separately for each record type. Pipedrive separates visibility groups, which control what people see, from permission sets, which control what they do.
• Connect your other tools through the HubSpot App Marketplace or the Pipedrive Marketplace before you pay for a custom connection.

Then run a two-week test:

1. Write down the records your business runs on, and the stages each one goes through.
2. Set them up in a trial with real records, not sample data.
3. Ask the people who will use it every day to run a week of real work in it.
4. List every workaround: each time someone reached for a spreadsheet, an email thread or a sticky note.
5. Sort the list into three piles: fixed by configuration, fixed by a marketplace connector, fixed only by building.

That's the order we work in: configure, then connect, then build. The third pile is usually short. If it's empty, you have your answer, and no developer was needed to get it.

Configure the product; don't bend it

The expensive mistake sits between the two paths: buying a product, then paying to rebuild your old system inside it.

The clearest public example in the UK is Birmingham City Council's finance and HR system. It's an ERP (enterprise resource planning system) rather than a CRM, but the mistake carries over. The council replaced its old SAP system with Oracle Cloud and went live in April 2022. Its own principle was to adopt Oracle's standard processes and change the council's processes to fit.

The council's auditor, Grant Thornton, published a public interest report in February 2025. It found that the programme did the opposite, adapting Oracle to the council's existing processes. Council staff wanted to replicate SAP inside Oracle, and the design board meant to stop that couldn't say no.

One result was an access-control model built entirely custom to copy the old SAP system. The auditor found flaws in it that let staff reach, and potentially change, data outside their areas of responsibility. The council's data protection officer had reported no breach of that kind. After go-live, the report says, end users were "unprepared and unequipped to use the system".

A small firm's CRM goes wrong the same way, on a smaller scale. It starts with custom fields that copy the columns of an old spreadsheet, then automations only one person understands. If your configuration list starts to read like a rebuild, stop. That's the sign the product doesn't fit this part of your work.

When a custom CRM pays off

Building pays off when the record at the centre of your work isn't a sale. HubSpot and Pipedrive are built around the sale: who you sell to, and the deal in progress. When your day runs on jobs, sites, cases or placements, those records get squeezed into deals and activities, and the workarounds start.

You're probably in that position if:

• Most of the work happens after the deal is won, and the CRM only sees the part before.
• The thing you schedule and report on is neither a person nor a company.
• Most of your users need one small screen, such as engineers logging a visit, rather than a sales tool.
• Other systems, such as invoicing, need to read from the same record.

Say you run a 40-person company that services commercial kitchens. Your records are sites, equipment, service contracts, visits and engineers. Selling is a small part of the work: new contracts and renewals.

In Pipedrive, every visit becomes an activity on a deal that closed two years ago. In HubSpot you could model sites and visits as custom objects, but only on Enterprise. Either way, your engineers still need a phone screen built for logging a visit on site.

That firm has three options:

1. Check whether its industry has its own software. Estate agents, recruiters, law firms and field service companies all have products built for how they work.
2. Move to HubSpot Enterprise and use custom objects, if that plan makes sense for the whole team.
3. Keep the CRM for sales and build the jobs system around it.

Option three is the middle path, and it's where building most often pays off. Our guide to custom software vs off-the-shelf applies the same test more widely. Buy for work that runs the same way in every company, and build for the part that's yours.

The middle path: keep the product, build the missing piece

The middle path keeps HubSpot or Pipedrive as the system of record for contacts and deals. You build only the part the product can't hold, and connect it through the product's API.

An API (application programming interface) is a documented way for one system to read and write another's data. Both vendors publish theirs: HubSpot's developer documentation and Pipedrive's API reference.

Three rules keep the middle path from turning into two half-systems:

• Decide which system owns each kind of record. The CRM owns contacts and deals; the jobs system owns sites and visits. Each record is edited in one place only.
• Sync in one direction where you can. When two systems can edit the same field, you need a written rule for which one wins.
• Give the connection an owner, because the vendor's API changes on the vendor's schedule.

HubSpot stopped supporting API keys after 30 November 2022, to protect customer data. Every integration that used them had to be moved to HubSpot's newer private apps. The change was sensible. The lesson is that the connecting code is software, and someone has to look after it.

What you take on when you build

A custom CRM makes you the vendor. Everything HubSpot or Pipedrive did in the background becomes a job on your list.

Generating a CRM that looks finished has never been easier, and several pages ranking for this question argue that AI has made building cheap. The first screen was never the expensive part. The email sync, the second release, the deletion request and the upkeep are.

Under the UK GDPR, you must answer a subject access request within one month, extendable by two months when a request is complex. The EU GDPR sets the same one-month limit in Article 12.

HubSpot documents a permanent delete for privacy requests, and Pipedrive says it is ready to handle requests to delete or transfer a person's data. In a custom CRM, someone has to build the search that finds one person across every record and attachment, and the export that hands it over.

Data location is where building can win: you choose where the data lives, which helps when a client contract names a country.

The products give you some choice too. HubSpot offers hosting in the EU, in Germany, and says some sub-processors may handle data outside that region. Pipedrive hosts in Frankfurt, Dublin and London among other regions, and says an account can end up in a different data centre from the usual one. Check your own account's region.

Owning a custom CRM isn't automatic either. Under UK law, the code belongs to whoever wrote it until the copyright is assigned in writing, as our guide to building versus buying software explains. When we build, the code, the repository, the hosting account and the documentation sit in your own accounts and are transferred at handover.

What sets the cost on each side

This guide has no figures, because every build is quoted and both vendors publish their current prices. What we can list is what moves them.

HubSpot and Pipedrive both charge per seat, by plan. What you pay moves with:

• How many people need a paid seat, and how many of those barely log in.
• Which plan holds the feature you need, such as custom objects in HubSpot (Enterprise) or custom permission sets in Pipedrive (Premium and Ultimate).
• Add-ons, marketplace apps, and a partner to set it up and import your data.
• Contract length, and the notice period for leaving.

A custom CRM grows with:

• How many kinds of record there are, and how many states each one can be in.
• Connections to email, calendars, accounting and your website forms.
• Data from the old CRM, plus its automations, which have to be rebuilt because they don't leave with the data.
• Roles, and what each one may see and change.
• Phones and offline use.
• Who maintains it after launch.

A good quote for a custom CRM names each of these, says what's out of scope, and says whose accounts the code and hosting sit in. If yours doesn't, ask before you sign.

When not to build a CRM

Don't commission a custom CRM in any of these cases, whoever offers to build it:

• Nobody has configured the product properly yet.
• Your team doesn't keep the current CRM up to date. A new system won't change the habit; it will inherit the gaps.
• The only complaint is the cost of seats. Check who really needs a paid seat before you price a build.
• The sales process isn't agreed, and you're hoping the software will settle it.
• Nobody will own the system after launch.

If your sales team still works from spreadsheets, start with a product, not a build. Our guide to the signs you've outgrown your spreadsheets compares the four ways out.

You may not need a studio either. A HubSpot or Pipedrive partner can configure the product, often faster than anyone can build a replacement. If you can't tell which side of the line you're on, ask for an honest read before you commit. The written recommendation is yours to use whether or not you hire us.

Start by writing down the record

This week, write one line for each record your business runs on: what it is, who creates it, which stages it goes through and who needs to see it.

If every line describes a person, a company or a deal, configure HubSpot or Pipedrive and stop there. If one line describes something else that most of your team touches every day, that record is the piece to build. Your list is already the first page of the brief.

Questions

Can we move from HubSpot or Pipedrive to a custom CRM later?

Yes. Both products let you export your records. What doesn't move is the logic: pipelines, automations and reports have to be rebuilt in the new system, so list them before you start. Import into a test copy first, then check record counts and a sample of records against the old account. Keep the old account read-only for a while after the switch, so the history is still there to check.

HubSpot or Pipedrive, which should we trial first?

Pipedrive is built around the sales pipeline, so it suits a team whose main job in the CRM is moving deals forward. HubSpot puts marketing, sales and service on the same contact records, which suits a firm that wants to see which campaign led to which customer. Trial both with your own records for two weeks, and give the people who will use it every day the loudest vote.

What about Salesforce, Zoho or Microsoft Dynamics 365?

The same order applies: configure first, connect second, build last. The larger platforms let you configure more, including record types of your own. A platform that can model almost anything also needs someone who knows it well to keep it tidy, so count that person in the decision.

How we wrote this: drafted with AI, then checked and edited by the people who build our projects. Figures come from our own work or from the linked sources.