The go-live moved twice. The consultants have gone quiet, or they’re still emailing but nothing is changing. Nobody in your building can say with confidence what’s actually configured versus what’s still a promise in a scope document. We take these over, and the first thing we do isn’t technical.
Inventory before decisions
Before you can decide whether to restart, replace the vendor or repair what’s there, you need to know what’s there. That’s an inventory problem, and most people skip straight to “let’s start over” because nobody has done it. We go through scripts and workflows (deployed, and deployed-but-not-active), saved searches and reports, bundles and SuiteApps, custom records and fields, and compare it to what the SOW says. The triage guide is the checklist we use, published so you can run it yourself.
Get access, in writing, today
If nobody on your side has full administrator access to production and every sandbox, that’s the first fix, and it’s a contract problem, not a technical one. We’ll help you ask for it properly.
Then one of three paths
- Repair: what’s built is mostly right and needs finishing. Usually the cheapest, and more common than people expect.
- Restart parts: keep the configuration that works, rebuild the pieces that don’t, document the boundary.
- Replace: rarely the answer, and we’ll say so if it is.
We also run implementations end to end, and the same people do both — Renee on the finance and operations side, David on commerce and web. Who you’d be working with.
The first hour is free. Bring us the thing that’s been bothering you and we’ll spend an hour on it with you, in your account, and send written notes afterward whether or not you hire us.