Start with the job the website must do
A useful website starts with a job: helping customers understand the service and take the next step. Write down your audience, offer and desired action, whether an enquiry, call, booking or purchase. Decide what information people need for that decision.
An initial service website may need an offer overview, evidence of work, the process and contact details. Catalogues, multiple languages or payments make sense when they solve a real need. Separate desirable features from essentials required to start.
How to compare website quotes
There is no single correct price for every website. Pages, copy preparation, photographs, languages, integrations and support affect the quote. Instead of using old price lists, request current proposals for the same clearly described job.
Compare deliverables: who prepares content, what gets tested, how many revisions are included and who connects the form to message receipt. Agree deadlines and approvals. A lower initial price is not a saving if essentials you assumed were included require extra payment after handover.
Website builder, CMS or custom development
A website builder can suit straightforward editing and a standard layout. A CMS such as WordPress provides different ways to organize content, with maintenance of extensions, security and compatibility. Custom development may fit a particular workflow, with agreed support.
Choose based on who edits the website and what must connect to the business. Ask what you can export when changing providers. Check restrictions on forms, languages and payments before commissioning, rather than after the design has been produced.
Build it yourself, hire a freelancer or use an agency
Building it yourself reduces external costs but uses your time. Assess whether you can prepare content, test mobile usability and maintain the website. Ask a freelancer who covers support when unavailable. With an agency, establish who manages the project.
Request examples of similar work and an explanation of the process. Reliability and access to your own website matter more than the provider's category. Nominate one person to approve content so conflicting feedback does not leave the project waiting.
Prepare materials before development
Collect the logo, your own photographs, service descriptions and customer questions. Record what was actually delivered for each project. Include the phone number, service area and address if customers visit your premises.
Agree who writes the copy and checks its accuracy. Tools can help draft it but should not invent references, prices or experience. Good preparation reduces later revisions and leaves more time to verify content and the contact process.
Include ongoing costs
Separate development from the domain, hosting, licences, email and maintenance. Ask which items renew and who pays them. Clarify whether support includes security updates, backups, content changes or only technical issues.
Keep control of the domain and essential accounts. Request a recovery process and a record of access for handover. Compare costs over the full period of use, rather than only the launch date.
What to check before handover
Review the offer, photographs, links and error messages on a phone and computer. Send an agreed test enquiry and verify its original content where your team works. Editing instructions should support your actual role.
Record unresolved issues, an owner and a correction deadline. Start with a version you can maintain and expand when a justified need emerges. This connects spending to things that help customers and the team.
Frequently asked questions
What does a small business website need first?
To start, an overview of your services, proof of your work, how you work with customers and a way to get in touch is often enough. A catalog, several languages or online payment make sense only when they solve a real need. So separate the features you cannot start without from the ones that would merely be nice to have.
How do I compare quotes for a website?
Ask for current quotes for the same clearly described job. Compare what is delivered: who prepares the content, what is tested, how many changes are included and who connects the form to the place where messages are received. A lower starting price is not a saving if you pay separately after handover for things you assumed were included.
What does a website cost to run after it is built?
Besides the build, count the domain, hosting, licenses, email and maintenance. Ask which items renew and who pays for them. The domain and key accounts should be under your control.
Should I build my website myself or use a freelancer or an agency?
Building it yourself lowers the outside cost but takes your time: you have to prepare the content, check the site on a phone and keep it up to date. With a freelancer, ask who takes over support when they are unavailable, and with an agency, who runs the project. A reliable process and access to your own website matter more than the type of provider.
What should I check before I accept a finished website?
Review the site on a phone and a computer, including the offer, photos, links and error messages. Send a test enquiry and check that it arrived where your team reads it. Write down any gaps and agree who fixes them.
Request a clearly scoped first version, with a separate list of possible additions. That keeps the price and expectations clear.
