Two weeks. Fixed price. A document you own.
Every engagement starts here — and it stands on its own. Most of the value is in knowing exactly what you're running on, whoever ends up doing the work.
The terms
Nothing we do can take your system down.
Two on-site days, the rest remote. We read, we copy, we ask. The system keeps running and your team keeps working.
Week one — on site
We watch the work.
Order desk, warehouse, and back office at the busiest hour of the day. What the software is really used for.
Server, backups, network, licences. We attempt a live restore from your most recent backup.
Data and code read remotely: schema, record counts, and the pricing and ordering rules buried in the source.
Week two — remote
We write it down.
Risk register: every failure point, ranked, with what it would cost you the day it happens.
Options priced: keep and stabilize, migrate in phases, or move to a named package — with the case for each.
Draft to you. You read it before it's final and tell us where we've misread the business.
Final report, walked through in ninety minutes with whoever you want in the room.
The deliverable
Seven sections. About thirty pages.
Written for an owner, not an engineer — with the technical appendix an engineer needs to act on it. Delivered as a PDF and an editable document, both yours.
Vendor-neutral clause
Where a packaged system is the better fit for cost, timeline, or risk, this report says so — by name.
What the system is, and what it does for the business
Risk register, ranked, with the cost of each failure
Data inventory: what's inside, what's recoverable, what isn't
The rules that run the business — documented, or flagged as unknown
Options priced: stabilize, migrate, or move to a named package
Our recommendation, with the reasoning attached
Technical appendix, for whoever does the work
Know what you're standing on.
Thirty minutes on the phone first. We'll tell you whether an assessment is worth your money.
A small, steady light that shows up when it gets dark.