A clear brief, agreed milestones and a useful handover.
What happens after the review?
We clarify the outcome, identify the highest-value priorities and agree the next step. The opportunity review is human-led; it is not an automated website score.
You do not need a complete specification to start a conversation. Bring the problem, the people affected and the outcome you want. If you have a current website, include its address. If you do not, describe how enquiries or tasks are handled today.
The initial review helps identify priorities and unanswered questions. It is not a promise of an automated score, a completed quotation or a booked appointment. Those outcomes require the relevant review, agreed scope or confirmed booking step.
Avoid sending passwords, confidential customer data or private documents in the first message. Describe the systems involved and arrange access separately if it becomes necessary. A short, clear example of the task is often more useful than a large unsorted folder.
How long does delivery take?
Timing depends on the approved scope, content, integrations and decision-making. Milestones and responsibilities are agreed before production; there is no universal delivery promise.
Timing depends on more than implementation. Content approval, design decisions, integrations, migration and testing all have owners and dependencies. Discuss the date you are aiming for, why it matters and which parts of the first release are essential.
A delivery plan should show review points and what is needed from each side. Agree how feedback is consolidated and who has authority to approve a stage. If a dependency changes, review its effect on scope and sequencing rather than silently compressing the testing period.
Ask how progress and decisions will be recorded. Shared acceptance checks help everyone distinguish between something that has been built, something that has been tested, and something ready to release. Those are related milestones, not interchangeable claims.
What should I prepare?
Your goals, current website if one exists, relevant systems and the people who will approve work. The project planner helps you capture a brief and keep a local copy. When approved adapters are configured, it can submit that brief and continue to real consultation availability; receipt or booking is shown only after provider confirmation.
Prepare a concise description of your organisation, current tools, intended audience and desired outcome. Add any known constraints such as a launch event, required integration or internal review process. Mark uncertain information as a question rather than guessing.
The planner helps organise that information into a brief. Review it before submitting and retain a copy for your records. A downloadable brief is not evidence of delivery: rely on the confirmation shown after the configured submission service has accepted the request.
Booking is a separate confirmation. Choose only from availability supplied by the connected provider, and look for a confirmed outcome before assuming the time is reserved. If booking or submission is unavailable, use the contact route and explain what you were trying to arrange.