Your launch date moved for the third time. Here is the one document that stops it.
When a software project keeps slipping, the problem is rarely the code. Nobody wrote down what “ready” means.
A year ago, you signed the contract for a new system to run your company. The launch date was March.
In March, the software company asked for two more months. “A few adjustments left.” Then it was July. Now they are talking about January.
Each time, the reason sounds fair. Each time, your team keeps working out of spreadsheets while they wait. And each time, you sense something is off, but you don’t know what to ask.
What is actually going on
Nobody wrote down what “ready” means. Without that definition, there is always one more adjustment, one more feature that would be nice to have before go-live, and the date keeps sliding. The vendor isn’t necessarily acting in bad faith. They are aiming at a target that doesn’t exist.
The fix: a launch-day list
This week, ask for one thing in writing: a short list of what must work on launch day. Keep it concrete and operational:
- Send an invoice.
- Ship an order.
- Close out the day’s cash.
- Pay a supplier.
Your operations lead signs the list, not the software company. Everything that isn’t on it moves to a second phase, with its own date.
How this usually plays out
Consider a typical case: a food distributor fourteen months into a new operations system, with the date moved three times. Building the list takes one morning with the people who run the operation. It usually comes to ten or twelve tasks. Once the vendor has a fixed target, those tasks get done in weeks, not quarters, and the company launches with a short list of small items logged for later.
Asking for the list is not distrust. It is your job as the owner.