What Can You Actually Build with Custom HubSpot Development? (Real Examples)

Most HubSpot buyers know the platform as a configurable CRM: properties, workflows, forms, dashboards. All point and click. So when someone says "custom HubSpot development", it can sound like a vague upsell. What does it actually produce? What can you build that you could not configure your way to?

The honest answer is that HubSpot is no longer just a SaaS product you switch on. It now ships a genuine developer platform. In March 2026 HubSpot released Developer Platform version 2026.03, its first date-based version, which brought serverless functions back into the unified Projects framework and put a formal 18-month support lifecycle around the whole thing. That matters because it means HubSpot is something you can build on, not just something you set up. This article walks through the categories of custom HubSpot development, with concrete (illustrative) examples and indicative costs, so you can tell what is genuinely possible.

If you want the overview of how we approach this work, start with our HubSpot development hub. Each section below links down to the specific capability page.

1. UI extensions: custom apps inside HubSpot's own screens

UI extensions are custom React-based components that render inside HubSpot's interface itself: on CRM record pages, and now in App Settings and App Pages too. They are built with HubSpot's official @hubspot/ui-extensions component library and tested in developer accounts before they go anywhere near your live portal.

The point of a UI extension is to stop reps tab-switching. A realistic example: a panel on a deal record that pulls live order or contract status from your ERP and shows action buttons right there, so a salesperson never leaves HubSpot to answer "where is my order?". This is where most "why is my CRM not telling me what I need" problems get solved. UI extensions start from around £8,000. See UI extensions for what that includes.

2. Custom-coded workflow actions: real logic inside automation

HubSpot workflows are powerful, but they hit a ceiling fast. The moment you need genuine calculation, conditional maths, or a call out to another system mid-flow, the standard actions run out. A custom-coded workflow action lets you write JavaScript (or Python, currently in beta) that runs as a single step inside a workflow. It needs Data Hub Professional or Enterprise (Data Hub is the current name for what was Operations Hub), and it runs as a HubSpot-managed serverless function.

It is worth knowing the limits, because they shape what is sensible to build here: a 20-second execution timeout, 128 MB of memory, up to 50 HubSpot properties per action and a 65,000-character output cap. Within that, you can do real work: a live postcode or credit lookup, bespoke lead-scoring maths, or a call to an external pricing API to enrich a record on the fly. Custom-coded workflow actions start from around £2,500. More on custom-coded workflow actions.

3. Serverless functions: server-side logic you host in HubSpot

Serverless functions are server-side code that runs within HubSpot, without you standing up your own infrastructure. They used to be locked to Content Hub Enterprise, but the 2026.03 platform release returned them to the Projects framework and widened their availability across Enterprise hubs.

This is the building block for anything that needs secure, server-side rules: processing an inbound webhook, validating a payment, or powering a form submission with business logic the browser is not allowed to see. There is a credibility point hiding in the version history here. Projects v2025.1 reaches end of support on 1 Aug 2026, and apps need to move to a supported version to keep working. That is exactly the kind of platform deadline a configurator will miss and an engineer will track. Serverless functions start from around £2,000. See serverless functions.

4. CMS memberships and gated customer portals

HubSpot can gate web pages, landing pages, blog posts and knowledge-base articles so only logged-in contacts can see them. It uses your CRM plus access groups (static or dynamic) to decide who can register and what they see. Memberships need Content Hub Professional or Enterprise (the legacy CMS Hub Professional tier does not support them).

Memberships are the native foundation, but a real self-service customer portal is usually memberships plus UI extensions plus serverless logic plus CRM data, combined. That is where the categories above start compounding into something a customer actually logs into. A CMS membership portal starts from around £15,000. See CMS memberships, and if you are scoping a full self-service experience, our customer portals page covers the combined build.

5. Marketplace and public apps

If you have built something good internally, you can productise it as a listed public app, now built on the same Projects platform. Worth knowing if this is on your roadmap: from 26 May 2026, creating new legacy public apps through the Developer Platform UI is permanently disabled, so new apps must be built on the current platform. Certification requires a supported platform version, at least 60 active unique installs and a set of security, privacy, reliability and accessibility criteria. Marketplace apps start from around £18,000. See Marketplace app development.

6. Custom Conversations channels

HubSpot's Inbox and Help Desk natively connect the obvious channels. The Custom Channels API lets you bridge any two-way text messaging service into the same inbox your reps already use, including channels with no native integration (LINE, Telegram, WeChat, Viber, Apple Business Chat) or your own proprietary in-app messaging stream. It now supports HubSpot-managed threading, the same model as WhatsApp and SMS.

The practical win is one inbox. Instead of agents watching a separate console for a niche regional channel or your app's chat, every conversation lands where the team already works, properly associated to the right contact. A custom Conversations channel starts from around £12,000. See custom Conversations channels.

7. Complex and compliant cookie controls

This one is a quiet liability for a lot of HubSpot sites. The native consent banner has real limits: it does not block third-party scripts loaded through custom HTML modules, theme templates or external tag managers, so things like YouTube embeds, analytics and ad platform tags can fire regardless of what a visitor chooses. In practice it behaves more like a notification than a true consent gate, and it does not keep the granular audit log that genuine GDPR and ePrivacy compliance expects. HubSpot is auto-migrating the banner from v1 to v2 from 11 May 2026, but the underlying gaps remain for multi-source sites.

The engineering answer is bespoke consent gating, or integrating a dedicated consent management platform, so non-essential scripts genuinely do not load before consent. See complex cookie controls.

8. Integrations and data migration

Most custom HubSpot work ends up touching another system. Integrations are not a rate card item, because cost depends on what you connect and how. As a directional guide (these are third-party market estimates, not our quotes), a modern, well-documented REST API integration tends to land around £3,000 to £8,000, while a legacy or poorly-documented system can run £8,000 to £20,000, with high-volume real-time builds adding queuing, retry and hosting cost on top. We scope larger custom integrations individually. See integrations.

Migration deserves its own caution. Gartner is widely cited for the finding that roughly 83% of data migration projects run over budget or time, or fail outright (again, a directional third-party figure). That is precisely why migration should be engineer-led rather than treated as a bulk import. See data migration.

Why this is engineering, not configuration

Notice what runs through every category above: platform version deadlines, serverless execution limits, native banner gaps, certification thresholds, support windows. None of that is point-and-click. It is the difference between a configurator who fills in HubSpot's standard fields and an engineering team that tracks the platform and builds on it.

That distinction shows up in HubSpot's own programme too. We are a UK HubSpot Diamond Partner (one tier below the invite-only Elite), and we hold HubSpot's Custom Integration Accreditation, which validates first-hand experience scoping and deploying complex, multi-object or bidirectional integrations through genuine custom development rather than brittle off-the-shelf connectors. We are also HubSpot Onboarding Accredited and Cyber Essentials Plus certified, with an in-house engineering team, productised solutions hosted on Railway that you can own, and a simple promise: delivered on time, or you get 20% back.

Where to start

The real value of custom HubSpot development is not any one of these blocks in isolation. It is what happens when you treat HubSpot as a platform to build on and combine them: memberships plus UI extensions plus serverless logic become a customer portal; a custom workflow action plus an integration becomes real-time enrichment your reps never have to think about.

If you are weighing up what is worth building, the best next step is a conversation about your specific stack and the outcome you are after. Browse the full HubSpot development offering, or tell us what you are trying to achieve and request a quote. We will tell you honestly what is configurable, what needs building, and roughly what each path costs.

Frequently asked questions

What is the difference between configuring HubSpot and custom HubSpot development?

Configuring HubSpot means using the standard, point-and-click features: properties, workflows, forms and dashboards. Custom HubSpot development means writing code on HubSpot's developer platform to build things the standard product cannot do, such as UI extensions inside CRM records, custom-coded workflow actions, serverless functions, gated membership portals and custom integrations. Configuration handles the common cases; development handles your specific logic, data and systems.

Do I need a paid HubSpot tier for custom development?

It depends on the capability. Custom-coded workflow actions require Data Hub Professional or Enterprise (Data Hub is the current name for the former Operations Hub). CMS memberships require Content Hub Professional or Enterprise, and the legacy CMS Hub Professional tier does not support them. Serverless functions and UI extensions are tied to Enterprise-level access on the relevant hubs. We can confirm exactly what your current subscription supports before scoping anything.

How much does custom HubSpot development cost?

Indicative starting prices on our capability pages are: serverless function from £2,000, custom-coded workflow action from £2,500, UI extension from £8,000, custom Conversations channel from £12,000, CMS membership portal from £15,000, and a Marketplace app from £18,000. Integrations are scoped individually because cost depends on what you connect and how. These are starting points, not fixed quotes.

Can I build a customer portal in HubSpot?

Yes. The native foundation is CMS memberships, which gate pages to logged-in contacts using your CRM and access groups. A genuine self-service portal usually combines memberships with UI extensions, serverless logic and live CRM data, so customers can see and do things specific to their account. That combined build is what our customer portals service covers.

Why use an accredited partner rather than a freelancer for custom HubSpot work?

Custom HubSpot development is shaped by platform realities that move: version support deadlines, execution limits on workflow code, certification thresholds for apps, and gaps in native features like the consent banner. An accredited engineering team tracks those and builds accordingly. We are a UK HubSpot Diamond Partner with HubSpot's Custom Integration Accreditation and Onboarding Accreditation, Cyber Essentials Plus certified, with an in-house team and an on-time-or-20%-back guarantee.