What we learned shipping the Solution Matrix in 48 hours
Two days from internal strategy doc → live on the public site, with full JSON-LD schema alignment, 9 Total Solutions, 6 GEO add-ons, and a 6-row customer-archetype recommendation table. Here's the actual sequence — and why we split the work into two waves.
On 2026-05-02, our internal strategy team finalized the AI Commerce OS Solution Matrix doc — 4 layers, 9 Total Solutions, 6 GEO Enhancement add-ons, 6 customer-archetype combos. By 2026-05-03 it was live on leapunion.com with full JSON-LD coverage.
The work split into two waves: Wave 1 was the visible UI — a new `solutions.ts` source-of-truth feeding both the homepage Services section (4-layer framework with anchor solutions per layer) and the Solution Matrix deep-dive page (9-solution catalog grouped by P1/P2/P3 priority, 6-card GEO add-on row, customer-combo recommendation table). Wave 2 was the AI-readable surfaces — `index.html` JSON-LD `hasOfferCatalog` jumping from 6 generic offers to 15 (9 Solutions + 6 GEO add-ons), `llms.txt` rewriting §About + §Total Solutions + §Customer Archetype Recommendations, and the `knowsAbout` array expanding from 8 to 23 entries.
The lesson: separating "visible UI ship" from "AI-readable schema ship" let us validate each independently. The Wave 1 build verified before Wave 2 touched index.html, so when JSON-LD changes inevitably needed iteration, the visible site never drifted out of sync. Same playbook works for any site refresh: change UI first, schema second, never both at once.
Tools used: Vite 7 + React 19 + Tailwind 3 + shipped via Vercel's GitHub Actions workflow. Total dev time: ~3 hours of focused work split across two sessions. The expensive part wasn't the code — it was the strategy doc that came before.
Want to discuss this with the LEAP team, or get a working call against your own stack? Email contact@leapunion.com with [BLOG] in the subject line.