Proposal · RFP v2.1

Planning & roadmap

Chrysal Website 2027 · Extended draft · 19 October 2026

RFP 15 · 18 · 19

From a shared direction to a strong launch.

An indicative 2027 roadmap with concrete milestones, decision points and Chrysal’s involvement. The final schedule will follow budget approval and discovery.

Selected scenario

Core launch

Including stabilization

Approximately 24 weeks

Start · planning example

11 January 2027

The phases below follow the roadmap from the proposal: kick-off on 11 January 2027, launch in weeks 21–22 (late May or early June, after the Mother’s Day peak) and monitoring through week 24. The final dates follow budget approval and discovery. Future options will receive a separate roadmap and will not automatically shift the base launch.

Before the start

November – December 2026

Selection & budget decision

Commission and availability confirmed

Partner selection, clarification, scope selection and budget approval.

Chrysal’s contribution

Sponsor, Marketing, IT and procurement assess the proposal and assumptions.

Dependency

Internal investment approved

Week 1–2

January

Discovery

Go/no-go 1 · Direction and scope approved

Site structure and navigation, six customer journeys, content model, CMS and localisation agreements and the SEO baseline.

Chrysal’s contribution

Stakeholders join one or two discovery sessions; access to sources, analytics and exports.

Dependency

Sources, accounts and experts available

Week 3–6

Late January – February

Design

Go/no-go 2 · Design approved

Five key page designs and a recognisable block library.

Chrysal’s contribution

Brand and content review; consolidated feedback within five working days.

Dependency

Visual material and brand agreements available

Week 6–13

February – early April

Development

Platform ready on the test environment

A working WordPress platform with blocks, content types, languages and markets, search, forms and the technical SEO/GEO foundation.

Chrysal’s contribution

Short weekly check-in; technical information and local contact data.

Dependency

Design and content model approved

Week 11–18

March – May

Fill workshop & content

Content deadline week 18

Fill workshop in week 11; Chrysal fills content and translations, with redirect mapping in parallel.

Chrysal’s contribution

Product owner, experts and local marketeers supply and review content; content deadline week 18.

Dependency

Usable export, rights and translation capacity

Week 19–20

May

User acceptance test

Go/no-go 3 · Launch approved

Customer journeys and editorial tasks tested with real content; findings resolved and rechecked.

Chrysal’s contribution

Product owner and editors test; the privacy officer reviews consent.

Dependency

Content complete, no open blocking findings

Week 21–22

Late May – early June

Launch

Production accepted

Controlled go-live after the Mother’s Day peak, with verified forms, measurements and a recovery route.

Chrysal’s contribution

Product owner, IT and contact follow-up available on the agreed working day.

Dependency

Chrysal gives content and technical launch approval

Week 22–24

June

Monitoring & stabilisation

Short evaluation and handover

Two weeks of monitoring, issues fixed directly and a short evaluation.

Chrysal’s contribution

Consolidate reports; discuss results and follow-up priorities.

Dependency

Reliable production and measurement data

Governance that monitors progress

One product owner

Chrysal consolidates feedback and content-related decisions. The sponsor decides on scope and budget; experts validate claims and local teams validate translations.

Fixed working cadence

Weekly progress updates on schedule, budget and risks; fortnightly demonstrations during the build. Feedback within five working days is a working assumption.

No hidden scope growth

The impact of every change on time, money and management is assessed in advance. Decisions are recorded, with written approval before additional work.

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.