Core launch with room for growth

We recommend a core launch in which brand, information architecture, independent editing, localisation and findability fully come together. Advanced AI, personalisation and complex integrations receive an implementation decision only when the value in use, owner and management costs are clear. Technical preparation for these is, however, included from the start.

Prioritising with MoSCoW

During discovery, we work with MoSCoW: Must have, Should have, Could have and Won’t have this time. ‘Would have’ is not a separate category. For each feature, we also identify dependencies and the cost of adding it later. This keeps prioritisation useful when making a budget choice.

Before the working sessions, we analyse the existing results, content and technology. With Marketing, sales, subject-matter experts and representatives from priority markets, we translate the given brand strategy into target groups, customer journeys and requirements. We do not restart the business strategy. The outcome is a validated sitemap, content model, architecture, measurement plan, scope and budget. Chrysal approves this foundation before detailed design and further development begin.

We develop the navigation, content relationships and key screens. Wireframes and prototypes show how a visitor moves from a question to knowledge, evidence and help. We incorporate findings from user tasks before the detailed visual design. The benefit is that structural problems are resolved while changes are still relatively straightforward.

After the visual direction has been selected, we design the components and representative pages for relevant screen sizes. We also discuss how the editorial team will build the pages. Chrysal approves the design system and core templates; two consolidated feedback rounds per design step are included in the budget.

We build the CMS, components, permissions, languages, search function, forms and agreed interfaces. In short iterations, the team demonstrates working elements. Analytics, GTM, consent, performance, security and accessibility are incorporated during development. This avoids separate finishing projects just before launch.

In parallel with development, Chrysal prepares content and translations. Afdeling Online guides the mapping, import and priority content editing within the volumes of the chosen scenario. Together, we check technical content, image rights and local variants. Migration is first performed in the acceptance environment and then checked.

The editorial team receives training before validating the final content. We then conduct technical tests and user acceptance testing. The privacy officer assesses the agreed privacy and consent configuration. The go/no-go also covers migration, measurement configuration, WCAG checks, contact follow-up and the recovery procedure. Chrysal gives explicit approval for the content and the move to production.

Launch takes place on an agreed working day with decision-makers and specialists available. We immediately check the production environment, forms, measurement and redirects. The following two weeks are reserved for stabilisation, bug fixing and SEO/GEO monitoring. Deviations are investigated and corrected when attributable to the implementation. An improvement backlog and handover conclude this phase.