PROOF — ONE ENGAGEMENT
Sixteen years. Eleven sites. Under two days a week.
One mining company, one small senior practice, from 2009 to 2025. This is what a fractional engagement looks like over the long run. Every number on this page comes from our own records.
THE POINT OF FRACTIONAL
The goal is a team that needs us less over time, not more. The record shows it happening.
In 2017 the record shows 170 incidents, the most in any year. In 2018, the busiest year of the sixteen by hours, a third of the work went into documentation, monitoring and automation. Incidents fell to 83 that year, then 55, 54 and 41. The busiest year had half the incidents of the year before it.
Incidents per year
Hours on documentation, monitoring and automation
| Year | Incidents | Foundation hours |
|---|---|---|
| 2014 | 55 | 22 |
| 2015 | 128 | 22 |
| 2016 | 167 | 84 |
| 2017 | 170 | 239 |
| 2018 | 83 | 504 |
| 2019 | 55 | 174 |
| 2020 | 54 | 126 |
| 2021 | 41 | 67 |
| 2022 | 16 | 0 |
| 2023 | 42 | 44 |
| 2024 | 75 | 245 |
| 2025 | 90 | 270 |
When one site went back into a build phase in 2024, incidents rose with it. Unplanned work tracks change, and the record shows where.
HOW THE WORK IS KEPT
Ask why something was done fourteen years ago, and the answer is retrievable.
4,459
dated entries: what was done, and why.
180
devices named individually in the record.
Since year two
configuration backup, running continuously.
Why a route pattern exists at one site. Why a management network differs at another, because of how it was first cabled. Which vendor defects were chased and closed as unfixable. The answer has never been more documentation. It is capturing why while the why is still known, so when people move on, the thinking does not leave with them.
A site can go quiet for four years, fail, and be diagnosed the same week, because whoever picks up already knows what is installed there.
Continuity is not a faster queue. It is a shorter path to the person who remembers.
NO ENGAGEMENT TEAM
Strategy to the firewall policy that implements it. No layers, no ramp.
2.3%
of all hours on planning and coordination, across sixteen years.
10
technology domains, from routing to industrial systems to automation.
16
years without a ramp or a re-brief. The context stays with the work.
No account management, and no meetings held for their own sake.
WHEN SOMETHING BREAKS
We have never offered an SLA. The record shows when the work happened.
94%
of 195 months with work logged.
11.4%
of all hours fell on a Saturday or Sunday.
24.8%
of hours in the time-record years began before 07:00 or after 18:00.
No contract required any of it. Clients call when something is on fire, and we pick up.
ABOVE ITS WEIGHT
The team you have can operate well above its weight without growing.
24 h → 922 h
automation work, the first five years against the eleven since.
4.2% → 12.4%
share of effort on documentation and standards, then and now.
11
sites across several countries, at a fraction of a week.
The constraint is no longer how many hands you have. It is the quality of the thinking directing them.
Fractional is how you get access to this alongside the team you already have.
This is how every engagement is kept: the decisions, the reasoning and the work behind them, connected. It is what a monthly commitment gets sized from: levels a client has already lived through, not a forecast.
BOOK A CALL →Figures are drawn from our own monthly reports and time records for one client engagement, 2009 to 2025. The client is not named.