How to Plan a Website Before Development Begins

The single most common reason website projects run over time and over budget is not that the designer was slow, or the developer made mistakes, or the technology was too complex. It is that the project started before anyone truly understood what they were building — and why.

When requirements are vague, every decision gets revisited. A page gets designed one way, then the client sees it and remembers something they forgot to mention. A feature gets built, and then it turns out there was a policy or a workflow that changes everything about how it should work. These are not failures of execution — they are failures of planning. And they are almost entirely avoidable. The planning stage is where the most valuable work of a web project happens, and yet it is almost always the most rushed.

The framework below is what I walk through with every new client before a single wireframe is sketched or a line of code is written. It is not a bureaucratic process. It is a short series of focused decisions that pay for themselves many times over by the time the project reaches launch.

Step 1 — Define Your Goal Clearly

Before anything else — before colours, before page count, before technology — you need to answer one question honestly: what is the single most important action you want a visitor to take on this website? Not a list of five things. Not a general idea like “learn about us.” One specific, measurable action. Book a consultation. Request a quote. Purchase a product. Download a guide. Subscribe to a newsletter. That one goal should drive every design and content decision that follows. If you cannot name it in a single sentence, the project is not ready to begin.

The reason specificity matters so much is that your designer and developer cannot optimise for a goal they do not know. When the primary goal is clear, it shapes where the call-to-action button appears, what information lives above the fold, how the navigation is structured, and which pages deserve the most attention. A website that tries to serve five equally important goals will serve none of them well. Narrow your focus deliberately, not by accident, and the entire project becomes easier to scope, easier to build, and easier to measure once it goes live.

“A website without a clear goal is just an expensive brochure.”

Step 2 — Know Your Audience

Your website is not for you — it is for the people who will visit it. This sounds obvious, but it is the source of a surprisingly large number of design and content mistakes. Business owners tend to fill their websites with information they are proud of rather than information their visitors are looking for. Before you write a single word of copy or choose a single image, spend time answering: who is this person? How old are they roughly? What problem brought them to your site? How technically confident are they? Are they comparing multiple providers, or have they already made up their mind and just need reassurance? What device are they likely using — a phone on the morning commute, or a desktop in an office?

Beyond demographics, think about the emotional journey of your visitor. Someone visiting a law firm’s website is likely anxious. Someone visiting a wedding photographer’s website is excited. Someone evaluating a software tool is sceptical and cautious. Trust signals — testimonials, case studies, recognisable clients, certifications — matter enormously, but they need to be the right kind for your audience. A consumer audience responds to reviews and relatable stories. A corporate buyer responds to data, guarantees, and proven process. Design your website around the visitor’s psychology, not your own preferences, and you will immediately have an advantage over competitors who have not thought about this at all.

Step 3 — Map Your Pages

Once you know your goal and your audience, you can make informed decisions about which pages your website actually needs. Most business websites need far fewer pages than their owners initially think. Start with the essentials and only add more once you have a solid reason. Here is a practical structure that serves the majority of service-based and product businesses:

1. Home — The home page is not a summary of everything you do. It is a curated first impression. It should immediately communicate who you help, what outcome you deliver, and what the visitor should do next. Lead with the clearest version of your value proposition, support it with one or two trust signals, and end every section with a purposeful call to action.
2. Services or Products — This page (or set of pages) earns the most conversions when it focuses on outcomes rather than features. Instead of listing what you do, describe what changes for the client after they work with you. Include scope, pricing context if appropriate, and a direct route to enquire or purchase. If you offer multiple services, consider giving each its own dedicated page for SEO and clarity.
3. About — Visitors come to the About page after they are already interested. They want to understand who is behind the business, what shaped your approach, and whether you are the kind of people they want to work with. Avoid corporate jargon. Tell a real story. Include a photo. Authenticity converts far better than polish on this page.
4. Contact — A contact page should do everything it can to reduce friction. Include a form with only the fields you genuinely need, your response time expectation, and at least one alternative method — an email address or phone number for visitors who prefer not to use forms. If your work is location-sensitive, a map embed helps. If your availability is limited, say so — it signals quality and builds credibility.
5. Optional Extras — Depending on your business, you may need a Portfolio or Work page to show examples, a Blog or Insights section to build authority and organic search traffic, a Testimonials or Case Studies page to provide social proof at depth, or a Pricing page to filter enquiries and save everyone time. Add these only when they serve a clear purpose in the visitor’s journey, not simply because competitors have them.

Step 4 — Gather Your Content Before Design Starts

You do not need everything to be perfect before you hand it over — first drafts are fine, and a good copywriter or designer will help refine them. But the raw materials need to exist. If you are waiting on a photo shoot, say so and schedule it before the design phase. If your service descriptions are not written yet, write them first. Every day of delay on content is a day of delay on the whole project, and content delays are the most common reason projects slip past their original deadlines.

Here is what you should have prepared or in progress before your designer opens a single artboard:

• ✓ Logo files — Preferably in SVG or high-resolution PNG with a transparent background. If you have both light and dark versions, provide both. If you do not have a vector logo, flag this early — a designer may need to recreate it.
• ✓ Brand colours and fonts — Your primary and secondary colours in hex or RGB format, and the names of any brand fonts you are already using. If you do not have established brand guidelines, note this — it is an opportunity, not a problem, but it needs to be addressed at the start rather than mid-project.
• ✓ About text — A written description of who you are, what you do, and why you do it. This does not need to be polished prose — bullet points and rough notes work fine as a starting point for a copywriter or designer to shape.
• ✓ Service or product descriptions — What each offering includes, who it is for, and what the outcome is. If you have pricing, decide now whether you will include it publicly — this is a strategic decision that affects design layout and page structure.
• ✓ Photographs and images — Professional photography is worth the investment. A website is judged heavily on visual quality, and generic stock photos undermine credibility immediately. At minimum, have a professional headshot and a few images that represent your work environment or output.
• ✓ Contact information — The email address(es) that should receive enquiries, any phone numbers, business address if relevant, and social media profile URLs. Confirm these are active and monitored before they go live on a public page.

Step 5 — Decide What Functionality You Actually Need

Functionality scope is where budget can expand significantly if it is not defined early. Every feature has a cost — in development time, in maintenance effort, and in the ongoing complexity of the system that has to support it. The goal of this step is not to minimise features, but to be deliberate about which ones you genuinely need at launch versus which ones would be nice to have later. A website with focused functionality that works reliably is worth far more than one with ten half-implemented features.

• Contact form — The baseline for almost every business site. Decide how many fields you actually need — the shorter the form, the higher the completion rate. Consider whether responses should go to one inbox or be routed by type of enquiry.
• Booking or scheduling system — Valuable for consultants, clinics, salons, and service providers. Tools like Calendly can be embedded without custom development, saving significant budget and maintenance overhead.
• Payment processing — Required if you are selling products or collecting deposits. This triggers additional considerations: security compliance (PCI-DSS), refund policies, and often a more complex hosting setup. Scope this carefully.
• Image or project gallery — Useful for photographers, architects, interior designers, and tradespeople. Decide whether it needs filtering by category, lightbox preview, or client-facing password protection for private galleries.
• Blog or insights section — A powerful long-term SEO and credibility tool, but only if you will actually publish content consistently. An empty blog with three posts from two years ago hurts more than it helps. Commit to a realistic publishing cadence before adding this to scope.
• User login and accounts — If clients need to access invoices, documents, or project portals, a login system is necessary. This significantly increases development complexity and should be scoped as a separate phase if budget is constrained.
• Live chat — Can increase conversions meaningfully for e-commerce and high-consideration purchases. Requires someone to monitor and respond promptly. If it will sit unanswered, do not add it — an unanswered chat widget destroys trust faster than not having one at all.
• Multilingual support — If you serve audiences in multiple languages, this needs to be planned from the very beginning — not retrofitted later. It affects URL structure, content management, and potentially the entire CMS choice.

Step 6 — Set a Realistic Budget and Timeline

The most damaging expectation in a web project is an artificial deadline that has not been tested against the actual scope of work. Timelines should be built from the phases of work required, not backwards from a launch date someone picked on a calendar. Equally, a budget stated before the scope is understood is not a budget — it is a guess. The table below reflects typical durations for a well-scoped, professionally executed website project of moderate complexity:

Phase	What Happens	Typical Duration
Planning	Requirements gathering, goal definition, sitemap, content audit, and final scope agreement. This is the phase that eliminates surprises in every phase that follows.	1–2 weeks
Design	Visual mockups of key pages — typically Home, one interior page, and mobile views. One or two rounds of feedback and revision. Typography, colour, and layout decisions are locked here.	1–3 weeks
Development	Building the approved designs into a functioning, responsive website. Integration of forms, CMS, third-party tools, and any custom functionality. The longest phase by effort.	2–6 weeks
Review	Client walkthrough of the complete build. Browser and device testing. Content proofreading. Final feedback incorporated and changes confirmed in writing before launch.	1 week
Launch	DNS transfer, SSL certificate, final performance checks, redirect setup if the site replaces an existing URL, and post-launch monitoring for any unexpected issues.	2–3 days

These ranges widen when content is delayed, when feedback rounds are numerous, or when additional functionality is introduced mid-project. They compress when a client arrives fully prepared, decisions are made quickly, and the scope stays consistent from start to finish. The fastest projects are always the best planned ones.

What to Prepare Before Talking to a Developer

When you approach a developer or studio for a quote, the more prepared you are, the more accurate the proposal you will receive — and the more confident you can be that it reflects the real project rather than a best guess. Arriving with the following five things done signals seriousness, accelerates the scoping conversation, and often results in a better working relationship from day one:

• ✓ A written brief — One to two pages covering your goal, your audience, the pages you need, any functionality requirements, your rough budget range, and your target launch date. It does not need to be a formal document — clear notes in a Google Doc are perfectly sufficient.
• ✓ Three reference websites — Sites whose design, tone, or structure you admire. Note specifically what you like about each one: is it the layout, the colour palette, the photography style, the navigation? This shortens the visual alignment conversation enormously.
• ✓ A defined decision-maker — Know who on your side has final approval on design and content. Projects slow dramatically when multiple stakeholders have equal authority and disagree. Identify one primary point of contact before work begins.
• ✓ Your content readiness status — Be honest about what you have and what still needs to be created. A developer can help you plan around content gaps, but only if they know they exist. Surprises during development are expensive.
• ✓ Access to your existing assets — Domain registrar login, existing hosting details, previous website files if applicable, and any accounts with tools you currently use (email marketing, booking systems, payment processors). These take time to locate — start now, not during a deadline.

The websites that succeed — the ones that attract the right clients, convert visitors efficiently, and hold up well over time — are almost always the products of thorough planning rather than exceptional design alone. Design and development are craft skills. Planning is a strategic skill, and it operates on a different level. Invest the time in this framework before anything else begins, and the rest of the project will be faster, cheaper, and far less stressful than you might expect.