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.