Objects, properties and associations
Decides what a contact, company, deal, ticket and custom object mean in your business, then names, types and prunes properties and property groups so two reports stop disagreeing.
Fractional Teammates · CRM & Systems
Your portal gets objects, workflows, lifecycle stages and dashboards that hold up under scrutiny. A HubSpot specialist from our Vancouver studio works a set share of each week in your tools, your standups and your reporting.
A senior specialist, not a junior placement You own the work and the accounts Reply within one business day
Agent running - queue empty
Flow 04
01
Trigger
Webhook
02
Enrich
Normalise
03
Decide
Policy
04
Act
Resolve
Run log
> Matched 42 records
> Routed 7 exceptions to a human
> Closed 35 tickets automatically
35
Auto-resolved today
6h
Engineer time saved daily
OlDevs runs one client's HubSpot portal with a senior specialist who works a defined share of each week, on an ongoing basis.The work is portal administration and design: modelling contacts, companies, deals and custom objects, naming and pruning properties, building workflows, sequences and forms, defining lifecycle stages and the evidence that moves a record between them, connecting HubSpot to the website, billing and support systems, and building dashboards whose numbers survive a conversation with finance. They work in your portal, your standups and your reporting, never in an agency portal of ours. You keep the portal, the data and every integration.
Key facts
CRM & Systems
What this teammate takes off your plate
Decides what a contact, company, deal, ticket and custom object mean in your business, then names, types and prunes properties and property groups so two reports stop disagreeing.
Custom objects · Properties · Associations · Property groups · Deduplication
Sets lifecycle stage, lead status and deal stages against evidence rather than opinion, and writes down who moves a record, when, and what sales is entitled to expect when they receive it.
Lifecycle stages · Lead status · Deal pipelines · MQL rules · Handover
Builds routing, task creation, internal alerts, sales sequences and data-hygiene workflows, then retires the ones nobody can explain and labels what each surviving workflow is for.
Workflows · Sequences · Routing · Task automation · Data hygiene
Rebuilds forms and landing pages so submissions arrive with clean source data, tracking behaves the same across the site, and subscription types and consent are recorded properly. Forms meet WCAG 2.2 AA.
Forms · Landing pages · Source tracking · Consent · Subscription types
Native apps, field mapping and sync direction set up and watched, with the errors that fail quietly surfaced. Heavier custom builds go to the studio's integration engineers rather than to one admin.
Native apps · Field mapping · Sync direction · Error monitoring · Escalation
Builds reporting for sales, marketing and the board, then checks the revenue figures against the finance system. Where the two disagree, the reason is written down and fixed at source.
Dashboards · Attribution · Revenue reporting · Reconciliation · Board reporting
Benefits
Merging pipelines, renaming properties and changing association labels are decisions the whole portal lives with afterwards. They are made by someone who has watched those choices age badly in other portals, and knows which ones cannot be undone.
Property naming rules, why each workflow exists and what every lifecycle stage means are written into your own HubSpot account and your own documentation. Whoever holds the super admin seat next inherits the reasoning, not just the login.
Lists are built from properties that mean what they say, and suppression is set deliberately rather than inherited, so the audience a send reaches is the one marketing chose. Mistakes surface before the send, not in the replies.
Marketing and sales read the same lifecycle stage the same way, so a contact arriving in a rep's queue carries a meaning nobody relitigates on Monday. Both teams stop keeping private counts of the same people.
Deal stages, close dates and amounts in HubSpot are maintained well enough to quote out loud, so the leadership dashboard is the number rather than a starting point somebody re-checks in a spreadsheet first.
Changing enrolment criteria stops being the job nobody volunteers for, because it is clear which workflows send customer-facing email and what re-enrolment will do. The portal behaves the way your team believes it behaves.
How it works
A portal review before the quote
We look through objects, properties, workflows, integrations, permissions and the reporting that nobody trusts. You get the findings written up whether or not you go ahead.
Seats you create, super admin you keep
They join your portal, chat and project tracker under named accounts you control. Super admin stays with your team, and access can be revoked in a minute without asking us.
Corrective work first
The opening weeks fix what is misreporting, retire dead workflows and document what exists. Structure comes later, because rebuilding on top of bad definitions only moves the problem.
Structural changes behind a staging step
Object and lifecycle changes are trialled in a sandbox where the licence allows one, released on a schedule your team knows about, and never on a Friday afternoon.
A weekly walkthrough in the live portal
Not a slide deck. You see the actual records, workflows and dashboards that changed, what each fixed and what is queued, with written notes for whoever missed the call.
Who it's for
HubSpot rewards steady attention more than it rewards bursts of it. These are the situations where a set share of a senior week does more than another project would.
Configured during onboarding, drifted ever since. Nobody owns the portal, the reports are quietly distrusted, and the parts of the platform that would help most are the parts nobody has switched on.
You know what the portal should do and you are the one clicking it together after hours. The specialist takes administration off you and leaves the strategy where it belongs.
Membership records, renewal reminders and committee communications all in HubSpot, with a small staff and a board that expects the same figures every quarter.
Closed-won in the portal does not match what accounting recognises, and each department defends its own version. Somebody senior has to reconcile the definitions before the reporting means anything.
12+
Years of studio experience since 2014
Half
Typical commitment — Half to 1 day a week
EN/FR
Languages this engagement can be delivered in
Other fractional roles
A senior specialist from OlDevs owns your CRM for an agreed share of each week: the data model, pipeline stages, lifecycle automation, routing and reporting.
Explore02A senior integration specialist from our Vancouver studio joins your team part-time, in your repositories and your standups.
Explore03One senior specialist owns your GA4 and server-side tracking, the event design underneath it, and the experiment programme that tests pages, forms and funnels.
ExploreFAQ
Yours, always. The portal is your account under your billing, and we work in it through named seats you create and can revoke in a minute. Workflows, custom objects, dashboards, integration keys and documentation all live in your HubSpot and your document store, not ours. There is no studio copy of your data, and nothing has to be rebuilt for you to carry on without us.
You deal with the person doing the work, not a service desk, and the work happens in your standups rather than behind a ticket queue. OlDevs is a studio, so the specialist is one of our own team rather than someone sourced for your job. The honest trade-off is hours: you get a defined share of a senior week, not all of it, and urgent things queue behind the schedule.
When you are implementing HubSpot from scratch or migrating into it, that is a project with an end, and we would quote it as one. When someone is needed in every meeting and every inbox, that is a job, not a share of a week. And when nobody internally can decide what a qualified lead is, the portal is not your first problem.
To reconcile HubSpot with finance, yes, and it is arranged on your terms. We agree in advance what can be read, in which environment, and who approves changes to production syncs. Field mapping, sync direction and error handling are documented as they are built. Credentials stay in your vault; we never ask for a shared login. Anything touching revenue records goes past your finance owner first.
The studio answers. Cover is the difference between a fractional teammate and a lone contractor: someone else here has access to your portal documentation and picks up anything urgent, and you still hear back within one business day. Routine work waits for the specialist, because context matters more than speed when you are changing a live portal. Planned absence is flagged in the demo well ahead.
Sooner than a rebuild, but not in a fortnight, and we will not put a date on it. The first weeks go on finding why the numbers disagree: duplicate records, properties written by three different workflows, deals closed in the wrong pipeline. Causes are fixed in the order your board reads them, so a few dashboards become reliable early and the rest follow.
Let’s connect
Tell us what is not getting done and roughly how much of a week it needs. We’ll reply within one business day with who would cover it and a tailored quote — no obligation.
Thanks — we’ll reply within one business day.