A website built around your business
Define the customer journey before choosing pages, features or a price.
Start with the outcome
Who needs to find you, what do they need to understand, and what should happen next? Connect the website brief to enquiries, sales, service or a useful customer workflow.
Begin with a real visitor and a concrete task. For a service business, that might be understanding whether a service covers their location, checking what information a consultation requires, and sending a useful enquiry. Write that journey in plain language before turning it into a list of pages.
Bring the questions your sales team answers repeatedly. Product limitations, service areas, delivery responsibilities and the next step often matter more than an elaborate opening animation. Decide which information must be visible before a visitor contacts you, and who in your business can confirm that information is accurate.
A useful discovery output is a short statement: this audience needs to complete this task, and we will recognise success through this evidence. Keep that statement available when deciding whether a proposed feature belongs in the first release.
Make the scope specific
List the content, integrations, languages, accessibility needs and launch responsibilities. Separate the first release from later improvements so the proposal describes a deliverable, not a wish list.
Make a content inventory: existing URLs, service descriptions, documents, photography, forms and downloadable resources. Mark each item as keep, rewrite, combine or retire. Identify an owner for every piece that needs approval. Missing content is a delivery dependency, not a detail to resolve after the design is finished.
Describe integrations through their behaviour. Instead of writing “connect our CRM”, explain which form creates a record, what fields are required, who receives the enquiry and what happens if the CRM is unavailable. That gives the design and implementation teams something specific to estimate and test.
Separate launch requirements from later ideas. Include acceptance checks for navigation, forms, mobile layouts, content editing and broken-link handling. Agree who supplies access and test data, and which decisions require your approval. These boundaries make a proposal easier to compare and a change request easier to understand.
Build an improvement path
Agree how enquiries and important actions will be measured. Launch is the beginning of a review cycle: observe, prioritise and improve.
Choose a small set of meaningful actions to observe after launch: a completed enquiry, an appointment request, a product-document download or a qualified conversation. A busy page is not automatically a useful page. Review what visitors attempted and where they needed help, alongside the quality of enquiries reaching your team.
Plan a review with the people who maintain the content and respond to leads. Ask what has become outdated, which questions keep coming up and where manual work remains. Use those findings to select the next improvement instead of continually adding features without checking their effect.
Keep a practical handover record covering content ownership, administrative access, recurring services, support contacts and recovery responsibilities. A website project should leave the organisation able to operate its new site, not dependent on remembering decisions scattered through messages.
Understanding website investment
Compare scope and responsibilities, not just headline prices.
The VTECH starting point
Website Foundation starts from R75,000. This is a guide anchor, not a binding quote. Content depth, bespoke design, integrations and delivery requirements determine the agreed scope.
A price is only useful when the included work is visible. Compare the audience, content, templates, interaction design, integrations and migration described in each proposal. Two offers that both say “business website” may assume very different responsibilities and deliverables.
Ask whether writing, photography preparation, redirects, forms, accessibility review and content handover are included or supplied by your team. Record assumptions explicitly. An attractive headline figure can be difficult to compare if important work has been left undefined.
Use the public guide as an opening point for discussion, not as confirmation that your project has already been quoted. Bring your existing site and intended outcomes so the first conversation can identify which assumptions apply and which require a different scope.
What changes the investment?
A catalogue, customer portal, migration or immersive 3D journey adds different work from a straightforward business website. Identify these requirements early and keep third-party charges visible in the proposal.
Complexity often sits behind a simple-looking screen. A product enquiry may need conditional questions, file uploads, spam handling, routing to different teams and confirmation emails. A catalogue may need structured records, filtering and migration from inconsistent spreadsheets. Explain those needs before comparing page counts.
Content readiness also changes the delivery plan. Confirm who can provide approved service information, branding and images, and whether existing material needs rewriting. Decide how feedback will be collected and who can make the final decision when several stakeholders disagree.
Discuss dependencies such as third-party access, internal approval dates and staff availability. Ask how a changed requirement will be assessed, documented and approved. The objective is a clear route to a useful release, with no ambiguity about work added after the original agreement.
Plan beyond launch
Ask what handover, hosting, support and ongoing improvement include. Confirm tax, usage charges, ownership and milestones in the final proposal before committing.
Keep implementation and operation separate in your comparison. Hosting, domains, paid services, support and future improvements may have different owners and billing cycles. Request a list of recurring dependencies and clarify which are included in the proposal and which are purchased directly.
Agree what handover includes: access, account ownership, instructions for routine updates and the route for reporting a problem. Clarify the boundaries of support and how new functionality is requested. These details matter after launch when the original project team may no longer be available every day.
If the initial scope is too broad, reduce it through priorities rather than unexplained quality cuts. Keep the complete customer journey for the first release and defer secondary features deliberately. Record the deferred work so it can be reviewed against real use later.
Where automation should start
Map one useful workflow, its exceptions and its human checkpoints.
Find the repeated work
Choose a process with a clear owner and a measurable problem: repeated data entry, enquiry routing or status updates. Document the current steps and what successful completion means.
Choose one repeated process that your team can explain from start to finish. For example, an enquiry arrives, somebody copies details into a tracker, another person checks the request, and a reply is prepared. Record who performs each step and what information they need before doing it.
Collect representative, appropriately redacted examples. Include incomplete enquiries, duplicate records, unusual requests and cases that require judgement. A demonstration using only ideal inputs does not explain how a workflow will behave during ordinary operations.
Decide what should remain human-led. Pricing approval, sensitive decisions and unclear requests may need a person even when other steps are automated. Make those handoffs visible in the workflow instead of treating them as an exception to discuss later.
Keep people in control
Identify approvals, sensitive information and cases that need judgement. AI is one possible component; a dependable integration or a clear rule may be the better tool for a particular step.
For every proposed connection, identify the system owner, the available access and the record that should be created or updated. Define which system is authoritative when information differs. Clarify how duplicates, missing fields and rejected updates will be handled.
Separate deterministic rules from interpretation. A rule may route requests according to a selected service; interpretation may suggest a category from free text. Agree how uncertain suggestions are reviewed, what users are told, and what information is retained for troubleshooting.
Plan the failure path before the pilot begins. Somebody needs to know when a connection stops working, what can be retried safely and how work returns to a manual queue. A useful workflow includes recovery and ownership, not simply a sequence of connected tools.
Scope a practical pilot
Agree the systems involved, test cases, failure handling and ongoing usage costs. Compare the pilot with the original process before expanding it.
Write acceptance examples together with the team that will use the workflow. Include the expected result, the information that must be preserved and the cases that should pause for review. Test a small, controlled set before increasing the volume or adding more processes.
Compare the pilot with the current process using evidence you can actually collect. That might include handling time, unresolved requests, rework or response quality. Do not assume that a faster automated action improves the whole process if it creates more checking elsewhere.
Confirm the ongoing responsibilities: who reviews exceptions, who maintains connections, which services incur usage charges and how changes are approved. Expand only when the first workflow is understood and supportable. Your initial brief can describe this one process without committing to a company-wide rollout.
Website, portal or application?
Choose the experience around what people need to do.
Explain and convert
A business website helps people understand your offer, find evidence and make an enquiry. Content structure, search visibility and clear next steps matter.
A public website usually helps people understand an offer, find information and take a next step. A web application lets people perform sustained tasks with records, permissions and changing state. A portal commonly gives a particular group a controlled view into those tasks and records.
These categories can overlap. A service company might need a public site and a customer area for documents or project updates. The useful question is not which label sounds more advanced, but what people need to do and whether they need an account to do it.
Describe a representative task from arrival to completion. Include the information entered, the decision made and the result shown. That description helps establish whether a straightforward website feature is sufficient or whether a separately scoped application is needed.
Let people get work done
A portal or application supports tasks: accounts, permissions, bookings, approvals, records or a connected workflow. Start with the users and their main tasks.
List the roles before listing screens. A customer, a staff member and an administrator may view the same record but have different permissions. Specify who can create, edit, approve, export or delete information, and what another user should see after each action.
Design the states around the task: nothing has been entered yet, a record is waiting for approval, a request failed, or an action has already been completed. Clear status and recovery matter as much as the successful screen. Include help and confirmation where a mistake would be costly.
Bring device and working-environment constraints into discovery. Explain whether users work mainly at a desk, on phones, in a warehouse or with intermittent connectivity. Do not assume that a responsive browser interface and a dedicated native application have identical requirements or costs.
Connect the two deliberately
A website can introduce the service while an application delivers it. Define shared data, authentication, support and release boundaries rather than forcing everything into one undifferentiated build.
Choose a first release that completes a coherent task for a clearly defined group. A smaller finished workflow is easier to evaluate than many disconnected screens. Agree the records, roles and integrations needed for that release, then identify what can be introduced later.
Prepare non-sensitive examples of the data and the business rules. Explain where the information currently lives, who owns it and what needs to be retained during migration. Arrange any confidential access separately rather than placing passwords or customer records in an initial enquiry.
The delivery plan should include validation, handover and operation. Decide who checks the release, manages access and responds when an integration fails. The public Applications experience and the service guides can explain the possibilities; the project brief turns your actual requirements into a scoped conversation.
Clear websites for complex services
Make technical capability understandable without losing the detail buyers need.
Organise around buyer questions
Group capabilities by the problems they solve. Explain who each service is for and what a useful next conversation would cover.
Start with the people making the buying decision. An engineer may need specifications, a procurement team may need supporting documents, and an operations manager may need service coverage or maintenance information. Organise the site around those questions rather than an internal department chart.
Use language your customers recognise, while retaining the technical detail they need. Explain the application, compatibility boundaries and conditions that affect suitability. If information requires specialist confirmation, make the next step clear instead of implying that every product fits every use.
Collect the material already used in sales conversations: product sheets, diagrams, photographs and common questions. Identify outdated versions and appoint a reviewer. Technical content needs a maintenance process so the website does not become another uncontrolled document archive.
Use evidence responsibly
Show approved project facts, technical capabilities and authentic proof. Keep illustrative concepts clearly labelled and avoid invented performance claims.
Give related products a consistent information structure. Decide which characteristics users need to compare and which belong in supporting documents. Keep names, units and version references consistent. A filter is only useful when the underlying records have been prepared consistently.
Connect examples to real, approved evidence. Use published case studies only when the client, scope and results can be substantiated. Concept images can illustrate an application, but they should be labelled rather than presented as completed installations or customer endorsements.
Plan how people find a document and return to the relevant product or service. Explain what a download contains before asking someone to open it. Important next steps should remain clear on a phone as well as on a large office display.
Make enquiries useful
Give people a clear route to describe requirements, share a brief and reach the right team. Ask for information that helps the next conversation, not unnecessary friction.
Make an enquiry specific enough to be useful without turning it into a full engineering specification. Ask for the product or service, intended application, relevant location and a way to respond. Request additional technical details progressively when they are actually needed.
Agree how the request reaches the appropriate team and what happens when details are incomplete. A well-designed enquiry form still needs a dependable response process. Define the confirmation message honestly; submission should not imply that suitability, availability or pricing has already been approved.
Review the experience with someone outside the project team. Give them a realistic task, such as finding a document or asking about a service, and observe where they hesitate. Use that evidence to refine labels, navigation and information before adding decorative complexity.
Your project questions, answered
A clear brief, agreed milestones and a useful handover.
What happens after the review?
We clarify the outcome, identify the highest-value priorities and agree the next step. The opportunity review is human-led; it is not an automated website score.
You do not need a complete specification to start a conversation. Bring the problem, the people affected and the outcome you want. If you have a current website, include its address. If you do not, describe how enquiries or tasks are handled today.
The initial review helps identify priorities and unanswered questions. It is not a promise of an automated score, a completed quotation or a booked appointment. Those outcomes require the relevant review, agreed scope or confirmed booking step.
Avoid sending passwords, confidential customer data or private documents in the first message. Describe the systems involved and arrange access separately if it becomes necessary. A short, clear example of the task is often more useful than a large unsorted folder.
How long does delivery take?
Timing depends on the approved scope, content, integrations and decision-making. Milestones and responsibilities are agreed before production; there is no universal delivery promise.
Timing depends on more than implementation. Content approval, design decisions, integrations, migration and testing all have owners and dependencies. Discuss the date you are aiming for, why it matters and which parts of the first release are essential.
A delivery plan should show review points and what is needed from each side. Agree how feedback is consolidated and who has authority to approve a stage. If a dependency changes, review its effect on scope and sequencing rather than silently compressing the testing period.
Ask how progress and decisions will be recorded. Shared acceptance checks help everyone distinguish between something that has been built, something that has been tested, and something ready to release. Those are related milestones, not interchangeable claims.
What should I prepare?
Your goals, current website if one exists, relevant systems and the people who will approve work. The project planner helps you capture a brief and keep a local copy. When approved adapters are configured, it can submit that brief and continue to real consultation availability; receipt or booking is shown only after provider confirmation.
Prepare a concise description of your organisation, current tools, intended audience and desired outcome. Add any known constraints such as a launch event, required integration or internal review process. Mark uncertain information as a question rather than guessing.
The planner helps organise that information into a brief. Review it before submitting and retain a copy for your records. A downloadable brief is not evidence of delivery: rely on the confirmation shown after the configured submission service has accepted the request.
Booking is a separate confirmation. Choose only from availability supplied by the connected provider, and look for a confirmed outcome before assuming the time is reserved. If booking or submission is unavailable, use the contact route and explain what you were trying to arrange.
Plan for the markets you serve
Bring your customer locations into discovery, not just the footer.
South Africa
The public VTECH website guide prices are in South African rand. Confirm the agreed scope, tax treatment and third-party costs in your proposal.
Start with where your customers operate and how your team serves them. A company based in one country may need to support buyers in several others. List service coverage, contact arrangements and the practical limits of what you can deliver in each location.
For South African enquiries, distinguish public guide pricing from the proposal for the actual project. Confirm the currency, scope, applicable tax treatment and third-party services through the commercial discussion. Do not treat a guide figure as a complete cost breakdown.
Use genuine local information: supported regions, relevant examples and accurate contact details. A page that simply substitutes a place name into generic copy does little to explain whether the service is appropriate for a customer in that location.
United Kingdom and United States
Share your operating locations, customers, currency and delivery needs. We confirm the applicable market and commercial terms during discovery; a ZAR guide is not a local-currency quote.
For UK or US work, explain the operating locations, decision-makers and customers the experience needs to support. Clarify working hours, communication expectations and who approves content or commercial decisions across time zones.
Discuss currency and proposal terms directly rather than converting a South African guide figure and treating it as an international offer. The actual scope, delivery arrangements and ongoing services still need to be defined.
Identify any requirements that need qualified legal, tax or compliance review. The purpose of discovery is to surface those dependencies and assign responsibility, not to imply that a standard website package automatically resolves them.
Localise the experience
Language, content, contact routes, time zones and customer expectations should inform the build. Any legal or compliance requirements need appropriate review for the actual project.
Localisation includes the tasks people perform, not just translated words. Review contact routes, address formats, terminology, dates, supporting documents and the information needed before an enquiry. Decide which content is shared and which genuinely differs by audience or market.
Give each regional page a clear purpose and a useful route to the relevant service. Explain availability and local considerations with approved facts. Keep links between the market guide, service guide and project request understandable so visitors do not have to restart their research.
Assign an owner for updates when service coverage, contact arrangements or commercial information changes. Review regional pages alongside the main site rather than leaving them as disconnected landing pages. Consistency matters, but local detail should remain accurate and meaningful.
