You've seen the design. The photographs look right, the typography is polished, and the homepage is much better than the one you're replacing.
Then comes the familiar update: "We're nearly there."
A week passes. Another update arrives. Still nearly there.
It's not necessarily a sign that anything is wrong. A website can look complete while testing, content approval or publishing arrangements remain unfinished. Ask for the remaining tasks, their owners and the checks needed before release.
But "nearly ready" is a description of how a project feels, not a particularly useful measure of progress.
If you're trying to coordinate a launch with customers, colleagues or a forthcoming event, you need something more concrete.
A polished preview isn't necessarily a finished website
Design previews are useful because they let people understand the direction of the project.
They don't always show whether everything behind the design works.
A manufacturing company's homepage might present its capabilities beautifully while the technical downloads remain incomplete.
A professional services website might have convincing service pages but an enquiry form that hasn't been tested with the company's actual email system.
A construction business might approve its new portfolio layout before the final project descriptions have been checked by the people responsible for the work.
None of these necessarily means the project is failing.
It means the visible design and the finished deliverable are different stages.
The important thing is knowing which stage you're looking at.
Ask what remains, not how close it feels
When a supplier says a website is nearly finished, the most useful response is straightforward:
"What still needs to be completed before we can launch?"
A helpful answer identifies actual tasks and their owners.
Perhaps two service pages need factual approval, the contact form needs testing and the old URLs need redirecting.
Those are identifiable pieces of work.
"Just a few final touches" could mean any number of things.
A short list of outstanding items makes the position clear. Each item should explain what's needed, who is responsible and when it can realistically be completed.
This also protects the supplier from being pressed to launch a website that isn't ready.
Distinguish three kinds of completion
It helps to separate the project into three practical states.
Visually ready: The design direction is settled. The major layouts, imagery and typography have been reviewed.
Functionally ready: The agreed pages, navigation, forms and features work in the test environment. Content is sufficiently complete for a meaningful review.
Ready for launch: Outstanding issues have been resolved or explicitly agreed, required checks are complete, the business has approved the release and the publishing arrangements are in place.
These stages may overlap. A small website can move through them quickly. A more involved site may need separate review dates.
What matters is that an attractive screenshot doesn't automatically count as a completed project.
Give your team a practical approval job
Clients can contribute to delays without intending to.
A designer sends a preview to the managing director. It gets forwarded to sales, operations and the finance team. Everyone reviews different aspects of the site, at different times, with different expectations.
The result is a collection of comments rather than an approval.
Instead, agree who is checking what.
For a hypothetical engineering business, operations might verify the technical descriptions, the commercial director might approve service positioning, and one named person might return the final consolidated decision.
Make sure reviewers know whether they're checking design, factual accuracy or working functionality.
And don't expect a designer to settle disagreements that belong to the business.
Our article on website feedback and revisions explains how to keep approvals from becoming a continuing debate.
A launch date should have an actual definition
Before agreeing to a date, establish what "launch" means.
Does it mean the complete approved website will be available at the live domain? Will old URLs redirect correctly? Have mobile layouts been checked? Have enquiries been tested? Who will verify the site once the domain change takes effect?
A launch can also depend on access to existing hosting, domain settings or business email arrangements.
For larger redesigns, preserving search visibility and existing content may require additional planning.
These tasks shouldn't come as a surprise during the final afternoon.
Include keyboard navigation, visible focus, readable text and form labels in the review. W3C's Easy Checks for accessibility offers a useful starting point, though it is not a complete accessibility assessment.
Agree who will check the live site afterwards too. Our post-launch handover guide explains those responsibilities.
Our guide to website delivery times explores what makes a short turnaround realistic. The same principle applies to longer projects: a credible date follows from the work and dependencies, not simply from enthusiasm.
Don't confuse speed with certainty
A straightforward website can sometimes be completed in around a week when the scope is settled, content is ready and approvals happen promptly.
More complex sites need more time. The broader redesign timeline guide covers preparation, migration and review across a longer programme.
Neither is inherently better.
A short project with unclear expectations can be just as frustrating as a longer one with no visible progress.
What business owners usually need is a realistic timetable, a way to see what's completed and advance notice when something changes.
At Smartcon Works, we aim to agree those practical arrangements before production begins, including the points at which clients review and approve the work.
Because "nearly ready" is encouraging the first time.
By the fourth, a proper task list would be rather more useful.