Platforms · HubSpot Development
We are a Vancouver studio that sets up HubSpot the way a sales team actually works: tidy records, pipelines that match your real process, automation you can read, and forms wired straight into the website. Request a quote.
You own the code and IP Weekly demos 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 is a full-stack technology studio in Vancouver, British Columbia that builds, repairs and migrates HubSpot portals.The work covers CRM setup and data hygiene, deal pipelines and lifecycle stages, marketing automation and workflows, forms and lead capture wired into the website, CMS Hub pages and themes, custom objects, reporting dashboards, and integrations with ERP and ad platforms. Migrations are planned so records arrive deduplicated and mapped to properties your team will actually use, rather than a copy of the mess you already had. Every engagement runs with one accountable team, a working demo every week, and full client ownership of code, data and accounts.
Key facts
HubSpot platform specialists
We structure companies, contacts, deals and tickets around how you actually sell, then clean what is already there: merge duplicates, retire unused properties, fix owner assignment and set validation rules so the data stays trustworthy.
Deal stages named after buyer behaviour rather than internal wishful thinking, with entry and exit criteria, required properties, rotting rules and lifecycle stage definitions that sales and marketing both sign off on before anything is switched on.
Workflows built to be read by a human six months later: clear naming, documented enrolment triggers, suppression lists and re-enrolment settings chosen deliberately. We test with sample records before anything touches a live contact list.
HubSpot forms embedded with the native script or posted through the Forms API from your own markup, with hidden fields for source and campaign, consent handling, accessible labels to WCAG 2.2 AA, and routing that gets each enquiry to the right owner fast.
Custom themes, modules and templates in HubL, landing pages and blog listings that match your brand, plus custom objects and associations for the parts of your business standard records do not cover, such as properties, courses, fleets or member records.
Dashboards that answer real questions about pipeline, attribution and campaign performance, backed by integrations with your website, ERP, ad platforms and finance systems so the numbers reconcile instead of quietly disagreeing across tools.
Process
Discovery
A working session with sales, marketing and service to learn how deals really move, what reporting leadership needs, and which systems must stay connected.
Portal blueprint
A written plan covering objects, properties, pipelines, lifecycle stages, workflows, integrations and permissions, agreed before any configuration begins.
Build and configure
Configuration, HubL theme and module work, forms, custom objects and dashboards, with a working demo every week so you see progress rather than status reports.
Migrate and test
Deduplicated data loaded in staged batches, starting with a pilot import. Workflows tested on sample records, forms tested end to end, associations verified.
Launch and hand over
Go-live with monitoring, a written portal map, recorded walkthroughs and role-specific training. You keep every credential, and we stay available for iteration.
How we work
We start by reading what is already there: objects, properties, active workflows, form submissions, integrations and permissions. You get a plain summary of what works, what is duplicated and what nobody has used in a year.
Pipelines and lifecycle stages are drawn from how your team really sells, not a template. Each stage gets a definition, an owner and the properties that must be filled before a deal can move forward.
Deduplication, field normalisation and property rationalisation happen before any migration or automation, so you are not building rules on top of records nobody trusts.
Short workflows with clear names and documented triggers beat one giant automation nobody dares edit. Suppression and re-enrolment settings are set on purpose, then tested on sample records.
Forms, tracking, chat and CMS pages are connected to the CRM properly, with consent and source data captured at the point of submission so attribution holds up later.
Dashboards are built around the questions leadership asks each month, then checked against the ERP and ad platforms so the same number means the same thing everywhere.
Who it's for
Multi-team portals where marketing, sales and service each need their own view without breaking each other's reporting. We handle permissions, teams, custom objects and the integrations that keep HubSpot aligned with the ERP.
Member and stakeholder records, renewal and event journeys, accessible forms built to WCAG 2.2 AA, and bilingual EN and FR communications, with clear documentation for procurement and internal audit.
Location-level pipelines, lead routing by territory, shared templates that head office controls and franchisees can use, plus roll-up dashboards that compare locations on the same definitions.
A first HubSpot portal built to grow into: sensible properties, a pipeline that matches your actual sales motion, forms on the website from day one, and no automation you cannot explain to a new hire.
1 day
Reply to every enquiry
Weekly
Working demo cadence
2014
Building software since
FAQ
We work across Marketing Hub, Sales Hub, Service Hub, Operations Hub and CMS Hub, now marketed as Content Hub, from Starter through Enterprise tiers. Some features, custom objects among them, are limited to higher tiers, current at the time of writing, so we confirm what your portal actually includes before designing anything around it.
Yes. We audit the source system first, agree the object and property mapping, dedupe and normalise the export, then load in staged batches with a small pilot import ahead of the full run. Associations, record owners, historical activity and open deals are checked after each batch so nothing lands orphaned or silently overwritten.
Duplicates usually come from unmanaged imports and forms that create records from partial data. We standardise on email and company domain as matching keys, set import rules, use HubSpot's duplicate management tools, and audit properties on a schedule so anything with no owner, no report and no workflow behind it is archived rather than left to rot.
We make no claim to partner status, certification or awards with HubSpot. We are an independent studio working inside your own portal, under seats you control. You own the code, the themes, the workflows, the data and every account we touch, both during the project and after it ends, with no lock-in to us.
Yes. Forms can be embedded with HubSpot's script, or you can keep your own markup and submit through the Forms API so styling, validation and accessibility stay under your control. Either way we pass source, campaign and consent fields through, then confirm each submission reaches the right record and the right owner.
Only if there is a reason to. CMS Hub, now Content Hub, suits teams who need to publish personalised pages against CRM data without waiting on a developer. If your site already performs well on WordPress or a custom stack, we usually keep it and integrate tightly rather than rebuild it for its own sake.
Always. Every build ships with a written portal map covering objects, properties, pipelines, workflows and integrations, plus recorded walkthroughs for the people using it daily. We run live sessions for sales, marketing and service separately, because each team needs a different half of the system explained.
Let’s connect
Tell us what you’re building. We’ll reply within one business day with next steps and a tailored quote — no obligation.