Add Sales Implementation Guides with L1-L4 autonomy ladder#627
Draft
jordanc-relevanceai wants to merge 14 commits into
Draft
Add Sales Implementation Guides with L1-L4 autonomy ladder#627jordanc-relevanceai wants to merge 14 commits into
jordanc-relevanceai wants to merge 14 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.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
/super-gtm/introduction(main restructured it into a directory), repaired the Guides tab nesting indocs.json, placed Guides at the end of the tab listTest plan
mintlify devand confirm the Guides tab renders at the end after Enterprise/use-cases/sales/getting-started— content should feel distinct, not three rewrites of the same page/get-started/chat/super-gtm/introductionautonomy ladderlink on/use-cases/sales/getting-startedand confirm it jumps to the L1-L4 section on/use-cases/guidesKnown follow-ups (not in this PR)
use-cases/talent-hr.mdxexists on disk but isn't in nav (orphaned)use-cases/enrichment.mdx(titled "Enrichment") — minor naming mismatch🤖 Generated with Claude Code