Addressing ten proposal components

Below, we explicitly address the ten requested proposal components. The references connect this compact decision summary to the full elaboration in the preceding chapters.

We recommend a WordPress content platform that connects Chrysal’s customer questions to knowledge, evidence, solutions and local specialists, with a recognisable brand experience and independent editorial management. Our advice is Core plus Recommended: €22,610 one-off (190 hours). Core alone is €14,756 (124 hours); the five Recommended building blocks add €7,854 (66 hours). Hosting, maintenance and plugins are separate at €240 per month (€2,880 per year). All amounts exclude VAT and remain draft until scope and commissioning are confirmed. AI, e-commerce and integrations are future extensions, not included launch functionality. The detailed arguments and conditions are in chapters 1–3 and 15–17 and in “Proposal & investment”.

The website supports the transition to an integrated solutions partner by connecting customer challenges with knowledge, evidence and different types of solutions. The existing flower-care offering remains directly accessible. Growth domains can be set up using the same model. The strategic alignment towards 2035 lies in this extensible foundation and a repeatable decision-making cycle, not in a promise that technology will require no maintenance until 2035. See chapters 1–5 and 9.

The six customer journeys determine the information architecture and priority screens. Technical content receives clear document metadata and source references. A responsive design system unites technical authority with human imagery and understandable language. A small editorial team manages pages using components and patterns. See chapters 4–6 and 10.

Launch includes research, technical SEO, question-driven content structure, search, a measurement foundation and controlled migration. A new generative AI interface is optional. The second brain will, however, be prepared as a managed knowledge source. We measure search performance, user behaviour, qualified enquiries where feedback is available and a repeatable sample of AI mentions. See chapters 7, 8, 11 and 12.

WordPress with the block editor, managed components and an explicit language and market model offers an appropriate combination of editorial freedom and manageability. Hosting, caching, security, privacy, accessibility and continuity are set up in an integrated manner. Integrations are selected based on business usefulness. Regional commerce receives a documented expansion path. See chapters 9, 10 and 13.

We inventory what exists, preserve valuable content and URLs where possible and test the entire transition. Training starts before the final content round and is assessed using real tasks. Two weeks of monitoring with SEO/GEO monitoring is included; warranty and support follow on from this. See chapters 12, 14 and 17.

Two published Afdeling Online projects illustrate relevant parts of the assignment. We present these as experience with B2B, UX, content, findability and scalable commerce. The sources do not demonstrate an identical global rollout; scope, period and reference contacts will be additionally confirmed before submission.

Moduplus as a relevant example

Moduplus is relevant because one website serves two audiences: professional partners and dealers through a secured login environment, and end users looking for information and inspiration. For Chrysal, this mirrors the desired dealer environment and the combination of B2B customers with consumers as end users. Thermaflex (multi-market B2B with technical products) and Solarge (visual storytelling around a sustainable proposition) are further websites built by Afdeling Online. [5]

Bamboovement as relevant experience

The Bamboovement is relevant because of the combination of brand story, UX, a workable CMS and expandable e-commerce. The published case also describes attention to preserving existing URL value. This aligns with Chrysal’s wish to add commerce functions later while independently managing the website in the meantime. Here too, we link the experience to the approach; we do not claim equivalent international platform complexity. [6]

Explaining the core team and allocation

For Chrysal, we propose a compact core team with specialists at set points. In this draft, Jaap is the intended strategic lead and commissioning party on the agency side; his availability and the other names will be established before the final proposal. The roles and involvement below already make clear who actually bears responsibility. The hours are part of the budget in chapter 16 and are not additional to it.

Organising continuity through replacement

Continuity is organised with a second technical contact and a substitute for project coordination, plus shared documentation and code. In the event of unavailability, the current handover is used first and Chrysal receives a replacement and scheduling proposal. The final proposal includes names, relevant experience, specific availability and substitutes. This is a supporting document still to be completed, not an already confirmed staffing plan.

A phased schedule runs from discovery to design, build, migration, training, UAT and launch. Approval takes place on specific deliverables. Chrysal provides one product owner, subject-matter experts and local owners. A sponsor decides on scope and budget. We safeguard coherence and report weekly on progress and bottlenecks. See chapters 15, 18 and 19.

Core and Recommended have separate budgets and explicit quantities. Future functions, regional commerce, licences, variable costs, maintenance and support are listed separately. Unknown integrations and content volumes are not a hidden fixed-price commitment. A changed scope requires a decision on price and scheduling in advance. See chapters 16 and 17.

The biggest risk is that international content and decision-making fall behind the technical build. A second risk is that local variation leads to an unnecessarily large number of versions. We limit this with clear source owners, a central architecture and early content deadlines. We also assess whether desired integrations genuinely add value. The risks below are tracked in the project register.