Planning a website project: scope, timeline and who updates it after launch

A new website is one of the most visible projects a business takes on. It is also one of the easiest to underestimate. Most website projects that go wrong do so long before design begins, in unclear goals, shifting scope or a platform nobody can update. Here is how to plan one well.
Start with goals, not pages
Before thinking about layouts, write down what the website must achieve. For example:
generate enquiries or bookings,
sell products online,
recruit people,
explain a complex service clearly,
support existing customers.
Each goal shapes the structure, the content and the calls to action. A site built to sell needs a smooth checkout; a site built to generate leads needs clear paths to contact you.
Define the scope in writing
Scope is everything the project includes. Agree it early and in writing:
Pages and templates: which pages exist, and which share a design.
Features: forms, booking, e-commerce, search, member areas, multiple languages.
Integrations: CRM, ERP, payment gateways, shipping, analytics.
Content: who writes the copy, who supplies photos, and when.
Content is the most common cause of delay. Decide early who owns it.
Set a realistic timeline
Timelines depend on scope. As a guide from our own projects:
a basic business website takes around 3 to 4 weeks,
a custom corporate website around 6 to 8 weeks,
an e-commerce store around 8 to 12 weeks.
A good plan breaks this into stages, typically discovery, design, development and testing, with milestones you can review.
Choose a platform your team can actually use
The best platform is the one that fits your goals and the people who will maintain the site. Options include Wix Studio, Webflow and WordPress, or a custom build with React or Next.js when you need more flexibility.
Ask two questions:
Who will update the site after launch, and how technical are they?
How much do we expect to grow, in pages, features and traffic?
A site built on a user-friendly CMS lets your team change text, images and content without technical skills. Make sure training and documentation are part of the project.
Make it SEO-ready from day one
Search visibility is much easier to build in than to bolt on. Every new site should have:
clean code structure,
fast load speeds,
a fully responsive design for phones, tablets and large screens,
optimized images,
unique page titles and meta descriptions,
structured data (schema markup).
If you are replacing an existing site, keep your current URLs where you can, or set up redirects, so the rankings you have already earned carry over.
Plan for launch, and for the day after
Before launch, test every page on real devices and browsers, check every form and link, and confirm analytics is working. After launch, plan who handles updates, fixes and improvements. A website is never really finished; it should improve as you learn from your visitors.

Who should be involved
A website touches many parts of a business. Involve the right people early:
A decision-maker who can approve scope, budget and design.
A content owner responsible for copy, images and accuracy.
Sales or customer service, who know the questions customers actually ask.
Whoever will maintain the site after launch.
Fewer, clearly responsible people usually move faster than a large committee.
What drives the cost
Every project is different, but the main cost drivers are predictable:
Number of unique templates, not just the number of pages,
Custom features such as booking, member areas or calculators,
E-commerce, including payments, inventory and shipping,
Integrations with CRM, ERP or other systems,
Content creation, if copywriting, photography or video is included,
Multiple languages.
Agreeing priorities early lets you launch with what matters most and add the rest in later phases.
Make it accessible
An accessible website works for more people, including those using screen readers, keyboards or zoom. Good practice includes:
clear headings in a logical order,
enough colour contrast for text,
descriptive alt text for images,
visible focus states for keyboard users,
labels on every form field,
touch targets large enough for phones.
Accessibility also tends to improve usability and search visibility for everyone.
Common mistakes to avoid
Designing before the content exists. Layouts built around placeholder text often break when real content arrives.
Adding features late. Late additions are the most common cause of missed deadlines.
Forgetting mobile. Many visitors will see your site on a phone first; design and test for it from the start.
Launching without redirects. Moving or renaming pages without redirects can lose hard-earned search rankings.
No plan after launch. A site with nobody responsible for it quickly goes out of date.
Measure what matters
Set up analytics before launch and decide which actions count as success, such as enquiries, bookings, sales or downloads. Review them regularly and use what you learn to improve pages, calls to action and content.
Write content that helps visitors decide
Good website copy answers the questions visitors arrive with: what you do, who it is for, why you, and what to do next. Keep it plain and specific:
lead with the outcome for the customer, not your internal process,
use short paragraphs and descriptive headings so pages are easy to scan,
give every page one clear next step, such as a consultation or a call,
answer common questions directly, for example in an FAQ section,
keep facts, prices and contact details accurate and up to date.
Real photos of your team, your work and your workplace build more trust than generic stock imagery.
Plan for growth
Think about where the site needs to be in two or three years. Will you add services, locations, languages, a blog or an online shop? A sensible structure and a flexible platform make those additions straightforward instead of forcing a rebuild.
How we approach it at NEXAR
We start with discovery and analysis of your goals and audience, plan a clear site structure, design user-centred layouts and build with clean, SEO-friendly code on the platform that suits you, then test on every device before going live. We also train your team so you can manage the site with confidence.
See our Web Design & Development service, or send us your brief.
Recent Posts
ERP or CRM first? How to pick the system your business needs now
ERP runs your operations; CRM runs your customer relationships. How to tell which one your business needs first, and how to roll it out with less risk.
Native or cross-platform? Choosing how to build your mobile app
Swift and Kotlin or Flutter and React Native? A plain-English guide to choosing how to build your iOS and Android app, and when an MVP comes first.

