Tool decisions
We recommend which tools to keep, which to retire, and which not to add. The reason is written down.
Fractional CTO & Technical Advisory
Fractional CTO advice on which tools to keep, a review of vendor proposals, and a check on work that is already underway. The engagement is one day a week, and you make the final decision.
The problem
Technical decisions are being made while the work is already underway. A full-time hire is more than the work requires, and a vendor proposal still needs an independent review.
What you get
A technical officer for the work in front of you, without a full-time hire.
We recommend which tools to keep, which to retire, and which not to add. The reason is written down.
A vendor proposal is reviewed against the work you need done, including whether you should own that work yourself.
Work in progress is checked against what was agreed. You are told about a gap while it is still small.
Questions that cannot wait are answered on a set day. Everything else is written down, so the week does not become a series of calls.
Who does what
An example
Which tools to use, keep or retire.
We start with the decision in front of you and what it affects: cost, time, risk and who has to live with it.
Sample: Replace the booking tool, or extend it?
Each option is set out with what it costs, what it needs and what it leaves you tied to.
Sample: Three options, cost over two years
You receive a recommendation and the reason for it, written down so it can be shared with the team.
Sample: Extend the current tool. Reason: cost and risk.
You follow it, change it or decline it. We record what was decided and why.
Sample: Decision logged
Proposals and work in progress, checked against what you need.
A proposal is reviewed Read before you sign. A vendor's proposal is read against what you need, and anything unclear or missing is listed. Sample: 4 questions to ask the vendor
Scope and cost are checked Is it what you asked for? The scope, the timeline and the price are compared with the work you actually need done. Sample: Scope covers 3 of 5 requirements
Work in progress is checked Is it on track? Work in progress is compared with what was agreed, and drift is raised early. Sample: Milestone two is a week behind
A weekly review The same day each week. One day a week is set aside for your questions, and the notes are kept in one place. Sample: Tuesday review, notes saved
What changes
You get a recommendation and the reason for it.
The recommendation concerns the work in front of you. It is not a reason to buy another product.
You receive a recommendation and the reason for it. The decision remains yours.
The engagement is one day a week. You are not paying for a full-time role the work does not require.
How it works
One working session on the decisions, then the same day each week.
We start with one working session on your current tools, your vendors, and the work that needs a review.
You receive a written note on what to change, what to leave as it is, and what it will cost if the choice is wrong.
Each week we review what has progressed, what is delayed, and what needs a decision from you.
No. It is one day a week.
Reviewing work in progress is part of the weekly day. A separate build is quoted on its own.
You do. You receive the recommendation and the reason for it.
Pairs well with
Each service works alone. These are the ones that make it work better.
Book a call or send us a message, and we will come back to you.