accilium is not becoming a software company. We are still consultants; the unit of value is still a decision made well, written down, and delivered on a slide. What is changing is what an organization is. A consultancy used to be a collective of people held together by hierarchy, rules, and shared method. AI is turning organizations into something closer to intelligent systems, where capability lives partly in people, partly in the tools they share, and partly in the cadence that connects the two. The operating model has to evolve with that. How we evolve the firm is itself becoming part of the work.

Becoming AI-native is the direction. The clearest place that has shown up is in how the firm governs new capability. Adding a new tool used to be a yearly rhythm: procurement, approval, rollout. AI capability arrives on a different clock, and the firm’s governance moved to match it. This post is about how that second clock runs.

Consultancies historically run one cadence: the project cadence of kickoff, interim, final, archive. We still run it; client work has not changed shape. What is new at accilium is a second cadence running alongside the first, on a faster clock. Late 2025 into early 2026, the tools got good. Consultants inside the firm had quietly built useful things: a prompt that turned messy German RFPs into a structured brief or a workflow that produced a consistency-checked PowerPoint in fifteen minutes. None of it was reaching anyone else. We borrowed the second cadence from software companies and pointed it at one thing: the firm’s AI capability, in whatever form it currently takes. Today the most-shipped form is skills: markdown files that encode a consulting workflow. A year from now skills will probably be a deprecated word, bundled into plugins or whatever replaces them. The weekly cadence is the constant; the artefacts are variable.

accilium consultants sort themselves into four classes: Rookie, Apprentice, Ninja, Pioneer. Rookies consume. Apprentices use a skill on real client work and give feedback, but do not build. Ninjas test what is not yet ready for everyone. Pioneers build. We have roughly ten Pioneers in a firm of about a hundred.

That distribution is the point, not a phase we are growing out of. The model we borrowed from the AI labs is not “every consultant a builder.” It is a thin builder tier producing artefacts that fan out through a reviewer tier to a mass of users. Open-source projects work this way: most committers are not contributors, most contributors are not users, and the counts go up by an order of magnitude at each step down. A skill written by one Pioneer this Friday is, a few weeks later, how an Apprentice in Bucharest handles an RFP without thinking about it. That sentence is the whole product.

Underneath, this is skill lifecycle management: a skill is in-progress, in preview, or live, and promotion between those is metadata, not engineering.

There are three problems we have not solved. The first is pace: new tools arrive every fortnight, and consultants - like everyone else right now - feel the anxiety of things moving faster than they can absorb. The second is maturity: we are still learning what holds up, and some of what we ship breaks in real use before we catch it. The third is commercial: transforming the firm internally is one thing; helping clients run the same transformation is another, and the offer is still too bleeding-edge for most clients to buy.

The lesson, eighteen months in, is that the hard part is not the technology. The tools have got good and they keep getting better, mostly without our help. The hard part is the firm: its sequence, who builds and who consumes, what gets rewarded, what gets quietly tolerated. A consultancy is a particular kind of organisation, with particular reflexes about expertise and authority and what counts as work. AI presses on every one of those. We did not choose this; we chose to take the pressure seriously and let it change how the firm is built. The result is not finished. It will not be finished. That is the point.