Why Standard North Is Built to Leave

Sun Tzu wrote that no country has ever benefited from prolonged warfare. Twenty-five centuries later, the observation applies uncomfortably well to enterprise consulting: no company has ever benefited from a prolonged engagement. Someone benefits. It just isn't the client.

This is not because consultants are dishonest. It's because of how most consulting firms make money. When revenue equals headcount multiplied by months, the incentives write themselves: staff as many people as possible, embed them as deeply as possible, and treat every completed task as an opportunity to discover three more. Success, measured internally, is account growth. An engagement that ends is a failure of business development.

Nobody says this out loud. It shows up instead in the shape of the work: scopes that describe activities rather than outcomes, roadmaps that always seem to add a phase, and projects whose completion criteria were never actually written down. Ask when the engagement ends and you'll hear about journeys.

The AI version is worse

AI has given this model its best fuel in a generation. An "AI transformation" is the perfect prolonged engagement: the scope is nebulous by nature, the technology changes fast enough to justify perpetual reassessment, and no one can say precisely what done looks like because no one defined it. Budgets attach themselves to the buzzword, teams embed, and eighteen months later the company has a portfolio of pilots and a burn rate instead of a capability.

A project without a defined endpoint isn't a project. It's a subscription you didn't know you bought.

How Standard North is built differently

We made three structural choices that cut against the standard model, and they explain almost everything about how we work.

We don't do AI, ML, or LLM implementation. This matters more than it sounds. When the firm that assesses your readiness also sells the build, the assessment is a sales document, and "you're ready" arrives suspiciously often. Standard North has nothing to gain from inflating your score. The SNARS™ Evaluation exists to tell you the truth about your data foundation, including the truth that you're not ready, and precisely what fixing that costs. Our independence is why the number is worth anything.

Every engagement has a defined endpoint, and we prove it. The audit produces a score. The Northbound Flight Plan sequences exactly what must change. The remediation work is scoped in modules with completion criteria written down before anyone starts. And when the work is done, a second SNARS™ evaluation measures the improvement. Done is not a feeling or a steering-committee consensus. It's a number, compared against the number you started with.

The goal is to hand the keys back. We right-size the project, execute it as fast as correctness allows, document everything as we go, and leave your team owning infrastructure they understand. No orphaned systems only we can operate. No renewal conversation disguised as a dependency. There is a moment, and we build toward it deliberately, when a company gets to mark data foundations complete and move its attention to what the foundation was for.

Why we work this way

Partly it's philosophy: we think consulting should work like surgery, not like a tenant. But mostly it's practical. A company that owns its own foundation becomes a reference, a referral source, and a return client when the next real project appears. A company paying for its fourteenth month of embedded staff becomes a procurement review. We would rather be invited back than impossible to remove.

Prolonged warfare exhausts the treasury, dulls the army, and invites every neighboring risk. Prolonged consulting does roughly the same thing to a budget, a data team, and a roadmap. The alternative is simple to say and rare to find: diagnose honestly, scope an endpoint, prove the result, and leave.