Guide · Technical decisions
A useful website on a small budget.
To reduce a website budget, narrow the first version to one audience, one clear offer and one working contact route. Reuse a suitable design or existing booking tool where it fits. Keep readable content, mobile usability and reliable delivery of enquiries in scope; they are the reason to publish the site.
Define the enquiry the website should bring
Hypothetical example: a repair business wants visitors to describe the fault and request a visit. The first site needs to explain the work offered, the area actually served, relevant evidence and how to send that request. It does not automatically need accounts, online payment or a customer portal.
Prepare the service text, contact details and usable photographs before comparing quotes. If writing and image preparation are still needed, include them explicitly rather than hiding that work inside “a simple website”.
Choose a template when it fits the content
A template can reduce layout and component work. Test it with your longest service description, real menu and contact form on a small phone. An attractive demo with short placeholder text does not establish that your content will fit.
A bespoke build is worth comparing when the template needs extensive changes or the workflow is unusual. Ask which parts are reused and which are developed. A standard design with a reliable booking integration may be enough.
Keep the parts that make the site usable
Use clear titles, real links and useful service explanations that search engines can access. Google’s starter guide describes these foundations; paying for more pages does not replace a clear answer.
Test form labels, keyboard use, validation and confirmation. W3C’s guidance helps make those steps understandable. Send a test enquiry and verify receipt, then simulate an error: a successful-looking button is not evidence that the message arrived.
Use lighter images and postpone optional features
Start with a small set of appropriately sized images and defer features that do not help the enquiry. Image dimensions, format and loading affect performance; a full-resolution photograph should not be sent merely to fill a small card.
For the repair example, postpone a custom estimator until the team knows which answers it needs to price a visit. Keep a short form now. Write down the deferred feature so a lower quote is not mistaken for delivery of the full wish list.
Compare the full first-year scope
Ask separately for initial delivery, domain, hosting, paid services, maintenance and content changes. State who owns the accounts, what can be exported and how another developer could take over. Do not compare a one-off build with a subscription without those details.
Use the same brief for every quote: intended customer, required pages, available content, contact route, integrations, languages, acceptance tests and ongoing responsibilities. If the total exceeds the budget, remove a feature and compare again rather than silently dropping testing.
- 01 Service Explain the repair and real service area
- 02 Contact Provide a short, labelled enquiry form
- 03 Test Verify delivery and the failure message
- 04 Decision Publish; add a portal only when needed
Publish a complete small version
Acceptance for the repair site means a customer can understand the service, read it on a phone and send an enquiry that the business receives. Check indexing controls, broken links and the final domain before launch. Agree who will update opening hours or service details afterwards.
A free consultation or agreed basic demo can help define the scope. I quote the full website separately. Add features when actual enquiries reveal a missing step or new requirement.
To define the next step, read what a demo, prototype and MVP each validate.
Sources and further reading
Questions before we start
Can a cheap website still be professional?
Yes, if the scope is small enough to finish properly. A focused site with clear information and a dependable contact route can be more useful than a larger unfinished one.
How much does a basic business website cost?
There is no reliable figure without pages, content, languages and integrations. Ask for an itemised scope and recurring costs. A quote should state what is included, excluded and maintained.
Can I use a template and improve it later?
Yes, provided you can edit the content, retain account access and extend or export what matters. Check those conditions before choosing the platform.
Does the free demo include the complete website?
No. The consultation and a basic demo with agreed scope are free and carry no obligation to hire. The full website is a separate, agreed quote.