Wired to the rest of your stack

The problem

Paying Professional prices for a free-tier portal.

HubSpot’s free tier is a real CRM, not a trial. Contacts, companies, deals, a pipeline, and view-only access that costs nothing, so the whole team can see the data and you only pay for the people who edit it. That is why upgrading feels anticlimactic. You move to Professional, the screens look identical, and nothing improves, because the thing you actually bought was the workflow engine and a workflow engine does nothing until somebody builds workflows in it.

So the portal drifts. Two or three workflows get built in the first month by whoever was keenest, then that person gets busy. Properties pile up until nobody can find the one that matters. Imports create twins, because HubSpot merges contacts on email address and a contact with no email has nothing to merge on. Deals never merge at all, since they are not deduplicated automatically in the first place. Six months later nobody trusts the reporting, so people keep their own spreadsheet, which is where you started.

The licence is rarely the problem. The build is. Most small teams do not need Enterprise. They need the workflows written properly, the phone and the calendar writing into the timeline, the property list cut back to the fields people actually fill in, and somebody who knows which of HubSpot’s limits are real and which are just defaults nobody switched on.

Built around how HubSpot actually behaves.

Workflows Worth The Tier

Workflows are the reason to be on Professional or Enterprise at all, and most portals we open are running a handful of half-finished ones. We build the enrolment logic, the branches and the re-enrolment settings, which are off by default and quietly explain why a workflow only ever fired once per contact.

Calls On The Contact Timeline

A call from your voice agent or your phone system lands as a logged call engagement on the right contact, associated to the open deal or ticket, with the outcome and the recording attached. It then counts in HubSpot’s own call reporting instead of sitting in a separate dashboard nobody opens.

Deduplication And Property Clean-Up

HubSpot merges contacts on email address and companies on domain automatically, and does nothing at all for deals or tickets. We set unique-value properties where they belong, fix the forms and imports creating twins, and archive the properties nobody has filled in for a year.

Modelling Without Enterprise

Custom objects are an Enterprise feature, so on Professional a job, a policy or a property has to be modelled as a deal, a ticket or a labelled association. We tell you which of those still reports cleanly in two years and which becomes a pipeline full of things that are not deals.

Keeping Contacts Off The Marketing Bill

Marketing Hub bills on marketing contacts, and the status is frozen at the start of each billing period, so a sync that flips your whole database to marketing costs you the full month before you can undo it. We default every contact our integrations create to non-marketing and promote them only when you actually intend to email them.

API Work That Respects The Quotas

HubSpot counts the burst limit per app but shares the daily quota across every app in the portal, and the search endpoint has a much tighter limit of its own. We batch writes, cache reads and back off properly on a 429, so a new integration does not quietly starve the ones you already depend on.

Questions we get a lot.

Do we need HubSpot Professional, or will Starter do?

Workflows are the dividing line, and it is worth deciding before you pay. Starter gives you simple automation with a short list of allowed actions and no branching, so anything needing an if-then decision is out. If your list is genuinely "when this form comes in, send that email and create a task", Starter is enough and the jump to Professional is not worth making. If you need routing, scoring, stage-based follow-up or anything conditional, the workflow engine is what you are buying. We will tell you which of those two you are before you upgrade rather than after.

What can you build for us on the free HubSpot tier?

More than most people expect. The free CRM holds contacts, companies and deals properly, and our integrations can read and write all of it through the API without any paid tier. What free does not include is the workflow engine, so conditional logic has to live outside HubSpot, usually in n8n, and write its results back in. That works well and we build it that way regularly. The honest trade-off is that your team cannot see or edit that logic inside HubSpot, so it becomes something you ask us about instead of something you change yourself.

We are on Professional and we need custom objects. What are our options?

This is the sharpest limit in HubSpot and we would rather be blunt about it. Custom objects are Enterprise-only, so on Professional there are three workarounds: model the thing as a deal in its own pipeline, model it as a ticket, or hold it outside HubSpot and surface it on the record with a CRM card. All three are compromises, and the first one quietly poisons your sales reporting because your deal figures now include things that are not deals. If your business has a genuine first-class entity that is not a contact, a company, a deal or a ticket, and you need to report on it properly, HubSpot Professional is a poor fit, and Enterprise carries a seat minimum that makes it an expensive answer for a small team. We have told people to stay on a different CRM for exactly this reason.

Will connecting things to HubSpot increase what we pay HubSpot?

It can, in two specific ways, and both are avoidable if somebody is watching for them. Marketing Hub is billed on marketing contacts, so an integration that creates contacts and marks them as marketing moves you up a tier, while non-marketing contacts do not count towards it at all. That status is frozen at the start of each billing period, so a bad import costs you a full month before the correction takes effect. Separately, HubSpot’s usage-based AI features run on credits that reset monthly and do not roll over, and the feature pauses when they run out unless you have enabled overages. We create non-marketing contacts by default and keep our automation off the credit meter wherever an ordinary workflow action does the same job.

Can an AI voice agent dial and answer from inside HubSpot?

Those are two different jobs with very different effort. Logging a call into HubSpot is straightforward: a private app writes a call engagement against the contact, and that covers what almost every client actually wants. Putting a working dialler panel inside the HubSpot record is a bigger build, because it needs a publicly listed app using HubSpot’s calling extensions SDK and it goes through HubSpot’s review before anyone can install it. If your team lives in HubSpot all day and wants click-to-call from the record, we will scope that honestly, including the review time. If you just want every call on the timeline with a recording and an outcome, that is the smaller and cheaper piece of work.

Why does our workflow only run once for the same contact?

Because re-enrolment is off by default and almost nobody realises it. HubSpot enrols a record the first time it meets the trigger and then never again, unless you have explicitly configured re-enrolment, which only filter-based triggers support anyway. So a workflow meant to fire on every new enquiry from a returning customer fires once, in the year they first appeared, and looks broken ever after. It is a short fix once you know, and it is among the first things we check when a client says their automation stopped working.

Is HubSpot the right CRM for us, or would you tell us to use something else?

We are not resellers, so no commission is steering the answer. HubSpot suits you if sales, marketing and support all need the same contact record, and if you want non-technical staff editing automation on a canvas rather than raising a ticket with a developer. It suits you less if you need deep quoting, stock control or field-service scheduling, or if your data is genuinely relational and you cannot justify Enterprise. The other thing to weigh is the step from Starter to Professional, which is a large jump in monthly cost and only pays back if somebody is going to build the workflows. If nobody is, you are buying an engine and leaving it idle, and we would rather say that on the call than take the work.

Tell us what your portal is not doing yet.

Send us your workflows list and your property count. We will tell you what is worth building, what you are already paying for and not using, and what your current tier will not let us do.

Book a Free Demo