Planning a small business website starts with decisions about customers, content, scope and ownership. A useful brief connects those decisions before design begins. This guide walks through the brief, platform choice, launch checks and ongoing responsibilities, using examples from my published work.
Define the job of the website
Choose the main commercial action: a consultation, estimate request, product purchase or training application. Write down who should take that action and what they need to know first. Secondary actions can support the journey, but a service page should not ask visitors to choose between several unrelated offers.
- A contractor needs service information, coverage areas, completed work and an estimate path.
- An accounting business needs clear service scope and information that helps a prospect assess fit.
- A store needs a usable catalogue, product details, delivery information and checkout.
Write a page and content brief
List the pages, their audience, the question each answers and the next useful step. A practical starting structure is home, services, selected work, about and contact. Add separate service pages only when the offer and content justify them; changing a town name does not create a useful new page.
For Ummah Financial Solutions, the project brief called for dedicated accounting service information and a consultation flow. That is a different structure from BMark’s training platform, where application details, locations, seats and approvals drive the workflow.
Choose WordPress or Shopify around the requirements
Start with your catalogue, content, integrations and who will maintain the site. WordPress with WooCommerce offers control over content and custom workflows, but hosting and maintenance need an owner. Shopify provides a hosted commerce platform; check the plan, theme, app and payment requirements against your specific market.
Compare my WordPress development service and Shopify store development service. A platform decision should follow the brief, not a promise that one system always produces better rankings or sales.
Separate build cost from running cost
My WordPress starter scope begins at $800 for 5–7 pages, while a Shopify store build starts at $1,200. These are starting scopes, not a quote for every project. Custom functionality, catalogue preparation, copywriting, integrations and migration can change the work involved.
Budget separately for the domain, hosting or platform subscription, premium licences and ongoing support. Compare the WordPress website cost guide with the Shopify cost guide. For an initial WordPress scope, use the website cost calculator before requesting a written proposal.
Design for content, mobile and accessibility
Use your real service descriptions, project images and product information during design. Placeholder content hides layout problems and delays decisions. Make headings scannable, keep text readable, and show the action when the reader has enough information to decide.
Check menus and forms with a keyboard and at narrow widths. Inputs need visible labels and errors that explain how to recover. W3C’s form guidance provides practical examples. If you already have approved layouts, my Figma to Elementor service covers turning that design into a WordPress build.
Build a useful search foundation
Give each page a clear purpose, descriptive title and crawlable links to relevant pages. Keep important information in accessible text, use image descriptions where they help, and make sure the pages you want found are indexable. Check redirects carefully when replacing an existing website.
Google’s link guidance and AI search guidance support the same practical foundation: useful content that can be discovered and understood. There is no special AI schema that guarantees inclusion. For an existing site, my WordPress SEO service starts with the technical and content problems affecting it.
Test the complete launch journey
- Confirm each important URL, redirect, canonical and sitemap entry.
- Submit a labelled test enquiry and verify receipt, reply-to and confirmation.
- Complete and cancel an internal test booking if the site uses a calendar.
- Check WhatsApp links on mobile and desktop, plus the fallback contact option.
- For shops, use the payment provider’s supported test flow to check taxes, shipping and order messages before accepting live orders.
- Review loading, interaction and layout stability using appropriate lab and field data.
- Document backups, account ownership and how to restore the previous version.
Assign ownership after launch
Decide who updates content, renews licences, tests backups and handles technical problems. A launch is a handover, not a permanent guarantee that every integration will keep working. My maintenance packages describe ongoing options; substantial new features need their own scope.
If your site is already live, use the companion ten conversion checks to prioritise improvements. To plan a build, send your website brief with the pages, integrations and deadline you have in mind.
