Discuss your task

Search

Start typing to search articles, cases, and services.

↑↓ navigate Esc close

Which HubSpot developer you need and how to vet them

“HubSpot developer” is not one profession but three different ones: a developer who builds sites on HubSpot CMS, a developer who builds integrations on the HubSpot API, and an admin who writes code inside automations. Their skills barely overlap, so define the task first and then look for the person who fits it. The best way to vet a candidate is with specific questions - about API limits, repeated event delivery, the test environment and code ownership.

In Exceltic.dev integration projects we often step into a HubSpot account after another contractor. The picture repeats itself: the company was looking for a “HubSpot developer”, hired a strong site template specialist, but the actual job was a two-way sync with billing. A couple of months later the sync runs on a chain of Zapier Zaps, and nobody can explain why some payments never reach their deals.

The problem is not the contractor’s skill level. It is that one request hides several different kinds of work. Below we cover how the three roles differ, who you need for typical tasks, what changed in the HubSpot developer platform by the end of 2026, and which questions to ask before you sign a contract.

A hiring mistake costs more than the contractor’s rate. Integration tasks stall for months, sales works with numbers that don’t match accounting, and marketing stops trusting the reports. When the contractor leaves, it turns out the app was created in their account, and the data depends on Zapier Zaps with all the limitations of the HubSpot and Zapier combination: duplicates, lost records and failures when load spikes.

HubSpot developer: a specialist who extends HubSpot with code - through site templates on HubSpot CMS, through the platform API or through code inside automations - where standard settings are no longer enough.

Three roles under one title

All three specialists work with the same platform, but they solve different tasks and depend on different HubSpot subscription tiers. Keep in mind that some products were renamed: Content Hub used to be CMS Hub, and Data Hub replaced Operations Hub, so you will see both names in resumes and job posts.

HubSpot CMS site developer

This specialist builds the website, blog, landing pages and email templates on HubSpot’s built-in CMS. Their main tool is HubL, HubSpot’s templating language based on Jinjava, which renders pages on the server side. On top of that come HTML, CSS, JavaScript and React components.

Typical tasks:

  • a site theme with a set of modules that marketing uses to build pages without a developer
  • blog, landing page and email templates
  • dynamic pages built from HubDB tables or CRM objects
  • serverless functions for forms and data processing on the site

The site runs on Content Hub. Serverless functions are available only in Content Hub Enterprise, and custom email templates require Marketing Hub Professional or Enterprise. This specialist’s territory is what a site visitor sees, and integrations are usually not their strength.

HubSpot API integration developer

This specialist connects HubSpot to other systems and builds apps inside the platform. What matters here is architecture, not layout: queues, retries, idempotency, working within rate limits.

Typical tasks:

  • two-way sync with an ERP, billing, inventory or product database
  • receiving HubSpot events via webhook and processing them in an external service
  • custom objects for entities that do not exist in the standard data model
  • React app cards that show data from an external system right on a CRM record
  • choosing the authentication scheme: a static token for a single account, or OAuth if the app is installed in multiple accounts

Private apps with API access work even on the free tier (new ones are now created on the projects platform, covered below), while the tier determines rate limits and access to specific features. Custom objects require an Enterprise subscription, as does installing an app that uses HubSpot serverless functions.

One example of this kind of work is GPT call summaries on the contact record, where a webhook, an external service and the CRM API replace manual rep notes. We cover the choice between a native integration, Zapier and custom code separately in our article on three ways to integrate a CRM.

The admin who writes code

The third role is closer to sales operations than to development, and job posts often call it RevOps. This specialist sets up pipelines, properties and workflows, looks after data quality, and writes code only selectively - where standard actions fall short.

Typical tasks:

  • lead rotation rules between reps
  • database cleanup - duplicates, phone number formats, empty required properties
  • calculating and auto-populating properties
  • a custom code action inside a workflow - a short JavaScript script (and, in beta, Python) that can call the API

Custom code and webhook actions are available only in Data Hub Professional and Enterprise. According to HubSpot’s documentation, such an action must finish within 20 seconds and 128 MB of memory. That is enough to process a single record, but not to sync with an external system.

Why experience from two years ago is no longer a guarantee

The HubSpot developer platform changed significantly over 2025-2026, and a candidate with outdated experience may propose a setup that can no longer be built in your account. Here is what matters as of Q4 2026:

  • Apps are built as developer projects: configuration and code live in files and are deployed via the HubSpot CLI. Supported platform versions are 2025.2, 2026.03 and 2026.09.
  • Since October 26, 2026, you can no longer create a legacy private app in existing accounts. Those created earlier keep working but do not get new features.
  • According to HubSpot’s announcement of September 15, 2026, legacy private and public apps, as well as API versions v1-v3, lose support after September 2027. Projects on version 2025.2 and older must be moved to 2026.09 before March 2027.
  • Classic CRM cards have been unsupported since October 31, 2026, and React app cards replaced them.
  • Since November 3, 2026, you cannot create new custom code actions on Node.js 20, and HubSpot recommends moving existing ones to Node.js 24.

The practical takeaway for hiring: ask the candidate which platform version they used for their last app. An answer along the lines of “I’ll create a private app in settings and copy the token” describes a path that is already closed in your account.

If your current integration runs on a legacy private app, plan the move to the new platform before September 2027. It is a good first test for a new contractor: ask them to estimate the scope of the migration.

Which role fits a typical task

Before you hire a HubSpot developer, match the task to a role and a subscription tier - it saves weeks of back-and-forth. Below is the mapping we use in our first conversation with a client. Timelines are reference points from Exceltic.dev projects with an already configured account, not a promise.

TaskWho you needWhat it takes in HubSpotTypical timeline
Site redesign on HubSpot CMSSite developerContent Hub, Enterprise if you need serverless functions4-10 weeks
Two-way sync with an ERP or billingIntegration developerAn app on the new platform and an external service with a queue4-8 weeks
Custom object for a non-standard entity (subscription, license, real estate listing)Integration developer together with an adminEnterprise subscription1-3 weeks
Lead rotation rulesAdminWorkflows, plus Data Hub Professional for non-standard logic3-10 days
Cleaning duplicates and junk out of the dataAdmin, plus an integration developer for bulk operationsBuilt-in tools, plus the API or Data Hub Professional for scripts1-3 weeks
External tool data on a CRM recordIntegration developerReact app card, Enterprise if you need HubSpot serverless functions2-4 weeks

The most common mistake is giving the second row to a site developer or an admin. A billing sync is a separate service with a queue and a log, and a custom code action with a 20-second limit will not replace it.

What a HubSpot developer should answer in an interview

You can spot a strong candidate by their answers to five technical questions, even if you do not write code yourself. Below are the questions and what you want to hear.

  1. How do you handle API limits? Under HubSpot’s API usage guidelines, a private app on Professional and Enterprise gets 190 requests per 10 seconds. The daily limit is shared across the account: 625,000 requests on Professional and 1 million on Enterprise, and once you exceed it HubSpot responds with a 429 error. A good answer includes a queue, caching and a pause on 429 errors, not “we’ll just resend it right away”.
  2. What happens if an event arrives twice? HubSpot retries webhook delivery up to 10 times over 24 hours if your service did not respond within 5 seconds or returned an error, and it does not guarantee event order. So the handler must be idempotent: a repeated event does not create a second deal or duplicate a payment.
  3. Where will the code live, and who owns the app? The app is created in your HubSpot account, and the repository lives in your organization on GitHub or GitLab. Tokens and secrets stay with you, and the contractor gets access for the duration of the project.
  4. Where do you test changes? “Right in the production account” is a bad answer. HubSpot lets you create up to 10 developer test accounts for free, with 90-day trial access to many Enterprise features, and Enterprise tiers include a standard sandbox that copies the structure of your production account.
  5. How will you know the integration broke? You need an operations log with record IDs and an alert in Slack or by email when errors rise. To certify an app in the HubSpot marketplace, HubSpot requires error responses to make up no more than 5% of daily requests, and without a log you cannot even measure that.

Red flags

  • The candidate proposes building a two-way sync out of Zapier Zaps or workflows, with no external service.
  • They want to create the app in their own account, or ask for a shared super admin login instead of separate access.
  • They cannot show code from past integrations, even in anonymized form.
  • They suggest a legacy private app or classic CRM cards.
  • They do not ask about your HubSpot tier, even though it determines what can be built at all.
  • They estimate the integration without finding out the data volume and the source of truth for each field.

In-house employee, freelancer or agency

The right hiring format depends on how much work will remain after launch. The hourly rate is secondary here: a system nobody can maintain costs you more.

An in-house specialist makes sense when HubSpot work is ongoing: a Content Hub site with weekly changes, several integrations, regular automation updates. The risk is that one person becomes the only one who understands the system, so you still need documentation and a repository.

A freelancer fits a clear, bounded task: a landing page template, a few properties and workflows, a one-time database cleanup. The risk is support after handover: six months later the freelancer may be busy, and you have neither documentation nor access to the code.

An agency makes sense when the task needs several roles at once. For example, moving to HubSpot means migrating data, connecting the CRM to billing and rebuilding the pipeline. If you are just rolling out HubSpot or rebuilding it, this work is easier to run as a single HubSpot implementation project than to coordinate across three contractors. The risk is paying for roles you don’t need, so ask for a breakdown of work by specialist.

What this looks like in a typical project

Below is the scenario we see more often than any other in Exceltic.dev projects, with figures typical for it.

Starting point. A B2B SaaS company with 40-60 people, on Sales Hub and Marketing Hub Professional. Payments and renewals go through an external billing system, and the deal amount has to match it. The previous contractor, a strong theme developer, built the sync from 10-15 Zapier Zaps and several workflows.

What we usually find. Between 2 and 5% of payments never reach their deals or arrive twice. An account manager spends 4-6 hours a week on manual reconciliation, and nobody uses the revenue report in HubSpot.

What we do.

  1. Audit: which system is the source of truth for each field and where events get lost.
  2. An app on the new HubSpot platform with a static token, plus an external service with a queue. The service receives an event from billing, checks whether it has already been processed, and updates the deal via the API within the rate limits.
  3. An operations log, alerts when errors rise, and a nightly reconciliation of discrepancies.
  4. Switching off the Zapier Zaps one by one after a parallel run.

Result. In projects like this, getting from the audit to switching off the last Zap takes 4-7 weeks. Discrepancies between billing and HubSpot drop to isolated cases per month, and each one is visible in the log. Manual reconciliation goes down from several hours to 30-60 minutes a week.

Who this guide is for

This guide is useful for companies with 15 or more people where HubSpot has already become the main sales and marketing tool, or where a move to it is planned. Especially if money lives in an external system such as billing or an ERP, HubSpot tasks pile up for months, and the previous contractor left without documentation. If all you need is a landing page on HubSpot CMS, a good site developer is enough, and this breakdown of roles will help you avoid overpaying.

Frequently asked questions

How long does a custom HubSpot integration take?

It depends on the number of systems, the sync directions and the data volume. In Exceltic.dev projects, one-way event delivery from an external service into HubSpot usually takes 1-3 weeks, and a two-way sync with billing or an ERP takes 4-8 weeks, including the audit and the parallel run. Most of the time goes not into code but into agreeing on the source of truth for each field and testing edge cases: refunds, partial payments, merged duplicates. If a contractor gives you a timeline without asking these questions, the estimate is most likely too low.

Which HubSpot tier do you need for custom development?

Private apps with API access, including new projects-based ones, work on any tier, including the free one, but the limits differ: 100 requests per 10 seconds on Free and Starter, 190 on Professional and Enterprise. The restrictions start at the level of specific features. Custom objects require an Enterprise subscription, serverless functions on the site require Content Hub Enterprise, and custom code actions in workflows require Data Hub Professional or Enterprise. So before hiring, check your task list against your current tiers: sometimes moving the logic to an external service is cheaper than upgrading.

How is a HubSpot developer different from an admin?

An admin configures the platform with built-in tools: pipelines, properties, permissions, workflows and reports. A HubSpot developer extends it with code: builds the site on HubSpot CMS, writes integrations via the API, creates app cards and custom objects. In between sits an intermediate role - an admin who writes short scripts inside workflows. For lead rotation or data cleanup an admin is usually enough, but syncing with external systems takes an integration developer.

Can you use Zapier instead of a developer?

For simple one-way scenarios with low volume, yes: a form submission creates a contact, a closed deal sends a notification to a chat. Problems start when data flows both ways, the number of events grows, or an error costs money. Without idempotent processing, a queue and a log, you get duplicates and lost records that nobody notices for weeks. The working rule: if a data mismatch costs you money or a customer, the integration should be code that you control.

Who owns the code after the project ends?

Settle this in the contract before work starts. The right setup is: the app is created in your HubSpot account, the repository belongs to your organization, tokens and secrets are kept in your own secrets storage, and the contractor gets access to them for the duration of the project. On the new HubSpot platform, the app’s configuration and code are described in project files, so with this setup, changing contractors comes down to handing over access. If the code stays only with the contractor, you are effectively renting the integration.

Key takeaways

  • Define the task first, then choose the role: a HubSpot CMS site, an API integration and automation with code are jobs for different specialists.
  • Check your tasks against HubSpot tiers before hiring: custom objects, serverless functions and code in workflows are not available on every tier.
  • Vet candidates with questions about API limits, duplicate events, the test environment, the error log and code ownership.
  • If your integration runs on a legacy private app, plan the move to the new platform before September 2027.

If you are looking for someone to handle HubSpot work and are not sure which role you need, describe the task to the Exceltic.dev team. We will break it down, tell you which specialist and tier it will take, and estimate the scope of work - even if you end up hiring someone yourself.

More articles

All
Get in touch your way
WhatsApp Telegram

Before you go: bonus months of Kommo

The implementation estimate is free: describe your sales process in a few words and we propose a solution, a plan and a quote with timelines.

We are an official Kommo partner in Europe: pay for the subscription through us and get bonus months.