Make the next step clear
Good websites start with good questions.
The exact steps depend on the work. A small repair and a new website need different plans, but both benefit from a shared understanding of the problem, the scope and how success will be checked.
01 / Tell the story
Share what your business does, what your website needs to achieve and what is getting in the way. Existing pages, examples, deadlines and constraints make the first conversation more useful.
02 / Agree the scope
Define the work, deliverables, responsibilities, cost and review points. Identify the content and access needed, the things outside the scope and the checks that will support acceptance.
03 / Design, build and review
Use the agreed direction to develop the site or repair. Review work at appropriate points, connect feedback to the original goals and make any scope changes explicit.
04 / Check the complete path
Review the actual visitor tasks, content and key technical behavior. A launch plan should include the public pages, inquiry route, access needed for deployment and a way to recover if a release goes wrong.
05 / Hand over and keep learning
Agree who owns the accounts, content and ongoing tasks. Review the available evidence after launch, separate observations from assumptions and decide what deserves attention next.
Explore ongoing website careWhat should be checked before a website goes live?
Start with the customer tasks agreed in scope. Verify the important pages and links, readable layouts, keyboard access, contact route and error messages. Review public names, services, contact details and search metadata against the approved content.
- Check the real deployment address and redirects, including what happens at a missing page.
- Confirm that private records and access credentials are outside public files.
- Verify the agreed contact or transaction path using an authorized test.
- Name the release, remaining limitations, responsible account owners and recovery procedure.
How long will the project take?
Timing depends on the scope, content readiness, integrations and review availability. A targeted repair and a new website need different plans. Agree on milestones after those dependencies are understood, and make the effect of delayed content or new requirements explicit. No fixed delivery time is promised before that review.
Link to this answerYou can start without all the answers
The project brief is a starting point, not a contract. Describe the goal in your own words. Details that are still undecided can be worked through during scoping.