We did not build another consulting menu. We built the capabilities organizations actually need.

The same problem wearing different clothes

There is a particular moment I have encountered repeatedly in organizations.

The people are capable. The leadership is serious. There is no shortage of meetings, reports, systems, policies or professional expertise. Yet important work is still struggling to move.

Contracts accumulate. Procurement becomes consumed by transactions. Good ideas remain ideas because nobody owns the difficult journey between imagination and implementation. Executives find themselves spending disproportionate amounts of time resolving operational questions that should have been resolved before reaching their desks.

At first glance, these appear to be different problems. I have come to believe that they are often manifestations of the same one.

The organization does not necessarily have a people problem. It has a capability problem.

That distinction matters enormously. It is also one of the principal reasons we built Jan Law Consulting differently.

The gap between advice and capability

Traditional consulting has created extraordinary value for organizations around the world. I have tremendous respect for the profession and for the intellectual discipline that excellent consulting brings to difficult problems.

But there is a gap in the traditional model that I have found increasingly difficult to ignore.

An organization identifies a problem. Consultants are engaged. Research is conducted. Stakeholders are interviewed. Findings are developed. Recommendations are presented.

Then comes Monday morning. Someone inside the organization still has to make it work.

The hardest part of organizational improvement is frequently not knowing what ought to be done. Experienced executives often already have a remarkably accurate understanding of their problems. The real difficulty is creating sufficient structure, ownership, discipline and sustained senior attention to move from what the organization knows to what the organization consistently does.

Expertise can answer a question. Capability allows the organization to keep answering the question after the meeting is over.

I did not want JLC merely to become another source of recommendations. I wanted us to occupy that space between advice and institutional capability.

Why we built Signature Solutions

COaaS, PROaaS, SIaaS and EADaaS are not simply four consulting practices given distinctive names. They represent a different way of thinking about how sophisticated expertise can be delivered.

Contracts Operations as a Service. Procurement Operations as a Service. Strategic Innovation as a Service. Executive Advisory as a Service.

The important words are not merely contracts, procurement, innovation and executive advisory. The important words are as a Service. That language is deliberate.

Our proposition is not simply that an organization can hire JLC to complete a project. It is that an organization can access a defined professional capability without automatically having to recreate the entire infrastructure, headcount and permanent cost traditionally associated with possessing that capability internally.

Instead of asking how many consultants you need, I would rather ask what capability your organization needs to possess. Instead of beginning with hours, I want to understand what must reliably happen. Instead of measuring consulting activity, I want to understand organizational movement.

COaaS: contracts are not documents

Contracts are commonly treated as documents. I see them differently. A mature contracts function is an operating system for commercial relationships.

The signed agreement is only one artifact within that system. Before signature there is intake, prioritization, commercial assessment, stakeholder alignment, negotiation, decision making and escalation. After signature there are obligations, performance questions, renewals, amendments and institutional memory.

When those activities are fragmented, organizations experience familiar symptoms. Nobody knows precisely where an agreement sits. Business teams chase updates. Leadership becomes involved too late. Renewals become emergencies. Important commercial knowledge remains trapped inside documents instead of informing decisions.

I think of COaaS as a managed contracts capability rather than a document review service. The objective is not simply to process agreements faster. Speed without judgment merely allows an organization to make commitments more efficiently. The real objective is to create enough discipline around contracting that decisions become visible, responsibilities become clear and commercial commitments are managed intentionally.

PROaaS: procurement is an economic function

Procurement suffers from a similar misunderstanding. It is often viewed principally through the lens of purchasing.

But excellent procurement is not simply about buying things. It is about how an institution organizes demand, approaches markets, creates competition, evaluates choices, governs suppliers and converts external spending into institutional value.

A purchase order can tell me what an organization bought. It cannot tell me whether the organization approached the market intelligently, whether requirements were properly constructed, whether supplier concentration creates vulnerability or whether the purchasing decision actually advances enterprise strategy.

The central question is deceptively simple: how does this organization use the market intelligently? That question reaches much further than price. Every organization has limited capital, limited management attention and limited tolerance for failure. The quality of procurement therefore influences resilience, performance, risk, innovation and ultimately the organization's ability to execute its own strategy.

Handled transactionally, procurement processes demand. Handled strategically, it shapes outcomes. Our interest is in the latter.

SIaaS: ideas are plentiful, execution architecture is not

Innovation may be one of the most overused words in modern business. Almost every organization wants it. Many hold workshops devoted to it. There are whiteboards full of it. Yet remarkably little of what organizations call innovation survives contact with operations.

The problem is rarely a shortage of ideas. It is a shortage of architecture.

An idea has to survive increasingly unforgiving questions. What problem are we actually solving? Who experiences that problem? Why does the current model fail? What assumptions are we making? Who will own the solution? What will it cost? What has to be true for it to work? How do we test those assumptions before committing significant resources? And ultimately, can this idea live inside the real organization rather than only on a presentation slide?

Sometimes innovation work leads to a new operating model, service or strategic initiative. Sometimes disciplined analysis reveals that an attractive idea should not proceed. I consider the second outcome every bit as important as the first.

Innovation requires imagination. Strategic innovation requires judgment. SIaaS exists at the intersection of the two.

EADaaS: leadership attention is a scarce resource

Senior executives routinely confront matters important enough to require experienced judgment but not sufficient to justify another permanent executive appointment.

The issue may cross contracts, procurement, operations, governance and strategy. It may be temporary. Its intensity may fluctuate. What the organization needs is not necessarily another title on the organizational chart. It needs access to mature judgment.

We speak frequently about financial capacity and operational capacity. We speak much less about the finite amount of serious thinking an executive team can perform. Every hour a senior executive spends reconstructing information, mediating an avoidable process failure or resolving something that should have arrived with a clear recommendation is an hour unavailable for work that genuinely requires that executive's authority and perspective.

The purpose is not to put another voice in the room. The purpose is to help a better decision leave the room.

The Commercial Capacity Framework: counting work is not enough

Once we began thinking about professional services as capability rather than simply labor, another question became unavoidable. How should professional capacity actually be measured?

Consider two contracts. One is familiar, low risk, commercially straightforward and requires limited coordination. The other involves substantial financial exposure, multiple stakeholders, technical requirements, difficult negotiations and executive escalation. Calling them simply two contracts tells us almost nothing about the professional capacity required to handle them responsibly.

The same problem appears elsewhere. Two procurements are not necessarily equivalent. Two strategic initiatives may consume radically different levels of senior attention.

The JLC Commercial Capacity Framework considers the characteristics that actually consume professional capacity, including complexity, significance, negotiation intensity, responsiveness, stakeholder coordination and operating context. Internally, Commercial Capacity Units provide a disciplined way of understanding and planning capacity. The client engages JLC through a defined written scope and service commitment.

A client should not have to understand our internal machinery in order to understand what we have promised. The principle underneath the framework is simple: effort should follow complexity, not arithmetic.

Boutique, to me, means deliberate

We describe JLC as a boutique enterprise advisory practice. For me, boutique is not a description of size. It is a description of intention.

I do not believe clients should meet senior expertise while an engagement is being pursued and discover, after the work begins, that the actual thinking has descended several levels down an organizational pyramid.

Senior judgment should not be ceremonial. It should be present where consequential decisions are being made.

That philosophy naturally constrains volume. It requires us to be thoughtful about the work we accept. It means fit matters. I am comfortable with that. I would rather build a practice known for the quality of its thinking and the seriousness with which it assumes responsibility than one known principally for the number of people it can deploy.

What we are really building

COaaS, PROaaS, SIaaS and EADaaS address different organizational needs, but intellectually they belong to the same family. Each begins with a simple proposition: organizations sometimes need capability without bureaucracy, expertise without unnecessary permanent overhead and advice that remains present long enough to become operationally useful.

Artificial intelligence will alter professional workflows. Contract operations will become increasingly integrated with enterprise systems. Procurement will become more data intensive. Executives will have access to quantities of information that would have been unimaginable only a few years ago.

If information becomes easier to obtain and analysis becomes easier to produce, where does professional value migrate? My answer is toward judgment. Analysis will become abundant. Judgment will not. Accountability will not. Neither will the ability to understand an institution deeply enough to distinguish the technically correct answer from the answer that can actually work inside that institution.

The premium will increasingly fall on people who can distinguish signal from noise, understand consequences, challenge assumptions, make difficult recommendations and remain sufficiently close to implementation to know whether those recommendations survive reality.

Not as another pair of hands. Not as another presentation. Not as another layer. But as a serious extension of organizational capability, brought in where it matters, structured around an outcome and judged ultimately by one question: is the organization stronger because we were there?