Why Big HubSpot Projects Fail Before They Start

From the June 24th, 2026, edition of How Teams Work

I could write you a proposal covering 15 different projects.

I've done it.

Every pain point we uncovered in the sales process, every initiative we could tackle over the next two years, all organized and scoped and detailed. We could take all of it on. The work is real, the problems are real, and the solutions exist.

But here's what I've learned. When you try to solve too many things at once, the scope creeps, the priorities blur, and the project starts to feel unmanageable before the work even begins. Most companies underestimate what it actually takes to execute across that many initiatives at the same time. And when the reality sets in, things stall.

Our approach is different.

We see the full list. We understand it. And then we set most of it aside, focus on what matters most right now, and go get it done. Because the teams that make the most progress aren't the ones with the most comprehensive plans.

They're the ones who narrowed it down to what actually mattered and started executing.

How big scopes kill momentum before the project even starts

When you've been sitting on a long list of problems, getting a partner involved feels like the moment to finally tackle all of it. You know what's broken. The pain points are real. And now that you have someone to help, the instinct is to put everything on the table.

But a project plan built around everything that’s broken is very different from one built around what matters most. Here's how we've seen these projects stall:

1. The project never gets full buy-in. The people who need to approve the work weren't part of the conversation when the scope was being defined. So when the full plan lands in front of leadership or other key stakeholders, they're seeing the complexity and cost for the first time. What should be a green light turns into a long back-and-forth. Momentum dies before anything gets approved.
2. Priorities shift before the work is done. New problems can surface, and they feel urgent in the moment. It's easy to let those take over, especially when the foundational work is less visible and harder to tie to an immediate business problem. What felt like the most important thing in January looks different in March. A large project with many dependencies can't absorb that kind of change. The team ends up chasing what feels important week to week, and the foundational work keeps getting pushed aside in favor of short-term fires.
3. The review and approval process becomes its own bottleneck. There's only so much bandwidth to go around. Your stakeholders are busy, and so is your team. Reviews get pushed to next week, then the week after. In the meantime, your consultants are blocked, waiting on decisions or approvals before they can move forward. Decisions take longer than expected. A six-month project quietly becomes a twelve-month one, and nobody can point to exactly where it went wrong.

The thing is, most teams have been living with these problems for a while already. Nothing is so broken that it's unworkable right now. Which means you can afford to be deliberate about where you start and what you prioritize.

What happens when you try to solve everything at once

A few years back, we were talking with a company that was evaluating HubSpot partners. They ended up going with a different agency.

That partner ran a long discovery and design phase and tried to solve for everything upfront. But instead of taking the time to truly understand the business, they jumped to solutions. They developed what they thought was the perfect answer, recommended moving to a new tool, got the requirements wrong, and ultimately moved the company onto a platform that wasn't right for them.

They had to go backwards. Time lost, money spent, and more tech debt than when they started.

When they came back to us, they were nervous. A little scarred, honestly. And that's fair. They'd gone through the whole process already and ended up worse off.

Here's what we did differently. We ignored the full list. All of it. We asked one question: what's the one thing your team needs most right now? For them, it was quoting. Sales reps couldn't get proposals out fast enough. That was costing deals. That was the one thing they truly needed to make an impact.

So that's all we worked on. Everything else went onto our project board’s backlog so nothing would get lost, giving us a clear way to track secondary priorities and circle back to them once the initial project was done. The rest could wait. Because before we could do anything else, we had to rebuild trust. And the way you rebuild trust is simple.

You get the work done. You do it well. You show up the way you said you would.

That's how every project should start, not just the ones where someone's been burned before.

The questions that actually matter

Most discovery conversations start with some version of: "What do you need fixed?" That question opens everything up. And once everything's open, you're back to that list of 15 projects.

The question you should be asking is: What is your organization focused on right now?

• What is your leadership talking about in their meetings?
• What are you being held accountable for?
• What are your investors or your board asking about?

That's your north star. If you can connect what you're working on in HubSpot to that answer, you're working on the right things. If you can't, it doesn't matter how important it feels.

From there, you can separate what's foundational from what's additive. Foundational means that if it isn't working, everything downstream breaks. Additive means it would make things better, but the engine still runs without it.

We always ask: what can you live with right now versus what's actively blocking you? That question takes a long list and starts collapsing it into something more manageable.

What to prioritize when you don't know where to start

If you're in HubSpot right now trying to figure out what to actually work on, start with the foundations. Everything else depends on getting these right. Here are some key areas that we work through with almost all of our clients:

1. Data structure and architecture. What does your business need to know about a customer? What properties, objects, and fields do you need to track? Get those defined and agreed on before you build anything else.
2. Lead management and lifecycle stages. How does someone go from first touch to the right person's hands? When does a contact become a lead? When does a lead become an opportunity? What triggers those transitions?
3. Lead source and attribution. Where are your leads actually coming from? Who touched the lead before an opportunity was created? If you can't answer that cleanly, you can't make good decisions about where to invest your resources.
4. CRM segmentation. Who are you marketing to, and how do you distinguish them in your system? Without clean data and defined property values, your segmentation breaks down, and your nurture programs have no foundation to run on.
5. Deal and pipeline management. Define what reports and dashboards you actually need across marketing, sales, and customer service. What questions is leadership asking? What does your team need to show their work? This is where the data you've built starts answering those questions instead of leaving people guessing.

Here's a simple test. Go into your CRM and pull a list of your active customers. Can you do it accurately? If you can, your foundation is probably in decent shape. If you're fumbling with filters, getting inconsistent results, or realizing nobody ever agreed on what "active" means, you just found your starting point.

Progress over perfection

You can spend an enormous amount of time building the perfect HubSpot. Perfect data, perfect automations, perfect reporting across every team and every use case. I've watched teams spend years trying to get there.

Or you can pick the one thing that matters most right now, get it working, show your team what's possible, and build from there.

Trying to solve everything at once feels thorough. Picking the right starting point and executing on it is how you actually move forward.

If you know what you need to work on but don't have the bandwidth to get it done, that's exactly what fractional support is built for. Pick the two or three foundational projects that matter most, bring in a team to help you execute, and get them done without committing to a multi-year engagement. That's how you build momentum without overextending.

The temptation is always to do more. Start with less than you think you need, get it working, and expand from there. You can't get back the months you spent on a project that stalled.

Do you have any internal projects that you’ve struggled to get moving? Would love to hear about your experiences.

Want to get the "How Teams Work" newsletter sent to your inbox? Subscribe Now.