Sales Enablement

Writing down the tactical detail of how you personally do the job — call volume, timing, follow-up, organisation, the funnel and its conversion rates — until what looked like personality turns out to be a repeatable recipe someone else can run.

The point, usually three to six months in, where a rep stops obediently executing the playbook and says: I get it, I know how to do this, and I'm going to bring myself to the job.

An exercise in which a rep writes what their manager, peers and customers will say about them when they leave the job — and then works backwards to the behaviours that would earn it.

Translating the qualitative reputation you want — responsive, honest, knowledgeable — into stated numeric service levels, then publishing them to the people who will judge you by them.

The table-stakes contract Cole gives anyone on a revenue team he leads: know what good and bad performance look like and be aligned with your manager on it; be compensated fairly; be treated with respect; have the tools necessary to execute the job.

Running strategy by objectives at the leadership level — four to six priorities aligned to the founder's vision, reviewed with leaders every two weeks — while getting far more prescriptive about activity expectations at the individual rep level.

Proactively catching a high performer's base and OTE up to what the role is now worth, rather than waiting for them to lobby or for a competitor's offer you would then match.

Cole's rule for maturing leaders: people will roll problems to your feet, and the moment you pick one up you own it — so choose deliberately rather than reflexively.

The moment a career stops being a ladder of obvious next steps and becomes a set of trades — once basic needs are met, every promotion is a compromise between satisfaction, impact, title and compensation rather than a straightforward step up.

The five ingredients Cole weighs in any job — compensation, title, industry, leading people, and impact — tested by asking whether more money, a better title and a different industry would make you happy if you led nobody and felt no impact.

Joey's view that the live conversation is the most valuable unit in go-to-market. Data and dialers are the subatomic particles, and the conversation is the atom you have to stack to build anything valuable. He also calls cold calling 'conversational advertising' — delivering a tailored ad to an intended target and getting a reply.

Outbound succeeds or fails on four things: the list (right accounts, right contacts, good data), the messaging (right message to the right contacts), the rep (ramped, trained, doing the right inputs) and the follow-up (systematic circle-backs on conversations that did not convert).

A cold call structure where the first gate is an honest opener that signals a cold call and asks for help, and the second gate declares the reason for the call. It then offers two buckets of pain for the prospect to self-select into, followed by a tight pitch, a call to action and a correct disposition.

An idea Joey credits to Ryan Reisert: a rep doesn't need to be memorable on early cold calls, but must not be forgotten when it is time to be remembered.

The ceiling of any outbound effort is the quality of the list — primarily the targeting of accounts and titles, with accurate contact data as a subcategory — so list building must pass a quality assurance check before it reaches the floor.

Account research from AI and third-party signal tools, compared with an intel-gathering (IG) report built from real conversations with people across the target organisation.

A shift away from large, low-paid, high-volume SDR teams toward teams half or a quarter of the size, made up of highly paid specialist conversationalists who stay longer because they are more effective.

A role Joey has run for about two years: an SDR who can book meetings from intercepted inbound but may not book meetings on outbound. Their outbound job is to have conversations below the decision-maker level inside target accounts and gather intel for the AE.

The share of a prospect list you will ever reach by phone if you keep calling it. Joey says for 1,000 prospects it usually never exceeds 200, no matter how many rounds you dial.

TitanX's model triangulates telecom and carrier, consumer and professional data to answer three questions about a number: is it the prospect's, is it active, and how does it respond when unfamiliar numbers call it?

Voicemail rules that depend on answer intent: skip voicemail on high-intent prospects, leave voicemails and AI-screener messages on low-intent prospects, and point voicemails to the email you sent.

Joey's position that outbound itself works and a failing motion reflects execution, because outbound is continuous experimentation — much like a PLG motion — run inside the four containers of list, message, rep and follow-up.

Automate the back of the house — administrative, repeatable, rule-bound work — and keep humans in the front of the house, where the business touches customers, prospects and the market.

When channel headwinds reduce effectiveness — blacklisted email domains, LinkedIn throttling, spam-flagged phone numbers — teams try to make up for it with effort, raising volume to recover their previous results.

Power dialing places one call from one number to one person. Parallel dialing places several calls at once, connects the rep to whoever answers and hangs up on the rest.

Carriers such as AT&T, T-Mobile and Verizon share data and score outbound numbers, which rise or fall with dialing behaviour — much as Google and Microsoft blacklist spam email domains.

The visible part of enablement — the SKO presentation or the classroom lecture — is a small fraction of the work. The rest is the operating environment that makes a program stick and the monitoring that shows whether it worked.

Treating MEDDIC, a widely used sales qualification methodology, as an environment to build rather than a session to deliver. The CRM captures it, call recording picks it up, leaders use its language in decisions, and its impact is tracked.

Short, frequent formative assessment after instruction, to see whether learning is landing and steer in time. In the classroom that was a daily exit-slip quiz. In go-to-market it is a call recording scorecard.

Pairing role-specific lagging metrics with leading indicators drawn from call intelligence. Lagging: SDR pipeline, AE sales, customer success engineer cross-sell opportunities, applied engineer calls supported. Leading: product mentions, proactive versus reactive mentions, and objection handling.

When no launch is setting the agenda, start from a lagging metric that is suffering and pull the thread through layers of segmentation until the source appears.

Before running a program, model its revenue impact in conservative, medium and best-case scenarios, for the revenue org and for each rep's quota attainment and commission. Afterwards, report the actual results.

Go-to-market enablement should report to the CRO, because its purpose is revenue through both retention and new sales. Reporting into RevOps risks a helper function, and reporting into marketing risks distance from the front line.

Three conditions have to hold before hiring enablement, rather than an ARR or headcount threshold. Founder-led sales has already been handed off to a sales team. Product marketing has a strong point of view on who the product is for. The executive enablement reports to is ready to trust the enabler.

Treat maintenance of employee-built AI tools as an enablement problem. Take inventory of what people have created, notify owners when an underlying input such as pricing or ICP changes, and route promising tools through enablement so they can be scaled.

Two questions decide whether to build or buy. Is the tool customer-facing? If so, lean toward buying. What will maintenance actually look like? Build only what is cheap to keep current.

Internal, silent attrition — the gap between when a person disengages and when they resign. It appears on no dashboard, and by the time it does the institutional knowledge is already leaving.

Culture is keeping your word and communicating honestly, not perks, parties or snacks. A company that openly says it is about the bottom line is more workable than one promoting engagement it does not deliver.

Neither a disciplinary session when results are bad nor a pep rally deodorising a real problem — an honest account of what worked in the field, what worked at leadership level, and what did not.

A gesture that is obviously performative is worse than no gesture. Send something people can actually use, or send nothing.

Treating any role as permission to ask what the problem is, where it lives, who owns it, and how to affect the outcome — across departments, without asking first.

Surfacing context (information you could gather yourself, more slowly), process (an end-to-end workflow the skill now owns entirely), and infrastructure (maintaining the terminal, folder structure and the system itself).

If a process requires more than three tools, rethink the workflow. If more than one person follows it, it has breadth worth capturing. If you say or do something more than three times, it should be a skill.

The stated problem and the real one differ. Nobody says they cannot get follow-ups out on time; they say they are up late on email and always feel behind. The second is the pain point to build against.

For each CRM field, the agent returns bullet points of times someone explicitly said the thing, written so it cannot be copy-pasted, with a rule preventing it — the human rewrites the entry.

If you removed AI from a workflow and would still get the same output, AI only made it faster — you have not redesigned anything.

A wrap skill that summarises decisions, updates a cache and writes a compact handoff file at the end of a session, paired with a pickup skill that resumes exactly where it left off after clearing context.

A split between back-office RevOps (systems, process, tickets, quota fixes — never touches the field) and field-operator RevOps (lives between the sales team and the machine, injecting value into forecast calls, campaigns, and programs).

Build your internal operating rhythm around the four phases of how a customer consumes you — awareness, consideration & decision, implementation, and value realization — rather than around your org chart.

Staff sales enablement by treating every non-quota role (managers, RevOps, SEs, enablement) as overhead wrapped around a $1–2M-quota AE, and asking what each role gives back. Budget it zero-based and build it as a living sales academy, not a content factory.

Stand up formal enablement once a frontline manager's span of control passes five or six reps — earlier if you sell complex, enterprise, high-consideration products.

Split the field into hunters who acquire new logos (traditional sales path) and farmers who grow the install base aggressively, then engineer the bridge so neither feels the other is interloping.

In consumption revenue, the signed PO is where the work starts. Because revenue recognizes on usage, the entire post-signature job is driving adoption and demonstrated value.

Land small as a paid pilot, prove value fast, run a ~6-month 'double-tap' true-up, then bridge to the 12-month renewal — which is really the first real deal.

Acquisition and install reps carry different numbers; acquisition sellers ideally carry no consumption quota. Build a bookings plan for hunters and a consumption plan for farmers, layered with spiffs and target-incentive mixes.

Go-to-market gathers raw materials (account plans, commercial events, product releases, macro signals); a centralized data-science function owned by finance turns them into a forecast. Sellers cannot predict consumption.

Leverage is forcing your way into the room by making leaders unprepared without you. Trust is being invited in because sales leaders want you there. Only trust builds durable influence.

RevOps sits in a strange seat: reporting to the CRO but excluded from the CRO's peer conversations, while simultaneously knowing more than most of its peers and hearing things in rooms sales never enters.

AI is a productivity multiplier that requires clean data and human oversight. A productivity gain should be reinvested in more capacity to go faster, not banked as headcount reduction.

A three-layer split of GTM ownership: executives (CEO, CRO) own the WHY (market, category, how we win); the VP of RevOps owns the WHAT (processes, business and operating strategy, scalable design); GTM engineers own the HOW (enrichment, automation, ICP plumbing, execution).

The RevOps role is splitting from a generalist (decent at business and systems admin) into two lanes: the deeply technical GTM-engineering lane, and the strategic decision-maker accountable for the GTM infrastructure overall.

Effective AI transformation must change all three legs at once — people (how teams work and are structured), process (re-architected end-to-end), and technology (AI-first infrastructure and data) — not just automate external workflows.

The central tension for a RevOps leader: keep running the non-stop operating machine (forecasting, pipeline, QBRs, territory and account planning, comp) while simultaneously leading an AI-first transformation — usually with the same headcount and a mandate to use fewer people.

Tessa's methodology scores an operator's or org's AI adoption from 0 to 5 — where 0 or 1 is basic use (asking questions, rewriting an email) and higher levels reach standardized workflows and autonomous agents.

Sort work by urgency and importance: do the highly-important-and-urgent first, delegate the urgent-but-low-importance, and protect time for the highly-important-but-not-urgent — always weighing level of effort per initiative.

Start in 'analog mode' — write your own thoughts, plan, and hypothesis manually using your own judgment — then use AI to find examples, metaphors, and crunch data to back it up and level it up.

A tactical first step for any operator: open a Google Sheet, list the core tasks you do daily, weekly, monthly, and quarterly, mark the level of effort and whether each is manual or automated, then map where AI or an agent could help — and how peers in your role are doing it.

The fear that native-AI companies will displace SaaS incumbents that bolt AI onto legacy architecture — and the buyer's inability to tell a truly native-AI product from a SaaS wrapper.

Meet the customer in the middle by proving value in their own environment through a proof of concept, sharing risk, then expanding — making the POC the default go-to-market move rather than a concession.

AI deals require selling horizontally across the functional buyer (HR generalists, HR ops, HR leadership), IT, an AI committee, and security — any of whom can veto or delay the deal.

The economic buyer — the person with discretionary authority to say yes and move budget — has gone horizontal in AI deals; IT is often the new economic buyer even on an HR purchase.

Embedding technical forward-deployed engineers into the implementation team to manage LLM change, build guardrails against hallucination, and hand-hold customers through early adoption — modeled as an accounts-per-FDE/CS gearing ratio in headcount planning.

An implementation philosophy (borrowed from Indiana football coach Curt Cignetti's 'stacking days, stacking wins') of engineering a continuous drumbeat of provable metrics and success stories the champion can tell internally.

Extending the go-to-market engineer role beyond top-of-funnel prospecting into mid-funnel deal execution — automated SOWs from call transcripts, company-specific deal coaching, and CRM-plugged GTM diagnostics.

The enterprise qualification methodology Scott helped develop; in AI's chaos the two most decisive elements he stresses are Champion ('no champion, no deal') and Decision Criteria — the capability shopping list a buyer uses to evaluate vendors.

Rather than extracting the buyer's decision criteria, supply it: an editable, weighted, unbranded capability scorecard that lets the customer objectively compare vendors for the problem they're solving.

Auto-fill MEDDPICC in the CRM from Gong call transcripts while also keeping rep-entered MEDDPICC, then compare and contrast the two to triangulate what's actually happening in accounts.

When a company hires a go-to-market leader, RevOps and enablement are the first two hires; the ecosystem is built before AEs so reps ramp fast into a well-oiled machine.

Demystification of the vocabulary: a 'repository' is a folder, and an 'agent' is a folder containing a set of instructions saved as a file. You 'program' or 'train' the agent by writing its SOP in natural language and triggering it with an automation.

The operating system is built on four repos/folders: (1) transcript warehouse (raw call input), (2) customer warehouse (per-account intel and context), (3) GTM library (in-depth playbooks), and (4) company context (brand guidelines, customer avatars, pain points).

A relay where each agent prepares data for the next: a transcript agent annotates and routes calls, a customer-warehouse agent enriches account files from those notes, and a working agent (e.g., territory design) consumes the pre-built context to do real GTM work.

A body of enriched files — per-customer context, playbooks, company avatars and brand — authored so agents can inherit memory. The documents are written for agents to read, not humans: 'made by agents, for agents, used by agents.'

The agent platform (Claude Code, Claude Cowork, OpenAI Codex, Google Antigravity) becomes the central interface for the whole organization because, via MCP, it is tool-agnostic — pulling from and writing to HubSpot, Salesforce, Google Drive, Snowflake, and Intercom.

Because agents can write back into files, every implementation can update the source playbook with new learnings, so the system improves itself with each customer and prospect rather than staying static.

The remote-vs-office debate is a false binary. The real variable isn't where people work but how intentionally the right people are brought together — connection can be engineered without full-time co-location.

The magnet that makes an office worth showing up for is the interactions with the right people, not the space or its amenities.

Coordinating people day-to-day in space — honoring individual flexibility, team adjacencies, and the actual work being done — is a Rubik's cube problem that exceeds human capability and is well suited to AI.

A workplace failure mode where a building holds scattered pockets of two or three people with gaps in between, so it's technically occupied but feels low-energy and dead.

Distributed organizations progress through stages — a single co-located hub, a fully distributed org, then localized clusters — each requiring a different connection cadence.

When a company demonstrates tangible care for employees — above all, respect for their time — employees reciprocate that care back into the business with dividends.

Adopt AI by targeting real, painful processes and asking whether AI can do each one — or do it better, faster, or cheaper — rather than handing everyone an open-ended LLM.

Andy's written checklist of the go-to-market foundations fast-growing (roughly Series A) companies forget: the data foundation, GTM tooling, the right metrics to track, efficient processes, CPQ, and enablement.

Build formal enablement when you start cloning sales teams and multiplying products and complexity. Below that — one manager, fewer than ~10 reps — the manager owns enablement and rep ops themselves.

Enablement hires come in two shapes — the former rep you train up, and the teacher-type with an ops mind. Either succeeds only if they partner with sales leaders as the prioritization function and hold an opinion on what to train.

You're a passive job-seeker — always with a role lined up or recruiters chasing you — until you get 'punched in the face': laid off, in conflict with a boss, or at a company that ran out of money, forcing a proactive, jarring search.

At the VP/C-level, the odds of a role being publicly posted are low; it's whispered to you through the network. Whispered captures the confidential company insight execs gather while interviewing (and then normally throw away) into a durable edge.

A resilience test for data architecture: if we deleted your CRM instance today, how exposed are you? Teams with a true data warehouse as source of truth could bolt on a new front end and be fine.

The core RevOps mindset: configure systems to fit the business rather than deeply customizing them into brittle, un-maintainable states. Paired with a data skill set (SQL, which AI now makes easy).

Put the GTM engineer role inside the RevOps org: first build the data foundation, then build AI agents on top of it. Keep it aligned so automation solves root problems, not just the surface problem in front of it.

RevOps spans six functions — sales ops, marketing ops, CS ops, GTM systems, strategy, and enablement. You won't be great at all of them, so build a full-funnel operator by rotating across them, ideally under a leader who moves you around.

A GTM platform should be designed from the ground up as one system spanning data, engagement, and machine learning — not assembled by bolting point solutions together — the way a self-driving car is engineered whole rather than by strapping cameras and radar onto an ordinary vehicle.

AI augments the seller rather than replacing them. Duo, launched September 2024, is a human-in-the-loop companion — the rep's Pokemon or Iron Man suit — that learns each individual through reinforcement learning and grows with them.

Amplemarket is 'in the business of matchmaking' — connecting buyers who have problems with sellers who have solutions, so that every time a problem exists the buyer is made aware of the best possible solution.

In non-transactional, high-consideration buying, the purchasing experience — the craft, the care, the reverence for the product — is part of the value itself, and that care transfers to the buyer.

AI lets far more people build, so there will be more companies ('planets') to connect, each with smaller sales teams, and the space between them grows more opaque as creating information drops to near $0.

Every 24 hours the rep lands on a fresh feed of the most relevant accounts and buying signals in their book of business (the Spotify Daylist), paired with a recommended action for each — swipe the lead in or out (the Tinder system of action).

Low-quality, high-volume outbound is not a small positive but an active negative — it burns your domain, your leads, and your single chance at a first impression, signaling that your company doesn't care.

The highest-value trigger is timing — reaching a buyer when the problem you solve is already the last thing on their mind before sleep. You find that moment by composing signals (e.g., 100%+ team growth plus ten open AE roles) rather than relying on any single one.

The intelligence layer is a paradigm shift bigger than the internet, but it's raw power like the discovery of fire. Value comes only when you invent the 'pan' — thoughtful, purpose-built tooling — to cook something with it.

Vendors sell inside-out ('what I know, therefore you must know, therefore I'm best'), but buyers grade you outside-in through their own set of lenses — their pain, prior tools and research — most of which you can't see.

A B2B buyer moves from curiosity/pain through searches, forums, reviews and peers, forming impressions the whole way. Around 60–70% of the journey they build a shortlist of 3–4 vendors, and the best-impression 'number one' vendor at that point wins ~84% of the time.

Two obstacles to becoming number one: marketing complexity — the buyer is anonymous and you can't see when or where their journey starts; and sales complexity — by the time they engage they're highly informed on problem, solution and competitive landscape.

A large language 'thinking' model trained to think like a specific customer's buying committee, wrapped in a synthetically generated company, org hierarchy and pain scenario — a high-fidelity representative of your real buyer.

A buying journey of ~400–600 touch points is organized into discrete 'episodes' (a Google search, asking the community, exploring a vendor website, reading a testimonial); episodes roll up into a journey, and journeys attach to a buying persona.

A sales manager coaches to internal process ('you forgot to book the next meeting,' 'you skipped MEDDIC'); the buyer scores you on impression, not process. Dodging a pricing question the buyer just saw a competitor answer is what actually costs the deal.

AdamX's three products. TopJourney scores your buyer journey episode-by-episode against competitors; TopRep has the synthetic buyer analyze every recorded sales call for patterns; RolePlay lets reps practice live against the trained synthetic buyer.

The moments buried in call recordings where buyers express what they love ('sold on the solution,' 'this beats your competition hands down'). The synthetic buyer captures, de-dupes and ranks them, filtering out noise like 'thanks for waiting' or 'love your Zoom background.'

Reject the freshman-classroom model where every rep takes the same required courses. Coach like athletics: don't teach a strong server to serve — drill each rep's actual weakness (the 'backhand').

Your buyer journey score only matters relative to competitors in the same shortlist. An average journey wins if everyone else is worse; a good journey loses if a rival is better. Winning is measure-improve-measure-improve against the competition.

Reframe underperformance as a people problem, not just a revenue problem: focus on the individual rep and their manager, and stitch together the data (calendar, CRM, enablement) that reveals where each is struggling.

PeopleLens' four-step loop: (1) unify siloed rep-touchpoint, org, and people data into one connective tissue; (2) run proprietary models over structured and unstructured data; (3) render a persona-specific lens (exec, manager, rep); (4) push personalized performance nudges and agents to the front line.

The same underlying data rendered three ways — an exec lens for strategic bets and stack-ranking, a manager lens that diagnoses why a specific rep is struggling, and a rep lens that gives each seller a 360 view of their own outcomes, competencies, time allocation, and nudges.

For decades GTM data centered almost entirely on the customer (spouse's name, pet's name, endless fields). True first principles put the customer on one side, the product at the center, and the rep on the other — bringing the 'forgotten' rep into the equation with their own data lens.

Grow-or-go decisions are usually driven by anecdote in a QBR, not by facts about where a seller breaks down. The biggest, cheapest ROI is the 'massive middle' B-pool; because letting a rep go is roughly 18 months of revenue, personalized coaching that lifts the middle beats cutting.

Consolidate every revenue signal — email and calendar from the mail server, conversation intelligence from calls, and CRM history — into the Salesforce opportunity, account, lead, and contact records, rather than scattering them across ten systems.

A score, tracked over time, that aggregates communication frequency, depth, and stakeholder engagement across an account or opportunity to indicate the strength of the relationship and the likelihood the deal closes.

Use an organization's own closed-won and closed-lost deals to set benchmarks — time-in-stage, deal age, stakeholders per stage — then flag opportunities that deviate from what winning normally looks like.

Analyze call transcripts with AI to auto-populate a qualification framework (e.g., MEDDIC) — recommending a score per element plus supporting notes the rep can accept, edit, or ignore — without the rep manually entering it.

A composite score where 0 equals closed-lost and 100 equals closed-won; it should rise as a deal moves through the pipeline and reacts to all positive and negative signals mapped against a 12-month benchmark of won deals.

A selling discipline of always securing the next meeting while you are still in the current one, so an opportunity never sits without a scheduled next step.

Reps submit a data-backed forecast (pipeline / upside / commit) weekly; managers then submit their own adjusted view, hedging a rep's commit to upside when qualification is thin. Coverage ratios and pacing roll up by the Salesforce hierarchy.

Compare a rep's actual pipeline coverage (e.g., 6.8x) to the coverage they historically require to hit target (e.g., 3.6x) to decide whether they need more pipeline or should focus on closing what they have.

Treat the accuracy and structure of your underlying data — the ontology — as the foundation for any AI strategy, because AI is only as good as the data it can access, and swappable models matter less than the data feeding them.

A research-derived methodology that distinguishes two selling environments — low-complexity/transactional and high-complexity/enterprise — and, in the complex environment, wins by Teaching the buyer something new, Tailoring it to their situation, and Taking Control from an advisory, expert frame.

The Challenger research profiled sales-rep archetypes and measured which won. Weiss names four: the Hard Worker (outworks everyone), the Challenger (teaches and pushes change), the Relationship Builder, and the Lone Wolf.

Neil Rackham's 1970s discovery framework: understand the buyer's Situation, the Problems inside it, the Implications of not solving them (cost of inaction), and the Need-payoff of solving them, to drive urgency around why change now.

A riff on SPIN designed to combat product-led, feature-and-benefit selling by first understanding the buyer's problems before offering a solution — best used to help a buyer see a problem they didn't know they had.

The discipline of reading where a buyer is in their own process and matching your motion to it: a mature buyer knows the problem, the solution criteria, and the competitors; an immature buyer knows little and needs co-creation.

A holistic system organized around engaging the buyer, qualifying, and closing — including 'upfront contracts' (pre-agreeing to a next step) and 'pain funnels' that probe first-, second-, and third-level pain.

The view that sales mastery is the deep execution of a full set of fundamentals — hunting, reaching decision-makers, discovery, creating needs, business-case building, presenting, multi-threading, negotiating, handling rejection — assembled in your own way, rather than any single methodology.

Gartner's framework, rooted in research on buyer decision fatigue and decision confidence, in which the seller's job is to help an overwhelmed buyer make sense of an overload of information and competing options so they can decide with confidence.

A build-from-scratch playbook for customer success operations: (0) Breathe and triage for impact; (1) Learn the lay of the land — roles, journey, and where time goes; (2) Bring in the right tech once the process is aligned; (3) Build KPIs and a customer health index; (4) Use the data to drive decisions; (5) Stay connected to the customer.

High product adoption and green dashboards do not guarantee a healthy customer. A single metric (logins, courses created, items assigned) measures activity, not the value the customer is actually extracting.

Automated Salesforce alerts that fire at six, three, and one month before a renewal date, pinging the right people to confirm conversations have started, questions have been asked, and adoption is on track.

Three gates that determine when a company is ready to buy a Customer Success Platform: (1) established processes for outreach, QBRs, and handling at-risk vs. healthy accounts; (2) trackable product-usage data (e.g., via Snowflake or a BI tool); and (3) an inability to stay proactive by hand at leadership's bar.

A composite health score that aggregates multiple signals — support (first-response and resolution times), satisfaction (NPS/CSAT), adoption, and usage — rather than relying on any single isolated metric.

Luster's core operating loop: first diagnose proficiency at the atomic skill level, then predict where a lack of proficiency is about to impact performance in the next 24–48 hours, then prescribe the specific practice or content to close that gap in real time.

The principle that you must objectively measure a team's competency gaps before deploying any learning, development, or training — otherwise the enablement is a waste of time and money.

The failure mode of the consultant-led skill audit: after three-to-four months and hundreds of thousands of dollars analyzing the team on poor CRM data and self-reported interviews, the firm 'plops' a diagnosis with no mechanism to fix it — and it's already last quarter's problem.

Grounded in behavioral and cognitive psychology, Luster offers two practice modes: full-call simulations that mimic an entire sales conversation (prospecting, discovery, QBR, proposal, negotiation), and isolated skill drills with a built-in AI coach that repeatedly tests one skill such as objection handling.

Two ways to build an AI product. 'Quick tech' is a user interface layered on a single shared LLM instance — fast to demo, but unable to control data sharing, latency, or per-customer context. The 'platform' approach builds a trained, closed-off instance per customer behind proprietary layers, trading feature speed for control, security, and stability.

Luster's proprietary stack that sits between the raw LLM and the user interface. Layered bottom-up: a per-customer trust-and-security layer, a custom ingestion model of the org's people and behavior, a company-specific insights/persona/goals layer trained on first-party plus third-party web data, a conversational-AI layer (latency, personality, context), and an output layer of predictive skill insights and prescribed actions.

When RevOps enters a company and what the first roles are: it typically starts from a systems need, so the first hire is a dedicated systems admin (CRM plus connected tools), followed quickly by a second, more strategic skill set focused on process, analytics, and reporting.

A ranked preference for where RevOps should report: first a true, full-scope CRO; if none, a COO; if none, a strategic (not accounting-led) CFO who owns corporate planning.

A distinction between a true CRO who owns the entire revenue organization — marketing, sales, and customer success/account management — and a 'CRO' who is really a VP of Sales moonlighting in the title, focused mainly on the sales motion.

The principle that RevOps needs to sit under an executive with scope over the entire GTM lifecycle so it has unbiased authority over every lever — and that placing it under a single-function leader strips that authority.

The sequence of roles a RevOps org adds as it scales: systems owner(s) → a manager/VP-level strategic leader with a seat at the table → a dedicated reporting-and-analytics owner → enablement → per-function RevOps PMs across marketing, sales, and CS.