The website, our top marketing driver of business.

Architecture, templates and most of the content are already produced

This is the single most important fact in this plan. Jesse and Chanti have produced the menu architecture, the page templates and the bulk of the content; the Keyrus AI manifesto copy has been live on the dev instance since 6 July (43 entries, 508 fields, 7 languages). The 18 September gate is therefore a validation, not a production phase, which is what makes the December release reachable.

Dev instance: keyrus-redesign.netlify.app, connected to the development-3 Contentful environment. Remaining housekeeping on the instance (placeholder entries, duplicated key plays, the services title to reposition) is tracked outside this plan.

7 decisions still open, 4 already settled

Choices and comments are saved live in this browser, and the summary copies in one click for the write-up. Recommendations are proposals from the project team.

From validation on 18 September to release on 3 December

Proposed sequence, to be adjusted and signed off. Validation steps, then development, then the full delivery track: alpha, UAT, a beta phase with its own UAT layer, and a production rollout. Development is 15 working days, Monday 21 September to Friday 9 October. Scroll the chart horizontally on narrow screens.

Exec validation cadence

Run by Stephan and Christophe, roughly every two weeks. The Shift workshop in Paris is the one in-person gate, with all Shift leaders.

Validation process, in order

Click a step for its owner and validation loop.

Four people join the setup in September

On group marketing, on the content that is not industry specific, and on customer references. Industry experts are mobilised per industry once the template is validated.

Joining

In place

HOM becomes the backbone of the site

The corporate presentation V1 (June 2026) sets the narrative: Architect of intelligence, carried by the Human Orchestrated Model™. The site must reflect this architecture: HOM's 3 layers, the portfolio of 4 capabilities, and the taglines sprinkled across all pages. It's also the GEO lever: a proprietary, structured narrative is exactly what AI engines reproduce best.

The narrative's taglines, to highlight and sprinkle across the whole site (hero, sections, CTAs, offer pages).

Open thinking: making HOM demonstrable

The concern raised by the exec team: the positioning is a little too intellectual. HOM and “architect of intelligence” land at manifesto level, and the business directions need real examples to see themselves in it. Not decided, and not blocking the build.

1,087 existing pieces of content, already mapped to HOM

The full portfolio audit (Jesse, June 2026): 553 blog insights, 434 key plays, 100 EPM pages. The 677 thematic content pieces spread across HOM's 3 layers in a balanced way (39 / 30 / 31 %): HOM isn't a narrative to fill in, it's a grid that structures editorial capital that's already there. The remaining 410 (136 industries, 85 events, 69 corporate, 19 client cases, 101 out of scope) cross-tag to a pillar or fall outside scope.

This mapping changes the approach: HOM isn't landing on an empty site. Every surface (HOM, portfolio, industries, insights) can be linked from V1 to existing content tagged by layer, and the editorial calendar can be driven by the grid's gaps rather than ad hoc. That's decision D9.

Who produces what, with which dependencies

The critical path runs through the 18 September validation: it releases development and the remaining content production. Most workstreams are already well advanced, so what follows is mostly finalisation and sign-off rather than production from scratch.