Why “Right-Size” Beats Biggest in EPM Consulting

The partner who closes your EPM deal shouldn’t be the last senior person you see. Here’s why the size of your consulting firm matters less than the structure of how they staff it—and what to ask before you sign anything.

No one ever planned to hire the B-team.

But we hear some version of the same story several times a year. A finance leader invests in an EPM implementation expecting to work with the experienced consultants who impressed them during the sales process. After kickoff, those faces disappear. The partner who scoped the engagement moves on to the next deal. Senior consultants become hard to reach. Day-to-day execution lands with junior resources doing their best—without the context or experience to navigate the complexity that every serious implementation eventually produces.

The other version of the story is quieter but equally frustrating. A company hires a small specialist firm because they want personalized attention, only to discover that a single staff change or a competing engagement can stall momentum for weeks. There’s no bench to draw from. There’s no escalation path. There’s just a gap where the project used to be.

Neither situation starts with bad intentions. Both are predictable consequences of choosing a partner based on the wrong criteria.

Size is not the problem. Structure is.

The firms that build the best reputations in EPM aren’t the biggest or the smallest. They’re the ones whose senior people stay in the room after the contract is signed.

What Scale Gets Wrong

Large consulting organizations carry real strengths—recognizable brands, deep bench depth, broad cross-industry experience. But scale introduces a structural problem that's hard to see from the outside: as firms grow, they specialize. Sales teams sell. Solution architects design. Delivery teams implement. Project management becomes a separate layer. Each transition is an opportunity for context to be lost, assumptions to change, and accountability to blur.

We’ve spoken with finance leaders who spent the first month of an EPM project re-explaining their business requirements to a succession of new faces. That’s not a failure of individual effort. It’s a systems problem—one that’s built into how large firms staff.

EPM projects aren’t software implementations. They’re business transformation initiatives that use software as the vehicle. Success depends on understanding how finance operates, how planning decisions get made, and why certain processes exist in the form they do. That understanding doesn’t live in a requirements document. It lives in conversations—the ones that happen over weeks of workshops, whiteboard sessions, and hard questions about the business.

When the people who build that understanding aren’t the people who build the solution, the project pays for the gap. Usually in rework. Sometimes in re-implementation.

What Boutique Misses

Smaller, specialized firms solve the continuity problem—the same people who scoped the project are still there in month four. That’s genuinely valuable. But it creates a different vulnerability.

Limited staffing creates key-person risk. When one consultant’s availability determines whether a project moves or stalls, that’s a structural fragility that has nothing to do with the quality of the work. Escalation paths are shorter because there are fewer people above the delivery team. Methodologies evolve organically rather than through repeated execution across dozens of complex implementations.

And organizations grow. A firm that’s right-sized for a 12-week NSPB implementation may not be equipped to support a multi-entity consolidation rollout two years later. The partner that got you live isn’t always the partner who can take you further.

The Right-Size Difference

At Myers-Holum, we’ve deliberately built a model that sits between those failure modes.

We’re structured to provide the methodology depth, partner-level relationships, and delivery experience that complex EPM projects require—without the organizational layers that separate the people who design a solution from the people who deliver it. Senior practitioners at MHI don’t hand off to junior teams at kickoff. They stay on the project. That’s not a talking point. It’s an explicit staffing philosophy that shapes how every engagement is structured.

Being named NetSuite Alliance Partner of the Year reflects that approach. The award isn’t based on revenue. It’s based on delivery quality and client outcomes—and it’s earned by a team that consistently closes the gap between what a planning tool promises and what a client actually experiences.

That gap, in most cases, isn’t a product limitation. It’s a configuration gap rooted in an incomplete understanding of how the underlying NetSuite ERP is structured.

NSPB’s native NetSuite integration is its greatest strength—but only when the implementation reflects the actual ERP configuration. That requires a team that understands both sides of the equation, not just the planning tool.

Why ERP Depth Changes Everything in NSPB

Planning models are only as strong as the operational data feeding them. Revenue recognition policies, chart of accounts design, dimension structures, subsidiary hierarchies, intercompany frameworks—all of it shapes what NSPB can do and how reliably it does it.

We see this play out in the same patterns across different clients:

Revenue planning

A company wants forecasts by product, customer, or sales region. But if the ERP isn’t consistently capturing those dimensions—or if different business units classify revenue differently—finance spends more time reconciling inputs than analyzing the output. The planning model isn’t broken. The operational data is.

Workforce planning

Finance leaders increasingly want to forecast hiring, compensation, and labor costs at the department level. That requires accurate employee structures, departmental ownership, and approval workflows in the ERP. Without it, headcount planning is a spreadsheet exercise with a fancier interface.

Financial close

Executives don’t ask whether the planning application worked. They ask why actuals differ from forecast. If the close takes longer than expected, or intercompany transactions aren’t reconciled cleanly, every forecast begins with uncertainty. The planning team ends up questioning the numbers before they can question the business.

Myers-Holum’s ERP and EPM practices aren’t two separate disciplines. They’re the same conversation. When we design a planning model, we’re thinking about how transactions originate in the ERP. When we discuss close cycles, we’re thinking about how they flow into the planning layer. Finance leaders shouldn’t have to bridge that gap themselves. Their implementation partner should already understand both sides.

What Transformation Actually Looks Like

One misconception we encounter regularly: that an EPM implementation is primarily about budgeting software.

It isn’t. The most successful EPM projects are business transformation initiatives that happen to include planning software. The software enables the change. The transformation comes from redesigning how information flows between departments, who owns key decisions, and how finance partners with the rest of the business.

We’ve helped organizations reduce budgeting cycles from months to weeks—not because they switched tools, but because they standardized planning assumptions across business units for the first time. We’ve replaced hundreds of disconnected spreadsheets with centralized models that give leadership a single version of the truth. We’ve helped finance teams move from quarterly forecasting to continuous planning, so leadership can respond to market changes in days rather than waiting for the next budgeting cycle.

In each case, the software was the platform. The process change was the result.

That’s why our consultants spend as much time on operating models, reporting governance, and organizational structure as they do on configuration. Technology supports transformation. Business process creates it.

Three Questions Worth Asking Before You Sign

If you’re evaluating an EPM implementation partner, company size is a starting point—not a decision. Here are the questions that tell you what size can’t:

Ask these in your first meeting:

1. Who specifically will be working on my project day-to-day—and what is their experience level?
‍
2. What does your escalation path look like if we hit a blocker mid-project?

3. Can I speak with a client in my industry who went live in the past 12 months?

The firms that are confident in their delivery welcome those questions. The ones that redirect to their partner tier or their total headcount probably should not.

At Myers-Holum, we’ll answer all three. We’ll give you names, recent references, and a candid account of a project that went sideways and how we fixed it. That’s not a guarantee of a perfect engagement. It’s a signal of a team that takes delivery seriously—and one that won’t disappear after kickoff.

Considering an EPM initiative?

We’d welcome a no-obligation discovery call to discuss your goals, your current NetSuite environment, and whether MHI is the right fit. The conversation itself should tell you something.

And if you’re looking for practical EPM and NSPB perspectives throughout the year, follow Myers-Holum. We publish monthly—designed for finance and operations leaders, not marketing audiences.