HubSpot development

Custom HubSpot development when configuration isn’t enough

We build HubSpot apps, UI Extensions, custom objects, serverless functions and workflow code so your process lives inside the CRM. Your team works on a single screen and the business logic runs by itself.

HubSpot Diamond Solutions Partner
4.9 Verified reviews on HubSpot
9 official HubSpot
certifications
+200 clients in Spain,
Italy and Dubai
19 people on the team
15 in Barcelona · 4 in Dubai

Real projects

What we’ve built inside HubSpot

A few developments already in production, described without client names.

Retail

A shopping cart with live stock inside HubSpot

A chain of bridal shops sells straight from the deal record: catalogue and stock read from Holded, partial payments and e-signature, all built with UI Extensions.

Retail

A dressmaker portal and per-shop booking calendar

In the same project: an appointment calendar by shop and professional, and a dedicated portal for the dressmakers who work with the shops.

SaaS

ARR, renewals and CLM

Around 12 microservices for a fintech SaaS: ARR and account type calculated daily, chained renewals and CLM with Ironclad, including a backfill of 1,615 workflows.

Read the case study
Law firm

A multi-company “Payments” object

A law firm with 5 companies records payments by Stripe, Redsys, bank transfer or cash in a custom object that lands in the right cash account in Holded.

Finance

Prepaid credit packs with automatic renewal

Signed quote, SEPA direct debit via a Stripe mandate, invoice in Holded and the customer’s balance in the CRM, which renews itself when it drops below a threshold.

Real estate

One-click publishing to portals

From the development’s record in HubSpot, one button publishes it on Inmovilla. Properties from other portals sync with change detection.

Read the case study

Capabilities

The building blocks of a HubSpot app

We use HubSpot’s official developer tools, so what we build fits into the interface and respects your portal’s permissions.

UI Extensions

  • Custom cards and tabs on records
  • Forms, tables and action buttons
  • Real-time data from other systems
  • Built in React

Custom objects

  • Payments, subscriptions, properties, appointments…
  • Labelled associations
  • Their own pipelines and properties
  • Reporting just like any standard object

Serverless and workflows

  • Serverless functions for business logic
  • Custom code in workflows
  • Sequential numbering and calculations
  • Scheduled daily jobs

Webhooks

  • Signed, verified webhooks
  • Idempotent processing
  • Retries and an error queue
  • A log of every event

Private and project apps

  • Least-privilege permissions per app
  • Versioning and controlled deployments
  • Separate test and production environments
  • Code delivered and documented

API and data

  • Integrations with any system that has an API
  • Bulk loads and backfills
  • Stage history for the data warehouse
  • Simulation mode before writing

Judgement

We only write code when it’s needed

Every line of code has to be maintained. So before proposing any development, we check whether HubSpot can already solve it with configuration, a workflow or an existing connector. If it can, we’ll tell you.

Custom HubSpot development makes sense when your process is your competitive edge and doesn’t fit in a standard CRM: when the team jumps between three tools to close a sale, when a calculation is done by hand every month, or when two systems need to agree with each other without human intervention.

Signs you need it

  • Your team leaves HubSpot to check stock, prices or balances
  • You calculate ARR, commissions or renewals by hand
  • Your business revolves around something that isn’t a contact or a deal
  • Standard workflows fall short of your logic
  • You need HubSpot to act on another system in one click

Why Vexco

Developers who speak business

01

Consulting and code in the same team

The person who understands your sales process is the one who designs and codes the solution. No specification gets lost between departments.

02

Built on HubSpot, not beside it

We use UI Extensions, custom objects and official apps so everything stays inside the CRM, with its permissions, reporting and audit trail.

03

Robust by design

Idempotency, retries, deduplication and simulation mode are standard in everything we build, not an add-on.

04

No lock-in

We hand over the code and the documentation. You can maintain it with your own team or with our monthly support.

Method

From idea to app in production

Specification

Understanding the case

We analyse the process, the users and the systems involved, and decide what can be solved with configuration and what needs code.

Use casesFixed scope

Prototype

Validate before building

We design the screens and the data model and validate them with the people who will use them every day.

Screen designData model

Development

Sprints with demos

We develop in weekly sprints, in a test environment and with real data in simulation mode.

Weekly sprintsAcceptance tests

Production

Deployment and handover

We deploy, train the team and hand over the code and documentation. If you like, we stay on for maintenance.

DocumentationOptional maintenance

Problems we solve

When HubSpot falls short

Our sales reps check stock in another tool.

We show the ERP’s catalogue and stock on the deal record with a UI Extension and build the order from there.

We calculate ARR in a spreadsheet every month.

A scheduled function calculates ARR and account type every day and stores them in report-ready properties.

We need sequential numbering for contracts or orders.

We generate sequential numbering with no gaps or repeats, using workflow code or serverless functions.

Our business revolves around properties, payments or appointments.

We create custom objects with their own properties, pipelines and associations, integrated with the rest of the CRM.

Renewals keep slipping through the cracks.

We automate chained renewals: when one period closes, the next deal is created with its amounts and dates.

We want an external partner to see only their part.

We build custom portals and views with access limited to the information that concerns them.

FAQs

What clients ask us before we start

What are HubSpot UI Extensions?

They are React components displayed inside HubSpot records as custom cards or tabs. They let you see data from other systems, fill in forms or trigger actions without leaving the CRM.

Which HubSpot edition do I need for custom development?

It depends on the component. Custom objects require Enterprise editions; custom code in workflows requires Data Hub (formerly Operations Hub) Professional or above. Private apps and API integrations work with more editions. We review this with you before proposing anything.

How much does it cost to build a HubSpot app?

It depends on the number of screens, the business logic, the systems it needs to talk to and the volume of data. After the specification phase we give you a fixed-price, phased quote.

Who owns the code?

You do. We hand over the code and the technical documentation. You can maintain it with your own team, with us or with whoever you choose.

What happens when HubSpot changes its API?

HubSpot announces changes in advance. If you have our monthly support, we review and adapt your developments before they affect your operations.

Is it safe to put our own logic inside HubSpot?

Yes, if it’s done properly: least-privilege apps, signed webhooks, securely stored credentials and GDPR-compliant data processing. Everything is logged so you can audit what happened.

Free audit

Is your HubSpot working for you?

In 30 minutes we review your CRM, your processes and your integrations, and tell you honestly what we would change first. No commitment, no sales pitch.

We reply within 24 business hours.

Free audit