A website project becomes expensive when design starts before anyone agrees what visitors need to do. Use this guide to turn the business offer into pages, evidence and a build brief a real team can deliver.
THE SHORT ANSWER
Build the journey before the pages
Plan one full visitor journey first. Then pick the platform and design around the content, the work of running the site and the actions it must support.
- Decide what the visitor needs to do and what each page is for before you pick a theme, plugin or layout.
- Plan the proof, the content and who does what alongside the design, so missing pieces do not delay launch.
- Test the full journey on phone and desktop: menus, forms, links, privacy notes and delivery.
- After launch, keep ownership, access, backups, updates and content reviews in view.
- 01UnderstandVisitor + question + offer
- 02StructurePages + proof + next step
- 03OperateOwnership + launch + upkeep
Rule of thumbA clear brief makes the design review a decision, not a guessing game.
- 1Define the visitor and the useful action
- 2Give each page a clear job
- 3Prepare content and evidence before design
- 4Choose a platform and cost the actual scope
- 5Design and build a consistent, usable system
- 6Review launch readiness across real journeys
- 7Hand over ownership and plan the first review
Planning framework and researched guide. Sources reviewed 18–19 November 2026. Prices keep their own check dates. We have not run a hands-on product trial or measured a business result. Our advice is based on the stated task and official docs. Read the evidence standards.
1. Define the visitor and the useful action
Begin with one real situation. A prospective customer may need to understand a service, compare a product, confirm delivery or contact the right person. Write the question they arrive with and the action the website should help them take. “Make it modern” is a design preference, not the purpose of the project.
For a small service business, the first journey may be: service page → proof → enquiry → saved confirmation → reply. For a shop, it covers choosing a product, delivery details, payment, receipt and dispatch. Map the whole journey before you sign off the sitemap.
- Audience: who is arriving, and what do they already know?
- Offer: what can the business actually provide?
- Action: what should a visitor be able to complete?
- Evidence: what genuine information helps them decide?
- Owner: who receives and acts on the enquiry or order?
2. Give each page a clear job
Build a small sitemap around the visitor’s questions. The home page explains the offer and points people onward. A service page says what is included and who it suits. About names the people. Contact says how to reach them. Avoid several near-identical pages chasing the same search.
Use plain navigation labels and descriptive links. Sketch the order of the page before choosing a theme. The 20-point homepage checklist owns the detailed opening-screen and proof review. This main guide sets the project direction.
| Page | Primary job | Information needed |
|---|---|---|
| Homepage | Explain and route | Offer, audience, relevant proof and next actions |
| Service or product | Support a decision | Scope, suitability, limits, price context and practical questions |
| About | Identify the organisation and people | Verifiable background, contact route and policies |
| Contact or checkout | Complete the task | Required fields, clear costs, error handling and confirmation |
3. Prepare content and evidence before design
Draft headings, the opening answer, scope, useful examples and the next action. Assign an owner to each piece of information. Use genuine author or team details and approved product images. Leave out claims, testimonials and client logos you cannot support or have no permission to publish.
Write a short content brief for every important page. Include the visitor’s question, the page’s job, required sources, supporting pages and approval owner. Use the content brief template where search is part of the acquisition plan. Search-friendly wording should make the page clearer to people.
Collect images with their sizes and owners noted. Resize each image for the space it fills; do not load a huge desktop file into a small card. Decorative images can have empty alt text. Images that carry meaning need a short description.
4. Choose a platform and cost the actual scope
Choose around operation and ownership. Self-hosted WordPress suits teams willing to manage hosting, updates and flexible content. Shopify centres on online selling. Wix offers a managed builder for a straightforward site. Webflow may fit a design-led team comfortable with its publishing model. None is the universal cheapest choice once the full scope is included. If you choose WordPress, test hosting with your own site before you commit to a plan.
| Platform | A sensible fit | Costs and responsibilities to inspect |
|---|---|---|
| WordPress | Editorial, service and flexible content sites | Hosting, updates, backups, extensions and maintenance owner |
| Shopify | A business primarily selling products | Plan, payment terms, apps, shipping and checkout requirements |
| Wix | An owner wanting a managed builder | Required plan, storage, forms, commerce and export limits |
| Webflow | A design-led publishing workflow | Site plan, CMS limits, workspace roles and handover |
Price one-off work apart from yearly running costs: discovery, content, design, build, integrations, migration, hosting, licences and upkeep. Count page types, not just pages. A product catalogue with delivery rules is a different job from five service pages.
Ask what is included and excluded, plus milestones, review rounds and how changes are handled. Content sign-off, domain access, product data and integrations all affect timing. A “two-week website” with no scope is not a plan. Use the complete-cost framework to compare ongoing costs.
5. Design and build a consistent, usable system
Define typography, colours, spacing, buttons, forms and content widths once. Reuse them across templates. Check contrast, readable type, visible focus and keyboard access as the build develops. Avoid visual effects that hide the next action, shift content or make a simple page expensive to load.
Build the key journey first. An enquiry form needs clear labels, plain error messages, a saved entry and a confirmation people can trust. A shop must show delivery and refund details before checkout. Test failures and duplicates, not just the happy path.
Add clear titles, meta descriptions, canonicals, social previews and crawlable internal links. Keep staging and pre-launch sites hidden from search (noindex) until the owner approves launch. A clean design does not fix an indexing block or replace useful content.
6. Review launch readiness across real journeys
Use the 40-check website launch checklist for content, mobile access, forms, downloads, metadata and operations. That checklist is the detailed sign-off record, so this guide does not repeat all forty checks.
Name who signs off the launch and who can roll it back. Take and test a backup, note DNS and hosting access, test the key transaction and keep the previous version where you can. Fix a broken payment or missing enquiry receipt before you polish an animation.
For speed, keep lab tests apart from real-user data. Use the hosting performance method to find the slow part before you assume a new host will fix it. Keep page content, cache state and test location the same.
7. Hand over ownership and plan the first review
The business should know who controls the domain, hosting, CMS and billing. Provide role-suitable access, an update and backup routine, a restoration route and a short guide to the tasks the owner will perform. Remove temporary access when it is no longer needed.
Pick one first review question. Do enquiries reach the right person? Can customers find delivery details? Do visitors get stuck at the same field? Record useful feedback and real technical errors. A few early visits cannot prove a lift in conversions.
Keep a change log and budget for operation. Review content when the offer, prices or people change. A finished project is a website the business can run and improve, not only a set of approved screenshots.
Turn the plan into a build brief
- Purpose and audience
- Required pages and visitor journeys
- Content, evidence and approval owners
- Platform, integrations and ownership
- One-time and recurring cost assumptions
- Accessibility, performance and launch checks
- Maintenance, handover and first review
Tools to consider
Research shortlist, not tested reviews. These are tools to look into, not endorsements or a ranking. We checked prices and plan limits on the linked official pages on 16 November 2026. Recheck the current quote, taxes, renewal terms and availability before you buy.
Choose a platform around who will maintain the site and what visitors need to do. These are buying considerations, not measured performance results.
| Tool | What it is for here | Who it may suit | Starting price and conditions |
|---|---|---|---|
| WordPress.org | Publish service pages and a journal with a separately chosen host. | A business that wants control and has an owner for updates, backups and support. | ₹0 for the open-source software. Domain, hosting, support and any paid extensions are separate. Official pricing / plan details Price checked on 16 November 2026. |
| Shopify Basic | Run a hosted product catalogue and checkout. | An Indian retailer prioritising a managed store and willing to budget for platform and app costs. | ₹1,499/month equivalent billed yearly (₹17,988/year), or ₹1,994/month billed monthly. Check tax, apps and third-party payment fees separately. Official pricing / plan details Price checked on 16 November 2026. |
| WooCommerce | Add a configurable store to WordPress. | A merchant with WordPress support and requirements that justify extension and maintenance work. | ₹0 for the core plugin. Hosting, payment processing, development and optional extensions are separate. Official pricing / plan details Price checked on 16 November 2026. |
| Razorpay Payment Gateway | Plan payment acceptance and settlement integration. | An Indian merchant checking onboarding, supported methods and transaction fees. | ₹0 setup and annual maintenance; standard successful payments: 2% platform fee + GST on that fee. Some payment methods have different rates. Official pricing / plan details Price checked on 16 November 2026. |
Map one full visitor task before you choose add-ons. Confirm who maintains each integration, and whether the platform charges extra when you use an outside payment provider.
Continue with the related guides
For a more specific decision, continue with these researched guides:
- Compare WordPress, Shopify and Wix
- Build a scoped website budget
- Compare hosting offers and operating responsibilities
- Homepage checklist: 20 elements for a clearer business website
- Website launch checklist for a small business team
- Small business SEO: a practical planning playbook
Questions about planning a business website
Should I choose a theme before writing the content?
Clarify the purpose, audience, important pages, and key content first. A theme should support those needs rather than define them accidentally.
How many pages do I need?
Use the questions and tasks the site must support. There is no universal page count for every business.
Do I need a case study before launching?
Use real evidence when you have it. If you have no verified case study, explain the offer and process clearly. Never invent results.
Is a working form enough to call the site complete?
Looking at the fields is only one step. With approved test details, check that entries are saved, delivered, acknowledged and owned.
What should happen after launch?
Give someone each job: access, backups, software, connected services and content review. Revisit the site when the business or the visitor’s task changes.
What should I prepare before asking for a website quote?
Prepare the offer, the target visitors, key pages, required actions, the content you have and real evidence. List integrations, who edits what, who owns what and any old URLs that must keep working. Ask the supplier to price the first build apart from hosting, upkeep and support. A clear brief makes quotes easier to compare and shows what work still sits with your team.
Should a small site use a custom build or a managed platform?
Compare the needs and the people who will maintain the site. A managed platform may suit a standard workflow with a fair plan and a way to export. A custom build may be worth it for needs the standard options cannot meet. Count editing, integrations, upkeep, recovery and exit work. Neither is better just because it is simpler, dearer or more technical.
Sources and further reading
- WordPress Theme Handbook: UI best practices.
- WordPress: alternative text for images.
- Google Search Central: SEO Starter Guide.
- WordPress.org: official plan and pricing information (checked 16 November 2026).
- Shopify Basic: official plan and pricing information (checked 16 November 2026).
- WooCommerce: official plan and pricing information (checked 16 November 2026).
- Razorpay Payment Gateway: official plan and pricing information (checked 16 November 2026).
Last updated: 21 November 2026. Individual prices retain their stated check dates.




