Someone senior to own the decisions, for as long as you need one.
If your IT works but nothing progresses, that is usually a leadership gap rather than a technical one. I fill it by the day.
You will recognise one of these
IT works, but nothing moves forward
Tickets get closed and renewals get signed, but the same questions come back to every board meeting because nobody owns the answer.
A written picture of what you have, what it costs and what is about to expire. Two weeks, and it usually pays for itself in the renewals it catches.
A system decision you cannot afford to get wrong
A CRM, a finance system, a move to the cloud. Every supplier in the running sounds convincing, and none of them will be there when the migration goes sideways.
Requirements written from your processes rather than a supplier's feature list, then a shortlist you can defend to trustees. If iMIS is on your shortlist, I may have a contracted restriction that affects whether I can work with you independently: easier to explain in conversation than in a paragraph here.
Support that closes tickets but never fixes causes
The same faults keep returning, the contract renews on autopilot, and nobody is asking why the underlying problem is still there.
Read the last six months of tickets, find the three causes behind most of them, and fix those first.
A gap where your IT lead used to be
Someone has left mid-project and recruitment will take months. The team needs a manager and the projects need someone holding the scope.
Cover from the following week, and a handover document your permanent hire will thank you for.
A day a week is usually enough. Half of it is decisions, half of it is making sure last month's decisions actually happened.
- Basis
- Retained monthly or by project
- Commitment
- Half a day to three days a week
- Where
- Remote-first, London & the South East
- Notice
- One month, either way
- Rate
- On request
Describe the situation and I will tell you what I would do first.
Half an hour, no charge, no proposal deck.