Quote 01
We run the whole revenue motion on spreadsheets and Gmail.
Pattern · no system of record · pre-CRM operator
Foundation · HubSpot · 6 Hubs
Move onto HubSpot once. Set it up around how you actually sell
HubSpot is one customer-record platform built in six parts, called Hubs: marketing, sales, customer support, website, automation, and payments. This service is for companies moving onto it from spreadsheets, a fragmented stack, or another CRM.
You get it set up around how your business actually sells, so it still holds up five years in.
You leave with a short written plan: what to decide first, the risks to watch before any data moves. You keep it either way. No obligation.
Certified across all 6 Hubs
1–2 week Revenue System Audit
100% audit credit toward build
HubSpot Gold Solutions Partner
You have probably said most of these out loud this quarter.
You might be consolidating a dozen GTM tools, replacing a CRM that no longer fits, or buying your first system of record. The symptoms rhyme either way.
Quote 02
We have 14 tools in the GTM stack and three of them claim to be the source of truth.
Pattern · stack fragmentation · three sources of truth
Quote 03
Salesforce was over-built for us. The operating cost is killing us.
Pattern · platform overbuild · CRM migration
Quote 04
Nobody can give the board one straight number.
Pattern · reporting drift · board-level visibility gap
3+If three or more of these land, you are in the right place. The next section names why this keeps happening, and what to decide before any data moves.
How it works
From subscription to the same mess in 18 months.
Most teams scope a CRM move by comparing platforms. The harder question — and the one that decides whether the move pays off — is how your business actually sells. That decision gets made, implicitly or explicitly, in the first three weeks. Here are the three options most teams try first, and why each one comes up short.
01
Doesn't fitBig-4 firm proposes a $2M digital transformation.
The tag exists because their pricing model assumes the migration is a custom build, which HubSpot is not. You pay for a slide deck and a 14-person roster, none of whom have shipped on HubSpot before. Procurement gets a TCO they can't defend, and the CRO can't tell you what ships in Q1.
Sticker price$2,000,000
Time to first shipped value12 months
02
Takes too longHire a senior RevOps lead to carry the architecture.
It is the right hire eventually. A senior RevOps person could carry the whole structure in their head. The problem is recruiting: the role takes nine months to fill at this seniority, and the migration is the work they are supposed to do after they land. So nothing moves until then.
Time to fill the role~9 months
Status of the migrationblocked
03
Wrong shapeHand it to a $50M HubSpot agency on hourly billing.
They will start. They will configure. But they will not produce the procurement-grade artifacts a $500M-to-$2B board needs before any data moves. No 30-50 page Blueprint. No named architect on the call. No defensible scope when the work creeps. The portal lights up, and a year later it breaks the same way Salesforce did.
Procurement artifactNone
Same mess by year twoYes
Six Hubs. The one decision each one forces.
HubSpot is one platform in six parts, called Hubs. Most companies start with one or two — usually Marketing and Sales — and add the rest as they grow. You do not need all six on day one. Pick the Hub that solves your worst problem this quarter. We sequence the rest.
01Marketing Hub
Marketing Hub
Runs your email, landing pages, lead capture, and campaigns. Where the marketing team lives day to day.
FromMailchimp · Marketo · Pardot · ActiveCampaign · nothing at all
The one decision it forces
When does a lead count as ready for sales, and how does it hand over cleanly?
You leave with
A working Marketing Hub, contacts moved over, and a clear way to prove which campaigns drive revenue.
02 · Most commonSales Hub
Sales Hub
The core CRM. Holds contacts, companies, deals, your pipeline, and forecasting. The central record sales, marketing, and support all work from.
FromPipedrive · Zoho · Salesforce · another CRM · no CRM at all
The one decision it forces
One pipeline for the whole company, or several split by how you sell?
You leave with
A working Sales Hub, deals and history moved over, a pipeline built around how you actually sell. Coming from Salesforce? Process Builder, Flow, and Apex rebuilt as HubSpot Workflows + Operations Hub actions, history intact.
03Service Hub
Service Hub
Runs customer support: tickets, a help center, response-time targets, and satisfaction surveys.
FromZendesk · Freshdesk · Intercom · Help Scout · nothing at all
The one decision it forces
How does a customer's health reach the renewal deal?
You leave with
A working Service Hub, tickets and help articles moved over, and routing in place — so your renewal forecast stops being a guess.
04Content Hub
Content Hub
Your website and blog, built on the same platform as the CRM. Pages, forms, blog posts, and SEO live here.
FromWordPress · Webflow · Squarespace · Drupal · legacy CMS Hub
The one decision it forces
Which page edits can marketing make on their own, and which still need a developer?
You leave with
Your site moved over, search rankings protected through the switch, and pages set up to be found by both Google and AI search. For a full rebuild, see HubCrafted.
05Operations Hub
Operations Hub
Keeps your data clean and your tools connected, and is where the heavier automation lives. (If you searched for "Data Hub," this is it.)
FromZapier · Workato · Make · custom scripts · MuleSoft
The one decision it forces
Which connections HubSpot handles itself, which need custom code, which need a connector tool?
You leave with
Tools connected, automations documented, and data-cleanliness rules in place — so "where did this number come from" meetings stop happening.
06Commerce Hub
Commerce Hub
Handles quotes, invoices, payments, and subscriptions, tied straight to your deals.
FromStripe · Chargebee · Recurly · Zuora · QuickBooks
The one decision it forces
What HubSpot handles end-to-end, and what hands off to your finance system?
You leave with
Quoting, invoicing, and payments working inside HubSpot, payment history moved over — and your books match the CRM.
Pick the Hub that solves your worst problem this quarter. We sequence the rest. Two Hubs live by month three is the realistic milestone — not all six in a big-bang cutover. See the full methodology for how the sequence gets decided.
Four levels of commitment. Public.
Start with the free 30-minute setup diagnostic. Move to the paid Revenue System Audit when you want a procurement-grade scope. The audit fee credits 100% toward Build or Architect within 12 months. Public pricing is on this page because most HubSpot partners hide it.
Discovery Call
Free/ 30 min
No obligation · written plan
A call with a named architect. You leave with a short written plan of what to decide first, and the risks to watch before any data moves.
- Same-week scheduling
- Short written plan
- You keep it either way
- No deck, no sales pressure
Revenue System Audit
$129one-time
1–2 weeks · Discover phase
A procurement-grade scope document with six architectural decisions named. 100% creditable toward Architect within 12 months.
- Source-system inventory
- Six decisions named
- Integration map
- Top three migration risks
- Lifecycle / pipeline audit
100% credit toward Architect
Build
From $1,000
Single Hub · 3–6 weeks
A single-Hub migration with a fixed scope. For teams who know which one Hub they need. Applies to existing HubSpot customers.
- 1 Hub migrated (your choice of six)
- Source-system data audit + cutover plan
- Integration map (up to 3 systems)
- 2-week post-cutover hypercare
Architect
From $3,000
Multi-Hub · 2–4 months
End-to-end multi-Hub Build with the full Focal Method. The default when you are moving onto HubSpot from a fragmented stack.
- Up to 6 Hubs sequenced across phases
- Architect Blueprint as a procurement artifact
- Named Revenue Architect + per-Hub specialists
- Full Discover → Architect → Engineer → Operate → Optimize
- Integration map across 10+ source systems
- 30-day hypercare + 90-day strategic review
Audit fee credits 100%
Need a custom quote? Request detailed pricing →
The Focal Method, mapped to a HubSpot move.
Every project runs through the same five phases. The first two decide how HubSpot is set up before any data moves; the build comes after. Each phase has a named owner and a named artifact.
- 01
Discover1–2 weeks
Paid Revenue System Audit. Source-system inventory, top three risks, integration map. 15-page deliverable. 100% credits toward Architect.
- 02
Architect4–6 weeks
The Blueprint. 30 to 50 pages naming every property, workflow, integration point, and cutover risk before any data moves.
- 03
Engineer2–6 months
The build. Hub-by-Hub configuration, data migration with full history, integrations, lifecycle workflows. Two Hubs live by month three.
- 04
OperateMonths 4–12
Hypercare and adoption. Same engineering team that built the portal stays on the same Slack, same SLA. 30-day hypercare + 90-day review.
- 05
OptimizeMonth 12+
Run-tier handoff. HubSpot SEO + AEO is the default. Same named architect available for quarterly review.
Buy each phase for what it is, not what it pretends to be.
Discover is not a sales call dressed up, it is a audit that ships an artifact. Architect is not "more discovery", it is the document procurement signs against. Engineer is not "configure HubSpot and hope". it is hub-by-hub work against the Blueprint. Operate is not hypercare forever, it is a named handoff window. Optimize is not the same agency running quarterly check-ins, it is a named Run-tier service with its own cadence.
We name anti-scope in writing, because procurement appreciates it.
If your scope falls outside this list, we will tell you in the Discover phase and refer you out. Better to say no now than to ship a portal that fights your operating model in year two.
Starter tier only
HubSpot Starter does not require a partner. For a free portal stand-up, book HubSpot's own onboarding directly.
Configuration-only without Discover
We will not commit to architecture decisions sight unseen. The Discover phase is non-optional. It is what makes the rest defensible.
Free or Starter without an upgrade path
The work we do assumes a Pro or Enterprise portal. If you are on Free or Starter, we will tell you whether to upgrade before we engage.
Consumer-CRM migration (Streak, Folk, Sales free)
Different stack, different buyer. Migrating off the HubSpot Sales free Chrome extension to a real CRM is not our shape of engagement.
Commission tooling (Spiff, CaptivateIQ, Performio)
That is an Operations Hub scope at the portal-wide level — a different engagement, not a HubSpot-onboarding scope.
Adoption guarantees tied to people decisions
We deliver the system. Your leadership owns adoption. We will not guarantee outcomes that depend on hiring, firing, or reorgs we do not control.
We tell you what we are not so you can spot the agencies that will say yes to anything: the position-1 promisers, the link-buying farms, the LLM content mills.
Why GiantFocal
HubSpot Gold Solutions Partner, certified across all six Hubs.
We work alongside HubSpot, not at the same layer as its own services team. Our HubSpot marketplace products (Hatch, Atomic, and March) have been installed 33,000x.
6/6
Hub certifications. Marketing, Sales, Service, Content, Operations, Commerce.
10+ yrs
On the HubSpot Marketplace. Three productized apps: Hatch, Atomic, March.
33,000+
Active app users. Across 50+ countries on our HubSpot marketplace apps.
Gold
HubSpot Solutions Partner. Active pathway to Platinum. #1 Solutions Partner in Indonesia.
We use HubSpot for our own company for over 10 years.
How much does HubSpot onboarding cost?
Four levels of commitment. The 30-minute setup diagnostic is free. The Revenue System Audit is $129 for a 1-to-2 week procurement-grade scope; 100% credits toward Build or Architect within 12 months. Build starts at $1k+ for a single-Hub migration with a fixed scope, 6-10 weeks. Architect is $3k+ for end-to-end multi-Hub Build over 4-9 months. Public pricing on this page because most HubSpot partners hide it.
What is a HubSpot onboarding partner, and why use one?
HubSpot's own services team is excellent for portal stand-up and Hub-by-Hub configuration. Multi-Hub migrations are a different shape of engagement: cross-Hub sequencing, source-system rebuilds, lifecycle redesign, and the procurement-grade Blueprint artifact. HubSpot routes those engagements to Solutions Partners by design. As a Gold Solutions Partner certified across all six Hubs, we operate the layer between HubSpot's services team and your internal RevOps function.
How do we migrate from Salesforce to HubSpot?
Salesforce-to-HubSpot is the most common Architect engagement. The work: replatform the pipeline around HubSpot's lifecycle (not Salesforce stages), migrate accounts / contacts / opportunities with full historical activity, rebuild custom objects natively (without Apex), rewire integrations through Operations Hub, and migrate the forecasting model so it ties to the CRO's revenue commit on day one. Process Builder, Flow, and Apex automations get rebuilt as HubSpot Workflows + Operations Hub custom-coded actions. Two-way Salesforce-HubSpot data sync runs during the transition window so the pipeline never goes dark.
What if our data lives in spreadsheets and Gmail?
You are buying your first system of record. The work is different from a CRM migration: there is no source schema to absorb, but there is a tacit operating model living in people's heads and in shared sheets. The Discover phase makes that operating model explicit before we build. We map who-owns-what, how a lead becomes a deal, what counts as a closed-won, and where the handoff between marketing and sales actually lives. Then we build HubSpot around that, not around someone else's defaults.
What's the difference between HubSpot onboarding, implementation, and migration?
Onboarding is the HubSpot-provided service that gets a new portal stood up, you can book that directly with HubSpot. Implementation is the configuration of a portal you have already purchased, usually one Hub at a time. Migration is the rebuild of an existing GTM stack onto HubSpot as the system of record, across one or more Hubs, with data, integrations, and the operating model redesigned around HubSpot's lifecycle. This page covers all three: they describe different starting points, but the work converges on the same Foundation engagement.
How long does HubSpot onboarding take?
Discover: 1 to 2 weeks. Architect: 4 to 6 weeks. Engineer: 2 to 6 months depending on Hub count and source-system complexity. Two Hubs live by month three is the realistic milestone for an Architect engagement. Big-bang multi-Hub cutovers are rare and we discourage them. Sequencing reduces cutover risk and gives the team room to absorb the new operating model. Single-Hub Builds run 6-10 weeks.
07Get started
Start with the 30-minute setup diagnostic.
A 30-minute call with a named architect. You leave with a short written plan of what to decide first, and the risks to watch before any data moves. You keep it either way. No obligation.
Request pricingWritten response · one business day
Or, before you commitSee the Focal Method →