When a web development proposal says 'custom business website', what are you actually paying for? The short answer is much more than a homepage. A well-built site brings business strategy, content, design, technology, search visibility and customer experience into a coordinated system.
Understanding each component helps you set a sensible budget, identify missing work in quotations and decide where custom development creates value. This breakdown is for business owners who want a serious online presence without paying for complexity they do not need.
What 'custom' should mean
Custom does not always mean that every line of code is written from scratch. It should mean that the solution is shaped around your goals, customers, content and operational needs rather than forcing your business into a generic template.
A developer might use WordPress with custom components, Webflow with a tailored design, or a React and Laravel application with original functionality. Each can be custom in a meaningful way. The important distinction is whether the work solves your real problem and remains practical to maintain.
Before commissioning any build, ask what is being customised: the visual design, content structure, integrations, database, user experience or all of these. If the answer is simply 'we changed the colours of a theme', the work may still be useful, but it should be scoped and priced accordingly.
Layer 1: Discovery and website strategy
A website should begin with questions, not Photoshop. Discovery establishes the job the site needs to perform, who uses it and how success will be judged.
A useful discovery process maps the target audience, customer objections, core services, strongest differentiators, geographic reach, competitors, conversion routes and operational dependencies. It also assesses the existing website, if there is one. The deliverables may include a brief, audience profiles, functionality list, initial site map and measurement plan.
Example: A construction company may have two audiences: homeowners seeking renovations and commercial clients needing a capable contractor. These visitors require different evidence, language and enquiry forms. Discovery reveals that difference before pages are designed.
Layer 2: Information architecture and user journeys
Information architecture determines what pages exist, how they relate and how people find information. A simple company site might contain Home, About, Services, individual Service pages, Projects, FAQs and Contact. A larger site may add sector-specific pages, resources, locations, careers or a portal.
The site map must reflect what people need to accomplish, not just the company's internal departments. Every important page should answer: What is this? Is it relevant to me? Why should I trust it? What happens next?
A user journey can be mapped as: search result →︎ service page →︎ relevant project example →︎ quote request →︎ confirmation and follow-up. Defining that path early affects menus, content, forms and tracking.
Layer 3: Content and conversion copywriting
Content is one of the most commonly underestimated costs. Developers can build a beautiful page, but someone must clearly explain the offering. Good copy answers customer questions in familiar language, uses genuine evidence and makes the next step obvious.
A thorough content scope should specify who provides service descriptions, team information, images, case studies, frequently asked questions, policies and testimonials. It should also cover editing, fact-checking, calls to action and the final approval process.
Avoid placeholder copy such as 'world-class solutions' or 'we pride ourselves on quality'. Replace it with practical details: who you serve, the services you perform, how the process works, what customers can expect and real evidence of capability. Content should never invent testimonials, certifications, customer numbers or guarantees.
Layer 4: User experience and visual design
User experience, or UX, deals with how easily someone can complete a task. User interface, or UI, deals with the visual and interactive elements supporting that task. They are connected but not identical.
The design phase often includes low-fidelity wireframes, page layouts, responsive design rules, typography, colour, components, buttons, forms, navigation and states such as loading, errors or success messages. A good design system makes the site feel consistent even as new pages are added.
A custom visual identity should support clarity. If visitors must wait through an elaborate animation before they see your services or contact details, the design may be working against the business goal.
Layer 5: Frontend development
The frontend is the part customers interact with: headings, navigation, forms, content, imagery, animations and responsive layouts. Strong implementation includes accessible HTML, appropriate headings, usable controls, fast-loading assets, predictable navigation and sensible behaviour across screen sizes.
This is where real-world testing matters. A page can look correct in a design file and still be difficult to use when a customer has a small phone screen, enlarged text or a keyboard instead of a mouse.
Layer 6: Content management and backend development
The backend stores and processes information and connects site functions. A simple marketing site may need only a content management system and lead forms. A more advanced site might require customer accounts, internal dashboards, permissions, quotation workflows, bookings, searchable data or approval rules.
The content editor experience deserves attention. Ask whether staff can publish blogs, update service pages, change images and manage metadata without a developer. For custom software, permissions should reflect actual jobs: a customer, support employee and administrator should not all see the same information.
Layer 7: Integrations and automation
A useful website rarely lives alone. Common connections include:
Contact forms to email or a customer relationship management (CRM) system.
Booking tools linked to confirmation messages or calendars.
E-commerce checkouts linked to payment providers and order management.
Accounting or invoicing software connected to customer records.
Customer portals linked to an existing ERP, helpdesk or document system.
Marketing analytics connected to meaningful enquiries and sales events.
Integrations need more than a visible button. Developers must consider authentication, data mapping, error handling, duplicate records, retry logic and what happens if the external service becomes unavailable. Ask which connections are native, third-party or custom, and who pays for any API subscriptions.
Layer 8: Search engine optimisation foundations
Technical SEO is not a substitute for valuable content, but it helps search engines find and interpret it. A launch-ready implementation normally includes descriptive title tags, suitable meta descriptions, headings, human-readable URLs, internal links, indexability checks, image alt text, an XML sitemap and sensible canonical handling.
For a Cape Town business, the content should also explain its actual location or service reach where relevant. For a national online business, location targeting may matter less than clear service categories and strong topical coverage. Keyword repetition is not a strategy; helpful pages that satisfy user intent are the goal.
A separate ongoing SEO programme may include research, new landing pages, content, technical improvements, internal-link work and reporting. Make sure the quote distinguishes the initial setup from future SEO services.
Layer 9: Performance, accessibility and security
These are part of the product, not luxury add-ons.
Performance: Compress images, serve appropriate formats, load scripts responsibly, optimise server responses and test key pages. Core Web Vitals help assess loading, interaction and layout stability.
Accessibility: Use semantic headings, descriptive labels, keyboard-operable controls, readable contrast, meaningful links and error messages. Designing for accessibility usually improves usability for everyone.
Security: Use HTTPS, appropriate hosting controls, strong access management, regular updates, backups and secure handling of submitted data. For any customer information, plan its collection, storage, access and retention responsibly, with attention to applicable law such as South Africa's POPIA.
No developer can make a website permanently immune to attack. A responsible provider explains risks, controls and ongoing responsibilities.
Layer 10: Quality assurance and launch
Testing should be based on real scenarios. A service business must know that a quote form is delivered to the correct inbox; a shop must know an order can be paid for and fulfilled; a portal must know users cannot access one another's private records.
Quality assurance can include responsive and browser testing, functional checks, accessibility tests, form validation, performance reviews, security configuration checks, redirects and content proofreading. For a redesign, preserve valuable existing URLs or map suitable redirects so customers and search engines do not hit unnecessary dead ends.
A launch checklist should cover domain and DNS, HTTPS, backups, final approval, analytics, Search Console, live payment or form tests, error monitoring and a rollback plan where appropriate.
Layer 11: Training, ownership and support
A website is not complete merely because it is publicly visible. Your team should know how to change content, where enquiries arrive, how to manage users and whom to contact when something breaks.
Request a handover with administrator access, domain and hosting details, relevant licences, brief operating instructions, backup responsibilities, support contacts and warranty or maintenance terms. Confirm which assets and code you own and which third-party elements are licensed.
Maintenance might include updates, security checks, uptime monitoring, backup verification, minor content work and continuous improvement. It should be priced and described separately so you can judge long-term ownership costs.
A realistic example of website scope
Imagine an established home-services company wants more qualified enquiries and less time chasing incomplete requests. A sensible first scope could include:
| Area | Example deliverable |
|---|---|
| Strategy | Audience, conversion goals and site map |
| Pages | Homepage, About, five service pages, Projects, FAQs and Contact |
| Content | Edited service copy, project descriptions and contact wording |
| Design | Custom responsive layouts and reusable page sections |
| Functionality | Quote request form with service selection and conditional fields |
| Integrations | Enquiry notifications and lead capture into an agreed system |
| SEO | Metadata, page structure, local relevance, sitemap and analytics |
| Quality | Cross-device testing, basic accessibility checks and launch QA |
| Handover | Content-editor training and maintenance guidance |
This is an illustrative scope, not a standard package or a promise of included features. A company needing a complex quotation engine or customer accounts would require a separate assessment.
Where website budgets often go wrong
Underestimating content: Without approved copy and images, design and development have to be revised repeatedly.
Starting with every possible feature: The first release becomes costly and difficult to test. Prioritise what creates immediate value.
Forgetting migration: Moving an existing site can require redirect mapping, data cleanup, email and DNS coordination and preservation of useful URLs.
Ignoring ongoing costs: Plugins, apps, domain renewal, hosting, support and marketing must fit the operating budget.
Leaving success undefined: 'Make it modern' is not an acceptance criterion. 'A customer can submit a mobile quote request and our team receives the required information' is testable.
Frequently asked questions
How many pages does a custom business website need?
As many as are necessary to answer distinct customer needs. One genuinely useful service page is better than ten shallow pages. Begin with the site's purpose and expand only where separate content helps visitors.
Do I need a custom backend?
Not for every site. A standard content management system can handle many company websites. Custom backend work makes sense when unique records, permissions, processes or integrations cannot be handled reliably through existing tools.
Can a custom website still use WordPress?
Yes. WordPress can support bespoke designs and structured content. The choice should depend on functionality, editing experience, maintenance and technical requirements rather than the word 'custom' alone.
What happens if we change our minds during development?
Reasonable refinements should be covered by agreed review cycles. New features or major scope changes should be evaluated for cost and schedule impact before work proceeds.
Is SEO included in web development?
Basic technical SEO often should be, but keyword strategy, ongoing content development, outreach and search performance work are distinct services. Ask which tasks are included in writing.
Invest in the whole experience
A custom business website brings together content, usability, technical quality and business operations. The strongest builds do not spend all the budget on appearance and leave the rest for later. They balance every layer around what customers need to accomplish.
ZA TechLabs builds business websites and web applications and can connect them to custom software and workflow tools when needed. Talk through your project to define a scope that makes business sense.
Further reading: Web development in Cape Town: A practical guide · Customer portals: What can they help you do?

