Add Sales Implementation Guides with L1-L4 autonomy ladder#627
Add Sales Implementation Guides with L1-L4 autonomy ladder#627jordanc-relevanceai wants to merge 20 commits into
Conversation
…e case pages New Implementation Guides tab with vertical sections (Sales, Marketing, Customer Success, Support, Solution Engineering, RevOps, Human Resources). Sales section includes overview with agent cards, quickstart guide, individual use case docs, and video library. Agent card CSS, Build overview page, and updated use case content for all verticals. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
Restructure the Sales section into a GAME START overview that forks into three persona Tabs (Just results / Customize / Build with code) on a single getting-started page. Tabs deep-link via URL hash so cards on the overview land on the correct tab pre-selected. Styling: new path-picker wrapper with a soft blue-to-purple gradient and layered shadow, pill-style tabs with an indigo gradient active state and a glow accent. Replaces hard borders with shadow-led depth to align with the Relevance AI brand language. Also: rename "Super GTM" to "SuperGTM" (one word) across all pages, redirect old templates page links to the Marketplace overview, and retire the top-level use-case stubs replaced by the sales/* tree. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
New /use-cases/blueprints landing as the entry point for the Blueprints
tab — a hook plus cards for each function (Sales, Marketing, Customer
Success, Support, Solution Engineering, RevOps, HR) and a brief
explainer on the persona-picker pattern.
Sales overview retired. Its hook, motions, and Lightspeed customer story
move into use-cases/sales/getting-started.mdx — motions are integrated
naturally at the end of each persona tab (no shared "Or pick a play"
header), with the customer story framed per-persona inside each tab.
Build with code tab rewritten to reflect what's actually there:
Programmatic GTM as an MCP for AI coding assistants, custom Python/JS
code blocks inside Tools, and the JS SDK for calling Agents from your
own apps. Drops earlier overstatements ("git-versioned prompts",
"workforces defined in code").
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
All six motion pages were walls of H2 + bullet list. Convert the repeating sections to visual components so the page reads at a glance: - "What the Agent does" → CardGroup with icons - "How to set it up" → Steps component - "Scaling it" → CardGroup - "Common pitfalls" (prospect-research only) → AccordionGroup Also fixes broken internal links uncovered while editing — the older motion pages used /agent/..., /knowledge/..., /workforce/..., and /agent/build-your-agent/escalations paths that don't exist in this repo. Redirected to the canonical /build/... paths and to /alerts in place of the missing escalations doc. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
- Rename Blueprints to Guides; the landing page defines L1-L4 once for all verticals - Refactor Sales getting-started to pull shared scaffolding (Marketplace, motions, video, ladder) out of the persona tabs so each path carries only what's unique to it - Rename persona tabs to "No build / Build visually / Build with AI" so they describe the actual surface, not a muddled "Customize" - Apply the prospect-research shape across all 6 sales motion docs: When this pays off / The shape / L1-L4 ladder / Common pitfalls - Replace <Steps> blocks with prose under the ladder per house style
…cture Main restructured SuperGTM from a single page into a directory of pages. A redirect from the old URL still exists in docs.json, but the canonical path is now /get-started/chat/super-gtm/introduction.
The auto-merge of docs.json during rebase promoted the Guides tab to a top-level product entry, which mintlify's schema rejected. Moved it back into navigation.products[0].tabs and positioned it at the end of the tab list after Enterprise.
Per team decision: existing SuperGTM docs stay, but no new content should reference it. Rewrote each motion doc's L1 to "Ask the Agent in chat" (open a cloned or built Agent, no super-agent dependency) and dropped the SuperGTM sections from the Sales getting-started No-build and Build-with-AI tabs.
Pre-SuperGTM-removal, L1 was "talk to SuperGTM" and L2 was "clone or build a reusable Agent." Now L1 already establishes the Agent exists (cloned or built), so L2's "Build a reusable X Agent" intro became redundant. Reframed L2 across crm-data-enrichment, meeting-briefs, lead-scoring, and competitive-intelligence to focus on shaping the Agent rather than re-introducing it.
Marketing → Autodesk (Allen Roh) + Lightspeed (Miles Smith) CS → Canva (Rob Giglio, CCO) Support → Canva (Behind the Scenes: AI Agent Strategy) SE → Canva (Michael Denari, Head of IT) + KPMG (Levi Watters, Partner) RevOps → KPMG (Lachlan Hardisty, Director of AI Lab) This is the video swap only. The full Sales-shape rebuild (per-vertical getting-started page + motion docs) is the next step.
Move use-cases/lifecycle-marketing.mdx → use-cases/marketing/getting-started.mdx and reshape it: intro, Marketplace cards, persona tabs (No build / Build visually / Build with AI), four levels in marketing, motion cards, two Agents@Work videos. Add three Marketing motion docs following the same shape as Sales motions: - lifecycle-campaigns.mdx - content-repurposing.mdx - campaign-analytics.mdx Each carries: When this pays off / The shape / L1-L4 ladder / For technical teams card / Common pitfalls. Update docs.json nav to add the Motions sub-group under Marketing and add a redirect from the old /use-cases/lifecycle-marketing path.
The Marketplace template cards (3 cards) and motion cards (3 cards) were in cols=2 grids, which left the third card orphaned on its own row. Switched to cols=3 so each row fills evenly.
Move and reshape each vertical to match the Sales pattern: a getting-started page (intro, Marketplace cards, persona tabs, autonomy ladder, motion cards, Agents@Work videos) plus three motion docs (When this pays off, The shape, L1-L4 ladder, Common pitfalls). Renames + new files: - customer-success.mdx → customer-success/getting-started.mdx + account-health, qbr-prep, renewal-expansion - customer-support.mdx → customer-support/getting-started.mdx + ticket-triage, response-drafting, kb-generation - solution-engineering.mdx → solution-engineering/getting-started.mdx + rfp-responses, demo-prep, discovery-summaries - enrichment.mdx → revops/getting-started.mdx + pipeline-hygiene, lead-routing, data-dedup Update docs.json: replace each flat vertical group with a Sales-style group (getting-started + Motions sub-group), add redirects from old URLs. Fix the function-picker cards on use-cases/guides.mdx to point at the new landing pages. All 3-card CardGroups use cols=3 to avoid the orphan-card layout issue.
Each vertical's getting-started.mdx had sidebarTitle "Getting started", which differs from Sales (sidebarTitle "Sales"). The sidebar should show the function name on the landing page so users can navigate by vertical.
- Replace the L1–L4 ladder with Where to start / Where to take it on all
21 motion docs; clone cards now link real Marketplace agents
- Reframe L4 "self-learning" claims to the eval-feedback loop and drop
fabricated target percentages
- Fix the inaccurate "full list at Integrations" wording
- Drop the chat-surface phrasing ("open in chat" -> "open")
- Remove the "Drop into code" subsection from getting-started pages
- Make the autonomy-ladder cards non-clickable
Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Resolved style.css by keeping both additions: main's changelog timeline / tag / availability styles and this branch's path-picker, in-page Tabs, and agent-card styles. They target different selectors, so nothing was dropped. All other files auto-merged. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
talent-hr.mdx was a "Coming soon" stub not in docs.json nav and with no inbound links; .agent-card CSS was used only by that page. Both removed. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
The pill/centered tab styling was global, hitting all 48 <Tabs> pages. Scoped the seven tab rules under .path-picker so only the use-case getting-started Guides get the pill look; every other page falls back to Mintlify's native tab styling. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
- Renamed use-cases/ -> guides/ (tracked as renames); the overview is now guides.mdx at repo root, giving /guides (same file+folder pattern as changelog.mdx + changelog/) - Updated nav paths, in-page links, and the autonomy-ladder link to /guides/... - Pointed the five legacy redirect destinations at /guides/...; kept their /use-cases/... sources so old links still resolve - Reverted the api-integration.mdx wording change (left as-is) Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
🎯 Vibe checkReviewed: 27 files (2 with issues, 25 clean) — 4 additional files were deleted ( Scores
Score key: 🟢 9–10, 🟡 6–8, 🔴 1–5. ✨ Overall vibe: This is a well-executed, high-volume PR — 26 new pages with near-perfect template discipline. The consistent L1–L4 autonomy ladder, day-one prompts, and "Common pitfalls" pattern across every motion page would make any technical writer proud. Two small fixes needed: one banned word and one missing redirect. 🔧 Issues (2)
✅ Clean files (25)
🔋 Credit usage
Files read: Non-doc files: |
alexrelevanceai
left a comment
alexrelevanceai
left a comment
There was a problem hiding this comment.
Added comments in Slack
- Landing-page sidebarTitle -> "Getting started" (was duplicating the vertical group name, e.g. Sales > Sales) - Nav subgroup "Motions" -> "Use cases" - In-page "motion(s)" -> "use case(s)" throughout the Guides - Common pitfalls: replaced the stacked, identical circle-exclamation icons with a distinct, content-fitting icon per pitfall across all 21 use-case docs Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
🎯 Vibe checkReviewed: 29 files (27 with issues, 2 clean) — plus Scores
Score key: 🟢 9–10, 🟡 6–8, 🔴 1–5. ✨ Overall vibe: This is a well-executed, high-volume PR — 27 pages, consistent template, zero banned words, no structural problems, solid concrete examples throughout. The only thing dragging it down is a mechanical find-and-replace job on two product terms ( 🔧 Issues (9)Product term:
Product term:
Product terms:
Grammar (6 getting-started pages)
Navigation: missing redirect (docs.json)
Navigation: redirect destination mismatch (docs.json)
🧩 Component suggestions (1)
🏗️ Page structure (1)
|
| Item | Count |
|---|---|
| Files reviewed | 29 MDX + docs.json + style.css = 31 |
| Context pages read | 0 (all changed files reviewed directly; no linked context pages needed given consistent template) |
| Total lines processed | ~4,100 |
Files read: guides.mdx (51 lines), style.css (379 lines), guides/sales/getting-started.mdx (196 lines), guides/sales/lead-scoring.mdx (96 lines), guides/sales/meeting-briefs.mdx (96 lines), guides/sales/personalized-outbound.mdx (96 lines), guides/sales/competitive-intelligence.mdx (96 lines), guides/sales/crm-data-enrichment.mdx (96 lines), guides/sales/prospect-research-use-case.mdx (105 lines), guides/marketing/getting-started.mdx (196 lines), guides/marketing/campaign-analytics.mdx (96 lines), guides/marketing/content-repurposing.mdx (96 lines), guides/marketing/lifecycle-campaigns.mdx (96 lines), guides/customer-support/getting-started.mdx (187 lines), guides/customer-support/kb-generation.mdx (96 lines), guides/customer-support/response-drafting.mdx (96 lines), guides/customer-support/ticket-triage.mdx (96 lines), guides/customer-success/getting-started.mdx (187 lines), guides/customer-success/account-health.mdx (96 lines), guides/customer-success/qbr-prep.mdx (96 lines), guides/customer-success/renewal-expansion.mdx (96 lines), guides/solution-engineering/getting-started.mdx (196 lines), guides/solution-engineering/demo-prep.mdx (96 lines), guides/solution-engineering/discovery-summaries.mdx (96 lines), guides/solution-engineering/rfp-responses.mdx (96 lines), guides/revops/getting-started.mdx (189 lines), guides/revops/data-dedup.mdx (96 lines), guides/revops/lead-routing.mdx (96 lines), guides/revops/pipeline-hygiene.mdx (96 lines), docs.json (partial, ~50 lines)
2 participants
Summary
Adds a Guides tab to the docs — a function-by-function persona walkthrough of building with Relevance — now built out across all six GTM/CX functions (Sales, Marketing, Customer Success, Support, Solution Engineering, RevOps).
/use-cases/guides): L1 Assisted → L2 Copilot → L3 Autopilot → L4 Self-driving. Each function's landing page references it rather than redefining it (the ladder cards are display-only, not links)..path-picker), so the other ~42<Tabs>pages across the docs keep Mintlify's native tab style.main— resolved astyle.cssconflict by keeping both sides (main's changelog styling + this branch's path-picker/tab styling); everything else auto-merged.Test plan
mintlify dev— the Guides tab renders at the end of the tab list, after Enterprisegetting-started, flick through the No build / Build visually / Build with AI tabs — each path reads as distinct, not three copies of the same page/use-cases/guides/get-started/chat/super-gtm/introduction<Tabs>page (e.g. abuild/tools/tool-steps/*page) renders native Mintlify tabsResolved since the first draft
use-cases/talent-hr.mdx(orphaned, not in nav) removed, along with its unused.agent-cardCSSuse-cases/revops/*(the earlierenrichment.mdxnaming mismatch is gone)🤖 Generated with Claude Code