# DemandIntel - Features - Canonical: https://demandintel.io/features - Last updated: 2026-08-21 - Source of truth: DemandIntel ## TL;DR DemandIntel scores every sales conversation against your framework, turns the gaps into coaching, manages that coaching to completion and then proves whether behaviour actually changed. Eleven features cover reporting, insight, quality, capability, coaching cadence, proof of change, Act coaching management, the MCP server, the training content skill, cohorts and community. --- ## 01 Reporting - one master report for your team - Who: sales leaders, managers and team heads who need a clear picture of quality, competency and progress without chasing down spreadsheets. - When: weekly or monthly, scheduled or on demand. - What: every rep in the date range aggregated into one report - executive summary, quality and competency views, a 30 day action plan and an evidence library where each claim traces to a timestamped moment. - Value: a defensible view of team performance that is already assembled when you walk into the review, built from scored conversations rather than opinion. ## 02 Insight - the Insights hub - Who: managers and heads of sales who want the numbers rather than the advice. - When: preparing a review, checking a hunch, deciding where coaching effort goes. - What: tabbed quality, competency and per rep trend views governed by one shared date range and rep filter. - Value: consistent comparisons, because every view is filtered the same way. ## 03 QA scorecards with cited evidence - Who: quality and compliance owners, and the managers who inherit the scores. - When: continuously, in the background, as conversations arrive. - What: your scorecard or one written from your conversations, weighted items, automatic fails for compliance breaches, and every score cited to the moment it came from with a click through to the conversation. - Value: consistent scoring at full volume, and challenged scores are settled by listening rather than debating. ## 04 Competency frameworks - Who: managers running development and enablement teams proving a programme worked. - When: each review cycle, and when deciding readiness for more responsibility. - What: four proficiency levels per skill, assessed from real conversations, current period shown beside the previous one. - Value: movement per person becomes visible instead of assumed. ## 05 Weekly and daily coaching plans - Who: reps and the managers running the weekly one to one. - When: every working day. Monday sets the week, Tuesday to Friday keep it moving. - What: 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. - Value: the cadence survives a busy week because nobody has to prepare it. ## 06 Continuous improvement plans - the behaviour change ledger - Who: anyone who has to show the training worked. - When: at the end of each coaching sprint, and whenever development spend is questioned. - What: improvement recorded conversation by conversation - the behaviour targeted, the conversations before, the conversations that show it in use afterwards. - Value: proof that survives scrutiny, rather than a score that drifted. ## 07 Act coaching management - Who: frontline managers carrying a team, and the leaders who need to know coaching is happening. - When: in the weekly one to one, and the ten minutes before it. - What: a cockpit ordering reps by who needs attention, evidence-backed tasks with owners and dates, and a review queue the system populates automatically with pending evidence from real conversations. Nothing is verified or completed without the manager saying so. - Value: the administration of coaching is handled, leaving the manager the judgement calls. ## 08 MCP - DemandIntel in your tools - Endpoint: https://mcp.app.demandintel.io - Who: enablement and training leads who work inside an AI tool, and technical owners who want the data programmatically. - When: when no dashboard answers the question, when you want to build something from the findings, and when you want the numbers inside the tool you are already writing in. - What: a hosted Model Context Protocol server exposing around thirty tools covering conversations, QA scorecards, competency assessments, reports, insights and coaching plans. One endpoint, one personal access token, no install. Works with Claude Code, Claude Desktop, Codex, Cursor, Continue, ChatGPT desktop and any MCP client. Tools read the same tenanted data as the interface, under the same permissions. - Value: removes the copy and paste step between knowing and doing, and grounds the assistant in your team's own scored conversations. The loop is query, plan, create, deliver, review. ## 09 Training content skill - Who: whoever builds the training - an enablement manager, a team lead, or an agency running sessions for several clients. - When: after a report or an Act review names the gap, and before the session is run. - What: a downloadable skill pack, installed by a one line installer or by dropping the files into the assistant's skills folder. It teaches the assistant how DemandIntel structures competencies, scorecards and evidence, and produces session plans, facilitator notes, handouts, conversation scripts and role-play scenarios in the same language as the scorecard. - Value: producing material has always been the slowest part of coaching. A named gap becomes a runnable session in minutes, and the next scoring cycle can tell you whether the session worked. ## 10 Cohorts - Who: teams standing this up for the first time, or restarting a stalled programme. - When: at the start, while the habit is being built. - What: a guided programme over a fixed period, working through the maturity stages using your own conversations as the material. - Value: software installs quickly, habits do not. The cohort supplies pace and accountability. ## 11 Community - Who: sales leaders, managers and enablement practitioners. - When: continuously, especially when designing something new. - What: a working group where frameworks, scorecards and coaching approaches are shared and pressure-tested by people running them for real. - Value: access to people a step ahead saves months of building the wrong thing. --- ## How it fits together 1. Evidence first: reporting, insight, QA and competency all read the same scored conversations, so a number in the report is the same number in Act. 2. Then coaching: weekly and daily plans, Act tasks and the training content skill take their subject from those scores. 3. Then proof: the behaviour change ledger shows, conversation by conversation, whether the coaching produced a different behaviour. ## Related pages - Platform overview: https://demandintel.io/platform - MCP setup guide: https://demandintel.io/mcp - Act & Enable: https://demandintel.io/act - Pricing: https://demandintel.io/pricing