Start with the customer's decision
List your main services and the questions customers ask before contacting you. A service page should explain the problem, the proposed approach, what is included and what information is needed for a proposal. Give each substantial service its own page when it has genuinely distinct information. A long list of keywords cannot replace that explanation.
Prepare the content for each market
Choose the countries you can serve and the languages your customers use. Prepare service descriptions, relevant examples and contact arrangements in those languages. A Spanish page can serve Spanish-speaking visitors without implying an office in Spain. Confirm delivery, support and commercial arrangements separately. We discuss who supplies, translates and approves the content before building.
Make the enquiry route clear
On mobile, visitors need readable text, usable controls and a form that asks only for the information required to assess their request. Define where a submitted enquiry goes, who follows up and what confirmation the visitor receives. A shop, booking system or client portal adds a separate transaction or account workflow and must be specified accordingly.
Compare costs on the same scope
Compare proposals by unique pages, copywriting, languages, design, forms and integrations. Ask whether hosting, maintenance, content changes and third-party subscriptions are included. The website configurator records preferences; it does not confirm a purchase. A delivery date can be agreed after the required content and functionality are known.
Prepare your enquiry
- Your services and priority customer groups
- Target countries and required languages
- Existing domain, website, logo and licensed photographs
- Required functions and existing software
- Budget range, timing and the person approving content
Questions before you start
Can I keep my domain?
An existing domain can be assessed as part of the project. Explain where the website and email are hosted so changes can be planned without unintentionally disrupting email.
Do all language versions need their own content?
Each version needs complete, understandable service information for its audience. Translate navigation, calls to action and forms as well as the main text. Add local information only when it is accurate and useful.
Is an AI assistant included?
An AI assistant, webshop or portal is a requested feature, not an automatically included product. Its purpose, data sources, access and cost must be agreed in the proposal.
Turn a requirement into a result you can verify
An example to discuss
A service business wants enquiries from two language markets. A visitor selects a service, reads the information in their language and submits an enquiry. Agree the target markets, languages and functions in the proposal first.
What should be checked before handover?
Test every language journey on mobile. Check that switching language opens the same topic, contact details are correct and the enquiry records its source page and language. Error messages should explain how the visitor can continue.