We killed our homepage graph. Here's what replaced it — and why.
We swapped the NetworkGraph for a live 8-agent CI terminal, ran a 3-agent copy review that cut 6 banned words, and signed our first design partner LOI with a team in Brno running 12% flake rate. Numbers, lessons, and what's next.
Tomas Mertin
4 min read
The NetworkGraph looked good in Figma. Real users didn't get it in 30 seconds. So we killed it.
Shipped
Hero terminal v3. The homepage now leads with a live-feeling terminal that walks through the full 8-agent SDLC pipeline — discovery, test generation, healing, triage, regression, perf, security, and release. It replaces the abstract NetworkGraph we shipped in W18.
3-agent content review. Copywriter, Brand Guardian, and QA Expert agents reviewed every section above the fold. 14 copy diffs landed: stronger verbs, dropped 6 banned words, tightened the trust pill from 23 to 14 words.
Design partner LOI #1. A 35-person SaaS team in Brno signed a letter of intent for the 4-week Design Sprint. Kickoff is W23. They have a Playwright suite with ~12% flake rate — perfect baseline for the case study.
Numbers
Unique visitors: 1,847 (+34% WoW). Discovery calls booked: 6 (vs. 4 last week). Newsletter signups: 22. Time on /pricing: 2m 18s median.
Learned
Concrete beats abstract every time. The NetworkGraph looked beautiful in Figma and tested poorly with humans. The terminal — which shows actual log lines from a fake CI run — communicates the product in 8 seconds. Lesson: if the hero needs explaining, it's wrong.
Brand Guardian caught 6 violations the Copywriter missed. Words like 'exciting' and 'powerful' kept sneaking back in. We added them to the banlist with explicit rejection rules in the agent's system prompt. Eval suite now blocks them at draft stage.
Next week (W22)
Ship pricing page redesign (currently the lowest-converting page). Run the second discovery call batch (4 prospects). Wire up the ROI calculator to actual case study numbers from Theridion users.