01 · Define the requirement through the work
We start with what needs to change
A new engagement normally starts with a business or organisational requirement.
Sometimes the company already knows what it needs. There is a project that needs leadership, a process that needs analysis, an integration that has to be built or a technical area where internal capacity is missing.
Sometimes the request is much less defined.
The company knows that something is inefficient, difficult to manage or simply not moving, but it does not yet know whether the answer is a business analyst, developer, project lead, automation specialist, AI Lead or something else.
That is fine.
Part of our work is figuring that out.
We spend the beginning of the engagement understanding what is happening, what the company is trying to achieve, who is involved, what has already been tried and where the actual constraint is.
Then we decide what capability makes sense.
This means the client does not need to write the perfect job description before we can start. In many cases, the work itself tells us what the role needs to become.
Once we have the right specialist, they work directly with management and the relevant teams. They get the access and context needed to understand the organisation and become part of the work rather than receiving isolated tasks from outside.
That context becomes more valuable over time.
A problem that looks technical may turn out to be organisational. A process issue may lead to automation. An automation may expose a problem with the data. Something that originally looked like a development project may turn out not to need development at all.
We would rather discover that before somebody has spent three months building it.
02 · Merit over visible activity
We do not measure specialists by visible hours
This is probably the part of the model that is most different from conventional consulting.
Our specialists are not expected to prove their value by filling a timesheet with activity.
We look at what they actually move forward.
Did the project progress?
Was a problem solved?
Was a decision made with better information?
Did we remove work that did not need to exist?
Did we identify that an idea should be stopped before more money went into it?
Some weeks require concentrated delivery. Other times the specialist may be waiting for a management decision, information from another team or a dependency outside their control.
Making them sit visibly inside one organisation for forty hours regardless would not improve the result.
It would improve the timesheet.
Because we work this way, one specialist can normally work with two clients at the same time. In some cases, where the required involvement is lower, that can be three.
Three is the maximum.
This only works if the capacity is real.
If one client needs most of the specialist's attention, then that specialist cannot meaningfully be embedded in two other organisations as well. We do not solve that problem by pretending the calendar contains more hours than it does.
The combination depends on what each engagement actually requires.
03 · Comparable cost, different commitment
The cost is similar to hiring. The risk is not.
We are not trying to be a cheap substitute for an employee.
A good specialist is valuable either way.
The client should expect the cost to be in roughly the same range as employing somebody with the appropriate level of experience.
What changes is the risk around that decision.
When a company hires somebody, it needs to get several things right at the beginning.
The company also provides the tools, carries the employment commitment and deals with the situation if the original assumptions turn out to be wrong.
We take on part of that uncertainty.
If the requirement changes, we can reconsider the capability.
If the specialist is no longer the right fit, that is something we have to solve with the client.
We provide the tools and professional environment around the person.
And if the client eventually discovers that the role should become permanent, they can hire based on what they have learned from the actual work rather than what they guessed six months earlier.
This is also why the model can work economically for us.
A company's need for a specialist rarely follows a perfectly flat forty-hour-per-week curve.
There are busy periods and quieter ones.
By working with a small number of clients, we can balance that capacity ourselves rather than asking one client to pay for unused time or inventing activity simply because somebody needs to look busy.
That utilisation risk belongs to us.
04 · Portfolio diversity is a constraint
We are selective about which clients we combine
There is an obvious condition attached to this model.
The same specialist should not be embedded in companies that are fighting for the same market.
We deliberately want a diverse client portfolio.
A publishing company and a property development company can have surprisingly similar technical and organisational problems while having almost no commercial conflict.
That works well.
We can take methods, technical patterns and lessons from one industry and apply them somewhere completely different without taking client-specific business information with us.
What we do not want is one specialist sitting inside two companies competing for the same customers, contracts or market share.
Even if confidentiality could technically be managed, we do not think that is a particularly intelligent foundation for a long-term relationship.
So client selection is part of the model.
We need enough diversity that the companies we work with are not competing with each other for the same business.
05 · Knowledge transfer is part of delivery
Coaching happens naturally as we work
Knowledge transfer is not something we add at the end because the proposal needed another service line.
It is already how we work internally.
Our specialists teach each other.
If somebody finds a better method, learns a useful tool, discovers a technical pattern that works or makes a mistake worth remembering, that knowledge should become useful to the rest of us.
We do the same with clients.
If we know something that would make the client's team more capable, we teach it.
Sometimes that means a workshop.
Sometimes formal training makes sense.
Sometimes it is documentation.
Most often it happens while working together: explaining why we made a decision, showing somebody how a tool works or helping them solve the next similar problem themselves.
We do not want knowledge to become a mechanism for keeping a client dependent on us.
If a client eventually no longer needs us for something because their own people have learned how to handle it, that is not a failure of the engagement.
It means that part worked.
We should remain because there is still something useful for us to contribute, not because we made ourselves difficult to remove.
06 · Boutique by design
Why we keep the consultancy small
This model would change significantly if we tried to turn it into a large staffing business.
We do not intend to.
We want to know our specialists.
We want to know the clients they work with.
We want to understand what is happening inside the engagements well enough to notice when something is going wrong or when the requirement is changing.
And we want the relationships to last long enough for that context to matter.
That means working with a relatively small portfolio of long-term clients rather than continuously adding accounts simply to increase headcount.
It also means saying no when the fit is wrong.
A new client may be commercially attractive but conflict with an existing one.
An engagement may require more capacity than we can provide properly.
Or the company may simply want a type of supplier relationship that does not fit the way we work.
That limits how quickly the consultancy can grow.
We are comfortable with that.
There are already plenty of technology consultancies designed around increasing headcount, utilisation and the number of billable people.
We are building a boutique consultancy around something different: a small number of specialists, a small number of clients, enough time to understand their organisations properly, and relationships that continue because the work remains useful.
The limitation is part of how the model works.
Choose the relevant route
The operating model is shared. The service depends on the need.
Use Coaching when the value comes from making the person already responsible more capable. Use Tech Consultation when the organisation needs additional specialist capability embedded into the work.