Four moves, no theatre.
The HubStack process is deliberately small: four phases, weekly reviews, and a real handover at the end.
How the HubStack HubSpot process works
Every HubStack engagement — a single HubSpot landing page from $150+ or a full CMS Hub website from $600+ — runs through the same four phases. The scope changes; the rhythm does not. You always know which phase you are in, what is due next and who owns it.
Discover
Two weeks of strategy, audits and direction. We stress-test the brief, meet the team and build a shared roadmap.
Design
Bespoke interfaces iterated in the open. Weekly live reviews in Figma — you see the work as it forms, not at the end.
Build
Edge-deployed, accessible, fast by default. Semantic HTML, schema markup and Core Web Vitals in the green from day one.
Grow
Analytics, SEO and iteration after launch. Optional maintenance retainer so the site keeps up with the business.
What you get in each phase
Phases end with something you can review, not a status update. These are the artefacts that leave each stage of a HubSpot project.
Written scope & roadmap
Goals, page inventory, HubSpot template plan, CRM requirements and success measures agreed in writing before design starts.
Design system in Figma
Wireframes, then a full visual system — type scale, colour, components and page layouts — reviewed live each week.
HubSpot build in your portal
Theme, templates and editor-friendly drag-and-drop modules built directly in HubSpot CMS, with forms wired to CRM properties.
QA & launch pack
Cross-browser and mobile checks, form and workflow submission tests, redirect verification, accessibility pass and Core Web Vitals measurement.
Handover documentation
A walkthrough call, short Loom library and module documentation so your marketers can publish without a developer.
Post-launch care
30 days of fixes and tuning included, with optional monthly HubSpot support afterwards.
Timelines and pricing context
HubStack scopes and quotes before work starts, so there are no hourly surprises. HubSpot landing pages start from $150+ and go live in 3 days to 2 weeks. Theme customization starts from $300+ over 1–2 weeks. Migrations onto HubSpot CMS start from $500+ and typically run 2–4 weeks. Full HubSpot website builds start from $600+ across 3–8 weeks. Larger multi-template programmes are quoted per engagement and top out around $3,000. Ongoing HubSpot support and maintenance is billed monthly so capacity is predictable.
Two things move a timeline: content readiness and approval speed. When copy, imagery and CRM decisions are ready at kickoff, projects land at the fast end of the range. When they are not, HubStack flags the impact in the weekly review instead of at the end.
- Weekly 30-minute review call
- Two structured revision rounds per milestone
- One shared channel, one point of contact
- 30 days of post-launch care included
- Full ownership of everything built
A worked example
A B2B firm arrives on a dated WordPress site with a half-configured HubSpot portal. Week one is discovery: portal audit, page inventory, redirect map and a written scope. Weeks two and three are design — wireframes then a visual system, reviewed live. Weeks four to six are build: HubSpot theme, custom drag-and-drop modules, blog templates, forms mapped to CRM properties, and a redirect sheet loaded into HubSpot. Week seven is QA and launch: cross-browser checks, form and workflow tests, Core Web Vitals measurement and redirect verification. Week eight onwards is growth — indexing checks, schema, and iteration on the pages that matter. You can read the same pattern in detail in our HubSpot case studies or on the HubSpot services pages.
Working with HubStack — how it flows
How long does a HubStack project take?
Landing pages ship in 1–3 weeks. Full websites take 4–8 weeks. Migrations and redesigns are 2–10 weeks depending on scope.
How does HubStack communicate during a project?
One shared Slack or Notion channel, a weekly 30-minute call, and asynchronous Loom updates whenever a milestone lands.
Do I own the code HubStack writes?
Yes. All code, design files and content are transferred to you at launch with a written handover.
What if I need changes after launch?
Every HubStack project includes 30 days of post-launch care. Beyond that, our Maintenance & Support retainer covers ongoing updates.
How does the HubStack process start?
With a short discovery call and a written scope. HubStack confirms goals, HubSpot setup, page inventory and success measures before any design work begins.
Who is involved from my side?
One decision-maker and, ideally, whoever owns marketing content. Fewer approvers means faster reviews and fewer rounds.
How many revision rounds are included?
Two structured rounds per milestone — design and build. Because reviews happen weekly, most feedback lands long before the formal round.
Does HubStack work in HubSpot or elsewhere?
Design happens in Figma; the build happens directly in HubSpot CMS using templates, themes and custom drag-and-drop modules your team can edit.
How do you handle QA before launch?
Cross-browser and mobile checks, form and CRM submission tests, redirect verification, accessibility passes and Core Web Vitals measurement on the staging domain.
What does the handover include?
A walkthrough call, a short Loom library, template and module documentation, and full ownership of everything built inside your HubSpot portal.
How do you keep projects on schedule?
Fixed scope, weekly milestones and a single shared channel. If content or feedback slips, HubStack flags the timeline impact immediately rather than at the end.