You’ll deal with the person doing the work.
One experienced architect, not a junior team behind a partner. The person on your first call is the person who reviews your estate.
Twenty years, both sides of the table
I’ve been the engineer, the architect, and the client paying the invoice.
I’ve built enterprise systems for twenty years — the kind of networks, servers and infrastructure that have to stay up around the clock, in businesses where downtime is measured in salary cost and in reputation.
I’ve also sat inside a regulated firm, rebuilding its whole IT estate from the inside. That’s the view most independent advisers don’t have: the invoices, the service reviews, the hardware proposals, the small decisions that quietly add up. I know where the gaps hide because I’ve been the one looking for them.
How I work
Fix the cause, not the symptom.
- Find the cause first. Slow systems and recurring tickets usually come from a few underlying problems, not many separate ones. I spend the time to find them before anyone writes a quote.
- One change at a time, measured. I don’t stack changes on top of each other. Each fix is isolated, applied, and checked against before-and-after numbers so you can see what the money bought.
- Plain English for the board. Every piece of work ends in a short written summary a non-technical director can take into a meeting. No jargon that only lands with another engineer.
- Your MSP stays the operator. I don’t take their work, their tickets or their contracts. I check their advice, review their quotes, and make sure the service you’re paying for is the service you’re getting.
Credentials
The ticket of entry.
CCIE for 14 years. MBA with distinction. Twenty years in enterprise systems architecture, infrastructure and security.
Experience includes
Next step
Find out in 15 minutes whether a review would help.
You’ll get an honest answer, even if it’s no. If it’s yes, the review can start within a week.