Most organizations of meaningful size are spending significant money on consultants, and most of that money is funding work that doesn't compound. The engagements happen. The deliverables get produced. The recommendations get implemented or shelved. The consultants leave. Six months later, the organization has another problem in roughly the same domain, hires another consultant, runs another engagement, and produces another set of deliverables. The cycle continues. The cumulative spend is substantial. The cumulative impact is much smaller than the cumulative spend would suggest, because each engagement addresses symptoms while the structural conditions that generate the symptoms stay in place.

This isn't a critique of consultants. Most consulting work is competent, sometimes excellent. The work the consultants are scoped to do, they do. The issue is what they're being scoped to do. Most consulting engagements are scoped to address specific problems, deliver specific recommendations, and complete in defined timeframes. The scoping produces engagements that work as intended. The work doesn't compound because the structural conditions underneath the symptoms aren't being addressed by the engagement's scope. The consultant solves the visible problem. The system that produced the problem keeps running. The next problem the system produces becomes the next consulting engagement. The organization is buying symptom relief in a sustained pattern that doesn't add up to structural improvement.

Here's how this plays out across the most common consulting engagement types in nonprofit and public-sector organizations.

A federal grant compliance consultant gets engaged to address a specific finding or to prepare for an upcoming audit. The consultant performs the work. Documentation gets reconstructed. Specific issues get remediated. The corrective action plan gets written and accepted. The engagement closes. The structural conditions that produced the finding, weak documentation infrastructure, inadequate monitoring systems, cost allocation that can't withstand scrutiny, are still in place. The next audit cycle produces the next finding. The next consulting engagement gets initiated. The pattern repeats, with each engagement costing more than the last as the cumulative remediation requirements grow.

A financial systems consultant gets engaged to address reporting inadequacies. The consultant rebuilds specific reports, designs new dashboards, and produces materials that address leadership's immediate visibility issues. The engagement closes. The chart of accounts inconsistencies that limit what reporting can produce are still in place. The cost allocation distortions that compromise the reports' analytical value are still present. The reporting structure that the new dashboards sit on top of is still misaligned with current operations. Within a year, leadership's reporting needs have evolved, the dashboards no longer serve those needs, and the next consulting engagement gets initiated to build the next set of reports.

An indirect cost rate consultant gets engaged to support rate negotiation or rate development. The consultant produces a defensible rate calculation against the cost data the organization has. The negotiation happens. The rate gets approved. The engagement closes. The cost allocation methodology underneath the rate hasn't been restructured to reflect operational reality. The documentation infrastructure required to defend a stronger rate hasn't been built. The next rate cycle requires another consultant, working against the same constraints, producing a similar outcome. The organization keeps recovering at levels well below what stronger structural foundation would support, year after year, paying consultants in each cycle to optimize within the constraint rather than addressing the constraint.

A strategic planning consultant gets engaged to support the development of the next strategic plan. The consultant facilitates the planning process, produces the strategic document, and frames the organization's priorities for the planning horizon. The engagement closes. The financial and operational infrastructure required to execute the strategy hasn't been examined. The plan gets developed against assumptions about what the organization can do that the existing infrastructure may or may not support. Implementation encounters infrastructure constraints that weren't surfaced during planning. The plan gets quietly modified, deferred, or partially executed. The next strategic planning cycle starts the process again, with another consultant, against the same unaddressed infrastructure conditions.

An AI or technology consultant gets engaged to support a specific deployment or assessment. The consultant produces recommendations for tools, vendors, or implementation approaches. The recommendations get evaluated. Some get adopted. The engagement closes. The data, process, and infrastructure conditions that determine whether technology deployments actually produce value haven't been addressed by the engagement's scope. The deployments that proceed encounter the foundation issues described in earlier discussion. The next consulting engagement addresses the consequences of the deployment. The pattern continues.

The aggregate effect of this pattern is significant. An organization can spend hundreds of thousands or millions of dollars on consulting engagements over a five-year period without making structural progress on the conditions that keep generating the need for consulting engagements. The spending produces visible activity. Each engagement produces deliverables. The deliverables look like progress. The progress doesn't compound, because the structural foundation that would let progress compound isn't being addressed by any individual engagement.

This pattern persists because of how consulting engagements get scoped and how organizations buy consulting. The buyer has a visible problem. The engagement gets scoped against the visible problem. The scope is specific, time-bound, and budgetable. The vendor selection, contracting, and engagement management infrastructure is built to support discrete engagements. The structural alternative, an extended infrastructure investment that addresses the conditions producing the symptoms, doesn't fit the engagement model the organization is set up to procure. So the organization keeps buying engagements that match its procurement infrastructure, and the procurement infrastructure keeps shaping the work toward symptom-relief rather than structural improvement. The pattern is reinforced by the structure of how consulting gets bought, not just by how it gets delivered.

Here's the structural alternative most organizations don't consider. Instead of running a series of consulting engagements that address symptoms, invest in the infrastructure work that addresses the underlying conditions. The chart of accounts that supports decision-ready reporting. The cost allocation methodology that survives scrutiny and supports defensible rates. The documentation infrastructure that closes the gap between practice and what audits would require. The compliance systems embedded in workflows rather than verified after the fact. The data foundation that supports AI deployment without producing distortion. The reporting structure aligned with leadership's actual decision needs.

This infrastructure work is harder to scope, harder to budget, and harder to communicate than discrete consulting engagements. The deliverables are less visible during the work. The payback is longer-horizon. The conventional procurement infrastructure doesn't accommodate it as cleanly. And it's the work that actually changes the trajectory of the organization, because it addresses what's producing the symptoms instead of treating each symptom in isolation.

The leadership question that exposes this clearly is whether the consulting spend over the past five years has produced cumulative structural improvement or cumulative symptom relief. Most leadership teams, examining this honestly, can identify that the spend has been substantial and the structural improvement has been modest. The same conditions that generated the early engagements are still generating engagements now. The organization is paying for a pattern that doesn't add up to transformation, and the pattern persists because alternatives haven't been considered seriously.

The argument against infrastructure investment is always the same. The visible deliverables of consulting engagements are easier to justify to boards and stakeholders. The longer timeline of infrastructure work doesn't fit the political cycles of organizational leadership. The skill set required to execute infrastructure work is different from the skill set required to manage consulting engagements. Each of these arguments is valid as a description of the constraints organizations face. None of them changes the underlying reality, which is that consulting engagements without infrastructure investment produce the pattern described above, and the pattern is expensive over time.

Organizations that break the pattern do something specific. They distinguish between symptom relief and structural improvement, and they make conscious decisions about which they're buying. When symptom relief is appropriate, because the underlying structure is sound and a specific issue needs targeted attention, they buy consulting engagements scoped accordingly. When the symptoms reflect structural conditions, they invest in infrastructure work, accepting the longer timeline and the less visible deliverables in exchange for outcomes that compound. The mix of consulting and infrastructure work changes over time, with infrastructure investment dominating in periods when structural improvement is needed and consulting playing a supporting role.

If your organization has been spending on consulting and the same kinds of problems keep recurring, you don't need another consultant. You need infrastructure. The next engagement isn't going to produce different outcomes than the previous engagements, because the conditions that shaped those outcomes haven't changed. Continuing to buy engagement-based work means continuing to buy the pattern. The pattern won't get better. The cumulative cost will continue to compound. The structural alternative requires different decisions than the procurement infrastructure makes easy, and those decisions are the ones that actually produce the change leadership keeps trying to buy through engagements.