Portal care in an agreed number of hours per month.
After go-live a portal keeps generating work that never adds up to a project: a stage to add, a report the board suddenly wants, a workflow that stopped firing, a new joiner who needs access. I take that work in a fixed number of hours a month, run it off one list in your order of priority, and show what the hours went on.

Six things that happen inside the hours.

Configuration changes
Pipelines, stages, properties, views and permissions as the process changes. Small changes land in days rather than waiting for a project.

Workflows and automation
New automation, fixes to what stopped firing, and cleaning up what overlaps. Automated tasks that pile up unclosed get dealt with rather than accumulating.

Reports and dashboards
New reports, corrections to existing ones and the honest answer when a report cannot be built on the fields that exist today.

Data hygiene
Duplicates, ownerless records, imports that went in wrong. This is the work that quietly decides whether reporting stays believable.

Integrations and keeping them alive
Connections between HubSpot and the other systems, plus watching what they overwrite. An integration that overwrites a manual correction is a reporting problem waiting to happen.

Help for the team
Questions from the people who work in the portal, answered as they come up, so nobody works around the system for two weeks in silence.
Care stands on an agreed number of hours and one list of priorities.
Hours agreed up front
A fixed monthly envelope, set after I look at the portal and the pace of change. Small portals need a couple of hours; a portal three teams work in needs more, and I say which one yours looks like.
One list, your order
Everything goes on a single list with an estimate per item. You decide the order. That way a report for the board does not sit behind a cosmetic fix.
You can see where the hours went
Every month you get what was done, how long it took and what is still open. Care without that visibility turns into an invoice nobody can check.
The account stays yours
Your portal, your super admin, your integrations. I work as a user in your account, which means nothing is hostage if I stop working together.
Handover. Hours. Rhythm. Quarterly review.
Handover
A walk through the portal as it is: what is configured, what is half-built, what nobody can explain. If the portal came from another agency, this step also finds what was left undocumented.
Setting the hours
The monthly envelope gets set against the real backlog, not against a hope. If the backlog needs a project first, I say so instead of spreading it over six months of care.
Working rhythm
Requests go on the list, get estimated, get done in your order. Anything that turns out to be a project gets called a project and quoted separately.
Quarterly review
Once a quarter I look at what the hours bought, what keeps coming back and whether the envelope is the right size. Recurring requests usually point at a configuration fix worth doing once.
Hours get agreed after I go through the portal.
How many people work in the portal, what keeps changing in the company and what jams today. The rest I confirm on the call.
Let me hear about who looks after your portal today.
On the call I go through what is waiting in the portal, who raises requests and how fast the process changes. A work email address and a topic are enough to book it.
An audit day or a training day to start working together.
Both have a fixed scope and take one working day. I quote a larger project only once I know what is really in it.
HubSpot portal audit day
- Half an hour with leadership on the one number the company cares about
- A read-only pass through the portal
- Twenty minutes with each team member, up to four people
- A document with fixes priced in hours, plus an hour to walk through it
AI training day for your team
- Six blocks in one day
- Opening with leadership, 30 minutes
- Hands-on work with the model on your team's materials
- Recording and a starter kit for every role
Questions that come up on a first call.
How many hours a month do we need?
That comes out of the portal and the pace of change, not from a package. I look at the backlog and the number of teams working in the account and give you a number with the reasoning attached.
What if we do not use the hours in a given month?
Then I spend them on something that always waits: data hygiene, a report nobody had time to build, documentation. Unused hours are a signal the envelope is too big, and I say that rather than let it run.
Will you take over a portal another agency ran?
Yes, and the handover step exists for exactly that. Expect the first weeks to surface undocumented automation; that is normal and it is cheaper to find it deliberately than during an incident.
How is this different from an implementation project?
A project has a scope, an end and a go-live. Care is the work that arrives afterwards and never forms a project. Mixing the two is how implementations stretch for a year.
Who on our side raises requests?
One or two named people, ideally including whoever keeps the portal. A queue anybody can write to fills with requests nobody prioritised.
Does care cover work outside HubSpot?
Integrations touching HubSpot, yes. Wider process automation and AI work are separate lines, and I say up front when a request belongs there instead.
A portal after go-live generates work that never forms a project.
<p>Tell me what is waiting in your portal and who handles it now. After the call you have the size of the monthly envelope and the list it would start with.</p>