Testing takes three days for a single flow, about a week for a full website or app, and up to two weeks for a large product with accounts and payments. Add time for your developers to fix what we find, then a day for retesting.
The mistake most teams make is not underestimating the test. It is forgetting the fix window.
The timeline in full
| Scope | Testing | Your fixes | Retest | Total |
|---|---|---|---|---|
| One page or one flow | 3 days | 2–3 days | 1 day | ~1 week |
| Full website or app | 7 days | 4–7 days | 1 day | ~2 weeks |
| Large product, accounts and payments | 14 days | 1–2 weeks | 2 days | ~4 weeks |
Work backwards from your launch date using the total, not the testing column.
Why the fix window is the part people forget
We hand over a report. It contains, say, 30 issues. Six are critical.
Your developers now have to read it, reproduce each issue, fix it, and not break something else while doing so. That is not an afternoon. For six critical bugs in unfamiliar areas, it is most of a week.
Then the fixes need retesting. Not just the six — the areas around them. Fixes cause regressions. That is not a sign of bad developers; it is a property of software.
If you book testing to finish the day before launch, you have booked a report you cannot act on.
What makes it take longer
Nobody is available to answer questions. A tester hits something ambiguous on day one. Is this a bug, or is it meant to work that way? With an answer, five minutes. Without one, the question sits in a list until someone replies, and the whole schedule drifts.
The environment is unstable. If the staging site is being deployed to while it is tested, half of what we find will be noise. Freeze the build.
Test accounts do not exist. Testing a seller dashboard requires a seller account with realistic data. Creating that ourselves takes hours we could spend testing.
The scope grows. "While you're in there, could you also look at…" is how a one-week engagement becomes three.
What makes it faster
Send these before day one:
- A frozen build on a stable URL
- Working test accounts for every user role
- Test card details for payment flows
- A note listing the three things you are most worried about
- One person who can answer questions the same day
That last item saves more time than everything else combined.
Can it be done faster?
Sometimes. Urgent work is possible, and a single critical flow can be checked in a day.
But compressing a two-week scope into three days does not make it faster — it makes it smaller. You will get a shallower pass with the same name on it. If someone quotes you a full product audit in 48 hours, ask them exactly what they will not be doing.
Working to a launch date? Our packages list turnaround times up front — three days, seven days, or fourteen.