When Demand Outruns Delivery

The question is why a strong pipeline can still feel like pressure. On paper, the ERP practice is entering the second half of the year with momentum: June is expected to surpass budget, 2.4 million has closed in the last 60 days, and the active ERP pipeline sits around 6.5 million. Three new projects are scheduled to start in early July. The usual summer slowdown may not arrive.

What is at stake is not only revenue. It is the operating system of the practice. Growth exposes the parts of the system that were previously hidden: hiring lag, skill concentration, unclear service packaging, regional coverage gaps, and the difference between selling work and being able to staff it well.

From first principles, a consulting practice is a capacity conversion system. It converts market demand into trusted delivery. If demand rises faster than capacity, the system does not merely become busy. It begins to leak opportunity, margin, confidence, and time.

The Signal Inside a Strong June

June appears to be the clearest inflection point of the year so far. The practice is ahead of budget, recent closes are meaningful, and the pipeline includes several opportunities near decision. A large portfolio-company opportunity, roughly 2.2 million, could materially change the shape of the second half.

But recognized revenue lags delivery activity. Work performed now may not appear in the numbers until July or later. This matters because leaders can misread the business if they look only at financial reporting. A team may feel overloaded before the revenue confirms it. By the time the P&L catches up, the delivery constraints are already real.

The practical lesson is simple: revenue is a trailing indicator. Staffing pressure, utilization patterns, project start dates, proposal velocity, and partner requests are earlier signals. A practice that waits for revenue recognition to confirm demand will often be late to hire.

Pipeline Is Not the Same as Capacity

A 6.5 million active pipeline is a healthy demand signal. It also creates a management problem. Each opportunity carries assumptions about timing, skills, geography, leadership, and delivery model. If those assumptions are not visible, the pipeline can create false confidence.

Two current examples make the point.

One client is evaluating other providers because the firm could not supply a London-based team with subscription billing capability on the required timeline. The demand existed. The relationship existed. The opportunity was real. But the capacity did not exist in the right location with the right skills at the right time.

Another client has announced a new body of work requiring a second full team. The issue is not whether the firm is qualified. The issue is whether it can respond without weakening existing commitments.

These are not sales problems. They are system-design problems.

What pipeline reviews need to include

A pipeline review should not stop at probability and close date. For a delivery-led firm, each meaningful opportunity should be reviewed through a capacity lens:

Required skills: subscription billing, field service, integrations, data, change management, industry expertise.
Required location: client preference, time-zone overlap, language, travel expectations.
Required start window: immediate, 30 days, 60 days, flexible.
Delivery leadership: who can own the account, manage risk, and protect quality.
Opportunity cost: which existing or future work becomes harder if this deal closes.
Confidence level: not only probability to win, but probability to staff well.

The last point is often missing. A deal may be 80 percent likely to close and only 40 percent likely to be staffed cleanly. Those two facts should be visible together.

Resourcing Constraints Are a Strategy Issue

The meeting surfaced a hard truth: hesitancy around bench investment during Q1 slowed hiring, and that caution is now showing up as a delivery constraint. This is common in consulting. After a softer period, leaders protect margin by avoiding bench. Then demand returns, and the practice has too little capacity to capture it.

Neither instinct is wrong. An unmanaged bench can erode profitability. But a zero-bench posture can erode growth. The better question is what kind of bench is strategic.

A strategic bench is not simply unused labor. It is targeted capacity in the areas most likely to unblock revenue and reduce delivery risk. In this case, the signals point to specific needs:

Subscription billing capability, especially in markets where demand is active.
Field service expertise, where too much knowledge is concentrated in one fully committed person.
Delivery managers who can absorb new project starts without pulling senior leaders into every escalation.
Global team members who can extend coverage without diluting accountability.

When expertise is concentrated in one person, the constraint is not just availability. It is fragility. The practice cannot scale a service line if the critical path runs through a single calendar.

Global Delivery Is Already Becoming Core

Fourteen global delivery hires have already been staffed. That is not a side note. It changes how the practice operates.

Global delivery can increase capacity, improve coverage, and support margin. But it only works when the operating model is explicit. Otherwise, offshore or nearshore capacity becomes a patch instead of a platform.

The questions to answer are operational:

Which work should global delivery own end to end?
Which work should remain close to the client team?
How are handoffs documented?
Who owns quality review?
How are time zones used as an advantage rather than a delay?
How are new hires trained into the practice methodology?

A global delivery model should not be measured only by headcount. It should be measured by how much reliable delivery capacity it creates. Reliability depends on process, documentation, manager depth, and trust between teams.

The risk in a fast-growing practice is that global delivery becomes reactive. People are added to projects because capacity is tight. The better path is to define repeatable delivery pods, clear role expectations, and escalation routes before every project has to invent them.

AI Demand Is Arriving Before the Offering Is Finished

AI was framed in two ways: as a client-facing service and as an internal capability. That is the right framing. Clients want help understanding where AI can improve operations, especially in ERP-adjacent processes. At the same time, the firm needs to use AI internally to improve delivery speed, knowledge reuse, proposal support, testing, documentation, and analysis.

The tension is that market demand is building while the service offering is still being defined. Private equity firms are already pointing to the team as a preferred AI partner. That creates opportunity, but it also creates delivery risk if the promise is not specific.

AI strategy should become concrete quickly. Not broad claims. Practical offers.

The first version does not need to be large. It needs to be clear:

AI readiness assessment: data, systems, governance, process fit, and risk.
Use-case prioritization: where AI can reduce cycle time, improve decision quality, or automate repetitive work.
ERP workflow augmentation: practical AI around finance, billing, service, procurement, support, and reporting.
Private equity portfolio scan: a repeatable review across portfolio companies to identify common value pools.
Internal enablement: training client teams to use AI safely inside existing workflows.

The firm should also decide where it will not play. Clear boundaries protect quality. AI work can drift quickly into experimentation without business value. A focused offer helps clients buy, helps partners sell, and helps delivery teams staff.

OKRs Should Make Constraints Visible

The internal OKR process matters because it can translate a busy conversation into operating discipline. Good OKRs should not simply restate ambition. They should identify the few constraints that must move.

For this practice, the second-half OKRs could focus on capacity conversion:

Increase qualified delivery capacity in subscription billing and field service.
Reduce single-person dependency in critical ERP domains.
Define and launch a minimum viable AI service offering.
Standardize global delivery pods and handoff methods.
Improve pipeline-to-staffing visibility for all large opportunities.

Each objective should have measurable key results. For example: number of certified practitioners, number of shadow resources trained, time to staff a qualified team, percentage of large opportunities with capacity plans, number of AI assessments delivered, or number of global delivery pods operating under a standard model.

The point is not process for its own sake. The point is to make the system observable. Once leaders can see the constraint, they can manage it.

The Management Pattern

The pattern across the meeting is familiar. Demand is rising. Delivery is stretched. Hiring decisions made months ago are now shaping current options. New service areas are emerging. Global delivery is scaling. The practice has more opportunity than it can comfortably absorb.

That is a good problem only if it is treated as a design problem.

The answer is not to chase every deal. It is to decide which demand the practice is built to serve, which capabilities need investment before they are urgent, and which operating rules will protect delivery quality as the team grows.

Consulting firms often talk about growth as if it is primarily a sales outcome. In reality, sustained growth is a coordination outcome. Sales, staffing, delivery, hiring, enablement, and finance have to move together. If one function moves faster than the others, the system strains.

Ultimately, the ERP practice is entering H2 with real momentum. The pipeline is strong, recent closes are validating the market, and global delivery capacity is expanding. The opportunity is not abstract. It is already here.

What this means is that the next phase depends less on generating demand and more on converting demand responsibly. That requires targeted hiring, clearer capacity planning, a defined AI offer, and operating discipline around global delivery.

The takeaway is simple: growth is not proven by pipeline alone. It is proven by the ability to staff the right team, at the right time, with the right method, and deliver without weakening the system that created the demand in the first place.