How It Works
One flat monthly fee. The first month is the assessment. Every month after that is your decision.
Most businesses have been burned by open-ended consulting: a discovery phase that never ends, a report nobody reads, an invoice that grows. This engagement is built to be the opposite of that. There is no hourly rate, no timesheet and no overage. You know the number before the month starts, and it is the same every month.
We talk about the problem, not the technology
A conversation about where information gets lost in your business: what the people doing the work know that the office doesn't, what gets entered twice, what gets emailed around instead of routed, what leadership can't see until it's too late. If I don't think I can help, I'll say so and point you somewhere better. Before any detail is shared, we sign a mutual NDA, yours or mine. Email me and we'll find thirty minutes; free, on Teams or by phone.
A working prototype and a plan, at the ordinary monthly fee
The first month maps where your operational data lives, where it leaks, and what it costs you. It ends with a working system connected to your real data, running in your own accounts (your Microsoft 365 subscription if you have one, or a custom application in your own cloud account where that fits better), and a roadmap for everything else with cost ranges against each item. You can put the prototype in front of your team and try it.
It costs the same as every month after it. There is no separate assessment fee, because a first month priced differently from the rest is a number that needs explaining. If the finding is that the sensible thing is to wait, or to stop, that is what the session will say. You keep everything either way.
Stop, or keep going
At the end of month one you have three options, and all three are fine: stop here and keep everything that was built; take the roadmap and implement it with your own people; or continue month to month. To stop, you give ten days' notice before the next month begins and the next month is never invoiced. If I end it, I give you thirty. The prototype, the documentation and every finding are yours regardless. They live in your accounts and stay there.
A priority list, not a timesheet
Each month starts with a single page listing the work in priority order, agreed together and worked from the top down. If something new comes up it goes on the list and something else moves down; that trade is visible and it is your call. Small things (a question, a fix, an adjustment) are absorbed without discussion. Training on everything I build is included, and so is every AI and development tool I use. You get written notes after each session and a one-page summary at the end of each month, which is where the accountability lives when nobody is counting hours.
Retained support, so you never need an IT hire
Once the system is built you can withdraw cleanly, at no cost, with a full handover inside thirty days. Or I stay on at a much smaller flat monthly fee to watch it: every business day I review the system's own overnight audit, fix what is small, and tell you the same day about anything that is not. A short session and a one-page health note each month. No new builds. For a company that does not have, and may never want, a full-time IT role, this is the alternative to hiring one.
The commitments that hold at every stage
You know the price before the month starts
One flat fee, invoiced ten business days before each engagement month and due on or before its first day. A month is thirty days from the day funds clear, never prorated. Nothing is billed by the hour and nothing is invoiced that you did not already know about.
Everything is built in your accounts
Your data, your subscription or cloud account, your access controls. Your data is never used to train anyone else's model. I hold delegated access you can revoke in one click. If we part ways, nothing has to be migrated, exported, or ransomed back.
Paper before access
NDA before discovery. Master services agreement and a signed statement of work before any paid work. A written data protection addendum and security protocol before I touch a system. Procurement teams get what they need without asking.
The report can say "don't hire me"
The assessment is priced so that its honest answer has value on its own. If the right recommendation is a process change and no software at all, that is what the findings will say.
Start with the conversation
Tell me where the gap is: between what you assumed when you priced the work and what it actually cost, or between what's happening on the ground and what you can see. That's the whole first step.
Not ready to talk? Take the first look instead: six taps, one page, no email needed.