The website, our top marketing driver of business.
The keyrus.com redesign is not a cosmetic project: it's the marketing asset that generates the most pipeline. Every call in this plan serves three optimizations: UX (conversion), SEO (organic traffic) and GEO (visibility in generative AI answers, where the structured HOM narrative becomes a direct advantage).
What the dev instance actually contains
Verified on 6 July via the Contentful API: keyrus-redesign.netlify.app is connected to
the development-3 environment of the keyrus space.
The new structure is in place, and the Keyrus AI manifesto copy is now integrated: master → development-3
promotion completed on 6 July (43 entries, 508 fields, 7 languages, published). The dev instance now starts from
an editorial base aligned with production keyrus.com.
Already in place on the dev instance Verified
- New homepage : "newHomepage" entry published, Services, Playbook, Testimonials, About, Join Us sections match the site.
- New Services format : 5 "topService" entries published: Business transformation & Innovation, Data & AI Foundations, Engineering, Applications, + Keyrus Academy in the menu.
- Insurance pilot industry : complete "industryPage" with a 6-step methodology (Diagnose → Sustain), linked use cases and insights.
- Playbook & use cases : key plays connected to the homepage and the industry pages.
- Level-2 service pages : full template: expertise areas, dedicated expert, form, resources, final CTA.
- Keyrus AI manifesto copy : "We operationalize intelligence", About, sub-pages and 13 rewritten services (Jesse's work + FR/ES/PT matrices): promoted from master to development-3 on 6 July, all languages.
To address before V1 Content
- Services title to relocate : the dev-3 "services" model has been reworked (redesign); "From intelligence to impact / De l'intelligence à l'impact" needs to be placed back into the new model (newHomepage / topService).
- Visible placeholders : fictional expert "Marie Dupont", "To be qualified" fields, KPIs with no value on the Business transformation page.
- Duplicated key plays : the Insurance page shows the same Anaplan case 3 times (variants 1 and 3).
- Orphaned topService : "Data & AI Strategy" exists in the database but is no longer in the menu; to be decided alongside the services renaming (decision D2).
- Outdated homepage narrative : the current hero "Transform Your Business with Data & AI" predates the Architect of intelligence positioning (decision D6).
| Surface | Contentful content (development-3) | HOM narrative alignment | Status |
|---|---|---|---|
| Homepage /fr/fr/home | newHomepage published, complete | To rework: hero, HOM block, taglines | To update |
| Services 5 topServices + sub-services | New offer format in place | Naming to decide (D2), HOM block to add | To update |
| Industries Insurance only | Full, rich template | Format to validate as reference, then duplicate | Pilot |
| Portfolio / Playbook Existing key plays | Connected, legacy content | Dependency: case rewrite + HOM integration | Dependency |
| About Us Legacy structure | Manifesto copy integrated on 6 July (7 languages) | Structure reformat still pending (D5) | To reformat |
| HOM Doesn't exist on the site | No dedicated entry | Location to decide (D1); 677 existing pieces of content already mapped to HOM (19 Jun audit) | To create |
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 3 layers of the Human Orchestrated Model™
Continuously steer decisions and execution toward measurable business impact. Proof: 12 % less spend on operations for a video giant.
Who decides, who governs, who's accountable: clear human oversight and pragmatic governance. Proof: 100 % ROI on a European bank's first GenAI programs, 20+ use cases.
Structure, activate and govern data and agents: the foundation for deploying AI at scale. Proof: $5M+ saved per harvest at an agribusiness producer.
Portfolio: 4 composable capabilities
The narrative's taglines, to highlight and sprinkle across the whole site (hero, sections, CTAs, offer pages).
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.
Mix by HOM layer 677 thematic content items
The blind spots the grid reveals To fill
- Semantic enablement & knowledge graphs : an official HOM capability, zero content. The portfolio's clearest white space.
- Agentic & autonomous AI : 30 insights but 4 key plays. We talk about it without proving it: critical for an "Architect of intelligence" positioning.
- AI governance, ethics & responsible AI : 8 pieces of content, no key play. The corporate portfolio's Trust & Governance pillar with no client proof.
- Planning, FP&A & predictive models : 38 key plays but 5 insights. The reverse: proof without thought leadership, an EPM lane to activate.
| Layer | Sub-theme | Insights | Key plays | Total |
|---|---|---|---|---|
| L1 | Data platforms & cloud architecture | 83 | 57 | 140 |
| L1 | Governance, trust & responsible data | 56 | 17 | 75 |
| L1 | Data products, monetisation & DataOps | 21 | 9 | 30 |
| L1 | Cybersecurity & resilience | 11 | 5 | 17 |
| L1 | Semantic enablement & knowledge graphs White space | 0 | 0 | 0 |
| L2 | AI strategy, value & adoption | 59 | 28 | 89 |
| L2 | Generative AI, ML & LLM platforms | 24 | 11 | 37 |
| L2 | Talent, skills, AI literacy & change | 17 | 16 | 36 |
| L2 | Agentic & autonomous AI | 30 | 4 | 34 |
| L2 | AI governance, ethics & responsible AI | 8 | 0 | 8 |
| L3 | Analytics, BI & dashboards | 33 | 44 | 79 |
| L3 | Planning, FP&A & predictive models | 5 | 38 | 63 |
| L3 | Performance, profitability & EPM | 10 | 33 | 46 |
| L3 | Decision intelligence & insight-to-action | 12 | 10 | 23 |
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.
9 structuring decisions to make before work can start
Each decision is checked off live: choices and comments are kept in the browser, and the summary copies in one click for the write-up. Recommendations are proposals from the project team.
Who produces what, with which dependencies
The critical path runs through the 17 July structure validation: it unlocks industries and offers content production, which then feeds creative and integration. Detailed backward schedule to be set the week of 7 July.
| Workstream | Scope of work | Dependencies | Owners | Milestone |
|---|---|---|---|---|
| Homepage | New manifesto hero, HOM block, taglines, image selection | D1, D6 · keyrus-new copy | Baptiste · Chanti | Jul 17 → Sep 10 |
| Services / Offers | New offer format (corporate presentation approach), generic offers via PAT, naming | D2 · refined corporate presentation | Jesse · Baptiste | Jul 17 → Sep 10 |
| HOM | Building the HOM surface on the site: content, design, linking with offers and portfolio | D1 · refined V1 narrative | Baptiste · Jesse · Chanti | Jul 17 → Sep 10 |
| Industries | Granularity validated → content format per industry → industry experts kick off | D3, D4 · Insurance format validated | Jesse + subject-matter experts | Jul 17 → Sep 25 |
| Portfolio / Playbook | Rewriting cases in HOM format, removing duplicates, quantified proof per layer; priority on the audit's blind spots (agentic key plays, AI governance) | D1, D9 · depends on cases supplied by the practices | Jesse · Baptiste | → Sep 25 |
| About Us | Full reformat: the manifesto copy is already on the dev instance (promoted on 6 July) | D5 · copy integrated ✓ | Baptiste · Jesse | → Sep 25 |
| Corporate presentation | Refine the V1 narrative, highlight the 9 taglines: the site's source of truth | None: upstream of everything | Stéphane · Christophe | → end of July |
| UX & creative | User experience, image selection, validation via Shift: homepage, portfolio, HOM, menu | D7 · mockups for the workstreams above | Chanti · Baptiste | ongoing → Oct 1 |
| Contentful integration | Manifesto copy promoted on 6 July ✓ · remaining: placeholder cleanup, HOM content model, taxonomy tags (D9), repositioning the services title | All content validations | Baptiste · Erwan | Sep → Oct 10 |
| Dev & go-live | Web development integration, QA, production cutover, comms plan | Everything above | Erwan | → Oct 15 |
Scaling up: a team of 6
The October target means expanding the team: Jesse and Chanti (EPM) join the setup, each on their own lane. Industry experts will be mobilized workstream by workstream.
Validate the structure of added content (typically Industries), drive validations with Eric Cohen, and refine the corporate presentation narrative.
Lead UX, content and creative proposals. Drives the plan, the Contentful instance and narrative integration.
Content and recommendations: rewritten About and Services matrices, audit of the 1,087 pieces of content mapped to HOM, industry formats, offers.
Creative and UX: a major contributor on the creative side, image selection, mockups for the new surfaces.
Integrates web development on the instance, QA and production cutover.
Two passes: V1 validation on 25 September, final validation on 10 October.
Brought in once the per-industry format is validated (decisions D3 and D4): which industries, which people.
From approved strategy to launch on October 15
Two milestones this fortnight: roadmap and strategy approved Thursday 10 July, structure approved on the 17th. Production then runs through 10 September with the ambition of a complete V1, for two Eric validation loops. The detailed backward schedule (dependencies, priorities, deadlines per workstream) is set the week of 7 July.