New Portals, Rescues, and Salesforce Integrations
B2B teams setting up HubSpot, or fixing it, usually in one of three situations:
- New HubSpot build: a net-new portal, often moving off Mailchimp, ActiveCampaign, or a basic Marketo setup
- HubSpot rescue: a live portal underperforming because the initial setup left the funnel half-configured
- HubSpot with Salesforce: connecting Marketing Hub to an existing Salesforce
The most common failure we inherit is misaligned lifecycle stages: marketing counts an MQL that sales ignores because the definition was never agreed. The fix is stages marketing and sales agree on before campaigns go out.
What We Build in HubSpot
Marketing Hub build
Forms, landing pages, email templates, workflows, lead scoring, smart content, and A/B testing, configured to your B2B funnel.
Lifecycle, lead status, and automation
Lifecycle stages, lead status, and deal pipelines mapped to your sales motion, with entry/exit criteria and the marketing-sales SLA defined first. Nurtures, routing, and handoffs built to stay maintainable.
Data migration and quality
Clean migration of contacts, companies, and deals from Marketo, Pardot, Salesforce, or a CSV source, deduped with opt-in status mapped. Data Hub and Breeze Intelligence keep the database clean.
Lead scoring
A scoring model with behavioral, demographic, and firmographic inputs, calibrated against your historical SQL conversion data.
Salesforce integration
Two-way HubSpot and Salesforce sync with field mapping, sync rules, and conflict resolution: the most common failure point in a HubSpot build, so we design it explicitly.
Reporting and attribution
Dashboards for funnel, pipeline contribution, and source. On Enterprise, we configure HubSpot's multi-touch attribution and agree the funnel definitions with you first.
When We Tell You Not to Use HubSpot
We run Marketo too, so we have no reason to push HubSpot when it's the wrong call:
- You rely on Salesforce Campaign influence reporting, which HubSpot doesn't sync to the way Marketo does
- Multi-region or multi-business-unit governance, where Marketo's workspace model is more mature
- Sophisticated revenue cycle modeling that Marketo handles natively
Full comparison in our Marketo vs HubSpot vs Pardot guide, or see Marketo consulting.
Get HubSpot Configured for Your Actual B2B Funnel
Most B2B portals we inherit arrive with default lifecycle stages, no scoring logic, and workflows built by whoever had time.
How a HubSpot Implementation Runs
Discovery call and a written SOW, then account setup (provisioning, domain authentication, tracking code), data migration and CRM architecture, the marketing build (forms, workflows, lead scoring, dashboards), and launch with a 2-week post-launch support window.
Proof: A Pardot to HubSpot Migration in Six Weeks
A $50M ARR cybersecurity company came to us off Pardot with 200+ programs and 12 integrations, and a marketing team that had shrunk to six people. We rebuilt the portal and migrated in 6 weeks with zero data loss.
After Launch: Keeping HubSpot Running
Most teams don't need an agency forever, and we don't build the dependency in. We hand over documentation and recorded training so your team can run and change the portal. When you want ongoing help, a retainer covers portal health, data quality, attribution, and new builds within an agreed budget. Pricing is scope-dependent: request a quote.
Why LeadFox for HubSpot
- B2B only: every architecture decision is made for B2B funnels and long sales cycles, not e-commerce or DTC
- Multi-platform: we run Marketo and Pardot too, so the recommendation on whether HubSpot fits is honest
- Salesforce depth: we've rebuilt broken HubSpot and Salesforce syncs from the ground up
Frequently Asked Questions
How long does a HubSpot implementation take, and what makes it run over?
Mid-market B2B Marketing Hub: 6-10 weeks. Basic Starter, no migration: 2-4 weeks. Enterprise multi-hub with custom objects and two-way Salesforce sync: 12-20 weeks. Overruns usually come from scope found mid-build: an unmapped integration, or a data model redesigned after data is already in.
What happens to our data when we migrate from Marketo or Pardot?
Contacts, companies, deals, properties, and opt-in status migrate cleanly with deduplication. We design the duplicate-handling rule before anything moves, because HubSpot enforces email uniqueness and a raw import merges records incorrectly. Full method on our Marketo to HubSpot migration service.
How much does a HubSpot implementation cost?
Scope-dependent: hubs and tier, data volume, integrations, whether a migration is in scope, and whether it's a rescue or a net-new build. We quote a fixed price after a scoping call. HubSpot's own license and onboarding fees are separate.
How do we know the senior person who scopes the work is the one who builds it?
Because that's the operating model. LeadFox is senior-only: no junior associates, no offshore pods, no account manager between you and the build. The practitioner on the scoping call configures your portal and is who you reach when something breaks.
We already bought HubSpot and onboarding left us stuck. Can you fix it?
Yes. That's a HubSpot rescue, one of our most common engagements. HubSpot's own onboarding is a guided coaching program: it walks your team through setup, but it doesn't migrate data, design lifecycle architecture, or build workflows for you. A rescue starts with an audit, then a prioritized rebuild.
How is a boutique different from a large HubSpot partner?
A large partner often staffs the pitch with a senior architect and the build with junior or offshore builders. Partner tier signals how much revenue an agency sources for HubSpot, not how well it will build your portal. Ask who specifically does the work.
When would you tell us not to use HubSpot?
Salesforce Campaign influence reporting, multi-region or multi-business-unit governance, and sophisticated revenue cycle modeling all still favor Marketo. See the section above for the reasoning. We run Marketo too, so the call isn't shaped by which platform we sell.
Do we need a HubSpot Solutions Partner?
Not required by HubSpot, but a Solutions Partner handles setup in place of HubSpot's templated onboarding and configures the portal to your B2B funnel rather than coaching your team through it. LeadFox is a HubSpot Solutions Partner. For mid-market and enterprise B2B, that's almost always worth it over a junior internal build.
Should we use HubSpot Smart CRM or keep Salesforce?
Keep Salesforce if you have substantial existing investment, custom objects, or enterprise sales-ops requirements HubSpot's CRM doesn't yet match. Move to HubSpot Smart CRM if your sales process is straightforward and you're under roughly $50M ARR. We model the trade-off in scoping.
What do we own at the end of the engagement?
Everything: the portal, the documentation, and recorded training, so your team can run and change the system without us. A retainer is available if you want ongoing help, but it's a choice, not a dependency we build in.
Talk Through Your HubSpot Build
A 30-minute scoping call. We review your goals, current portal, and timeline, then tell you whether we are a fit.