On this page
Eleven parts, one loop
- 01One master report for your team
- 02The Insights hub
- 03QA scorecards with cited evidence
- 04Competency frameworks
- 05Weekly and daily coaching plans
- 06Continuous improvement plans
- 07Coaching plans built for review
- 08Method, a sales method that keeps improving
- 09Eriqa inside the tools your team already uses
- 10The training content skill
- 11The practitioner community
01 Reporting
One master report for your team
A single, defensible view of team performance, built from real conversations rather than opinions.
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.
- 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.
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.
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.
- 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.
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.
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 scored items link back to the supporting moment, with the excerpt and a click through to the conversation.
- 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.
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.
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.
- 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.
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.
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.
- 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.
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 conversations.
Three things to do this week
- 1Ask what the current process costs, on every first conversation.
- 2Listen back to Tuesday 10:04, where it worked.
- 3Bring one conversation to your one to one on Thursday.
06 Proof
Continuous improvement plans
An audit trail of behaviour change, not a chart that drifted.
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.
- 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.
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 Coaching plans
Coaching plans built for review
Eriqa prepares the plan and evidence, and the manager makes the decisions.
A cockpit that orders reps by who needs attention, holds evidence-backed coaching tasks with owners and dates, and keeps a review queue of pending evidence from real conversations. Nothing is marked verified or complete without the manager saying so.
- 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.
Coaching usually fails on administration rather than intent. Eriqa 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 conversations
Compliance: disclosure
Disclosure missed on 1 conversation
Discovery
Improved, ready to close off
08 Method
Method, a sales method that keeps improving
Always listening, reviewing itself and proposing evidence-backed guidance to help keep your playbook current.
Method brings your playbooks, scripts and policies into one approved version, then checks conversation evidence against it. It flags guidance that needs review and proposes improved versions from relevant evidence. When a playbook change is approved, Eriqa drafts updated scorecards and skill frameworks, shows exactly what changed and alerts the owner. A person approves before anything goes live, and changes apply to future conversations only. A person approves every change.
- Who it is for
- Enablement and training teams who own the material, and the leaders who have to trust what reps are told.
- When you use it
- Whenever guidance is written, reviewed or questioned, and every time coaching or an assistant answer cites it.
Keeping a sales method current normally takes weeks of research, rewriting and chasing reviewers, and nobody knows if the training landed. Method does that work continuously, so enablement teams spend their time on decisions, not upkeep.More on Method
1. Brings it together
Connects the Google Drive, OneDrive and SharePoint folders you already use, or takes uploads. Every playbook, script and policy gets a named owner, a version and a review date, so there is one approved version everyone works from.
2. Listens constantly
Every conversation your team has is compared with the approved guidance, so you see what reps actually do and say, not what the playbook hopes they do.
3. Reviews itself
For each piece of guidance it keeps asking: does this appear to be working, is it unclear, or has it stopped working? Anything out of date or overdue for review goes straight to its owner.
4. Heals itself
When guidance stops working, Method proposes an improved version, built from the standout conversations your best people are already having. A person approves it before anything changes.
5. Builds from it
When a playbook change is approved, Eriqa drafts updated scorecards and skill frameworks, shows exactly what changed and alerts the owner. A person approves before anything goes live, and changes apply to future conversations only.
What it saves you
- No more researching what good looks like: your best conversations show it
- No more rewriting playbooks from scratch: improvements arrive drafted
- No more chasing reviewers: owners are reminded when something is due
- No more guessing whether training worked: you see it in the conversations
08 MCP
Eriqa inside the tools your team already uses
Stop copying data between knowing and doing.
Eriqa appears as a native tool set inside whichever AI tool your team already works in. One endpoint, one personal access token, no install.
Your data stays yours
Tools read the same tenanted data the interface reads, under the same permissions. An assistant only ever sees what the person holding the token can see.
Set up once
Generate the token in Settings, paste it once, and every tool appears in your assistant. Nothing is copied out of the platform.
Works with
claude mcp add eriqa \
https://mcp.eriqa.io \
--header "Authorization: Bearer iqa_pat_..."Generate the token in Settings, paste it once, and the tools appear in your assistant.
ConnectedAnalysis
Conversations
Transcripts and every score behind them.
Quality
QA scorecards
Item level scores against your own framework.
Capability
Competencies
Assessments, levels and the evidence for each.
Measurement
Reports
Every report and the history behind it.
Trends
Insights
Patterns across the team over time.
Coaching
Coaching plans
Act programmes and the evidence behind them.
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.
The loop it closes
- 01
Query
Ask, in plain language, what is really happening across the team's conversations.
- 02
Plan
The answer comes from scored conversations, and names the one gap worth fixing first.
- 03
Create
Your AI tool turns that gap into the session, the notes and the practice material.
- 04
Deliver
You run the session, grounded in the team's own conversations rather than a generic curriculum.
- 05
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 Eriqa structures competencies, scorecards and evidence, so the material it writes matches the framework your team is measured against.
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.
- 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 a coaching review has named the gap, and before you run the session.
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
Prefer not to run a script? Download the skill pack and drop the files into your assistant's skills folder. Same content, no installer.
11 Community
The practitioner community
A peer group of people solving the same problem, without the vendor in the middle.
A working group where frameworks, scorecards and coaching approaches are shared and pressure-tested by people running them for real.
- 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.
Most enablement teams are small and isolated. Access to people a step ahead saves months of building the wrong thing.See the community
How it fits together
Nothing here works on its own
- 01
Evidence first
Reporting, insight, QA and competency all read the same scored conversations, so a number in the report and a number in a coaching plan are the same number.
- 02
Then coaching
Weekly and daily plans, coaching tasks and the training content skill all take their subject from those scores rather than from a curriculum written in advance.
- 03
Then proof
The behaviour change ledger closes the loop, showing conversation by conversation whether the coaching produced a different behaviour.
Want the email cadence that carries all of this? It is described on the platform overview.
From
Eriqa 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 conversation
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.