Free tool · new pricing
Size the new HubSpot credit model before anyone quotes you.
Pricing changes on 1 October. You stop buying hubs and start buying an edition, seats, and one shared pool of credits that every action draws from. The calculator shows whether your monthly activity fits inside the pool.
10,000 credits buys one of
- HubSpot-sent emails
- 666
- Workflow actions
- 3,333
- AI service conversations
- 200
- AI content pieces
- 10
02Where should we send the result?
The calculator runs on our proposals platform. Your details come with you, so nothing is asked twice.
How to size it
Identify. Size. Match. Add.
-
01
Diagnose
Audit what is there before touching anything. You get the finding in writing whether or not you go further.
-
02
Architect
The data model, the integrations and the governance, agreed before a line of configuration is written.
-
03
Build
Shipped in increments you can see, so you are not waiting until the end to find out whether it works.
-
04
Operate
A governance and reporting rhythm, so the portal does not quietly drift back within a year.
The 1 October change
What actually changes, and what it costs you to get wrong.
Are you a HubSpot agency?
No. Marketing agencies implement software. We engineer systems. The HubSpot work is architecture, data modelling, integrations and governance, and it usually opens into a longer technical engagement rather than a campaign retainer.
What changes in HubSpot pricing on 1 October?
You stop buying individual hubs. You buy one edition for the portal, seats for the people who need them, and a shared monthly credit pool that every action draws from, emails, workflow actions, AI conversations, all of it. Sizing that pool is where most teams get it wrong, and the cost of getting it wrong only shows up in month three.
Can you take over a portal someone else built?
Most of our work starts that way. We audit what is there before touching anything, tell you plainly what is salvageable and what has to be rebuilt, and give you the finding in writing. You own that document whether or not you go further with us.
How long does an implementation take?
A focused build is six to ten weeks. A multi-region or multi-brand rollout with migration runs three to six months. We work in increments you can see, so you are not waiting until the end to find out whether it works. Anyone quoting two weeks is configuring, not implementing.
Will you work alongside our in-house team?
Yes, and it is usually the better outcome. We build the architecture, document it properly and hand over, rather than making you dependent on us. Some clients keep us on a governance retainer afterwards, others take it in-house entirely. Both are fine.
How do you handle AI safely?
Guardrails first, then the agent. That means scoped permissions, a data model clean enough to be trusted as input, logging on every action an agent takes, and a human checkpoint anywhere the output touches a customer. AI on top of a messy CRM just automates the mess faster.
We are not a large enterprise. Are we too small?
We work with teams from around twenty people through to global groups. The test is not headcount, it is whether you have a real sales motion and something worth engineering. If you want a cheap task executor rather than a system, we are the wrong fit and we will say so early.
What happens when the build is done?
Governance and a reporting rhythm, so it does not quietly drift back. Most portals degrade within a year of go-live because nobody owns the standard. We either run that with you monthly or set it up so your team can.
Next step
Find out what is actually wrong with your portal.
Data quality, broken workflows, unused licences. You get the report whether or not you speak to us.
No sales call unless you ask for one.