What you get
HubSpot CMS websites
Custom themes and flexible modules that let marketing teams publish without a developer bottleneck.
A useful CRM setup
Contacts, companies and deals configured around the way your sales process actually works.
Marketing automation
Forms, lead scoring and email workflows connected to timely, useful follow-up.
CMS
HubSpot CMS: websites marketing teams can actually edit
Most websites are built for developers, not marketers. When your team needs to launch a campaign landing page, update pricing, or swap hero copy, they shouldn't have to file a ticket and wait. HubSpot CMS puts content editing in the hands of the people who need it most: your marketing team. I build custom themes with drag-and-drop modules that let non-technical users build pages, update copy, and manage forms without touching code or breaking the design system.
Every HubSpot CMS site I build starts with a design system: consistent spacing, typography, and colour tokens baked into the theme so any page your team builds looks on-brand by default. Modules are self-contained: testimonials, pricing tables, hero sections, and CTAs that marketing can combine into landing pages without a developer. The result is a website that stays current because the people who need to update it actually can.
For teams that need more design flexibility than HubSpot CMS offers, I also build on Webflow. See the Webflow developer overview for a comparison of both platforms and which suits your workflow.
CRM
HubSpot CRM: set up for how you actually sell
Out of the box, HubSpot CRM gives you a generic sales pipeline that fits nobody's actual process. Your team has a way they sell: stages that make sense for your deal size and sales cycle, properties that capture the data your leadership needs in forecasting meetings, and automations that reduce manual data entry so reps spend time selling, not clicking.
I start every CRM engagement with an audit of your current setup, whether you're on HubSpot already or migrating from another platform. What pipelines exist? What properties are being used, and which ones are dead weight? Where are deals stalling, and does the CRM surface that to management? The audit produces a configuration plan: custom deal stages, required properties per stage, views and dashboards that answer the questions your team actually asks, and automation rules that enforce data quality without annoying your reps.
A well-configured CRM feeds your conversion data: which sources produce the highest-value deals, which pages convert visitors into qualified contacts. For the full picture, see conversion optimisation and my practical HubSpot and Chili Piper lead-flow teardown.
Automation
Marketing automation: workflows, sequences, and lead scoring
The difference between a CRM your team uses and one they ignore is automation. HubSpot workflows can handle lead routing, deal stage progression, task creation, and internal notifications; but only if they're built around your actual process. I design automation that maps to your team's workflow: when a contact fills out a specific form, they enter a nurture sequence. When a deal reaches a certain value, the right manager gets an alert. When a lead score crosses a threshold, the contact moves from marketing to sales.
Lead scoring is where most HubSpot setups fall short. The default scoring model is generic: page views and email opens. I build scoring models that weight actions based on your actual conversion data: which pages correlate with closed-won deals, which email clicks precede sales conversations, which form submissions signal buying intent versus tire-kicking. The scoring model is a hypothesis; I revisit it quarterly against actual conversion data and tune the weights.
For automation that spans beyond HubSpot, connecting your CRM to external tools and databases, see Airtable + Webflow integrations for how structured data layers feed both your website and your CRM.
Migration
Moving to HubSpot from another CRM or CMS
Migrating CRM data is where most projects go wrong. Salesforce to HubSpot, Pipedrive to HubSpot, or even spreadsheets to HubSpot: the data structures don't match, fields don't map one-to-one, and associations between contacts, companies, and deals break if you don't handle them carefully. I run structured migrations: field mapping first, then a test import to a sandbox, validation against your source data, and only then the production migration.
Website migrations to HubSpot CMS follow the same discipline. I map every URL from your old site to its new HubSpot equivalent, set up 301 redirects so you don't lose SEO equity, and validate that all forms, CTAs, and tracking codes work on the new platform before the DNS cutover. A migration is a process, not an event; I plan for a phased rollout where high-traffic pages move first and get validated before the long tail follows.
For the full website migration methodology, including SEO preservation and redirect mapping, see website migration.
CRM and CMS that work together
- Audit your current setupWhether you are on HubSpot already or migrating from another platform, I audit your CRM pipelines, CMS templates, automation workflows, and data structure. You get a ranked list: what is working, what is broken, and what to fix first.
- Build and configureCustom CMS themes and modules. CRM pipelines, properties, and views configured to your sales process. Automation workflows, lead scoring, and dashboards that answer real business questions. Everything built and tested in a sandbox before go-live.
- Train and launchLive training sessions tailored to your team, not generic HubSpot Academy videos. Written documentation that maps HubSpot features to your specific workflows. Phased rollout with validation at each step so nothing breaks on launch day.
Tell me what you need to build or improve.
Share the goal, the problem and what you already have. I will suggest a practical next step.