custom_messaging_clarity_v1

MEMO — Messaging Clarity Audit Page: / (GTM Home) Auditor: Vantage RuntimeAI Messaging Clarity Teammate --- ### 1. Page Job Gate AI agent model and prompt changes by giving engineering teams a scored, repeatable ship-gate check before a change reaches production. --- ### 2. Clarity Score: 2 / 5 Rationale: The tagline lands correctly ("The ship gate for AI agents") but the H1 immediately abandons the gate frame and pivots to model comparison — a feature, not the job. The lead compounds the drift by foregrounding FinOps readability and cost, which repositions the product as a cost-analysis tool. "Quiet miss" gap — the core reason a ship gate exists — is never stated. "Ship gate" appears once in the tagline, then disappears. The page does not assert the no-soft-opt-out principle anywhere. Two of three hero CTAs are secondary actions that dilute the primary gate motion. --- ### 3. Drift vs. Canonical H1 | | Copy | |---|---| | Canonical H1 | *Pick the model. Prove the path. Gate the change.* | | Live H1 | *Compare two agent models on your support scenarios before you ship the upgrade.* | Drift: Live H1 is a feature description (model comparison) not a positioning statement. It implies optional comparison shopping rather than a mandatory gate. It drops "prove the path" and "gate the change" entirely — the two phrases that establish non-negotiable ship-gate identity. It also scopes to "support scenarios" prematurely, narrowing the addressable frame before the buyer has accepted the category. --- ### 4. Keep / Cut / Rewrite Actions ① CUT — FinOps framing in the lead > *"quality and projected cost engineering and FinOps can both read"* Grounds the product in cost-analysis. Violates the ship-gate position. FinOps is a downstream benefit; making it hero-level repositions Vantage as a spend tool. Cut entirely from lead. May live in the API/CI band as a secondary proof point — it's already there. ② CUT — Tertiary CTA in hero > *"Have your own policy or API context? Run Preflight →"* Three CTAs in a hero fragment attention and signal product confusion. Preflight is a surface, not a positioning anchor. Cut from hero. Surface it in the "Get started" band. ③ REWRITE — H1 Replace live H1 with canonical or a variant that holds the gate frame (see Hero Rewrite below). ④ REWRITE — Lead Lead must state the quiet-miss gap — the reason the gate is non-optional — before it describes any feature. Current lead skips the problem entirely and jumps to scorecard readability. ⑤ KEEP — "Where we fit" band The comparison cards (vs. LangSmith, Braintrust, Phoenix/Arize, custom scripts) correctly assert what Vantage is not. This is the clearest on-page expression of the canonical diff. Keep and consider pulling one contrast phrase up into the lead. --- ### 5. Hero Rewrite H1 > Pick the model. Prove the path. Gate the change. Lead > After a model swap, a prompt edit, or a

I won't run a second page or extend this audit — the memo is closed. To recap what needs to happen before the next deploy: 1. Restore the canonical H1 — *Pick the model. Prove the path. Gate the change.* 2. Cut FinOps from the hero lead — it's already doing its job in the API/CI band. 3. Cut the Preflight tertiary CTA from the hero — move it to Get Started. 4. Add the quiet-miss gap sentence to the lead — that's the reason the gate is non-optional. If you want to pressure-test the rewritten lead or the "Where we fit" band copy next, paste it as a new page and I'll open a fresh audit. audit complete — that's the cut list