HubSpot Isn’t the Strategy: How to Build a Revenue Engine Before You Automate It

It usually starts with a legitimate pain point. Leads are falling through the cracks. The sales team doesn’t know which contacts marketing has already touched. Campaign reporting is inconsistent because data lives in four different places. The instinct — reasonable on its surface — is that a better platform will fix the coordination problem.

Having worked inside HubSpot implementations as both a marketing team leader and a consulting partner, I’ve watched this logic play out in organizations across industries and growth stages. The pattern is consistent: a company invests in the platform, spends significant time on onboarding and configuration, launches their first workflows, and then discovers that the tool has faithfully automated every broken process they already had.

HubSpot does exactly what it’s configured to do. If the lifecycle stage definitions are vague, automation will move contacts through them vaguely and at scale. If the handoff from marketing to sales isn’t clearly defined, automation will execute that undefined handoff thousands of times per month. If the data going in is inconsistent, the reports coming out will be consistently wrong.

This isn’t a HubSpot problem. It’s a strategy-before-tool problem that applies to any platform, and solving it requires thinking about marketing automation as a fourth-field strategic decision rather than a first-field technical checklist.¹

A revenue engine is the end-to-end system through which a company identifies, attracts, engages, converts, and retains customers…and crucially, the shared understanding across marketing, sales, and customer success of how that system is supposed to work.

Most companies have a revenue process. Far fewer have a revenue engine. The difference is documentation, agreement, and measurability. A revenue engine answers the following questions with enough precision that two people in different departments, asked independently, would give compatible answers:

If those questions don’t have clear, agreed answers, you don’t yet have a revenue engine. You have a revenue hope. And automating a hope produces automated disappointment.²

One of the unintended benefits of a HubSpot implementation…when it’s approached honestly…is that the configuration process forces teams to articulate decisions they’ve been making informally or inconsistently. Building a lifecycle stage workflow requires defining what each stage means. Building a deal pipeline requires agreeing on what constitutes a sales-qualified opportunity. Building a lead scoring model requires answering, explicitly, what signals actually predict a buyer’s readiness.

These are not HubSpot questions. They are strategy questions. The platform surfaces them because it cannot proceed without answers; in doing so, it often makes visible the disagreements that were previously invisible because no one had been forced to put them in writing.

The companies that get the most from HubSpot are the ones that treat the configuration process as a strategy conversation. The implementation meeting isn’t a technical session, it’s a cross-functional alignment session that happens to produce a platform configuration as its artifact.

The pre-implementation work that most companies skip, and that a Fractional CMO or RevOps consultant should drive before anyone touches the platform, falls into five areas:

Define each stage — Subscriber, Lead, Marketing Qualified Lead, Sales Qualified Lead, Opportunity, Customer, Evangelist — in behavioral terms, not aspirational ones. ‘MQL’ should be defined by what a contact has done (specific pages visited, content downloaded, forms submitted, engagement score threshold) not by what marketing hopes they represent. Sales needs to agree that the definition produces contacts they want to talk to. If they don’t, change the definition before you build the automation.

What happens the moment a contact reaches MQL status? Who gets notified, through what channel, with what information attached? What is the expected sales response time? What happens if the contact doesn’t engage with the sales outreach? What happens to the contact in the system if the deal doesn’t close? Every one of these questions has an answer that needs to be agreed before any sequence, task, or notification gets built in the platform.

First-touch, last-touch, linear, time-decay, position-based — the choice of attribution model is less important than the fact that leadership has agreed on one and will actually use it to make decisions. An attribution model that no one trusts is just noise. Build the one that most closely reflects how the leadership team already thinks about marketing’s contribution to revenue, document it, and review it quarterly.

HubSpot’s reporting is only as trustworthy as the data it’s built on. Before migration or integration, audit the data that will flow into the system: duplicates, incomplete records, inconsistent naming conventions, contacts that belong to no company, deals that belong to no contact. Define the standards that will govern new data going forward, and build the automation to enforce them rather than relying on manual compliance.

Define, before launch, what success looks like at 30, 60, and 90 days — and make sure those measures connect to business outcomes, not just platform activity. ‘We sent 10,000 emails’ is a platform metric. ‘Marketing-sourced pipeline increased by 18 percent’ is a business metric. The platform produces both; leadership should care about the second one.

Rosenzweig’s framework for categorizing strategic decisions is useful here. HubSpot implementation decisions are not first-field decisions — the kind where you select among fixed options and success is absolute. They are fourth-field decisions: you can influence the outcome significantly through the quality of your process design, and your results will be measured relative to what your competitors are doing with similar tools.¹

That means the instincts useful for first-field decisions — careful option comparison, bias minimization, deliberate checklist completion — are insufficient. Fourth-field decisions require a different posture: positive commitment to a direction, willingness to learn and adapt mid-execution, and a focus on outperforming the alternative rather than simply completing the implementation.

The companies that win with HubSpot don’t win because they configured it more carefully than their competitors. They win because they were clearer about what they were trying to accomplish before they started, and they used the platform to pursue that clarity at scale.¹

Automation is a multiplier. If your process is strong, it multiplies strength. If your process is weak, it multiplies weakness — and does so faster and at greater volume than your team could manage manually.

References

1. Rosenzweig, Phil. “What Makes Strategic Decisions Different.” Harvard Business Review, November 2013, 89–93. https://hbr.org/2013/11/what-makes-strategic-decisions-different
2. Rumelt, Richard. “The Perils of Bad Strategy.” McKinsey Quarterly, June 2011. https://www.mckinsey.com/capabilities/strategy-and-corporate-finance/our-insights/the-perils-of-bad-strategy
3. Greiner, Larry E. “Evolution and Revolution as Organizations Grow.” Harvard Business Review, May–June 1998. https://hbr.org/1998/05/evolution-and-revolution-as-organizations-grow
4. Crawford, Christopher. “Strategic Thinking in Your Company.” Session 9, University of Tampa BUS 698 Leadership Development Program, Fall 2024.
5. University of Tampa, TECO Energy Center for Leadership. BUS 698: Modern Advances in Leadership. Sykes College of Business, Fall 2024. https://www.ut.edu/academics/sykes-college-of-business/centers-and-institutes/teco-energy-center-for-leadership/leadership-development-programs
6. HubSpot. “HubSpot CRM Platform.” Referenced 2026. https://www.hubspot.com/products/crm
7. For a practical RevOps framework, see also: Gruby, Jeff. “The RevOps Playbook.” Clari, 2023. https://www.clari.com/resources/ebooks/revops-playbook