If your system works, why isn't it working for you?

I keep noticing something uncomfortable in the consulting and professional services market.

Sales consultants selling systems that are supposed to generate customers, while struggling to acquire customers themselves.

Marketing consultants promising predictable demand, while relying almost entirely on referrals.

Leadership consultants selling organizational development frameworks they have never successfully implemented within their own organizations.

Course developers teaching people how to build profitable businesses, while the courses themselves are their only profitable business.

Management consultants selling growth models they have never had to operate.

There may be perfectly reasonable explanations for every one of these situations.

But I think there is a question we should ask more often.

If the system you are selling works, why isn't it working for you?

The difference between understanding and making something work

There is an important difference between knowing how something should work and demonstrating that it actually works.

A consultant can understand sales theory, market segmentation, organizational psychology, leadership development or business strategy exceptionally well.

That knowledge can be valuable.

But creating a framework around that knowledge does not automatically turn it into an effective operating system.

A sales methodology is not evidence of sales performance.

A marketing framework is not evidence of market demand.

A leadership model is not evidence of better leadership.

A growth strategy is not evidence of growth.

These are proposed explanations and methods. Their value depends on what happens when someone tries to use them.

And this is where I think parts of the consulting industry have developed a strange relationship with evidence.

We have become remarkably good at packaging how things should work.

We are less consistent at showing what happens when they do.

The consultant's own business is an interesting laboratory

Imagine a consultant who has developed a system for identifying potential customers, creating demand and converting opportunities into paying clients.

The system is presented as systematic, repeatable and effective.

But the consultant's own business has no systematic customer acquisition.

Most opportunities come through personal relationships, referrals or chance encounters.

When asked why the system is not being used internally, the explanations begin.

There has not been enough time.

The company is too small.

The target market is different.

The consultant has been too busy delivering for existing customers.

Perhaps all of these explanations are true.

But they leave an important question unanswered.

Under what conditions does the system actually work?

If a method requires resources the intended customer does not have, that matters.

If it depends on relationships that cannot be replicated, that matters.

If it only produces results when an unusually talented person operates it, that matters.

And if it has never been tested under realistic commercial conditions, that matters too.

The consultant's own business is not a perfect laboratory. But it is a remarkably accessible one.

There are legitimate exceptions

I do not believe every consultant must have personally achieved everything they help clients achieve.

An executive coach does not need to have been the CEO of a multinational corporation.

A leadership researcher can develop useful insights without managing a large organization.

A management consultant may understand organizational transformation without operating a company of comparable complexity.

And someone who helps large companies improve their sales processes cannot necessarily reproduce the same results in a small consulting practice.

Context matters.

Expertise can come from research, observation, experimentation and work across many organizations.

But these exceptions do not eliminate the need for evidence.

They change what evidence is appropriate.

If your system cannot reasonably be tested in your own business, show where it has been tested.

Explain the starting conditions, what was implemented, what changed and what can reasonably be attributed to the intervention.

Explain the limitations.

The problem is not that consultants lack personal success stories.

The problem arises when a proposed solution is presented as a proven solution without sufficient evidence that it works.

We have confused the product with the outcome

I suspect part of the problem comes from how professional services have evolved.

Consultants develop methodologies.

They create frameworks, maturity models, assessments, workshops, courses, playbooks and increasingly software.

These become recognizable products.

They can be named, branded, explained, demonstrated and sold.

And the more sophisticated the product appears, the easier it can become to mistake that sophistication for effectiveness.

A beautifully designed leadership framework may still fail to change how managers behave.

A detailed sales playbook may never produce another qualified opportunity.

A marketing automation platform may simply automate activities that were never commercially useful.

The deliverable becomes the achievement.

But the customer did not buy the framework to own a framework.

They bought it because something was supposed to change.

The test is not whether the methodology was delivered correctly.

It is whether it helped produce the intended outcome.

AI makes this question more uncomfortable

I think artificial intelligence will make this distinction increasingly important.

It has become much easier to create sophisticated frameworks, presentations, assessments, learning programs and software.

A capable person with good AI tools can produce materials that previously required teams of consultants, designers and developers.

This is an extraordinary development.

But it also creates a problem.

We can now produce the appearance of sophisticated expertise much faster than we can establish whether that expertise creates value.

A framework can be developed in an afternoon.

Evidence that it works may take months or years.

That gap matters.

As buyers gain access to similar tools, I expect them to become less interested in paying for the existence of a methodology and more interested in understanding what it actually accomplishes.

Why should I buy your sales system instead of building one with my own AI?

What have you demonstrated that I cannot reproduce?

Where has the system succeeded?

Where has it failed?

What does it require from my organization?

And perhaps most importantly:

Can you show me what happens when someone actually uses it?

These are reasonable questions.

The same standard has to apply to my own work

I cannot make this argument without turning it toward myself.

I have worked with sales, leadership, commercialization and organizational development for years.

I have developed models, methods, analyses and systems.

Some have been applied in client work. Others remain hypotheses or experiments.

And I have certainly spent time developing systems that were more complete on paper than they were in operation.

That is part of what I want to change.

With Entriva.ai, the ambition is to develop a system that identifies opportunities and sells services through autonomous agents.

But the existence of that system will not demonstrate its commercial value.

Neither will the number of signals it identifies, companies it analyzes, prospects it contacts or conversations it initiates.

Those are activities.

The meaningful test is whether it can generate real customers, complete genuine transactions and do so with economics that make sense.

If it cannot sell the services it was developed to sell, that is not an inconvenient detail.

It is evidence about the system.

And if I eventually offer that capability to others, I should be expected to explain exactly what it has and has not achieved.

What I think matters

I would like to see a different standard for how we evaluate commercial and organizational solutions.

Less attention to how impressive the framework looks.

More attention to the conditions under which it works.

Less emphasis on how many steps a methodology contains.

More emphasis on what changes after those steps have been completed.

Less reliance on testimonials describing how inspiring an experience was.

More evidence of what people and organizations do differently afterward.

And greater willingness to distinguish between an idea, a hypothesis, a tested method and a demonstrated result.

This does not mean every intervention must produce an immediate financial return. Leadership development, organizational learning and cultural change often involve outcomes that take time and are difficult to isolate.

But difficult measurement is not an excuse to avoid measurement.

It is a reason to be more careful about what we claim.

What remains uncertain

There is a risk of taking this argument too far.

A consultant's commercial success is not necessarily a reliable measure of professional competence.

An excellent specialist can run a weak business. A highly successful consultant can be exceptionally good at selling services that deliver disappointing outcomes.

Commercial success and client value are not identical.

I also do not know how much weight buyers actually place on a supplier's ability to demonstrate results from its own methods.

That would be worth investigating.

My working hypothesis is that the gap between a convincing methodology and a functioning solution will become increasingly visible as AI makes it easier for buyers to investigate, compare and test alternatives themselves.

For now, I keep returning to one simple principle.

Before asking someone else to invest in your solution, you should be able to explain what happened when you tried to make it work.

Not necessarily in your own company.

Not necessarily perfectly.

But somewhere, under conditions that matter.

Otherwise, you may have something interesting to sell.

You just do not yet know whether you have something that works.