Proposal · RFP v2.1
18. Expected project approach and 2027 roadmap
Chrysal Website 2027 · Extended draft · 19 October 2026
RFP-hoofdstuk 18
A realistic roadmap for 2027
Approximately 24 weeks from kick-off to stabilisation, with a start on 11 January 2027 and a launch in late May or early June as a planning example.
Our response & approach
Schedule and launch date as a proposal
We propose a lead time of approximately 24 weeks from kick-off to the end of stabilisation. The roadmap below uses a start on 11 January 2027 and a launch in late May or early June, after the Mother’s Day peak, as a planning example. The final date will follow after partner selection, budget approval and a check against Chrysal’s commercial calendar and staffing.
| Period and duration | Milestone and decision | Required contribution from Chrysal |
|---|---|---|
| November–December 2026, before project start | Selection, clarification, scope selection and budget decision. | Sponsor, Marketing, IT and procurement assess the proposal and assumptions. |
| Week 1–2, January | Discovery completed: site structure and navigation, journeys, content model, CMS and localisation, SEO baseline; go/no-go 1. | Stakeholders for one or two discovery sessions; access to sources and data. |
| Week 3–6, late January–February | Five key page designs and block library approved; go/no-go 2. | Brand and content review; consolidated feedback within five working days. |
| Week 6–13, February–early April | Development: WordPress blocks, content types, languages and markets, search, forms and the technical SEO/GEO foundation. | Short weekly check-in; technical information and local contact data. |
| Week 11, March | Fill workshop; Chrysal starts filling. | Editors and administrators practise with their own content. |
| Week 11–18, March–May | Content and migration (Chrysal), redirect mapping; content deadline week 18. | Experts validate claims; local marketeers review translations. |
| Week 19–20, May | User acceptance test; go/no-go 3. | Available testers, privacy officer and product owner with decision-making authority. |
| Week 21–22, late May–early June | Launch after the Mother’s Day peak. | Product owner, IT and contact follow-up available on the agreed working day. |
| Week 22–24, June | Monitoring and stabilisation; short evaluation. | Weekly feedback and prioritisation of the follow-up roadmap. |
Decisions and contributions per phase
We structure the planning around decisions and dependencies. Content approval and translations run in parallel with development, so that they do not only begin after the build. Feedback is provided in consolidated form within five business days, unless otherwise agreed in advance. A decision that changes architecture or scope first undergoes an impact analysis. Silence does not constitute content approval.
Monitoring dependencies and feedback
The Mother’s Day peak is a real point of attention in this example. The launch takes place after that peak, in late May or early June. During discovery, we confirm the availability of local editors and experts. Go-live preferably takes place on a Tuesday or Wednesday morning, outside an important trade fair, campaign or sales period. If readiness is insufficient, a new controlled date is chosen.
Availability around the summer
The project manager maintains an action list, decision log, risk register and budget overview. The working team has a brief weekly progress meeting; a demonstration follows every two weeks and a monthly steering committee meeting covers decisions, budget and risks. Chrysal has one product owner who consolidates input, and a sponsor who decides when priorities differ. The roadmap and this decision-making model are the deliverables of this chapter.
Save this page as PDF
The print version is formatted as a document, without buttons or navigation. Choose “Save as PDF” in the print dialog.