Stage 1 · Both accounts
The team's and the report's.
Four services, independent of every supplier and scoped to end.
We talk to the people doing the work rather than only the people reporting on it, because those two accounts of a project are rarely the same. The report gives a plain verdict with the reasoning, and sometimes that verdict is to stop — which is unwelcome, cheaper than continuing, and the reason an outside view is worth paying for.
The team's and the report's.
Realistically, not optimistically.
Finish, rescope or stop, costed.
Plainly stated, with reasons.
Agreed before starting.
The things actively causing harm.
As we go, not at the end.
To the permanent hire.
Interim work has one failure mode: becoming permanent by accident. Every engagement has an agreed end date and a handover deliverable from day one, and we document as we go rather than holding knowledge that makes us hard to replace.
Organisations routinely cannot say who holds their domain, their code repository or their administrative credentials until they try to leave a supplier. We inventory all of it with the renewal dates, and flag where you do not own something you assumed you did. Whether a contract term is enforceable is a question for a solicitor.
Every supplier, cost and renewal date.
Domains, repositories, credentials.
What you assumed and do not own.
Legal questions to solicitors.
Written for the person arriving.
Suppliers, systems and risks.
Short and deliberate.
On the date agreed.
The measure of an interim engagement is whether the organisation is less dependent afterwards. We write the documentation an incoming manager actually needs, induct them properly, and then leave on the agreed date rather than finding reasons to stay.
A free first call, and an honest answer — including that you may not need us.