The engagement
Strategy and implementation. No retainer. No dependency. No reason to keep calling.
Here's what's actually broken.
You have probably tried to fix this before. A new tool here. A contractor there. Maybe a consultant who delivered a report you never fully implemented. And yet the problems are still there - the manual workarounds, the disconnected systems, the IT costs that nobody can quite justify.
Every engagement runs for exactly three months. Fixed fee. Three equal payments. A hard stop at the end. The goal is simple: you finish with systems that work, a team that understands them, and no need for ongoing outside help. This is a defined piece of work with a beginning, a middle, and an end.
Four phases. Twelve weeks. One outcome.
Audit
Weeks 1–2Before anything gets fixed, you need to know what you actually have. Most businesses your size have never had a proper audit. Tools get added, licences get renewed, and nobody ever maps it all together. Every tool. Every licence. Every integration point. The output is an honest picture of where you stand - not a sales document for more work. You will see the unused licences, the duplicate systems, and the manual processes that should have been automated years ago. Whatever happens next, that document is yours to keep. The deliverable is an honest picture of your technology - written down, specific, and yours to keep regardless of what comes next.
Prioritise
Weeks 2–3Technology decisions that are not grounded in the business problem are just expensive guesses. This phase is where your priorities drive what gets built - not the other way around. You will know exactly what the engagement will deliver before a single hour of implementation begins. No surprises. No scope that quietly expands. You agree on what success looks like, and that is what gets built.
Build
Weeks 3–11This is where the real work happens. Systems that currently operate in isolation get connected. Manual, repetitive processes get automated. Software spend gets rationalised. Reporting gets built so you can actually see what is happening in your business. Your team is involved throughout. This is knowledge transfer, not a black box. You will see progress as it happens - not a finished product that appears at the end. Where the foundation supports it, AI gets introduced - not as a trend, but as a tool that earns its place.
Hand over
Week 12Everything handed over. Everything documented. Your team trained and ready. The documentation is written clearly enough that someone else could pick it up tomorrow. Thirty and ninety day check-ins are included. After that, you are on your own - which is the whole point.
Here is what is different twelve weeks from now.
A clear picture of your tech spend
Every tool, every licence, every line item mapped against what is actually earning its place. No more renewals on autopilot. No more paying for software nobody uses.
Systems that connect to each other
Your tools will talk to each other and to how your business actually runs. Data flows where it needs to go without someone copying it between spreadsheets.
A team that knows how to use what has been built
Training is built into every phase, not bolted on at the end. Your people will understand the systems they are using and why they are set up the way they are.
Documentation so someone else could maintain it tomorrow
Every decision, every configuration, every process written down. If you hire an IT person next year, they will be able to pick up without a single call back.
Measurable before and after outcomes
What matters gets measured before the start and again at the end. The results are specific, not vague. You will know exactly what changed and by how much.
No new dependency created
The goal of every engagement is to leave you needing less outside help - not more. You are not starting a relationship that requires ongoing fees. You are building self-reliance into your business.
Pricing
Three equal payments: on signing, start of month two, and on completion.
The fee covers the full three-month engagement including post-engagement check-ins at 30 and 90 days.
Pricing is published because it saves everyone time. If it doesn't fit your situation, that's useful to know now rather than three meetings from now.
The engagement ends at three months. That's not a policy - it's the whole point.
Most advisory relationships drift. Scope expands. Timelines extend. What was supposed to be a fix becomes a permanent fixture. Before long, the outside help is a cost centre the business cannot operate without. That is the opposite of what you need.
A fixed end date forces clarity. It forces prioritisation. It means every hour is focused on building something that lasts - not on finding reasons to continue. If three months is not enough time to make a meaningful difference, the problem is not the timeline. It is the approach.
Every hour of this engagement is focused on building something yours. Due to the personal nature of the work, only three engagements run per year. By application.