Technology Operator
The technology health check that ends in a plan, not a list.
Two weeks, every system in the company read, and one document at the end: what is wrong, what it costs to fix, and what to fix first. Written by the senior engineers who would be asked to do the work.
What is a technology health check?
A technology health check is a fixed review of every system a company runs: licences, network, cloud tenant and identity, core systems, reporting, and backup and recovery. It ends in a ranked list of what to fix, with the cost and order of each. Ours takes two weeks, uses AI for the reading and senior engineers for the judgement, and is written by the team that can deliver the fixes.
- How long
- Two weeks
- What is read
- Every system
- What you get
- One priced plan
Estate AI reading
-
Licences and cost5 Needs work
-
Network and remote access4 Needs work
-
Cloud tenant and identity3 At risk
-
Core systems and integrations6 Fair
-
Reporting and data4 Needs work
-
Backup and recovery5 Needs work
Findings, ranked 6
- 1 Critical Global admin held by a former contractor
- 2 High Vendor remote access that never expires
- 3 High ERP to warehouse sync failing quietly
- 4 High Board pack built on a source that stopped
- 5 High Backups run, a restore has never been tested
- 6 Medium Seats still paid for people who left
Projects Twelve week plan
-
Identity and admin clean-up 2 weeks1 security engineer
-
Backup restore test and runbook 1 week1 engineer
-
Remote access and segmentation 6 weeks2 engineers
-
ERP and reporting assessment 5 weeks2 engineers1 PMO
-
Licence right-sizing at renewal 2 weeks1 engineer
What a health check usually finds
None of these show up on a dashboard, and every company a fund owns has at least a few of them.
-
Licences paid for and not used
Seats for people who left, tiers nobody needed, and renewals that went through because nobody was watching the date.
-
Firewall rules nobody has reviewed since install
Temporary openings that became permanent, and remote access that outlived the supplier it was set up for.
-
Administrator accounts with no owner
Global admin rights held by a former contractor, a shared mailbox, or a person who changed roles years ago.
-
Reports built on a source that stopped updating
The board pack looks right because the numbers are plausible, not because they are current.
Why not ask the IT team to do it?
They should be in the room for all of it. They should not be the ones writing it, and none of these reasons is about their ability.
-
Nobody marks their own homework well
The person who set the estate up is the least able to see what is wrong with it, because every decision in it made sense to them.
-
They are one deep and already busy
A review of everything is a fortnight nobody on a small team has spare, so it becomes a quarter and then it becomes next year.
-
They have seen one estate
Ours is judged against the companies we already run, so a finding comes with how common it is and what fixing it usually involves.
-
A finding without a price is not a decision
An operating partner can act on a cost and an order. A list of concerns goes into a drawer.
What we read, and what you get
The same areas at every company, so two health checks across a portfolio can be laid side by side.
What we read
- Licences, systems and what they cost
- Network, remote access and segmentation
- Cloud tenant, identity and admin rights
- Core systems and how they connect
- Reporting, data quality and access
- Backup, recovery and who could restore it
What you get
- One document, written for an operating partner
- Every finding with what it costs to fix
- The order to fix them in, and why
- What a buyer, insurer or lender will ask about
- A readout with the people who run the company
- A plan the same team can deliver
How the two weeks run
Read access and some time with the people who run the systems. Nothing is changed while we look.
-
Start
Access and conversations
Read access to the tenant, the network and the core systems, and an hour with whoever runs each of them today.
-
Week one
Every system read
AI does the reading across configurations, licences, logs and reports, so nothing is sampled and nothing is skipped.
-
Week two
Engineers judge and price
Senior engineers decide what matters, what it costs to fix, and what has to happen first.
-
End
The readout
One document and one meeting. You leave with the plan, and the option of the same team delivering it.
What changes
The point of a health check is the decisions it lets you make in the week after it, not the report.
-
A plan with prices on it
The first hundred days start on the work, rather than on arguing about what the work is.
-
Risk you can name
The questions an insurer, lender or buyer will ask, answered before they ask them.
-
Cost out you can find
Unused licences and overlapping tools come out of the review with the renewal date beside them.
-
A baseline for the whole portfolio
The same areas at every company, so the second health check is a comparison and not another starting point.
When to run one
Each of these is a moment when the answers are about to be asked for by somebody else.
-
In the first hundred days after close
Before the plan is written, so it is written against the estate rather than the data room.
-
Before an add-on acquisition
So the platform knows what it is asking the next company to join.
-
Before an insurance renewal, audit or refinancing
The questions arrive whether or not anybody at the company can answer them.
-
Before exit
So the buyer's diligence confirms the equity story instead of discounting it.
Questions operating partners ask
What is a technology health check?
A fixed review of every system a company runs, ending in a ranked list of what to fix with the cost and order of each. Ours covers licences, network, cloud tenant and identity, core systems, reporting, and backup and recovery.
How long does a tech health check take?
Two weeks. AI does the reading across every system, so nothing is sampled, and senior engineers spend the second week judging and pricing what it found.
What do you get at the end of a technology health check?
One document: what is wrong, what it costs to fix, and what to fix first, with a readout for the operating partner and management team.
How is a health check different from technology due diligence?
It is the same method on a company you already own rather than a target you are buying. Both end in a priced plan, and both are written by the team that can deliver it.
Is a technology health check fixed price?
Yes. Fixed scope and fixed price, with no obligation to go further. You keep the report whether or not we do the work it recommends.
Does the IT team have to stop work for it?
No. It needs read access to the systems and an hour or so with whoever runs each of them. Nothing is changed while the review runs.
Who is a technology health check for?
Operating partners and management teams at private equity portfolio companies, family offices and founder-owned groups, usually after a deal, before an add-on, or before an exit.
The rest of what we run
Where to start
A two week technology health check. One document. No obligation.
Fixed scope, fixed price. It reads your systems and tells you what is wrong, what each fix costs, and what to do first. You keep the report either way.
What it turns up
- Licences paid for and not used
- Firewall rules nobody has reviewed since install
- Administrator accounts with no owner
- Reports built on a source that stopped updating
- An integration failing quietly, nobody alerted
What it reads live
- Licences, systems and what they cost waiting
- Network, remote access and segmentation waiting
- Cloud tenant, identity and admin rights waiting
- Core systems and how they connect waiting
- Reporting, data quality and access waiting
One document: what is wrong, what it costs to fix, and what to fix first.
