What this work is built on, and why.
A plain account of the beliefs that guide how engagements here are structured, what they produce, and what they do not try to be.
Back to homeWhere this practice begins
The advisory work done here grew out of a specific observation: that many companies run on shared assumptions that have never been written down, tested against evidence, or examined for the conditions under which they would fail.
That is not a criticism. Shared assumptions are how organisations function efficiently. The problem arises when significant decisions — capital commitments, direction changes, responses to regulation — are made on the basis of assumptions that have quietly aged past usefulness, or that different members of the leadership team hold differently.
The work this practice does is to surface those assumptions, examine them, and help the company build something written from them — a plan, a register, a report — that can be revised as conditions change.
Clarity over comfort
The most useful thing an adviser can do is tell a company what it does not already know, including when the picture is less favourable than expected. This practice does not soften analysis to avoid difficult conversations.
Work that holds after the engagement closes
A deliverable that requires the adviser to interpret it has not fully done its job. The goal is written work that a different member of the company's team could pick up and understand in twelve months' time.
Honesty about what is not known
Every plan rests on assumptions, and some of those assumptions may be wrong. Acknowledging that explicitly — stating which figures are measured, which are estimates, and which are guesses — makes a document more useful, not less.
What this practice is trying to do
The vision here is not complicated: that companies should make long-term decisions on the basis of written, considered analysis rather than on instinct or informal consensus — and that the capacity to do that should sit with the company's own team, not with an external adviser.
This is a narrow ambition compared to some advisory practices, which position themselves as partners in transformation. But narrow ambitions, clearly stated, are more likely to be achieved — and the companies that engage here tend to leave with something specific and usable rather than a general improvement in strategic thinking that is difficult to measure.
There is a place for broader advisory relationships. This practice is not that place. What it offers is rigour on a defined question, within a defined timeframe, for a stated fee.
The underlying conviction
Written, examined analysis produces better decisions than shared intuition, even when both point in the same direction.
The process of writing something down forces a specificity that discussion rarely achieves. Disagreements become visible. Assumptions become testable.
Specific beliefs that inform this work
On time horizons
Decisions taken today have consequences that extend further than the next reporting period
Capital commitments, hiring decisions and strategic direction choices tend to have effects that run three to five years forward. Evaluating them only against near-term performance is a form of mismeasurement. Planning work should match the horizon of the decision being made.
On written outputs
Advice that cannot be read in twelve months has limited durability
An adviser's recommendation, delivered verbally and not recorded, relies on the adviser's continued availability for its value. A written document, well structured and clearly argued, retains its value after the adviser is gone and can be revised as circumstances change.
On failure conditions
A plan that does not state when it would fail is incomplete
Every plan rests on assumptions about the future. Some of those assumptions will prove wrong. A plan that identifies which assumptions are most consequential, and what would need to change for the plan to be invalid, is more useful than one that does not — because it tells the company what to watch for.
On scope
A defined question produces a more useful answer than an open one
Open-ended advisory mandates tend to produce broad observations rather than specific, actionable analysis. Bounding the question — what is the company's plan for the next five years? what is the case for this investment? — makes it possible to answer it thoroughly rather than partially.
On dependency
The company should be more capable at close than at start
An engagement that leaves the company unable to maintain its own deliverable has not transferred enough. The sessions and working process in these engagements are structured so that the team understands the analysis, not just the conclusions.
On pricing
The fee should be known before the work begins, not after
Uncertainty about total cost distorts a client's ability to evaluate whether an engagement is appropriate. Stating the fee in full before work begins removes that distortion and clarifies what the company is deciding.
How these beliefs translate to how engagements run
Scope document
Before work begins
Every engagement opens with a written scope document: what is being addressed, what the deliverable will be, and what falls outside the engagement. This is agreed before the first session and holds for the duration.
Assumption register
During working sessions
As the engagement progresses, assumptions are recorded as they arise. At close, the deliverable distinguishes clearly between figures that are measured, figures that are estimated, and figures that are assumed. The company knows exactly where its analysis is solid and where it is approximate.
Failure conditions
In every deliverable
The final document includes a section addressing the conditions under which the analysis would not hold — changes in demand, regulatory environment, key personnel or cost structure that would require the plan or case to be revisited. This is not a disclaimer; it is practical guidance.
Working sessions
With the company's team
Sessions are structured around the company's team, not delivered to them. The analysis is built together, which means the team understands not just the conclusions but how they were reached — and can revisit them later.
Handover
At close of engagement
The deliverable is handed over in a format the company can use and revise — a written document, a working financial model, a populated register with a review schedule. The company does not need the adviser to interpret or maintain it.
Follow-up session
Included in the fee
After the team has worked with the deliverable for a period, a follow-up session is held to address questions that have emerged. This is included in the engagement fee and is not a pathway to further work unless the company finds that useful.
The company's situation is the starting point
Engagements here are not applied from a standard template. The structure of each engagement — the sessions, the format of the deliverable, the specific questions addressed — is shaped by what the company actually needs.
That requires the company to be willing to describe its situation honestly, including the parts that are not working well. The analysis is only as good as the information it is built from.
What this practice brings is a structured way of examining that situation — a set of questions, a framework for organising the answers, and experience of how similar questions have been addressed for other companies. The knowledge of the company's own situation belongs to the company.
What this looks like in practice
-
The first conversation focuses on understanding the company's situation before discussing what type of engagement might be appropriate.
-
Sessions are scheduled around the company's operational calendar rather than imposed on it.
-
The deliverable format is discussed and agreed during scope-setting — the company should understand what it is going to receive before the sessions begin.
-
Sector knowledge is brought to bear, but the final judgements about the company's direction belong to the company's leadership, not to this practice.
How this practice evolves, and how it does not
The structure of the engagements here changes when there is a good reason for it — when a format is not producing the kind of output that serves clients well, or when the field of practice has developed in ways that are relevant. It does not change in response to fashion or because a new methodology has acquired currency.
The horizon table — the three-column framework mapping what changes within three months, within a year, and beyond — was developed to address a specific problem: that planning documents often conflate near-term actions with long-term direction, which produces confusion about what to prioritise and when. It has been retained because it continues to address that problem.
The follow-up session, included in every engagement, was added after early engagements showed that the most useful questions often arose not during the working sessions but after the team had spent a few weeks applying the deliverable. Including it at no additional cost was a practical response to that observation.
Changes like these are made when they improve the work. Changes that would make the practice more visible, more scalable or more appealing to a broader market are evaluated separately from whether they would improve the work — and usually set aside.
On honesty and what it requires
About the analysis
If the analysis produces a conclusion the company does not want to hear — that the investment case does not hold, that the plan rests on an assumption that is probably wrong — that conclusion is reported clearly rather than softened. An adviser who modifies findings to suit the client's preferences is providing comfort, not analysis.
About the limits of the engagement
If a company's question is outside the scope of what these engagements address, that is said clearly rather than attempting to fit it into an existing format. Not every company that contacts this practice is a fit for these engagements, and saying so is more useful to the company than proceeding regardless.
About uncertainty
The future is not predictable and no planning document should imply otherwise. What a written plan can do is make the company's current best judgement explicit, document the assumptions behind it, and provide a basis for revision when those assumptions change. That is more valuable than a confident forecast that turns out to be wrong.
Working with the company, not for it
The distinction between working with a company and working for it is not merely a point of style. It has practical consequences for the quality of the output.
When the analysis is developed jointly — when the company's team is present for the thinking, not just the conclusions — the deliverable reflects knowledge the adviser could not have accessed alone. The team's understanding of the company's history, its relationships, its actual operational constraints, is information that does not appear in a briefing document but shapes every useful recommendation.
It also means the team understands the deliverable well enough to maintain it. A plan built by an external adviser, then handed over as a finished document, is often understood only at the level of its conclusions. A plan built with the team — session by session, assumption by assumption — is understood at the level of the reasoning.
That understanding is what allows the company to revise it correctly when circumstances change, rather than treating it as a fixed document whose conclusions apply regardless of what has happened since it was written.
Why this practice is organised around the long view
The name of this practice — Mast Core Lab, meaning ten thousand years — is deliberately excessive. No company plans on a ten-thousand-year horizon. The name is a statement of orientation: toward the far end of the time horizon rather than the near.
The reason for that orientation is practical, not philosophical. Most of the decisions that determine whether a company is in a good position in five years are made in the preceding three. Capital commitments, talent decisions, market positioning choices — these have consequences that compound. Attending to them carefully, and early, tends to produce better outcomes than addressing them under pressure.
The horizon table structure
0–3 months
Immediate actions, early signals and first decision points
3–12 months
Commitment decisions and resource allocation choices
1–5 years
Direction, position and the compounding effects of earlier decisions
Every engagement maps the question across these three frames to clarify when effects appear and what must be decided now versus later.
What these principles mean for a company engaging here
Practically, working with this practice means you will be asked more questions than you might expect — not to justify the work, but because the analysis is only as good as the information it is built on.
It means the deliverable you receive will include things the analysis cannot confirm — stated explicitly as estimates or assumptions rather than presented with equal confidence to the measured figures.
It means the engagement will close on schedule, the deliverable will be yours, and the follow-up session will be held without any pressure toward further work. If further work would be useful, that conversation is available — but it is not assumed.
You will receive
A written deliverable your team can use and maintain
Analysis that distinguishes clearly between what is known and what is assumed
Honest conclusions, including ones that complicate the picture
A follow-up session at no additional cost
You will not receive
Ongoing advisory presence after the engagement closes
Analysis modified to confirm what you already believe
Recommendations that require the adviser to interpret them
If this approach seems suited to what your company needs
The first step is a conversation. There is no obligation attached to it and no expectation that it leads to an engagement. If the question you are working on is a fit, the scope and fee can be agreed and work can begin on a schedule that suits your team.