Conversation
Co-Authored-By: mintlify[bot] <109931778+mintlify[bot]@users.noreply.github.com>
![cursor[bot]](https://avatars.githubusercontent.com/in/1210556?s=60&v=4){kind=small}
There was a problem hiding this comment.
Cursor Bugbot has reviewed your changes and found 2 potential issues.
Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.
| 2. **The conversation goes deeper.** Instead of surface-level "what are your challenges," you're discussing specific metrics, workflows, and decisions. | ||
| 3. **You're positioned as a strategic partner.** You're not selling software—you're helping them see their situation more clearly. | ||
|
|
||
| That's the difference between a vendor and a trusted advisor. That's how you productize sales. |
There was a problem hiding this comment.
Internal sales playbook published to public documentation
High Severity
This file is an internal sales enablement playbook (competitive positioning, buyer manipulation tactics, internal metrics like "48% of docs traffic is AI agents," talk tracks against competitors like Docusaurus and Confluence) being added to what appears to be the public Mintlify documentation repository. All other files in guides/ are user-facing docs. While omitted from docs.json navigation, the page is still accessible via direct URL and search-engine indexable.
| | --- | --- | | ||
| | New product launch | "When does the new product ship? What's the plan for docs?" | | ||
| | Headcount constraints | "If you can't hire more support reps, how do you handle growth?" | | ||
| | Competitive pressure | "When you lose deals to [competitor], what do they say about your docs?" | |
There was a problem hiding this comment.
Markdown link syntax breaks placeholder rendering
Medium Severity
[competitor] uses markdown reference-link syntax. Without a corresponding link definition, MDX parsers will either render it as a broken/empty link or strip the brackets entirely, losing the intended placeholder meaning. The brackets need to be escaped (e.g., \[competitor\]) to render as literal text.
Created a comprehensive sales training guide covering consultative selling techniques for Mintlify. The guide includes the hypothesis-question-depth framework, persona-specific discovery questions, AI-native positioning strategies, and practical scenarios.
Files changed
guides/sales-training.mdx(new)Note
Low Risk
Documentation-only change adding a new guide; no code paths, security, or runtime behavior are affected.
Overview
Adds a new
guides/sales-training.mdxdocument that trains reps on consultative selling for Mintlify, introducing an opinion-led discovery framework (hypothesis → question → depth).The guide includes persona-specific discovery questions (engineering, DevRel, writers, platform/KB, support), an AI-agent traffic positioning angle, and playbook sections for quantifying pain, creating urgency, and running sample discovery scenarios.
Written by Cursor Bugbot for commit ced6da7. This will update automatically on new commits. Configure here.