The Methods Your System Runs.

Ranking a market is four judgements at once: how well each account fits, how likely it is to move, how much attention the team can spend and what the quarter needs. Most lists get sorted on one of them. This skill ranks accounts from their current state using your ICP, Signals, Goals & Objectives and Territory Planning memories, with the reasons stated for every position. The Prospecting Daily Briefing runs on the ranking, Propensity Assessment feeds it, managers override or reallocate capacity when they see further, and what those accounts go on to do feeds back, sharpening the calls the next ranking makes.

Somebody on the team has already researched this account. It rarely helps: the next person starts again from a blank search bar. This skill does the work once, properly: the account's own record plus outside evidence, read against the ICP, Persona, Signals, Products and Competitors memories RevOps keeps, returning what the company is, how it fits and what has changed, with sources, confidence and open gaps. The result follows the account: sourcing tests fit with it, reps prep meetings from it, managers review deals against it. And the method itself improves, because missing evidence and what happens downstream feed each new version.

The usage chart points up and to the right. Whether the right stakeholders are reaching the outcomes they bought is a different question, and the chart cannot answer it. This skill can: usage, stakeholder and lifecycle evidence held up against what your Adoption, Customer Outcomes and Success Plan memories expect for this customer and use case, showing its workings and how sure it is. CSMs spot slow onboarding weeks before it would surface anywhere else, managers walk into QBRs with actual adoption against expected, renewal conversations start from proof, and every retention outcome refines which behaviours count as adoption here.

By the time a customer cancels, the reason on file is rarely where the loss began. This skill reads each churn against the account's whole history, applying your ICP, Sales Process, Customer Outcomes, Onboarding, Adoption, Value Realisation, Customer Risk and Renewal memories to the promise the deal was won on, how onboarding ran, what adoption and value followed and every intervention along the way. CS and sales leaders see where the account was really lost, and a cause that keeps recurring becomes an owner-approved change to the logic behind it, on either side of the handover.

14 people at one account clear the filters. Two of them will decide anything. This skill finds those two: every contact is weighed by the role the evidence gives them in the purchase, fit against the Persona and ICP memories RevOps maintains, the Lead Routing and Suppression rules in force and how each person has engaged so far. Contact Sourcing uses the ranking to choose which names get added at all and Prospecting Engagement to order who hears from the team first, while replies, meetings and deal outcomes keep teaching the method which people were worth the attention. The relationship nuance stays with the rep.

Six open tabs to understand one person: LinkedIn, the CRM, an old email thread, an enrichment record. This skill does that work one way, every time. It settles who the contact is, the role the evidence says they play and how they relate to the account, read against your Persona, ICP and Sales Process memories, sources attached. Contact Sourcing, Stakeholder Mapping and Meeting Preparation all draw on the same research, so a rep, their manager and RevOps work from one read on each person, and what deals go on to prove keeps sharpening how roles get interpreted.

A demo ends at four, the debrief runs late, the next call starts on the half hour. The CRM sits open in a background tab, untouched. This skill keeps the record moving with the deal: what meetings, emails and material changes actually evidence becomes proposed field updates under your Sales Process, Lead Routing and Escalations memories, each with its source, confidence and an approval threshold. Well-evidenced routine changes go through, a rep confirms the sensitive ones, and the skill only ever writes the record: anything that would reach a buyer stays with a person. Corrections teach the mapping, so the record grows more trustworthy the longer it runs.

The retention number moved. Weeks of report-building later, the team knows what happened, and still not why. This skill closes that gap: it reads outcomes, actions and the customer base against your Goals & Objectives memory and the definitions your team actually runs on, from Customer Health and Adoption through Value Realisation, Renewal, Expansion and Customer Risk, then explains the change and how strongly the evidence supports the explanation. Leaders and managers validate the causality, CS Ops and RevOps ship the agreed fix into the memory it belongs to as an experiment its owner approves, and the next quarter's outcomes judge it.

Two CSMs with similar books can post very different renewal rates, and the difference is usually habits: how each runs a QBR, when each raises a risk, what each does after a quiet month. This skill pulls those habits out of the work itself. Observed work is read against how your company runs customers, its Customer Engagement, Customer Outcomes, Customer Health, Renewal and Success Plan memories, and against what each book went on to do: renewals kept, value delivered, risks caught late. Managers get named, evidenced patterns to coach from, CSMs get feedback about specific accounts, leaders get a team that runs customers one way, and the weeks after each intervention show whether it took.

The first half hour of a CS day goes on reconstruction: the CSM reads dashboards and last night's email, the manager scans for trouble, the leader asks around, RevOps pulls a report. Four people, four private versions of the same book. This skill compresses customer state into a daily briefing per role, applying your Goals & Objectives, Customer Health, Customer Risk, Renewal, Expansion and Escalations memories: the CSM gets today's accounts and the reasons, the manager gets exceptions across the team, the leader gets material change against goals, RevOps gets where reality is leaving the plan. People act, dismiss, approve or override, and what gets used or ignored feeds what surfaces tomorrow.

Health scores turn complicated accounts into one colour, and nobody quite trusts the colour. This skill produces a health judgement you can defend: adoption, value delivered, support, engagement, stakeholders and commercial context, each judged against your Customer Health memory with the evidence and confidence shown. CSMs explain a yellow in one sentence, leaders trust the wall of green, and renewal and churn outcomes retune what health means.

What a customer says in a meeting should change the account. Mostly it changes a notes document nobody reads twice. This skill weighs each conversation against the account as it stands and your Success Plan, Customer Engagement, Customer Risk, Renewal and Value Realisation memories, then proposes what the meeting changed: commitments, risks, relationship shifts, actions, with the follow-up drafted. The CSM confirms anything sensitive, and nothing reaches the customer without approval. Records stay current between meetings, managers stop chasing for updates, and every correction a CSM makes teaches the next version of the method.

A customer meeting is a test of how well the team knows the account, and CSMs sit it open-book with the book scattered across five systems. This skill binds the book. Goals, adoption, value, stakeholders, risk and open commitments are each drawn from their own assessment and read with your Customer Health, Adoption, Value Realisation, Success Plan, Renewal and Persona memories, so a check-in, a QBR and a renewal conversation all run from the same grounding. Meeting outcomes retune what the briefing puts first, and the conversation itself stays the CSM's to run.

Every book has accounts quietly drifting toward churn. This skill finds them early: it weighs adoption, support, value and relationship evidence together against your Customer Risk, Customer Health, Adoption, Value Realisation and Customer Escalation memories, and gives the CSM the risk, its severity, the evidence and the next move. Churn stops being a surprise, and every churn or save that does happen tightens what the team treats as risk.

Relationships decide renewals, and maps of them go stale in weeks. This skill keeps the stakeholder map alive: who champions, who uses, who decides and where the gaps are, read from real interactions, product usage and account context against your Persona, Customer Engagement, Renewal and Expansion memories. The CSM sees coverage gaps before they cost a renewal, and managers see multi-threading across the whole book.

A CS week produces more change than its review ever hears about: health moves, renewals slip, interventions go in and either work or quietly fail. This skill works through the week end to end before the meeting, judging every customer-state change, outcome and intervention with your Goals & Objectives, Customer Health, Adoption, Value Realisation, Renewal, Expansion and Customer Risk memories, and prepares a review by role: what changed, what caused it, which intervention followed, what the evidence suggests upgrading. The team spends its hour deciding, managers and leaders challenge the causes, RevOps carries approved upgrade candidates into the logic they touch. The review keeps its slot in the week; what goes is the assembly that used to fill it.

One consistent answer to the question every rep, manager and leader keeps asking: is this deal real? The skill checks a deal's evidence against your Sales Process, Discovery & Qualification, Sales Methodology, Pricing and Competitors memories, then says what is solid, what is missing and how confident to be. Deal Risk, Forecasting and Pipeline Review run on the same judgement, so the deal's story stays the same whoever asks. And because every judgement is compared with what the deal went on to do, the method keeps improving.

Deals give notice before they die. Usually it gets read at the post-mortem. This skill reads it in time: deal evidence is checked continuously against known risk patterns and your Sales Process, Discovery & Qualification, Sales Methodology, Competitors and Pricing memories, and each threat comes back typed and sized, with its evidence, how sure the method is and the intervention it points toward. Managers approve the high-consequence calls, Deal Assessment and Forecasting read the same risk picture, and every deal that progresses or dies afterwards teaches the method which warnings were real.

Managers can only coach the calls they have time to hear. This skill reads every one of them: each discovery conversation is compared with what your Discovery & Qualification, Sales Methodology and Persona memories say a deal needs to establish, and comes back as what the call proved, what stays open and which questions to ask next. Reps get the gaps while the deal is warm, managers coach from the whole call record, and deal outcomes keep tuning which discovery evidence matters.

A usage spike and a genuine expansion opening look identical from a dashboard. This skill exists to tell them apart. Product fit, realised value, the customer's goals, stakeholder context and commercial timing are weighed against your Expansion memory, and what comes back is either a thesis carrying evidence, confidence and gaps, or a reasoned decision to wait. CSMs and reps stop pitching on instinct, managers review openings they can defend, and every expansion won or lost tightens what qualifies. The approach to the customer, and when to make it, stays a human decision.

Somewhere between the CSM who found the opening and the rep who will carry the deal, the expansion plan usually lives in a notes doc and a catch-up call. This skill gives the expansion what a new deal would get: one plan naming the stakeholders, the value case, the timing, the next actions and an owner for each, composed from your Account Plan, Expansion, Persona, Value Realisation, Pricing and Sales Process memories. CS and sales execute from the same plan, managers can read it whole, and every expansion outcome sharpens the planning patterns behind the next one. The strategic choices, what to ask for and when, remain with the people who own the account.

Commit means something different to every rep who says it. This skill gives each deal a forecast judgement built the same way: a category, a confidence and the evidence for both, judged against your Forecasting, Sales Process and Discovery & Qualification memories. Managers challenge specifics and own the final commit, leaders defend a number they can open down to deal level, and each quarter's actual outcomes retune how the evidence is weighed.

Every prospecting hour and ad pound goes where the ICP points. This skill measures whether it points at the right companies. Assessments against the ICP leave a trace, so the analysis knows which criteria were active when each account was chosen and can score every criterion against what followed: meetings, opportunities, wins and churn, judged with your ICP, Goals & Objectives and Products memories. RevOps sees which criteria predict outcomes and which just feel right, revisions arrive as versions carrying their evidence, and leaders can test a proposed ICP against history before adopting it. The strategic call stays human.

The ICP only works if every fit judgement applies the same definition, and filters, scores and gut calls each apply their own. This skill judges one account at a time against the current approved version of your ICP memory: criteria checked against live account evidence, exclusions enforced from your Suppression memory, product fit and buying roles weighed through your Products and Persona memories. The result reads fit, confidence and what is still unknown, so a rep can see why an account made a list and RevOps can change the definition once and see it applied everywhere. Every judgement leaves a trace, and those traces are the record ICP Analysis later tests the definition against.

At the moment a meeting is booked, prospecting holds the full story: why this account was targeted, which signal made now the right time, which message finally drew a reply and which stakeholders are already engaged. Handover notes carry a fraction of that, so AEs re-research accounts an SDR already knows. This skill runs at booking, reading the prospect record and the traced decisions behind the meeting through your ICP, Persona, Signals, Messaging and Sales Process memories, then hands sales a structured briefing for the deal this meeting may become. The SDR corrects nuance before it carries over, the AE opens the first call knowing why the meeting exists, and opportunity outcomes keep revising what the handover must include.

A meeting creates work the minute it ends: the record to update, the follow-up to send, the next step to choose. Different reps capture different fractions of that work, and what one misses, every review and forecast downstream inherits. This skill reads the finished meeting with your Sales Process, Discovery & Qualification, Customer Risk, Messaging and Escalations memories and sends the result straight to the rep: proposed record updates, the drafted follow-up, next actions in priority order, what to address before the deal moves and coaching points where the conversation earned them. The rep confirms commitments and anything ambiguous, the follow-up leaves as a draft only a person can send, and confirmed changes reach the record through CRM Update. Every correction improves the next run.

How well a meeting gets prepared usually depends on the day around it: a clear morning buys proper research, a stacked one buys a skim of the CRM. This skill removes the dependence. Before a prospect or deal meeting it gathers what the system already knows: the account's research, the deal's assessment, the stakeholders expected. Read with your Persona, Messaging, Sales Process, Discovery & Qualification and Customer Outcomes memories, that becomes one briefing: where things stand, what is missing, what this meeting could settle. The rep edits the priorities and chooses the strategy; whoever holds the meeting, rep, manager or CSM, the briefing comes out the same; and the briefing learns from each meeting's outcome which context and questions earn their place.

The argument that wins your best persona already exists. Today it is a template on one rep's screen, and nothing carries it to the rest of the team. This skill turns message performance into shared knowledge: every variant is analysed alongside the persona it addressed, the prospect's situation and the channel it ran on. What followed, meetings, pipeline and closed deals, is measured against your Messaging, Persona, ICP, Tone of Voice and Case Studies & Proof memories. Marketing and RevOps see which claims convert where, experiments run approved and measured, and the findings that survive testing get written into your Messaging memory, with marketing leadership signing off.

90 days in, every task on the onboarding plan can be ticked and the customer still short of first value. This skill judges onboarding against what the success plan promised: progress toward the outcomes the success model names, assessed with your Onboarding, Success Plan, Customer Outcomes and Customer Escalation memories, checkpoint by checkpoint. CSMs see whether first value is getting closer and read blockers one way; managers see which onboardings need help before the customer has to ask; and time-to-value outcomes, good and bad, reshape the milestone logic. Commitments to the customer stay the CSM's to make, and exceptions stay theirs to handle.

Who feels the problem first, who shapes the evaluation, who signs: a persona document is full of claims like these, and your pipeline quietly tests them all. This skill reads the results. It compares persona assignments and stakeholder decisions with the engagement, opportunities and wins that followed, using your Persona, ICP and Messaging memories as the yardstick. Where the definitions drift from the buyers who actually turn up, RevOps sees it first, and sales and marketing leaders read the same evidence. A revised persona can be tried through sourcing and messaging before it becomes the standard, and organisational nuance stays a human call.

A pipeline review exists to make decisions, and most of the hour goes on establishing what is true. This skill does the establishing before anyone joins: it aggregates every deal's assessment, risk, qualification and forecast evidence across the pipeline, judges the whole against your Sales Process, Discovery & Qualification, Forecasting and Goals & Objectives memories, and surfaces the exceptions with the question each one raises. The rest of the pipeline passes on record. Managers spend the meeting on coaching and resource decisions, leaders pull the same read on demand, and the decisions a review makes are compared with what followed, so next quarter's flags reflect which exceptions deserved the time.

One manager, 100 customers, one review hour a week. This skill reads the whole book before that hour starts: it gathers the current assessments and what changed across every account, weighs them against your Customer Health, Customer Risk, Renewal, Expansion and Customer Segmentation memories, and returns the exceptions, the evidence behind each one and the questions worth asking. The manager spends the hour on the 12 accounts that need judgement while the rest stand documented as steady. Resource and relationship calls stay human, and each review decision and its outcome sharpen what gets surfaced next time.

Two accounts sit three points apart on a priority score, and what those points are made of is anyone's guess. This skill replaces the number with a case: signals, engagement and fit weighed against your Signals, ICP, Persona and Goals & Objectives memories, returned as why this account, why now, and with what confidence. It runs again whenever the evidence moves, so no account's priority is older than its newest fact. Account Prioritisation weighs the judgement into the team's ranking, Prospecting Next Action reads it before choosing a move, reps and managers override the exceptional cases, and every meeting and opportunity that follows tunes the weighting.

A prospecting motion leaves two histories: the metrics its tools record, and the choices behind them, who got attention, what prompted it, what was said. The tools keep only the first. This skill diagnoses performance from both, reading prospect state, decisions, actions and outcomes against your goals and the memory versions that were active at the time. RevOps and leaders learn which segments, signals and messages create pipeline and which look busy without creating it, people validate the causal claims, and confirmed findings become owner-approved tests on the ICP, signals, messaging or territory, each shipped as a version and measured.

The messaging was signed off in January. By May every rep is sending a private dialect of it, and the lines that win replies sit in one person's drafts folder. This skill drafts prospecting messages the way the company would write them: built from your Messaging, Persona, Signals, Tone of Voice and Case Studies & Proof memories, matched to the prospect's circumstances and the signal that made now the moment. Reps edit detail, direction already set, marketing sees its positioning hold in the field, and its authority ends at the draft: a rep sends, or does not. New claims wait for an owner's approval, and upgrades to the skill and its memories ship as versions, argued from what messages went on to earn.

Alert, email, sequence, ad, task, approval or nothing: one of those is the right next move for any prospect on any given day. Choosing it means holding channel rules, suppression lists, routing and live conversations together, and reps make that choice dozens of times a day across tools that share nothing. This skill chooses from prospect state, applying your Channel Strategy, Suppression, Lead Routing, Escalations and Messaging memories, and shows its reasoning, including when the right move is none. High-risk actions wait for approval, anything a prospect would see needs the rep to send it, and overrides and outcomes keep sharpening how the choice gets made.

Checked boxes are where bad deals hide. This skill judges qualification on evidence: each criterion in your Discovery & Qualification memory comes back proven, assumed or missing, with the proof attached and the next question to ask. Reps stop working deals that were never real, managers stop policing fields, and the forecast counts deals that would survive scrutiny.

After every meeting, risk flag or review, the same question: what now? This skill answers it for the deal at hand: the next move, who owns it, when, and the reasoning behind it, all judged against your Sales Process, Discovery & Qualification, Sales Methodology, Messaging and Escalations memories. Deals keep moving between manager check-ins, and what reps accept and what actually works feeds back into better recommendations.

The renewal date sits in the diary a year out. This skill spends that year getting ready, keeping readiness current across the whole contract: value delivered, customer health, stakeholder cover, open risks and the commercial picture, each read against your Renewal, Value Realisation, Customer Risk, Customer Health and Pricing memories, with the evidence, the gaps and what would close them. CSMs work gaps months out, managers run the 120, 90 and 60-day checkpoints to one standard, and every renewal won or lost feeds the criteria for the next.

Win rate slips four points and everyone has an explanation before anyone has evidence: pricing, the market, a competitor, the new hires. This skill settles that argument from the record. It reads deal state, behaviours, decisions and outcomes through your Goals & Objectives, ICP, Persona, Sales Process, Qualification, Methodology and Forecasting memories, then says where the sales motion is losing deals and how confident the evidence makes it. Sales leadership and RevOps validate the causal read before anything changes, behavioural patterns go to Sales Coaching, and agreed fixes become owner-approved versions of the memory at fault, measured by the quarter that follows.

A sales manager carries a mental file on every rep: who rushes discovery, who discounts too early, who avoids the budget question. This skill builds that file from evidence. Each rep's observed work is compared with your Sales Methodology, Discovery & Qualification, Sales Process and Goals & Objectives memories and with what their deals went on to do, and the result is a coaching recommendation that names the rep, the behaviour and the commercial cost. Managers contextualise and deliver the coaching; the following weeks of behaviour and outcomes show whether it worked, and that record improves the method.

On Friday the account belongs to the rep who made every promise in it. On Monday it belongs to a CSM working from a summary. This skill turns closed-won deal state into the customer's starting state without the loss: goals, commitments, stakeholders, pricing context and known risks, mapped through an owned handover schema and your Products, Persona, Pricing, Customer Outcomes, Onboarding and Escalations memories. The rep vouches for each commitment before it carries, the CSM starts onboarding from what was actually sold and promised, and when churn later traces back to a handover gap, the handover requirements change, and the new requirement carries a version number.

RevOps writes the signal definitions. This skill shows which ones pay their way. Because actions taken on signals are traced, it follows each signal type through interpretation, action and outcome, judged with your Signals, ICP and Persona memories, and reports which definitions keep producing meetings and pipeline and which only correlate with activity. RevOps retires, revises or keeps each one on that record, and every change to a signal definition ships as an approved version that can itself be measured.

The same funding alert reaches two reps. One clears a morning for it, the other archives it, and both can defend the choice. This skill decides what a validated signal means for the account in front of it: the event is read against the account's current prospect or deal state and your Signals, ICP, Persona and Products memories, and the rep gets commercial meaning, a possible move and a stated confidence. Signal Intelligence, Propensity Assessment and Deal Risk all work from that one reading, a person reviews anything ambiguous, and what happens after each signal sharpens the next interpretation.

Signal feeds only answer questions somebody configured months ago. When a rep needs to know what is happening at one account today, the looking is manual, and no two people look the same way. This skill is the deliberate look, run to a method: sources checked in a set order, candidates validated, deduplicated and dated against your Signals, ICP and Market & Industry Intelligence memories, provenance kept for every finding. RevOps gets a signal supply it can stand behind, reps get fewer dead ends claiming their attention, a person inspects anything uncertain or sensitive, and a false positive has consequences here: it becomes the case for a rule change, and the method moves up a version.

A rep can name every stakeholder they have met on a deal. The deal will also be decided by people they have not. This skill maps the buying group from evidence: meetings, email threads, call transcripts and deal history, read against your Persona, Discovery & Qualification and Sales Methodology memories, to say who holds which buying role, how engaged each person is, where influence sits and which buying roles have nobody in them. Reps see the gap between coverage and close before it costs them the deal, managers run reviews on the map's evidence, reps and managers supply the political nuance no transcript carries, and closed deals, won and lost, are the test every role reading is marked against.

Every customer bought an outcome. This skill checks whether it is actually happening: the promises held in your Customer Outcomes and Success Plan memories are compared with real usage, operational and relationship evidence, and each outcome shows its proof, its confidence and its gap while there is still time to close it. QBRs, renewals and expansion conversations all start from the same evidenced value case.

A quarter of customer contact runs to 500 calls, a few thousand tickets and one survey round. No one reads it all, so teams sample, and the sample stands in for the base. This skill reads all of it: every call, ticket, review and survey, judged against your Products, Persona, Customer Outcomes and Customer Segmentation memories and each account's state and outcomes. A theme arrives with who is saying it, which segments carry it and what it is doing to retention and expansion. CS, product and marketing decide what a validated pattern should change, and what those decisions achieve retunes which themes get raised first.

Most win-loss stories are written by whoever argues best in the room. This skill writes them from evidence, on every closed deal. Each outcome is read against what actually happened: the ICP the account matched, the messaging it received, how the deal was qualified, what it was priced against. Because those decisions were recorded at the time, findings point at causes, and a finding that holds becomes an upgrade to the memory behind it, approved by its owner. The team stops relearning the same lesson every quarter.