How a project runs
A standard English corporate website takes 15 to 45 working days from the first conversation to launch. The main variables are the number of pages, the number of language versions, and how quickly product specifications and images reach us.
The seven stages
| Stage | What we do | What we need from you | Typical duration |
|---|---|---|---|
| 1. Discovery | Understand your products, target markets, buyer types and competitor websites | A description of your business and who you sell to; two or three competitor sites if you have them | 1–3 days |
| 2. Proposal | Propose the site structure, page inventory and an itemised quotation | Feedback on the scope; confirmation of budget range | 1–3 days |
| 3. Contract | Set out deliverables, timeline, acceptance criteria and payment stages | Signature; first payment | 1 day |
| 4. Design | Homepage design, then inner page styles extended from it | Logo, brand guidelines, product photography or access to your existing image library | 3–7 days |
| 5. Development | Front-end build and backend content management system | Product specifications, certification documents and any existing English material | 7–20 days |
| 6. Content and testing | Content filling, multi-device testing, speed and security checks | Final content review and acceptance testing | 3–7 days |
| 7. Launch and handover | Deployment, indexing submission, handover session and documentation | Acceptance sign-off; final payment | 1–2 days |
Where a project needs an unusual amount of content writing or a large number of languages, stages 5 and 6 extend. We tell you at the proposal stage rather than midway through.
What you receive at handover
- The complete source code and database
- Domain, hosting and SSL certificate credentials in your name
- Administrative access to the content management system
- Google Search Console and GA4 access under your ownership
- A written operations manual and a recorded training session
- Twelve months of fault maintenance from the launch date
What slows projects down
In our experience, delays almost always come from four things — none of them technical.
Product data arrives late
Specifications and dimensions are the backbone of an export website. Without them we can design pages but cannot publish them.
English naming is undecided
If product families have three different English names across your catalogue and your platforms, we have to settle that before writing content.
Approvals involve many people
A single decision-maker for design approval typically halves the review cycle.
Scope expands mid-project
Adding an online store or a dealer portal after development begins affects both timeline and budget. We would rather scope it properly at stage 2.
Ready to scope your project?
Send us your product range and target markets. We will reply with a proposed structure and an itemised quotation.