A rep gets marked down for "not confirming budget early enough" by an AI coach that has never seen the company's actual sales process. Nobody on the team teaches it that way. The AI just assumes it, because that assumption shipped inside the product.
Why this matters
Most AI sales coaching tools arrive with an opinion about what a good call sounds like already built in: confirm budget early, ask a set number of discovery questions before pitching, avoid filler words, close with a clear next step.
That opinion comes from generic sales methodology assembled by the vendor, and because every customer of that vendor gets the same rubric, "good" quietly comes to mean whatever that vendor's product team decided good should mean, whether or not it matches MEDDIC, a proprietary consultative process, or a homegrown approach nobody has bothered to name.
A rep who completed the org's own training can tell within a sentence when a score does not match what they were actually taught, and that mismatch is usually the first reason a coaching tool stops getting trusted, well before anyone questions whether the AI's grading is even accurate.
How it works
Outdoo does not ship a fixed opinion about what a good call sounds like. When generating a scorecard, a manager attaches the org's own playbooks, SOPs, or methodology documents from the Resources library alongside a prompt describing the call type and what should be evaluated.
The model builds the scorecard's criteria and language from that attached material rather than from a stock template baked into the product, so a discovery-questions line item can pull from the discovery section of one playbook while a pricing-objection line item pulls from a separate pricing guide.
Because the standard comes from an attached document rather than the product itself, two teams inside the same org running different sales motions, say a product-led team trained on low-pressure discovery and an enterprise team trained on assertive qualification, can generate two different scorecards that each match what that specific team was actually taught, instead of both being measured against one company-wide default nobody at either team wrote.
What this unlocks
An enablement leader who just finished rolling out a new methodology, a shift to Command of the Message or a homegrown qualification framework the team invented last quarter, can generate scorecards against it the same week, without waiting for a vendor's product roadmap to catch up to how the org actually sells now.
A fast-growing startup whose sales motion does not map cleanly onto any named methodology at all, because the founders built their own approach from scratch, can still get scored against that approach exactly as it exists in their internal docs, rather than getting bent into whichever framework a coaching vendor happened to templatize.
And a manager who inherits a scorecard built by a predecessor can regenerate it straight from the current playbook version, so scoring standards move when the methodology moves, instead of quietly drifting out of date the way a hand-built rubric does once nobody remembers to update it.
See Create a scorecard using AI (with resources) and Managing resources for setup.
A generic rubric can only ever grade against a consensus that nobody on the team actually agreed to. Outdoo grades against whatever standard the org decided was right, even when that standard exists nowhere but in the org's own documents.
See it in Action
Tell us what you're working on, whether that's sales calls, support tickets, or leadership coaching, and we'll show you how it fits.
Talk to Sales