How long it takes
Real timings, including the waiting
These are elapsed weeks, not billed days. The gap between the two is where most estimates quietly mislead.
| Stage | Elapsed | Notes |
|---|---|---|
| First chat to review starting | 1–2 weeks | Depends on our diary, which we will tell you honestly. |
| The review and written summary | About 1 week | A focused conversation, a few follow-up questions, then a short summary you keep. |
| First tool working | 3–8 weeks | From a signed scope. The range is mostly about how tidy your information is. |
| Handover complete | + 1–2 weeks | Training and instructions, included. |
The three things that make it run late
Getting access
The most common cause of a late project. If we cannot get into your systems, we cannot connect them. We give you a short list on day one so it can start moving before we do.
One person who knows everything
Most small businesses have one. They are also the busiest person in the building. Book some of their time before the project starts rather than discovering the problem in week three.
Scope that grows because it is going well
A happy reason to run late. We will still tell you it is happening and quote it separately, rather than quietly absorbing it and delivering everything a month late.