Features
Everything DemandIntel does, and when you would use it
Looking for the short version? The platform overview tells the same story in five minutes.
01 Reporting
One master report for your team
A single, defensible view of team performance, built from real conversations rather than opinions.
- Who it is for
- Sales leaders, managers and team heads who need a clear picture of quality, competency and progress without chasing down spreadsheets.
- When you use it
- Weekly or monthly, scheduled to run on its own, or on demand when a review lands in the diary.
- What it does
- Every rep in the date range aggregated into one report: executive summary, quality and competency views, the action plan for the next thirty days, and an evidence library where each claim traces back to a timestamped moment in a real conversation.
- Why it matters
- Reporting stops being an evening job. Because the report is built from scored conversations rather than opinion, the management picture is already defensible when you walk into the review, and the team sees the same evidence the coaching is based on.
02 Insight
The Insights hub
Every chart in one place, filtered the same way, so the comparisons hold.
- Who it is for
- Managers and heads of sales who want the numbers rather than the advice.
- When you use it
- When you are preparing for a review, checking a hunch, or working out where to spend the next month of coaching effort.
- What it does
- A tabbed hub covering quality, competency and per rep trends, all governed by one shared date range and rep filter, so switching tabs never quietly changes the population you are looking at.
- Why it matters
- Analysis is only useful when it is consistent. Sharing one filter across every view removes the most common source of disagreement, two people reading two slightly different slices of the same data.
03 Quality
QA scorecards with cited evidence
Consistent scoring at full volume, with evidence, so nobody argues about the mark.
- Who it is for
- Quality and compliance owners, and the managers who inherit the scores.
- When you use it
- Continuously, in the background, as conversations arrive.
- What it does
- Bring your own scorecard, or have one written from your conversations. Items are weighted, compliance breaches can be set to fail the conversation automatically, and every single score is cited back to the moment it came from, with the excerpt and a click through to the conversation.
- Why it matters
- Manual quality control samples a handful of conversations and still takes days. This scores what actually happened, at volume, and the citation means a challenged score is settled by listening rather than debating.
Overall QA
86/100
Critical / auto-fail items
04 Capability
Competency frameworks
Movement per person becomes visible, instead of assumed.
- Who it is for
- Managers running development, and enablement teams who have to show a programme worked.
- When you use it
- Each review cycle, and whenever you are deciding who is ready for more responsibility.
- What it does
- Four proficiency levels per skill, assessed from real conversations, with the current period shown beside the previous one so the direction of travel is explicit for each person and each skill.
- Why it matters
- Most capability frameworks are a document nobody scores. This one is scored continuously from evidence, so a development conversation starts from where somebody actually is rather than where they were last assessed.
05 Cadence
Weekly and daily coaching plans
Coaching that arrives without anyone having to prepare it.
- Who it is for
- Reps, and the managers running the weekly one to one.
- When you use it
- Every working day. Monday sets the plan for the week, Tuesday to Friday keep it moving.
- What it does
- One theme for the week and a short daily focus, both drawn from that person's own conversations, delivered by email and in the platform, with progress against the weekly theme tracked as the week goes on.
- Why it matters
- The reason coaching lapses is preparation time. Removing that step means the cadence survives a busy week, and because the focus comes from that person's own conversations, it never feels like generic training.
Week of 12 January
Get the cost of the problem on the table
Up 7 points on last week, across 24 scored calls.
Three things to do this week
- 1Ask what the current process costs, on every first call.
- 2Listen back to Tuesday 10:04, where it worked.
- 3Bring one call to your one to one on Thursday.
06 Proof
Continuous improvement plans
An audit trail of behaviour change, not a chart that drifted.
- Who it is for
- Anyone who has to show the training worked, from the enablement lead to the person signing off the budget.
- When you use it
- At the end of each coaching sprint, and whenever the value of development spend is questioned.
- What it does
- The behaviour change ledger records improvement conversation by conversation: the behaviour that was targeted, the conversations before it changed, and the conversations that show it in use afterwards.
- Why it matters
- A score moving up is not proof, it can move for a dozen reasons. Proving the change one conversation at a time gives you an answer that survives scrutiny.
07 Act
Act coaching management
The coaching plan runs itself, and the manager only makes the decisions.
- Who it is for
- Frontline managers carrying a team, and the leaders who need to know coaching is actually happening.
- When you use it
- In the weekly one to one, and in the ten minutes before it.
- What it does
- A cockpit that orders reps by who needs attention, holds evidence-backed coaching tasks with owners and dates, and keeps a review queue that the system populates automatically with pending evidence pulled from real conversations. Nothing is marked verified or complete without the manager saying so.
- Why it matters
- Coaching usually fails on administration rather than intent. Act does the finding, the chasing and the record keeping, and leaves the manager with the judgement calls only they can make.
Next step agreed
No agreed next step on 6 of 9 calls
Compliance: disclosure
Disclosure missed on 1 call
Discovery
Improved, ready to close off
08 MCP
DemandIntel inside the tools your team already uses
DemandIntel runs a hosted Model Context Protocol server, so the platform appears as a native tool set inside whichever AI tool your team already works in. One endpoint, one personal access token, no install and no copying data out of the platform.
- Who it is for
- Enablement and training leads who already spend their day in an AI tool, and technical owners who want the data programmatically rather than through the interface.
- When you use it
- When the question is unusual enough that no dashboard answers it, when you want to build something out of the findings, and when you want the same numbers available inside the tool you are already writing in.
- What it does
- Around thirty tools cover conversations, QA scorecards, competency assessments, reports, insights and coaching plans. The tools read the same tenanted data the interface reads, under the same permissions, so an assistant can only see what the person holding the token can see.
- Why it matters
- It removes the copy and paste step between knowing and doing. Because the assistant is grounded in your team's own scored conversations, what it produces reflects how your team actually sells rather than a generic model of selling.
Works with
The whole setup
claude mcp add demandintel \
https://mcp.app.demandintel.io \
--header "Authorization: Bearer di_pat_…"Generate the token in Settings, paste it once, and the tools appear in your assistant.
What the tools cover
- Conversations and transcripts
- QA scorecards and item level scores
- Competency assessments and levels
- Reports and report history
- Insights and trends
- Coaching plans, Act programmes and evidence
The loop it closes
Query
Ask, in plain language, what is really happening across the team's conversations.
Plan
The answer comes from scored conversations, and names the one gap worth fixing first.
Create
Your AI tool turns that gap into the session, the notes and the practice material.
Deliver
You run the session, grounded in the team's own conversations rather than a generic curriculum.
Review
The next scoring cycle shows whether the behaviour actually changed.
09 Training content skill
Turn an identified gap into a session you can run
MCP is the connection. The training content skill is the content. It is a downloadable skill pack that teaches your AI assistant how DemandIntel structures competencies, scorecards and evidence, so the material it writes matches the framework your team is measured against.
- Who it is for
- Whoever actually builds the training: an enablement manager, a team lead, or an agency running sessions across several clients.
- When you use it
- After a report or an Act review has named the gap, and before you run the session. It is the step between knowing what is wrong and having something to deliver.
- What you get
- A session plan, facilitator notes, handouts, conversation scripts and role-play scenarios, all built around the specific behaviours the conversations show are missing, and written in the same language as the scorecard.
- Why it matters
- Producing the material has always been the slowest part of coaching, which is why gaps stay open for months. This turns a named gap into a runnable session in minutes, and because it uses your framework, the next scoring cycle can tell you whether the session worked.
Route one
One line to install
A single command installs the training skill and wires up the MCP server at the same time, so the assistant has both the method and the data.
curl -fsSL …/install.sh | bashThe exact command, with your token, is shown in Settings once you are signed in.
Route two
Download and drop in
10 Cohorts
The guided programme
Structure and pace alongside the platform, for teams who want to be taken through it.
- Who it is for
- Teams standing this up for the first time, and leaders who want an external commitment to keep the work moving.
- When you use it
- At the start, when the habit is being built, or when an existing programme has stalled.
- What it does
- A guided cohort programme run over a fixed period, working through the maturity stages with your own conversations as the material, alongside other teams doing the same.
- Why it matters
- Software installs quickly, habits do not. The cohort supplies the pace, the accountability and the worked examples that make the habit stick.
11 Community
The practitioner community
A peer group of people solving the same problem, without the vendor in the middle.
- Who it is for
- Sales leaders, managers and enablement practitioners.
- When you use it
- Continuously, and particularly when you are designing something new and want to know what has already been tried.
- What it does
- A working group where frameworks, scorecards and coaching approaches are shared and pressure-tested by people running them for real.
- Why it matters
- Most enablement teams are small and isolated. Access to people a step ahead saves months of building the wrong thing.
How it fits together
Nothing here works on its own
Evidence first
Then coaching
Then proof
Want the email cadence that carries all of this? It is described on the platform overview.
From
DemandIntel Coaching
Subject
Today: one change to your discovery questions
This week you are working on
Discovery Proficient
What happened yesterday, 02:41 to 03:38
"So you are looking at a new system. Shall I walk you through what we do?"
You moved to your pitch before finding out what the current process costs them.
Try this on your next call
Asking what the current process costs them each month, before you describe anything you do.
See it against your own conversations
The quickest way to judge any of this is to point it at a fortnight of your team's conversations and read what comes back.