Revenue Operations

The default event motion: attend because you have always attended or because you think you have to be in the room, and expect the value to come to you.

Size the format to the share of attendees who are your buyers or customers: at roughly 10% or more, show presence is worth it; at three or four percent, skip the booth and run a targeted suite off-site.

Match the seniority and the specific people you send to the audience that will be there, using CRM data to pick reps by the pipeline that will be in the room rather than by event skill.

Replacing the common 3x event ROI target with an 18x or 20x bar, measured against closed-won booked revenue rather than pipeline.

Measuring an event over the six-to-eighteen-month period in which its true impact actually lands, instead of on booth leads scanned during the show.

Vendelux's data thesis: build the most robust data set of where people and companies are going to be, combining confirmed attendee data with a predictive engine, then overlay a customer's CRM on top of it.

Treating a multi-day event as a set of activations, each with a stated goal and a defined audience, staffed by the right internal people and scheduled around the event's own agenda.

Every buyer relationship at an event has to survive three phases — reaching out and booking before the show, showing up prepared during it, and following up after. Failing any one produces zero value from that buyer.

As AI avatars become convincing, being physically in a room is the only way to verify that the person you are buying from is who they say they are — making in-person the channel that carries trust.

Map the big tentpole events that matter to your market first, then work down and fill the remaining calendar with roadshows and local activations.

A machine- and human-readable description of what is in your data, deployed alongside the data itself: a SQL model definition plus a YAML file carrying the meaning, provenance, calculation choices and enumerated values for every field.

If you read your own semantic data and don't get clarity from it about what the data actually is, neither will your AI.

A way of organising a data warehouse in three layers. Bronze is a raw one-to-one copy of source data. Silver is cleaned and sanitised — fields extracted from JSON strings, readable date formats, human-readable column names, only the columns you need. Gold combines multiple tables into the final artifact used for tracking and reporting.

Living mostly in the silver layer, producing artifacts freely, and letting an artifact's survival through real business change decide whether it earns a place in gold.

A layer over your existing stores — knowledge articles, call transcripts, support tickets, the relational database — that knows how everything connects and, on demand, traverses those connections to assemble exactly the context a question needs before it reaches the model.

The recognition that an AI pipeline is mostly traditional software: a query handler script, an entity lookup, graph traversal, packaging — and only at the end a model call.

Sequencing infrastructure by maturity rather than building it all at once: hard-code context into skills while proving value, add a vector database when unstructured volume grows, and consider a graph database only when your semantics are held together by brute force.

Choosing models by what task they are fine-tuned to do well rather than ranking them on a single intelligence axis.

Structuring a combined data and revenue operations team so each ops head operates as a product owner, with analysts who are AI engineers and other technical people at their disposal, plus the business strategy and context from the sales or CS leader they partner with.

Replacing the sprint bucket with a triage question asked before anything is scheduled: what is the likelihood that this can hurt anything or cause any permanent damage? The assessment is done agentically and its output routes the request to one of three delivery tracks.

Track one is an experience-layer skin change on a custom app that touches no metadata, flows or business logic, creates no security or performance issue, and can go straight to development and out. Track two is a small metadata update that still needs a human in the loop but runs on demand. Track three is project work that resembles the agile process the team already runs.

Gate one is an agent modelled on the teammate who is best at interrogating a brief — trained on that person's comments and transcripts of them ripping briefs apart — which forces a request back to the underlying why and the value. Gate two is the architect reviewing the solution design.

Giving each role — SDR, BDR, account executive, launch specialist, integration specialist, strategic CSM — a fully custom experience layer that can be modified without touching metadata or business logic.

Holding business logic, automations and plumbing under tight control while deliberately experimenting with ways to open up the experience and application layer — including hosting internally built user creations the way Vercel hosts small projects.

A baseline ratio of go-to-market headcount to RevOps headcount used as the starting point for an investment conversation, with any deviation from it tied to particular metrics.

Deliberately making your first dollars-and-cents conversation with finance one where you protect budget — flagging a cheaper software swap, consolidating contracts — so the relationship is established long before any request for resource.

Converting declarative Salesforce configuration to Apex on the belief that it is easier for an LLM to manage the whole system the way it would a code base, replacing flow diagrams with SOPs and generated Mermaid diagrams as the documentation layer.

Reframing overload from 'how do I fit more into my calendar' to 'how do I consistently do my best work', on the basis that everyone has roughly the same hours once non-negotiables are covered and cramming more in has a ceiling.

Joe's three consistent practices for doing his best work: a weekly step-back block of 10–20% of his time, sleep and physical exercise as non-negotiables, and therapy used proactively rather than only in a crisis.

Google's 20% rule dedicated roughly one day of a five-day week to a passion project. Joe's adaptation reserves 10–20% of each week, depending on priorities and bandwidth, to step back and review all projects and initiatives from a higher level.

Anthony's framing that everyone needs a beast mode button — a NOS throttle — they can activate when it matters, but that holding it down all day and all year is what causes burnout.

Treating balance as seasonal rather than as one mode to optimise in perpetuity: a new role, the start of a career or a career pivot can justify a period of being unbalanced, provided there is a plan to come off it.

Separating ad hoc work (unexpected tasks, support requests, ideas from meetings) from roadmap work (projects and initiatives), then bringing both into one project management tool so they are planned against the same timeline.

Hassan's description of RevOps at an early-stage hypergrowth company: building processes and systems while the foundations underneath keep shifting.

A smaller company is a small boat that is easy to steer, while a larger organization is a cruise ship that takes hours or days to change direction, so RevOps design has to match the vessel.

RevOps that agrees with everything a CRO says and executes is a ticketing center. Strategic RevOps asks why, explains the risks of a bad decision and offers alternatives that still reach the goal.

A compensation model for a business with no contracts, in which sales, post-sale and solutions engineers all take a percentage of each customer's monthly revenue for a year.

A prediction model that estimates a new customer's annual revenue from roughly their first 60 days of usage, trained on historical customer usage and adjusted for known seasonal patterns.

Reconciling the top-down target investors set with a bottoms-up model of how many reps, and how much marketing coverage, are needed to hit it.

Hassan's build order for the function: a generalist at Series A, a strategic leader with technical and analyst layers from Series B to D, and a specialized team after IPO.

The early-stage goal for RevOps: not to stop the chaos of a startup but to give it a method, so the environment is still chaotic but makes sense.

At Series B to D, the head of RevOps adds a technical persona and an analyst persona beneath them to absorb tactical work.

Sales is the driver everyone watches. RevOps is the pit crew doing unseen tire changes in seconds, and truly world-class RevOps also designs the car.

AI agents should be evaluated against the same north-star metrics as any other investment, not by asking for the ROI of the agent itself.

The knowledge of how the go-to-market systems actually work and how metrics are defined, which Hassan calls the most important piece of any AI deployment, and which sits with RevOps.

AI deployed without RevOps governance makes disinformation faster: it returns a wrong answer with confidence, and that answer spreads.

When a CRO asks what the ROI of RevOps is, reverse the question and ask what it costs to run a scaling go-to-market machine with nobody strategically designing, overseeing or managing it.

Aimee's way of separating a true forward deployed engineer, as Palantir defined the role, from rebranded professional services. First, is it a paid engagement with a billable metric? Second, is the customer effectively renting an engineer for work that may or may not involve a product?

Two versions of what gets called forward deployed work. The Palantir model goes into the customer's environment and builds whatever the customer needs, fully bespoke. Solution architecture helps a customer use the vendor's software largely out of the box, perhaps with scripts or API extensions, without custom development.

Stand up professional services where customers are consistently asking for help. Avoid starting from the premise that services are a lucrative revenue stream to be packaged and sold.

The order for building professional services. Commit to the capability and hire people who can learn to do it. Build a repeatable playbook. Package it with deliverables, timelines, outcomes and a price. Only then run it as a P&L with utilization targets and margins.

Sourcegraph's three packaging models. A fixed-fee package, such as the mandatory implementation attach at $10K base or $25K advanced. A bucket of hours burned down over the contract, used for the resident architect package. An FDE-style engagement priced against delivered outcomes.

A way to validate services pricing. Take the fully loaded cost of an engineer and how many engagements that engineer can run at once. Work out the price point needed to break even, then what it would take to hit a services revenue goal.

Keep at least part of delivery in-house to preserve the feedback loop into the product and the customer relationship. Use partners for coverage, such as regional support, while keeping internal teams on complex or strategic accounts.

Sourcegraph's framing for its delivery competency as a core differentiator: years of playbooks that let it deliver adoption consistently and repeatedly.

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.

Scenario selection, product configuration, commercial terms, and a locked review step — designed around what the front-end user must do rather than how the plumbing works.

Treat guided selling design the way you would treat replicating any top performer: go into conversation intelligence, break down how the best sellers actually sell, and encode that rather than an idealised process.

The binding constraint on out-of-the-box quoting is not what it can produce but what it fails to prevent. Restrict the options a scenario allows rather than correcting errors after the quote goes out.

Before recommending anything, map CPQ, contract lifecycle management and billing/subscription — plus ERP or accounting where relevant — and confirm they can communicate flawlessly.

Automate granular alerts for the things you expect to go wrong — an invoice schedule that has not appeared, a billing date that has slipped — instead of reconciling on a quarterly cadence.

Running founder-led demos primarily for product feedback and word of mouth rather than for the revenue they close, on the basis that the calls simultaneously generate top-of-funnel, brand and a build loop with the product team.

Bring in the sales leader before the first reps, because founder win rates reflect easy early adopters rather than a repeatable process, and the leader is the one who can build the process and hire against it.

Hiring people who have personally lived the customer's problem, so their story lands on every call and their judgement about the space is earned rather than briefed.

Community fails when it is treated as a category rather than an offer. It needs specific value props and rituals — a recurring event, an outcome, a transformation — designed the way you would design any other business.

An audience is a one-to-many following measured in followers and engagement. A community is the down-funnel subset that pays and connects with each other, and it is usually where the actual business lives.

Renaming RevOps to reflect what the work has become — building agentic workflows and infrastructure across the company — rather than keeping a title that no longer describes the job.

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.

The single-player experience — one person with a folder, a harness and full access — is already excellent. The multiplayer experience, requiring governance, permissioning and personalisation at scale, barely works.

Individual agents and skills recreate the pre-SaaS spreadsheet problem: everyone with their own formulas, their own data, arriving at meetings with different numbers.

Children in an unfenced schoolyard stay close to the building; children with a fence range all the way to the boundary. Constraints expand exploration rather than limiting it.

Push centrally-controlled skills out like a web deployment, but have them live inside each person's own harness, so central updates land without overwriting accumulated personalisation.

Agents with a name, a job description, a defined skill set that can run on a schedule or a trigger, and capability tiers — rolled out to managers like a new hire class.

Review the actual day in the life of sellers across the last hundred meetings and threads, identify the missed moments, derive the recognition insight, review the automation granularly, then deploy edits across every personal harness at once.

The large stack decisions are determined by company characteristics rather than chosen — headcount decides the CRM, the pricing model decides whether metering exists.

Enterprise Salesforce suite; HubSpot growth stack (the all-in-one default under 200 people); modern AI-native lean stack (deliberately thin, Clay and a warehouse doing the work); dual CRM in transition (Salesforce and HubSpot in parallel, mid-migration or permanently split after an acquisition); and the consumption stack (usage billing wired to real metering).

Tier one — CRM, marketing automation, enrichment — table stakes at any stage. Tier two — sales engagement, CPQ, warehouse, routing — added when the motion demands it. Tier three — next-gen CRM, AI agents, usage metering — the frontier.

Prioritise the unglamorous systems between revenue and the invoice — metering, quote-to-cash — over more visible tooling, because those are the ones nobody funds until they break.

Apply first-principles reasoning to a backlog of requests to find the repeating root cause, collapsing fifty ideas into roughly three themes, then choose against the company's goal for the current or next quarter.

Require evidence of a first small milestone before funding scale, rather than skipping the messy manual trial-and-error phase that reveals what is actually scalable.

State the belief, the reasoning and the measurement in advance, then treat the outcome as a signal rather than the defining verdict, measuring the process separately.

Forward-deployed engineers and deployment strategists own post-sale activation and consumption, so account executives are compensated on bookings rather than on realised usage.

An application layer on a headless Salesforce holding the three things reps touch daily — a Kanban forecast board, a hackathon and AI-day calendar, and transcript-prefilled deal updates — with everything routing back to the CRM as source of truth.

An environment where non-engineers can ship internally built tools, with authorisation controlled at the integration level — read-only on some connections, read-write but never delete on others — rather than inheriting the builder's god-mode access.

Selecting partners on thought leadership first and technology second, and paying a premium for a forward-deployed style engagement that becomes part of the operating rhythm rather than a tool handed over.

Purchase the commodity layers — warehouse, CRM, the plumbing someone else should think about — and build only the intelligence and context that is genuinely unique to your business.

Recurring services revenue treated as SaaS, on the reasoning that the buyer wants an answer and does not care whether it came from software, AI or a person.

Customer preference is earned through expertise and presence rather than feature completeness; no product does everything, and the favourite one gets passes the best one does not.

Reps unprepared for the conversation; inability to ask and follow up on good discovery questions; sheepishness on pricing.

Owning the pipeline model end to end — coverage, pipe-gen, who builds it, what happens to it, the levers that move it — and being able to predict it several quarters forward.

The connective tissue agents run on — definitions, data model, skills and workflows — built and maintained as an operating function rather than assembled per project.

An agent pointed at a new client's connected data on day one, running the full teardown — funnel conversion by stage, stalled deals, rep coverage, quietly dead pipeline — and writing it up against the playbook in brand voice.

A quarterly review where unanticipated client questions are answered live from the client's own data and definitions, rather than deferred to a follow-up.

Three background agents operating the delivery business itself: project management turning call transcripts into scoped tasks, customer health reading transcripts and Slack for account signals, and team evaluation watching delivery quality and coaching needs.

Build the context graph first — the semantic layer resolving definitions, motion, plan and identity across systems — then build the skills, plugins, workflows and interfaces on it.

Measuring a customer-facing agent by how many people it prevented from reaching a human, rather than by the outcome the interaction exists to produce — satisfaction, conversion or revenue.

A layer that classifies and analyses every customer-facing conversation across email, chat, text and voice, used as an observability tool before any agent is built and as the foundation the agent stack sits on.

Voice realism is commodity and improving on someone else's release schedule; behaving like an effective operator, learned from a specific company's own conversations, is the durable differentiator.

Identifying the highest-performing reps automatically from conversation data, extracting their playbooks — jokes, analogies, phrasing for complex products — and reproducing those tactics in the agent.

Eighty percent of the work produces an impressive demo; the remaining twenty is unglamorous edge-case handling that only experience and failure supply.

Agents running the work that used to be non-humanly possible — the analysis nobody had time for and the answers that took a data team three sprints — on demand, in plain English.

ICP analysis cross-referencing deal size, sales cycle and six-month retention; a messaging teardown against recorded sales calls; and a live pipeline diagnostic run inside the forecast meeting.

Shared definitions, identity resolution, the plan, and memory — the four absences that make raw AI on a CRM return confident wrong answers.

Competitive advantage comes from constant recalibration during the quarter rather than from headcount or tooling — discovering you were wrong while it can still be changed.

Multiply each possible outcome by its probability and sum them: a $100k bet with a 50% chance of $500k and a 50% chance of zero has an expected value of $250k. Then check it against opportunity cost and against whether losing is survivable.

Judge a decision by the quality of the reasoning available at the time rather than by how it turned out — while treating an improbably long losing run as evidence the process itself is broken.

A decision has broadly known outcomes — eggs or yoghurt, water or coffee. A bet has material variables outside your control. Most business calls are bets that were never priced as such.

Master the basic disciplines first — they make you better than ninety-five percent of beginners — and only then work on reading signals, which is genuinely advanced and does not matter until the fundamentals are automatic.

Cost of the investment plus a rough estimate of the time it consumes, against a target number of leads at a target ACV. Three or four significant figures is close enough, and the model takes about ten minutes.

Declining to act is itself a bet, carrying the consequence that a competitor takes the opportunity you passed on.

The roughly twelve-month window — eighteen at the outside — between a Series A closing and the company being back out raising, in which the outcome of the Series B is determined.

The three sequential builds that fill the Capital Clock window: instrument every motion before scaling it, multiply the performance of each motion with technology, then prove the result on a segmented scoreboard.

Three layers of context every go-to-market decision runs on: Performance (all GTM data normalised into one semantic layer and tied to goals), Market (ICP, messaging, market conditions), and Process (a living repo of playbooks, hypotheses and decisions).

Efficiency saves money by removing effort; effectiveness wins the market by lifting the win rate, conversion and performance of each motion. At this stage, only the second one matters.

CAC, payback, conversion and sales cycle reported by channel, by motion, by customer segment and down to the individual rep and CSM, rather than blended across the business.

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 framework for evaluating a 'backwards' move from CEO to CRO: weigh product-market fit, founding-team fit, and investment thesis against the compensation, equity, and personal-fulfillment math of joining a high-growth build with strong culture.

The idea that the go-to-market motion — talent profile, process weight, and metrics — must be rebuilt at each ARR band rather than scaled linearly. Different stages leverage different areas of the process.

Gate sales hiring on two leading indicators: how well reps are ramping against a defined ramp curve, and what percent of quota (and ramped-quota capacity) they are attaining. Below threshold, pull the plan back.

The second-order damage of over-hiring sales: diluting territories and top-of-funnel demand across reps who won't stick, which starves top performers and eventually drives your A-players out.

A hiring heuristic for specialized verticals: emulate your customer base and screen for the common denominator of work ethic and mission alignment rather than a specific sales or industry pedigree.

An AI-adoption operating model: allow broad, decentralized experimentation to reduce fear and prove ease of use, then centralize the valuable skills, agents, and data pipelines — governed by RevOps — for anything mission-critical.

A pipeline philosophy that favors thoughtful, researched, use-case-specific outreach to a narrow buyer over high-volume, low-hit-rate blasting.

Treating in-person events as an operational play with three phases — pre-plan (targeting, pre-set meetings), execute (on-site, ideally with stage presence), and post-plan (structured follow-up tracked through CRM) — not as a booth you show up to.

The primary barrier to AI adoption is a mental model, not a skill gap: people onboarded in a pre-AI world treat AI as the next, harder evolution of technology and cling to point-and-click UI notions.

A model of selling as two blended disciplines: the art (psychology and influence — moving many stakeholders in the same direction) and the science (methodically progressing a deal through a rigorous process to signature).

The reframe that managing a sale is like managing a project — bringing operational and project-management rigor (sequencing, stakeholders, milestones) to progressing a deal to close.

A transformation framing in which agentic AI augments the revenue team rather than replacing it — the 'plus' signals that humans stay in the motion, owning relationships and accountability, while agents handle preparation and scale.

The higher the deal value and the more up-market the customer, the less AI belongs in the customer-facing interaction — and the further down the tail (SMB), the more the agent can own the motion with a human reviewing the output.

A two-variable decision model for how much AI to put into any motion: account value (ACV) and which product surface the customer is touching (and how mature that surface is).

Split customers into enterprise (large advertisers), mid-market (D2C brands, performance agencies), and SMB, and assign a different agentic role to each based on that segment's customer-service needs and risk tolerance.

The newer and less proven a product, the more human-in-the-loop the motion should be — because the fastest way to learn from customers experiencing something new is to talk to them, not to automate the interaction.

AI enablement swings between a centralized owning group and fully decentralized team-by-team ownership; the healthy resting point is in the middle — cost-and-tool guardrails set centrally, process redesign owned by the teams.

Whether you can decentralize AI at all is gated by the strength of your underlying data — a clean CRM and a healthy data stack are the precondition for letting functions own their own AI.

Judge AI initiatives by revenue and efficiency outcomes — speed to market, meeting volume, pipeline-stage conversion, revenue per head, ARPU — rather than by AI spend.

The operator's path to senior leadership: deliberately pursue new lines of business, international expansion, and reorgs so you see and understand the entire business, not just one function.

The point of 'carrying a bag' isn't the title — it's going through a period where you genuinely feel the pressure of contributing to the top line, a career experience you have to go collect.

Run your weeks against roughly four equal priorities, each assigned a color, and audit your calendar so it's about a quarter of each — a mechanism to keep strategic time allocation honest.

A two-tier model of leverage: the number-one and permanent form is talent — genuinely great people — and the number-two, fast-compounding form is technology (today, machine learning and AI). Technology multiplies talented people; it does not replace them.

The principle that a true A-player raises the standard of everyone around them, while a B- or C-player imposes a hidden tax that drags the whole system down. Illustrated by Kobe leveling up the Lakers and Michael Jordan's teammates learning 'no days off.'

The discipline of continuously scouting talent even with no open role — treating every conference, meeting, and relationship as sourcing — so that when a need arises you already have a list of people to call.

A three-part talent screen: a demonstrated track record of results (evidence they know what to do), resilience (how they responded to getting knocked down — ownership vs. victimhood), and hiring people who are better or smarter than you at the role.

The career thesis that the surest way to earn the next opportunity is to be extraordinary in your current role, so that results — not networking or shortcuts — pull opportunities to you unsolicited.

The practice of deliberately creating a gap — Chris forced himself to do nothing for six months — before the next move, on the premise that when you stop forcing an outcome, the right path and clarity show up.

A decision matrix with a person's non-negotiable values down the vertical axis (people, trust, integrity, emotional safety, belief in the vision, a path to winning, mutual respect) and the candidate opportunities across the horizontal axis, scored by which boxes each opportunity checks.

An M&A integration playbook whose single biggest success factor is how and when you bring people along and relentless over-communication — including a first all-hands that answers employees' real question (am I safe, what does this mean for me) before any company history or financials.

Deliberately rotate through operations, marketing, partnerships, consulting, sales ops, and product before ever carrying a quota, so you understand everything that actually affects revenue — rather than reaching the CRO seat straight up the sales track.

Stay in every role at least a year (sometimes two) to actually learn the skill, and when hiring, evaluate candidates on increasing responsibility and achievement rather than raw time-in-seat.

Convert a product-led motion into an enterprise motion by getting selective on collaboration-heavy segments, landing two or three teams or divisions, then uniting them under one executive with a combined security, collaboration, and cost case.

If you find yourself in a competitive cycle defined by a competitor's strengths, one of you is in the wrong cycle — and it's probably you. Know your weaknesses so you can avoid the fights they define, and concentrate on the ICP that values your strengths.

A private trial-run roadshow before the public IPO roadshow: executives travel separately to a low-profile event and pitch bankers who signal buy-or-pass on an app, letting the company watch the book oversubscribe and the price move before the S-1 debut.

An acquisition demands the acquirer audit every contract, approval, and pipeline metric to validate revenue durability, and then run a full integration of systems, org, and process — a burden an IPO never imposes.

Startup equity is worth literally zero until an IPO or acquisition. Secondary sales are rare, board-gated, and usually capped; in a buyout, investors are paid first, so if the exit isn't large enough your equity can be nothing.

Revenue leaders should personally build at least one or two agents (you can ask Claude to teach you) so they understand the power, scope, and correctness constraints well enough to manage AI-driven GTM — the same way understanding marketing and ops makes you a better revenue leader.

Lead with deep domain expertise and your own thinking captured on paper first — not with AI-generated first-draft language — then use AI to fill gaps and propel execution rather than to create ideas you can't defend.

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.

When standing up or fixing a go-to-market org, sequence your build in a deliberate order: put the systems (RevOps backbone) in place first, then the people, then the process.

In heavy industries the first contract is the audition, not the win. Delivering it at a high bar earns the right to the 'real contract' — the bigger, expansion opportunity that follows.

RevOps is 'the language in which companies test, measure, learn, and drive rapid scalability' — the first port of call at any company — not just Salesforce hygiene.

The senior CRO responsibility is demonstrating control over the number — knowing when you're behind, what the corrective actions are, and whether they're working — rather than merely landing the target.

In concentrated, capital-intensive industries, expansion doesn't come from more seats or another module — it comes from earning trust through delivery so the customer opens the aperture to bigger questions.

A hiring thesis for complex industries: recruit people who've operated in the space and can speak with credibility, then teach them the selling motion — screening above all for learning agility and structured communication.

Treat the service/delivery organization as a co-equal leg of the stool alongside sales and account management — not as a margin-enhancement play.

Patch's consulting arm embeds strategists directly with customers to navigate the complexity and information asymmetry of carbon markets — its version of the forward-deployed engineer.

Durable differentiation in complex industries comes from combining software, human expertise, and the proprietary data the product generates — not from any one of them alone.

The classic three-horizon framework (core business, adjacent bets, and future/experimental bets) becomes far more actionable when AI lets you experiment cheaply.

Three sales processes run in parallel and then fused: win the fintech that wants a banking/card product, sign a sponsor bank willing to back the program, and marry the two under a single tri-party agreement.

Bake forecasting into qualification as a trade: the customer shares projections (customer counts, average spend) and in return receives a professionally built deal model showing how the program becomes profitable — one shared document both sides work from.

Use the sales engineer's solution document — effectively a statement of work — as the artifact that holds every party accountable to exactly what was scoped and approved.

The sequence in which a founder should lay down go-to-market foundations — with RevOps placed effectively first, right after the first salesperson, before scaled AE or BDR headcount.

Treat each go-to-market segment (enterprise, mid-market, SMB, and their international variants) as its own line of business, with distinct product needs, marketing plan, ACV/LTV, conversion rate, sales cycle, and quotas.

Identify and win over the people who can kill a deal — often someone you never meet, like compliance or a bank's board — rather than over-investing only in the enthusiastic champion.

The market is splitting into companies that use AI to introduce precision (tighter ICP, enforced qualification, best-practice discipline) and companies that use AI to generate volume (infinite leads on top of an undefined motion).

Putting AI on top of an existing go-to-market motion exacerbates whatever is already broken — much like practicing a bad golf swing makes your game worse, not better.

When sellers carry too much pipeline, win rates drop dramatically because they engage and multi-thread less; a balanced pipeline wins at nearly twice the rate.

ICP is a small, well-understood segment defined by fit-and-timing signals — not the entire universe of companies you could theoretically sell to (TAM).

Keep the ICP you use for the fundraising/exit growth story in separate books from the tighter ICP your sellers chase every day.

The best sellers disqualify roughly three quarters of their opportunities by discovery, advancing only ~25% — which produces late-stage conversion above 70%.

Sales efficiency measured as dollars generated per day; larger deals ($70k+ ACV) are over 6x more efficient because they don't take proportionally longer and carry more expansion potential.

Deals with six or more stakeholders win at nearly 4x the rate, and buying committees keep growing — so multi-threading is increasingly decisive.

A 360-degree seller who self-sources pipeline, closes, and stays on as the commercial point of contact through land-and-expand — replacing the single-purpose relay of SDR → AE → CSM.

A recurring ~50-page audit that connects to the platform in two hours, looks back a year over won and lost deals, and reports across five chapters: sales-efficiency trend, win/loss analysis, live-pipeline risk, rep coaching gaps, and sales-process friction.

Small, stacked gains — 10% better ICP targeting, 10% better qualification, 10% more multi-threading — compound quarter over quarter into materially different results within three or four quarters.

A CRO knows what to fix and even knows candidate strategies, then freezes — either because execution looks like an overwhelming amount of work, or from fear of taking a step back and breaking what already works. RevOps is where that freeze thaws.

RevOps shows up with a point of view on what the business should do rather than waiting for direction — enabled by an information edge, because the field shares candid feedback with the head of RevOps that it won't share directly with the CRO.

Keep an annual anchor tied to strategic and fundraising commitments, but plan continuously: evaluate performance to plan monthly, decide on adjustments quarterly, and run a second-half replan as conditions change.

A one-hour, bi-weekly meeting between RevOps and sales leadership, anchored on a fixed dashboard of five to eight initiatives, that serves as the catch-all forum for the business.

Beyond standing metrics, instrument each strategic bet on its own — a spiff's multi-attach rate, deal progression past a stuck stage, or pipe from moved vs. unmoved accounts — so you can prove whether it's working.

Data-driven modeling of territories across three lenses — firmographic (segment thresholds), 'smart plan' (balance by priorities like ARR or tier-A account count while minimizing disruption), and geography — layered with coverage, quota, and policy modeling.

Run territory planning like a gold-mining company: first know where the gold is, then decide which miners to send where, and keep the operation flowing when a miner goes down.

Survey your total addressable market and assign a potential revenue valuation to every account, then use that field to carve and balance territories so each seller has an equal amount of gold to mine.

The most consistent RevOps career path leads to COO; the way to grow toward it is to run RevOps today as if you already held the COO role — operationally minded, program-driven, and confident enough to lead the CRO.

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.

Each major lab (OpenAI, Google, Anthropic) ships three distinct products: the model (baseline infrastructure — GPT-5.2, Gemini 3, Claude Opus 4.5), the consumer app (the browser chatbot for general-population Q&A), and the agent platform (for professionals to get work done).

The capabilities that only agent platforms have and consumer apps lack: a persistent internal to-do list (so the agent works 10–40+ minutes autonomously), the ability to launch sub-agents, reading and writing files on your local machine, permission/plan modes, queued messages, and context compaction.

A repeatable structure for building agent prompts: (1) supply context files, (2) instruct it to launch sub-agents, (3) have it maintain a to-do list, (4) tell it to be token-efficient, (5) direct it to write outputs to files, and (6) frame it to think like a strategist / thought partner.

A token is the atomic unit of how AI thinks (~3–4 characters). The context window is finite working memory holding all inputs and outputs (e.g., 200K for Claude 4.5, 1M for Gemini 3); once full, the agent forgets earlier context. 'Compacting' summarizes the current context and hands it off to a fresh agent with a clean window.

A skill is a folder of files that teaches an agent how to perform a task (make a PowerPoint, an SOP, a PDF, wireframes). The labs adopted a shared skills standard, so you can download skills from the internet or build your own and point the agent at the skill's path to execute it.

Getting an agent platform running in ~5 minutes: (1) download VS Code, (2) install the official Claude Code extension from Anthropic, (3) log in with a $20/month Claude subscription. Restart, click the orange icon, authorize, and the agent is enabled.

The single diagnostic Alex uses to decide when and how to change GTM: at any moment, identify who controls the client's decision, who controls the revenue, and who controls the margin. When the answer changes, the go-to-market must change.

A market maturity curve every industry travels: from a phase where you must educate buyers from scratch (highest margin, lowest competition), through growing awareness and competition, to full commoditization where price pressure peaks.

The 'golden era' — strong demand, high margin, still-low competition, educated buyers — is not a reward to enjoy but the starting point of commoditization, and it signals you should already be building the next product.

A talent principle (from The Science of Scaling) of evaluating people, customers, and standards by their worst-day performance rather than their potential — like a professional athlete who is great on their worst day, not just in flashes.

A portfolio-scaling model where a commoditizing, lower-margin core product is used as an entry wedge, and higher-margin products sitting earlier on the educational curve are layered on top — replicated in-house or acquired — repeating at every level.

A market-intelligence practice of tracking where venture capital — especially seed and pre-seed — allocates capital, categorized by segment, as the cheapest and smartest signal of the next big thing two to three years out.

An AI-native operating default: when you have a real need you'd pay for but can't find the right tool (or it's too expensive), build it yourself with AI coding tools rather than waiting on a vendor.

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.

Kotter's change-management allegory Brett invokes for the RevOps reality: you may be the one who spots the crack in the iceberg, but seeing it isn't enough — you have to sell the change to 'the elders' and earn consensus before anything moves.

A mentor's operating standard: if a leader asks for a square, come back with a square (or they'll discount everything else you say), but if you know a circle is what they really need, bring that too.

A boss's line — 'you're not a race car driver, but you know how to build a really fast race car' — that captured why an operator who understands funnel mechanics, handoffs, and the sales cycle can be handed the wheel of the team.

Resolve inside-vs-field conflict by defining discrete functions — specialists who do top-of-funnel work and AEs who land-and-expand existing customers — with executive-mandated boundaries nobody is allowed to cross.

Build a recurring team forum where anyone can say 'I need help with this,' because no individual coach can ever exceed the combined knowledge of the whole team — the highest-leverage part of a leader's cadence.

A meme of the modern SaaS stack — cloud, kernel, and applications neatly piled up — with AI as the Angry Bird flung in to topple the whole tower.

A productivity multiplier should be reinvested in output, not headcount reduction: if you can be a thousand times more productive, produce a thousand times more rather than gut the staff.

The load-bearing reason AI won't replace high-trust, complex sales: if something goes wrong, there's no one on the hook, no career on the line, no justice to be served.

As buyers research through AI chat, the website's job shifts: detect whether an LLM bot is visiting, serve it structured content to shape what it brings back, and push your information onto off-site links and affiliates the models cite.

Catalog every task each function performs, then sort each into two buckets — 'can I automate this with AI' versus 'this is inherent to the function itself' — alongside a competency matrix and clear career on/off ramps.

Brett's 2026 kickoff message: the only constant is change — or, in the truer Heraclitus phrasing, 'although you're standing in the same river, the water flowing through it is always different.'

Define the outcome you want and stay agnostic about how each person reaches it. Process is a safety net and a ramp for building habits, not the objective; the way an outcome is achieved should be 'completely irrelevant' as long as the outcome is right.

A leader's job, like a coach's, is to tap into the best parts of each person's natural style and put the right people in the right positions to build the best total team — not to standardize everyone toward one form.

Recruit for demonstrated problem-solving ability and internal drive rather than credentials (Ivy League degree, MBA, finance background). A sales role is fundamentally problem-solving done all day; pedigree is rarely the requisite it's assumed to be.

Compress a hard enterprise/government sales cycle by building an external ecosystem whose desired outcome equals yours — cooperative-purchasing bodies, complementary technology partners, and lobbyists — instead of scaling a bigger direct team.

Use cooperative-purchasing organizations (Sourcewell, HGAC) — which let one public agency's pre-competed, approved purchase serve as validation that another agency can buy the same way — as the engine that manufactures trust and shortens the buy.

When a competitor's strengths complement rather than fully overlap yours, convert the rivalry into an integrated co-sell: lead with the shared outcome ('if we compete, one of us loses; together we both win') and prove a repeatable joint motion on one marquee deal.

A market signal: legacy verticals that historically treated software as a cost center or risk-mitigation expense begin treating it as a competitive advantage, and the share of enterprises in-market for software jumps from a typical ~5% per year toward ~50%.

Since go-to-market process breaks whenever it depends on human compliance, the fix isn't more enforcement (mandatory fields, stage gates) but removing people from the data-capture loop entirely — letting AI listen and populate the system automatically.

Once AI captures CRM data automatically, the salesperson stops being a producer of data (data entry) and becomes a consumer of it — served a prioritized view of what's healthy, what's slipping, and what to work on next.

Adopt in stages: crawl (RevOps connects CRM, call recorder, Slack/Teams, and email, sets team structure and field mappings for a two-way sync), walk (auto-create and enrich records, remove humans from data entry), run (deal-health analysis, agents, and cross-functional data products).

Plot every opportunity on two axes: horizontal = how healthy the deal is (likelihood to win), vertical = how likely it is to close when the rep expects. The quadrants surface safe bets, acceleration opportunities (will close but not this quarter), and firm-decision-date deals where you may not be selected.

A full-reasoning agent wired to every captured touchpoint plus external research tools that executes deal tasks — building a custom ROI calculator to the prospect's own metrics, pulling industry benchmarks, and drafting the decision-maker email.

A per-contact score from -10 to +10 that identifies champions and blockers at a glance, with the reasons and specific quotes behind each. Filtering contacts by ICP persona and a high promoter score produces a live, shareable list of advocates.

Product roadmap signal should come from live sales conversations with the market — use cases, friction, competitors mentioned — not primarily from customer success and existing customers, who are biased because their problem already feels solved.

RevOps problems are hard to solve but remarkably consistent across similar-stage companies — a Series B sales-led company has the same problems and the same fixes as its peers — which is why the function outsources well while sales and product must stay in-house.

A maturity path for tying customer success to revenue: crawl (run a value cycle, lead with hard value, and book CSMs under S&M not COGS), walk (give CSMs CSQL goals and track the funnel), run (train CSMs to close simple upsells, or add an account-management layer inside the CS org for complex ones).

A way to tie business outcomes at the customer back to your product. Soft value is sentiment-based (how the customer feels); hard value is measurable — hours saved, dollars saved, headcount saved — that you can attach real numbers to.

When CSMs don't own the upsell directly, they're accountable for surfacing a set number of customer success qualified leads through normal customer work and handing them to sales; the leader tracks close rate, cycle time, revenue, and funnel shape.

Call it a bonus, not a commission, to shift the mindset. Pay 80% base / 20% bonus, split into two or three parts. The three-part version weights NPS, gross retention (an individual number), and net retention (a company/team goal) a third each; the two-part version drops NPS for individual gross plus company net, with an upside kicker above 115% NRR.

Give everyone in the company — not just customer-facing roles — a small bonus tied to NPS and NRR, so office managers and engineers alike have a stake in customer sentiment and retention.

Picture a bucket with capacity 100 (100% retention). The hose pouring in is revenue; you want to fill and overflow the bucket (>100% NRR). Every hole punched in the bucket is churn.

A CS-plus-sales/AM pod structure is justified only when the average contract value and the available 'green space' to expand support the coverage cost; otherwise a single AM covers the whole portfolio.

Have each team member list what they do daily, weekly, and monthly. Anything that doesn't require critical thinking is a candidate to hand to AI — via custom GPTs or purpose-built tools — freeing CSMs for critical thinking and human relationship-building.

As AI and no-code make building products easy, the hard problem shifts from creation to distribution — getting a great product in front of its rightful customers in an attention (eyeball) economy.

An outbound platform architected for AI from the ground up as a multi-agent system — each agent using the model it's best at — rather than a pre-AI product with AI 'slapped on top' via chatbots or plugins.

A workflow where you paste a domain, the system scrapes it, infers your ICP and buyer personas, writes them out as reusable context files, and converts them into a targeted lead list that also powers copywriting and qualification.

Use intent signals (job changes, hiring, department growth, 10-K priorities, life events) to decide who to contact and when — but keep them out of the message. Mentioning the signal wastes scarce email real estate and doesn't impress the buyer.

Replace the standard chain — Sales Navigator for lists, Apollo and other enrichment tools, a verifier, and ChatGPT deep research — with a single AI-native system on a fair, usage-scaled credit model.

Bridge the gap between sellers who understand angles but not tooling and 'GTMEs' who understand tooling but not selling by giving one strategy-fluent operator an easy-but-sophisticated execution system.

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.

Data silos are structural, not attitudinal: product and billing data sit with engineering or a data team, RevOps sits under go-to-market, and as long as they're distinct teams the data stays separated from the people who need it.

The data-team gatekeeper who deprioritizes RevOps requests as mundane while, in reality, those requests are the highest bottom-line-impact work at the company.

A 'data model' is a curated, reusable catalog of source fields you green-light (authorize) for syncing — built from a database table, a custom SQL query, or a spreadsheet — that anyone can then grab from to sync anywhere.

The single simplest usage field — the date a customer last logged in — predicts churn better than most sophisticated composite product signals.

Segment accounts by product engagement in the CRM and route the play accordingly: heavy users get an immediate upsell script, light users get an education pitch rather than a sales pitch.

A reframe that evaluates every data request by its revenue dimension — collections, overage monitoring, churn avoidance, or upsell — instead of by the data itself.

The practice of breaking cross-team silos by leading with curiosity about the other side's priorities — RevOps asking to be educated on the data team's world, and technical teams asking who's affected and why a request matters — in both directions.

A composite health metric combining the number of deals a rep works, the average deal size (ACV), the win rate, and the length of the sales cycle. Ebsta uses it to quantify the gap between top and average performers.

A seller who influences top of funnel, generates their own opportunities, and continues to own the relationship after the deal is signed — the opposite of the single-purpose-vehicle / hunter-farmer model where customers are handed from one specialist to the next.

A relationship-health score built from observable transactions — meetings, email traffic (inbound worth more than outbound), and call data (longer calls worth more) — deliberately excluding intent and sentiment analysis.

The difference between a firmographic, one-line ICP ('Series A–C startups') and a layered one that adds persona, buyer maturity, investors, and growth rate — and never confuses ICP with TAM.

Requiring every opportunity to carry written, scored qualification, with explicit gates and triggers to move from one stage to the next — and not allowing sellers to skip stages or self-score their own qualification.

The top-performer discipline of converting the fewest opportunities out of discovery on purpose — ruthlessly killing deals that won't close so time and resources flow to deals that will.

Model your target as current ARR + new ARR + expansion − churn/contraction. New ARR is new logos (and new contracts with existing customers); expansion and churn both come from the existing base.

Take the macro ARR goal and reverse-engineer it top-down through funnel metrics (net retention, SQL-to-close, sales cycle, MQL-to-SQL, average ACV) and bottom-up through the resources and team (CS capacity, quota/performance, ramp time, cost per SQL, salaries) required to hit it.

When executives challenge the outputs (reps, budget, pipeline required), don't defend the outputs — send them back to the inputs and ask which specific assumption they'd change: conversion rate, sales cycle, MQL-to-SQL, expected performance.

Because deals don't close the month a lead arrives, the length of the sales cycle dictates when pipeline must exist. A two-quarter cycle means the pipeline for Q3 bookings has to be built in Q1.

A rep is 'ramped' only when building pipeline and closing at full productivity — not when training ends. Ramp time should never be shorter than the sales cycle, which forces you to hire ahead of the number.

The board evaluates the plan not as a sum of initiatives but as unit economics balanced against growth, judging whether the company can graduate to the next funding stage. If it fails that test, the CEO and CFO reject it back to you.

Because you invest in SaaS before results arrive, unit economics degrade when you invest and improve as ROI lands. Plan a trend that grows into the economics the board wants — not a perfect green line every quarter.

Anchor and stress-test assumptions against VC/PE-published benchmarks (win rate by ARR band and deal size, quota-to-OTE ratios, funnel conversion rates) so the conversation becomes 'you vs. the market' instead of 'you vs. the person.'

Replace the static spreadsheet with scenario modeling for sensitivity analysis, live progress-to-target reporting, a core-vs-new-bets split, and a daily sales-tracker email that becomes the company's single source of truth.

There are no silver bullets. Compounding small, daily improvements — messaging, coverage, demos — is what drives real growth: 1% better every day is roughly 37x over a year, while 1% worse is a ~97% loss.

A founder raises capital only three to five times in a lifetime while an investor does it every single day — so the founder is structurally the amateur. Closing that gap with structure, data, and network intelligence is the mission.

Flowlie's positioning: a behind-the-scenes operating system for a raise — not a marketplace, broker, or middleman — that helps founders uncover the right investors and the right people in their own network to reach them.

The two pillars of Flowlie: a predictive fit-scoring model (version five) that ranks how likely a firm or partner is to be interested, and a network-analysis engine that maps warm-intro paths and ranks each with a 'path impact score.'

The core fundraising philosophy: the outcome is decided mostly by the preparation — target lists, investor updates, relationship-building, and warm-path lining-up — that happens before you ever say you're raising.

Deliberately forward-loading warm-intro requests — scheduling connectors to introduce you weeks out — so investor meetings cluster into a single window instead of trickling in one at a time.

A hiring filter that prioritizes innate curiosity and a demonstrated desire to learn over tool-specific experience or a pedigreed, linear resume. Hard skills on the go-to-market side can be taught; curiosity and teachability can't.

Define revenue and go-to-market operations by the actual work someone does, not by whether their job title said 'RevOps.' Many strong operators have the skills and experience under unrelated titles.

Hire for familiarity with the general tool landscape and a proven knack for learning new tools, rather than deep fluency in one platform — because the stack turns over constantly (~3 new MarTech tools a day).

A stage-specific set of interview questions that surface curiosity, resourcefulness, and problem-solving. Baseline: excitement about systems. Specialist: 'a time you used a tool in an unconventional way' + 'the last time you troubleshot an issue.' Manager: 'a RevOps project or tool you're curious about but haven't done.'

LeanScale's two hiring profiles — architects (strategic, engagement-facing) and systems engineers (technical system owners) — plus a live exercise for engineers: after baseline Salesforce/HubSpot certifications, build any go-to-market tool in Lovable or Bolt, time-boxed to a couple of hours.

A tooling discipline: before buying a new tool, ask whether the job can be done with what you already own. Weigh the full cost — operational overhead, cognitive load, and integration risk — not just the monthly fee.

Borrowing theater's 'notes' ritual — where the director publicly lists everyone's mistakes after a rehearsal — as a model for building the thick skin to say 'I don't know' and 'I got this wrong,' then fix it fast.

Because every public SaaS company answers to the same SEC rules, quote-to-cash should be a standardized, out-of-the-box process — not a uniquely engineered snowflake per company. A 'unique' process is a problem to fix, not a competitive advantage.

Instead of a separate CPQ, billing system, and revenue-recognition system integrated between CRM and ERP, run a single platform that handles CPQ, AR/billing, and ASC 606 rev rec — sitting between the CRM and the GL with no reconciliation and one product catalog.

An AI agent that lets any seller generate a compliant quote by typing a plain-English request into Slack (or mobile, email, or the CRM). The agent parses the request, asks for any missing policy-required inputs, applies product rules, and returns a quote PDF.

A business-focused Q&A layer that asks a seller simple questions (where is the customer located, what segment) and converts the answers into the right products, compliance, and discounting — instead of making the rep understand how the CPQ is configured.

Usage/consumption billing comes in distinct models: pure pay-as-you-go (no commitment, invoice on actual use), pre-committed plus overage (commit to a volume like 200,000 API calls/month, pay extra above it), and credit pools (buy a $100k pool and draw down across products, AWS/GCP-style).

A policy-driven method for turning variable consumption into a defensible ARR: for pay-as-you-go, take average consumption over a trailing 3-6 months and recognize a set percentage (e.g., 80%); for committed-plus-overage, the commitment is fixed ARR and overage recognition depends on how straight-line it is and what the auditor will accept (from ~95% down to ~20%).

When a customer adds licenses and renews early, you cancel the current term (crediting the unused period, like dropping a car lease) and restructure into a new term. Done right it's one opportunity, one order form, with credits and proration auto-calculated and reporting that shows it as upsell — not churn plus a new deal.

The design principle that the primary consumer of a CPQ should be the seller, not deal desk or RevOps. Reps should be able to run even complex deals (multi-year ramps, partner margins, special payment clauses) and the entire post-signature lifecycle themselves.

The seller creates an 'order' (draft during the sale cycle, confirmed once closed) and that same object generates the invoice and feeds finance. There's no separate quote-to-invoice re-keying, so numbers can't diverge between what sales sold and what finance bills.

A staged operating model for taking a company from nothing to a running revenue engine: first establish foundations and first principles, then instrument and stabilize, and only then layer in advanced and modern techniques (including AI) to sprint.

On joining, learn the existing systems by using and pushing them to their breaking point, then ship a working V0/V1 before soliciting input — collaborating afterward to fill in scope and context.

A CRM-based revenue-intelligence system resting on three pillars: (1) volume/activity — meeting depth and self-sourced pipeline; (2) accounts — tiering and account quality; and (3) accuracy/validation — clean, correctly-tagged data with automated backstops.

A single consolidated system — often an automated spreadsheet with 50-60 metric tiles rather than a visual 10-12-metric dashboard — organized in three levels: North Star KPIs (board/investor), functional KPIs (six to ten per team, in lockstep), and hyper-specific activity metrics.

Measure sales on the inverse of marketing's volume: only opportunities that pass a hard gate from discovery into 'prove value' count — deals genuinely closeable, and closeable within the quarter — and marketing's targets are pegged to that same gate.

Build custom, proprietary 'hubs' from scratch (e.g., in Replit) that solve a precise business problem and eradicate vendor spend; then transform their outputs into an agent-readable format (JSON) so agent 'spokes' (n8n, Manus, computer use) can run the downstream mission — with a human at the tail.

For any process, first ask whether AI can do the entire thing (path one: hardest but most efficient). If it can't be done cleanly, default to human-first with AI as augmentation (path two).

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.

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.

Attio's product philosophy: the CRM should adapt to how your organization already does business, not force you to change your process to fit the tool.

By syncing your inbox and calendar on signup, Attio auto-builds your network of companies and people, enriches it, and layers on last-touch, contact ownership, and relationship strength — with no separate tool.

A custom record attribute powered by an AI prompt: you write your ICP in plain language and Attio evaluates every inbound lead against it, flagging fit for the rep.

Five standard objects plus unlimited custom objects and attributes, including Workspaces and Users objects that pull product data in, so the schema mirrors your actual business.

An automated workflow that, on every new signup, uses a research agent to summarize and ICP-tag the company, then routes: enterprise to round-robin, non-ICP to self-serve, and ambiguous mid-market/startup leads to a Slack channel for a human to route via buttons.

Attio is both where customer data lands and where you take action on it — you can report on live data, drill into the underlying records, and immediately sequence, task, list, or route them without leaving the tool.

'Lean' should mean intentional, agile, right-sized structure for your stage — not the scrappy, disorganized, under-structured state most early teams actually describe when they say they're lean.

Import product engineering's agile operating system into RevOps — standups, definitions of done and ready, boards, user stories, QA and UAT stages — as the default way the team works.

A documented onboarding 'course' — tech stack, who-owns-what map, the agile working agreement, definitions of done and ready, systems, and roadmaps — that makes an incoming contractor or agency productive on day one.

Because RevOps has no fixed blueprint and fits differently into every company, assemble your function by borrowing proven patterns from more mature functions.

Divide the customer journey vertically into segments (four, from growth/brand marketing through sales, onboarding, CS, and support) and give each a product owner who obsesses over improving that stretch for customers, the company, and employees.

Dedicate a help-desk-and-comp role (backed by contractors) to absorb the daily end-user questions and recurring commission/quota cycles so developers and admins stay focused on the roadmap.

The recurring cycle where point tools proliferate around the CRM, category winners emerge and go vertical, the stack consolidates into a few big players — and then a new layer (now AI) fractures the ecosystem again.

Own the company growth model and go-to-market performance-to-plan — fully segmented, every way the business can be cut — as the source of strategic leverage that earns RevOps a seat in the room.

A short list of the company's top 'must-be-true' initiatives that the RevOps leader relentlessly surfaces cross-functionally — in every doc, roadmap, and prioritization call — to keep the whole organization aligned.

The career path out of the RevOps 'yes-too-much / no-too-much' trap: treat high-quality technical work as table stakes and win the next level on leadership — building a function that runs without you controlling every part of it.

Structure B2B support around the account as the centerpiece — its timeline, sentiment, history, and stakeholders — rather than around individual, disconnected tickets the way horizontal ticketing platforms do.

In B2B, AI's role is to assemble and surface the full context of an account — pre-sales data, call recordings, CRM history, previously-approved human answers — rather than to generate a single reply to a single question.

For technical, high-context B2B questions, AI should draft a documentation-grounded suggested response that a human reviews and sends — keeping a person in the loop instead of auto-replying.

Automatically convert existing Loom (and demo) videos into complete, screenshot-rich documentation, turning the thin, unowned docs AI draws from into high-quality source material — closing the data loop that makes AI answers good.

A workflow engine (triage, condition-based routing by time zone and ticket type) combined with AI-driven workflows (sentiment-based escalation, SLA-breach alerts) — the layer Tony argues actually constitutes a B2B support system.

Measure the business by revenue per full-time employee rather than by headcount hired or money raised. Top performers run $500K+ per head (versus an old $150–200K benchmark), driven by AI-leveraged operators.

Build marketing, brand, a reliable pipeline channel, and your own sales process before hiring a salesperson. Reps are harvesters of pipeline and closers — not creators of demand.

Land your first sales inside your existing network, then narrow to a hyper-specific micro-niche for whom the product is an absolute no-brainer, and make the economics the best deal of their lives early on.

In an AI-driven sea of sameness, brand generates demand. Aesthetics signal seriousness and a content strategy (written, tutorials, or podcasts) is the modern equivalent of commercials and billboards.

Start on HubSpot as an affordable, pre-built, scalable CRM; stand up Snowflake as the data warehouse for sales, product, and financial data; and report from there (e.g., Looker) rather than overloading the CRM.

Before buying any onboarding or CSP tooling, define exactly what first-time-to-value is for your product and sprint to reach it as fast as possible.

Let AI take work to roughly 90% and reserve the last mile for a human, so output sounds authentic and nothing goes out that doesn't resonate. The goal is producing better, not just producing more.

Treat go-to-market like health and fitness: track leading-indicator 'biomarkers' (onboarding speed, churn by segment, new-rep ramp, pipeline created, conversion) instead of reacting to lagging results after they break.

Each stage of growth — validation, product-market fit, product-channel fit, scale — is exponentially harder than the last, and you can lose product-market fit at every technology wave (on-prem to cloud, cloud to SaaS, SaaS to AI-native).

Design your offering as the thing you personally wished existed in your prior role, then scale the 'love' by hiring people better than yourself, guarding culture and integrity, and getting process and finances tight early.

RevOps is the business's family-clinic generalist — no single specialty, but a stream of problems from every function daily. Its job is to diagnose root causes by stepping into each function's shoes, not to treat the presenting symptom.

Take a reported symptom and break it into workflows and steps from first principles — for a conversion drop: lead source, count, region/quality, marketing activity, routing, scoring, and product pitch — then benchmark whether it's isolated (~20% of reps) or across the board.

Step 1: give the person comfort and let them talk (avoid seeding your bias). Step 2: validate the hypothesis quietly against the data in the background. Step 3: talk to other stakeholders of the platform, process, and functions to triangulate where the problem truly lies.

RevOps solutioning is a blend of people, process, and platform — never numbers alone. The revenue outcome can come through personal relationships, process, or systems, and usually a combination.

Four defenses that stop problems before they surface: (1) automation and AI to keep leaders out of low-value work, (2) learning and development so the team understands how the GTM machine fits together, (3) data hygiene with restrictive write-access to core systems, and (4) weekly/biweekly checks with real-time reports and fix-on-the-spot remediation.

A deliberate, agenda-less block of time spent exploring the data — the opportunity module, lead behavior, Slack signal — just to sense how the business is behaving, without a specific question to answer.

The two skills that carry a RevOps career: being a genuine people person who can build relationships with extroverted sellers and senior cross-functional leaders, and curiosity paired with a doer attitude — because the problems are new every day.

Prioritize RevOps work by identifying the few major 'pillars' or 'boulders' that create the biggest business impact for a given week, month, and quarter, and aligning them to the company roadmap and OKRs.

Most refusals aren't a hard no but a 'not yet or not now' — the request is acknowledged, logged into OKRs and weekly planning, and sequenced behind what the revenue-generating teams need right now.

An informal personal scale that rates each task by how easy or hard it is for you specifically to address, used alongside deadlines to decide what to work on and when.

Do the hardest, biggest task ('the frog') earliest in the day, so the rest of the day is easier to navigate.

The scoreboard isn't tasks completed but tasks completed that have purpose — work tied to a real company or RevOps priority.

Design departments and systems that run self-sufficiently without you — reducing your role to maintenance — so the business survives your absence.

Stand up a good-or-great process quickly and iterate on it, rather than trying to architect a perfect one up front.

Effective RevOps leadership requires all three at once: having strong opinions, voicing them, and having good opinions backed by data and field experience.

Direct disagreement at the plan and the best direction for the organization, never at the individual — because you're all on the same team.

Treat initiatives as calculated risks with an explicit hypothesis, a plan B/C, and a shared understanding of the odds — so a failed experiment that proves something still counts as a win.

RevOps is the kingmaker, not the king: the person who sees the entire big picture and moves everything forward through influence, without ever making the final decision or owning a department outright — regardless of whether they report to a CRO, CFO, or CEO.

Build trust with the executive you report to by knowing the entire business — every team, not just your function — better than they do, so that when they raise something you're already on the same page instead of catching up.

A daily operator ritual: wake up and scan a set of dashboards the way a fan checks their sports team — is anything broken in Salesforce, is pipeline building as expected, which reps are up or down — paired with a heavy cadence of one-on-ones.

Decide whether you're a very-early-morning worker or a late-night worker and commit to it, because the best, needle-moving work happens in an uninterrupted 'power hour' — not in the middle of a day full of meetings, Slack, email, and context-switching.

During business hours the operator is like a firefighter at the station — present and unpreoccupied because anything can happen — and does deep work outside that window. It's effectively an on-call role without necessarily being more stressful.

Rather than trailing a single executive from company to company, build a reputation within one or two industries where professionals and executives talk to each other, generating better referrals than personal loyalty ever could.

Treat your RevOps seat the way you'd treat a company: an inception phase where you build process, a growth phase where you scale it, and a deliberate exit strategy for growing out of the role toward the next level.

When asked something you can't answer, never say 'I don't know' or signal indifference; always respond 'let me look into it' and ask what resources might help — staying the approachable, curious person who will find the answer.

Build a private company's systems, data, and controls to a post-IPO enterprise standard before any event — so a pre-IPO startup already operates the way a public company must.

The three questions the IPO process forces a revenue org to answer over and over: Can we evidence for this? Are we SOX compliant? What is our system of record?

Move quoting, discounting, approvals, signatures, and revenue recognition from a manual, cross-team process into a formal, controlled CPQ engine (e.g., Salesforce CPQ) with product and discounting rules.

A way to slice a growing RevOps team into its core components: systems and tooling, enablement, compensation/commission, and data.

A documented, evidenced process for changing your systems of record: make changes in sandbox before production, log who deployed what and when, then sample and pressure-test those changes against the system on a recurring cadence.

Evaluate current-state process as if a skeptical outsider had just walked in and must independently verify it — at a tactical level: how would they know what changed, where would they look, and how would they trust it's accurate?

Sales velocity = (number of deals x average deal value x win rate) / time to close, expressed as a normalized dollars-per-day contribution per seller. The velocity delta is the multiple separating top performers from B/C players (11x in the 2025 report).

A view of the revenue motion where the left side is acquisition (lead to close) and the right side is post-sale retention and expansion. The insight: the right side must be multi-threaded and instrumented as deliberately as the left.

Compare the average number of days a deal spends in a stage when it wins versus when it loses. Once a deal exceeds ~14 days in a stage, win rate drops sharply; by four weeks it falls to about 5%.

Top performers close off roughly 30% of opportunities at the discovery stage, refusing to advance deals that were never properly qualified on budget, stakeholders, timeline, mutual close plan, and security/legal review.

Quantify what top performers do (e.g., six engaged stakeholders and a finance persona above a set engagement score by stage two), visualize it simply, and enforce those benchmarks as gates a deal must clear and triggers that prompt sellers and managers inside the CRM opportunity record.

A machine that connects to email, calendar, and phone systems to reconstruct every customer relationship, create and maintain CRM contacts, score engagement out of 100 (with trend and relationship-owner), and write it all back to Salesforce automatically.

Sum, across all possible outcomes, of each outcome's probability times its value: EV = P(outcome1) x V(outcome1) + P(outcome2) x V(outcome2) + ... . A positive EV is a good bet; a negative EV is a bad one.

From Annie Duke's book: judge choices by the quality of the bet given what you knew, not by whether the single outcome was good or bad. A good decision can lose and a bad decision can win.

A core value of Spencer's company: constant, incremental self-improvement — applied here to decision-making, by reviewing whether a choice had positive expected value regardless of how it turned out.

The ratio of the amount you must call to the total pot you stand to win, expressed as the minimum win probability that justifies calling. Call $100 into a pot that becomes $400 and you have 25% pot odds.

Model each go-to-market segment as a bet: win rate (probability) times ACV (value) gives per-deal EV; then layer in deal volume, fully-loaded rep cost, and marketing cost to get the true expected value of investing in that segment.

A calculated field in Salesforce or HubSpot — built from custom properties and workflows — that outputs how much a given account or open deal is 'worth' by expected value, so reps can filter to the highest-EV deals.

Build territories and quotas from expected value — TAM and account valuation weighted by expected conversion rate — rather than gross dollar value.

The replacement for servant leadership: lead from the front, believe no job is too small, and do the high-context work yourself instead of managing away from it.

A lens (adapted from Ben Horowitz's peacetime/wartime CEO) that treats the last 12 zero-interest-rate years as peacetime — stable, predictable, growth-at-all-costs — and today as wartime, defined by speed, precision, and survival.

A change-management ritual: every team member keeps a Post-it on their main screen that reads 'How can AI help me do what I'm about to do?' — retraining individual behavior before restructuring the org.

The missing middle between micromanaging and absentee leadership (credited to Rippling COO Ian McInnis): get close to a work stream to build context and coach, then step back and grant autonomy once you see consistency.

Michael's operating equation for trust: consistency over time equals trust. You earn the right to grant autonomy by observing consistent delivery, not by title or tenure.

Jim Collins's Good to Great bus metaphor (get the right people on the bus, in the right seats), extended with Michael's addition: you must design the seats themselves — the actual jobs — not just fill them.

A mentor's rule that a new leader has roughly 100–120 days to make their people and structure decisions; after that window, the team's output is the leader's own fault or benefit.

Taste is the human judgment to know whether AI's output is actually good. AI takes prompts and shows you a thing; determining if that thing is good is a nuance and sophistication AI doesn't have.

A model for what to outsource: well-defined work is a neatly wrapped present you can hand to an agency (or junior talent); ambiguous, high-context work is a plate of spaghetti where the noodles are snakes and you need the plate back.

Career market fit is the idea that the market may see your value more clearly than you see it yourself (Michael leads go-to-market but the market thinks of him as a marketer). Paired with it: know the neighborhood you're heading toward, not the exact destination, and take any avenue pointed that way.

A three-layer operating system: quarterly OKRs with an above/below-the-line priority cut and built-in slack time; two-week to-do/doing/done sprints with a Monday plan, Friday check-in, Thursday review + retro, and a Friday 20% block; and a monthly company-wide all-hands to prove what shipped.

A phrase from Rita McGrath's Seeing Around Corners: those closest to the work make the best, fastest decisions, while decisions made far from the work are colder and slower.

The time it takes a new user to 'get it' after logging in — a core PLG success metric Ocean actively drives down by putting the product's aha moment directly on the landing page.

Vectorize both companies (65M) and LinkedIn profiles (230M), then combine them in one search: input an example person's LinkedIn handle and find lookalike people, by role and context, inside the lookalike companies of a target account.

Target by a contextual understanding of what an individual actually does for a company, not by their title — because titles vary with company size (CMO vs. head of growth vs. VP marketing) for the same real role.

Build, filter, and preview the target list in Ocean without spending a single credit; export to Clay for enrichment only once the list is validated.

Gen 1 is an LLM wrapper around an analog/non-normalized database — a pretty face on messy data with broad, imperfect targeting. Gen 2 models the actual GTM process and automates the flow end-to-end, with human validation between steps.

Automation's real strength is micro-targeting: overlay intent and third-party data on a tightly defined audience so every message is highly relevant, producing 5–10% conversion instead of 0.1%.

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.

The core BCG method: read a broad problem statement closely to extract its keywords and clues, branch into a small set of hypotheses using judgment and calculated guesses, then validate or nullify each with data, experiments, and conversations — under real time and resource constraints.

Treat the stated problem as a symptom. Bring the right functional owners into the room, go deliberately broad first, and pull several years of historical data so the true root cause reveals itself layer by layer before you narrow.

Before analyzing, classify the work as either a backward-looking diagnostic (what went wrong?) or a forward-looking strategy question (how do we grow or break into a new segment?). The mode changes which hypotheses you form and how much value the analysis returns.

A small-and-mighty RevOps team protects strategic bandwidth by interrogating every meeting invite, pushing back on low-value asks, leaning on leadership for air cover, and delegating only when it serves the team — freeing time (and AI-reclaimed minutes) for deep thinking.

There are seasons to accelerate the business and seasons to maintain — to hold the speed limit rather than push the gas. Sustainable performance requires knowing when to brake, because it's genuinely hard to stand still and all-gas/no-brakes leads to disaster.

GTM Fund's early-stage evaluation model. The wave is the macro trend / 'why now' (falling AI costs, regulatory tailwinds, distribution shifts); the surfer is the founder's skill, vision, and tenacity; the surfboard is the product — important but the most flexible because it evolves.

A deep, non-obvious insight into a problem space that gives a founder an unfair advantage. It comes from either lived experience (having operated in the space and felt the pain intimately) or obsession (diving so deep into the problem you discover truths others miss).

A way to read early traction that ignores headline revenue in favor of predictive signals: concentrated, evangelical customers; enterprise validation; founder-led sales; usage depth and retention; and shipping velocity. The real question is never 'how much revenue?' but 'does this traction predict you'll find product-market fit?'

Fundraising is go-to-market pointed at investors. How a founder runs the raise — target lists, warm intros, tailored pitches, a disciplined intro-to-close funnel — is treated as direct evidence of how they'll run sales, partnerships, and customer acquisition.

Sophie's personal method for finding fulfilling work: reflect on what you keep returning to with curiosity and what consistently energizes you, write it down, look for patterns, and identify the two or three core forces (a 'triangle') that keep pulling you back. Aim for a role at the center of all of them.

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.

Instead of sending from a massive shared server (a shared IP pool) full of thousands of unvetted senders, give each user an isolated mini-server ('cluster') with its own IP address so one sender's behavior can't affect the others.

Regularly send emails from a customer's mailboxes to known reference mailboxes to observe where they actually land — inbox, spam, promotions, or undelivered — as the true indicator of email infrastructure health.

Simulate natural, two-way activity across real corporate mailboxes to balance the unnaturally low response rates of cold outreach, so email service providers don't flag the account.

Cap daily send volume per mailbox to what platforms now tolerate (15–25/day, down from hundreds), have the platform control the cap rather than the rep, and scale volume only after messaging is validated on a small sample.

Treat cold outreach like a paid-ad platform: give the system many message variations, test each against a small subset of the audience, and scale only the versions that generate positive engagement.

Use reinforcement learning — a distinct branch of AI from LLMs — as the optimization layer that looks at what has and hasn't performed to predict which hooks, lead magnets, and offers will resonate, and recommends new variations over time.

Blend autonomous AI (which ingests large data sources) with human review checkpoints — a sales rep reviews certain AI-generated copy before it reaches a prospect, and an admin reviews certain content before it reaches the rep.

The consistent core set of capabilities the market keeps asking to have in one place: sales engagement (cadences and sequences), conversation intelligence, data and enrichment, and predictable forecasting.

Bernardo's three equally-likely scenarios for these platforms: (1) consolidation and rebranding succeed into specialized all-in-one platforms; (2) vendors can't escape their legacy branding and stay boxed into what they were known for; (3) a platform becomes the ecosystem — builds a CRM and takes on Salesforce and HubSpot directly.

A re-evaluation discipline: dust off a structured scorecard and grade every vendor across its full, current feature set — not just its original category — and refresh it far more often than quarterly or annually.

The core buyer decision: assemble best-in-class point solutions for each category, or align the whole go-to-market operation on a single consolidated platform. As tools commoditize, the pull is toward picking one 'pony,' driven by cost, bundling economics, and current negotiating leverage.

A minimal scorecard for any partnerships team: (1) production to goal — pipeline sourced and revenue won, segmented by partner; (2) cost-to-carry ratio — fixed overhead plus variable cost per partner; and (3) cannibalization rate — direct deals that moved to a partner channel and what that cost.

Set production goals both overall and segmented by partner, and match the goal type to the partner type: a channel reseller carries a closed-won production number, while a referral partner (or one that risks cannibalization) carries a sales-qualified-lead goal for leads handed to the sales team.

The cost of running the partnerships motion, broken into operational overhead you can't easily influence and the variable cost per partner — events, sales, marketing, and partner-manager resources — that you can, expressed against the production that spend generates.

The share of deals that would likely have closed direct but moved to a partner channel — tracked by counting opportunities already registered in the direct channel that shifted to a partner, and the discount or referral fee paid to do so.

The cross-functional plan RevOps builds and owns, tying sales, marketing, customer success, and partnerships to one set of goals — and the first thing you measure RevOps against by asking whether the teams are actually achieving it.

A structured feedback loop that treats the departments and individual contributors RevOps serves as its customers: weekly one-on-ones with functional leaders, an IC 'champion' for day-to-day signal, and a formal RevOps satisfaction survey sent to everyone served.

The data-driven half of measuring RevOps: every operational initiative should show up as improving funnel metrics — rising conversion rates (e.g., SQL to closed-won) and falling cycle times — as a direct correlation to the work completed.

The idea that small adjustments to conversion-rate or cycle-time assumptions in a capacity plan or growth model compound into outsized, exponential gains as the business scales.

A defensive dimension of the RevOps scorecard that measures the issues the team prevents — for example, how many days you've gone without a serious priority-zero tech-stack incident or a serious data error in a board meeting.

Measuring RevOps's tactical and operational projects on budget and expected completion time — staying under budget and on schedule for work like a CRM implementation or a new set of board/offsite metrics.

Treat gross revenue retention and net revenue retention as a single paired metric. NRR sums churn, contraction, and expansion; GRR strips out expansion to isolate how much of the starting book remains. Reading only one lets expansion mask underlying churn.

Pick your health-scoring method based on your motion. High-touch, low-account-count books use sentiment-based human judgment (green/yellow/red from the CSM who lives the account). Low-touch, high-volume books use systematic signals (utilization, penetration, login/usage drops).

Capture customer sentiment through two surveys. NPS measures likelihood to refer — a directional proxy for renewal. CSAT measures satisfaction, read through specific engagements, journey milestones, or the overall relationship. Survey on the right cadence, across a representative cross-section, without pestering.

Marketing carries a quota of sales-qualified leads and created pipeline, set jointly with sales and interlocked with the bookings and revenue plan on both volume and timing, then tracked per channel.

Judge every marketing channel by concrete dollar efficiency — cost to create an SQL and cost to create a closed-won deal — alongside the differences in deal size, conversion rate, and sales cycle by channel.

A 2x2 visualization that matrixes two channel metrics — most usefully conversion rate against production (volume) — to gauge the efficiency of each lead source and rank high- versus low-performers.

Coverage of pipeline to quota where each deal is discounted by a stage-based probability weight (ideally drawn from your own historical closed-won rates) plus a deal-health or subjective adjustment for finish-line risk.

The rate at which sales-qualified opportunities become closed-won, calculated only on closed deals (never open ones) and segmented by product, business unit, region, and firmographic segment.

Systematic review of why deals are won and lost, using close reasons that are relevant and actionable, then hunting for overall trends and anomalies that fail a common-sense check.

The defining skill of a great RevOps leader: stepping in to get tactical for a specific business outcome when needed, then expanding back out to the overall strategy — while prioritizing the big-picture work.

The VP of RevOps is the cross-functional glue — a conductor who plays no single instrument but keeps sales, marketing, CS, partnerships, finance, and product aligned and producing one coherent strategy.

The VP of RevOps' single most important deliverable: a data-driven go-to-market operating plan — goals, assumptions, capacity planning — that is then monitored against actuals through the quarter and year.

A nested rhythm: annual planning; monthly plan/forecast tracking and internal board dry runs; weekly 1:1s with every functional leader; and a daily 'morning coffee dashboard.'

A blunt litmus test for the role: if you are not leading (not merely attending) the annual planning process and not in the board room, you're operating at a director level, not VP.

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.

A maturity model for the function. RevOps 1.0 is the tactical, reactive service center — implementing the tech stack, formatting sales calls, planning territories, comp plans, and CS playbooks, and managing requests. RevOps 2.0 is an internal management consultant that participates in corporate planning, sits shoulder-to-shoulder with finance on the board plan, and leads with insights and recommendations.

A planning discipline in which the analyses behind each metric, the plan assumptions themselves, and actual performance against those assumptions are all kept visible and updated in real time — rather than being computed once for the annual plan and filed away until the next board meeting.

The set of five or six drivers a well-built revenue waterfall contains — normalized prospect volume, sales cycle, time-based conversion distributions, close-won production, SQLs and MQLs — that you should have a pulse on at all times and be able to segment 20–30 ways (enterprise vs. SMB, region, product line, service center).

A five-part checklist for a trustworthy CRM: (1) enable field history tracking, (2) timestamp critical stage and status changes with custom fields, (3) freeze closed-won data, (4) flow lead data into every object on conversion, and (5) put validation rules in place.

Turning on Salesforce field history tracking to record how data evolves over time, providing an audit trail for diagnosing issues and a historical snapshot for admins, users, and downstream tools.

Dedicated custom fields that capture the date each important status or stage changed — lead status, lead lifecycle stage, opportunity stage, customer stage, or proof-of-concept stage — so change data is directly reportable.

Locking closed opportunity data so it can't be edited after the deal closes — restricting changes to a super admin and reinforcing it with validation rules, automation, and weekly backups.

Ensuring that when a lead converts, its important fields — lead source, lead source detail, owner/SDR, and lifecycle timestamps — carry across to the account, contact, and opportunity records.

Rules that block records from saving unless they meet your business process — from simple checks (required amount, no past close dates) to methodology-driven requirements that ask for the right data at each stage.

The single element of value that is most strongly connected to your brand — unique and special to you. Tom also calls it your superpower, and cites data that it can represent as much as 70% of perceived value.

A triangle whose three sides are the ways humans subconsciously perceive value: functional, emotional, and economic. In any value exchange the brain stacks one element as primary — up to ~70% of the perception.

Products are tools that help customers get jobs done. Whether a customer acquires a tool depends on the job they're trying to do and how functional or emotional that job is.

A maxim Tom credits to Kellogg's MBA program: the primary job of a marketer is to lower the cost of customer thinking. Adding feature on feature or benefit on benefit dilutes rather than compounds perceived value.

Tom's metaphor for RevOps: the 'plumbing' is instrumenting, maintaining, running, extracting, and visualizing the data; the 'poetry' is interpreting that data into a performance narrative. The combination is the value.

The main lenses for cutting a sales team's territories: (1) geographic — international/domestic regions, time zones, states; (2) product or service specialization; (3) industry/vertical; (4) firmographic tier — enterprise / mid-market / SMB; and (5) a fair round-robin or named-accounts approach when the others don't apply.

Balancing territories is not only a morale-and-attrition safeguard; it's a pure-business lever. Equalize a strong territory and a weak one and, in aggregate, the same sales headcount produces more revenue.

Design territories from evidence: mine historical SQLs and closed-won deals sliced by each segmentation bucket, backfill any data you failed to capture, and gather feedback from reps, product, and marketing before drawing the lines.

Roll new territories out at natural calendar breaks (a new quarter or month) and define explicit holdover criteria governing which prospects a rep can keep working after the reshuffle.

Anthony's go-to sequence for a typical B2B SaaS company: start firmographic (enterprise vs. SMB motions need different sellers), then geographic by time zone (buyer availability), then product or industry only if they genuinely differ, and fill the rest with round-robin or named accounts inside bigger buckets.

The most fundamental aspect of any business: an entity capable of creating a value exchange event. Until value is exchanged, an organization — however well-funded or well-intentioned — is not yet really a business.

The idea that winning in business — high performance that is predictable, repeatable, and inspires investor and board confidence — can be codified into a framework and 'bought' like any other service, rather than left to luck.

An operator who masters the science of value exchange and imprints a predictable, repeatable operating framework onto a business — calling, and hitting, their shots rather than making it up as they go.

The failure mode where a company diligently executes a systematically flawed system — practicing a bad golf swing. You may improve incrementally, but you only ingrain bad habits and will invariably 'hit the wall.'

Misleading data comes in two forms: the deliberately or maliciously wrong (rare in business), and the unintentional kind, where someone tried to convey something reasonable but introduced biases in how they approached it.

A chart crime is a visualization designed to evoke a certain emotion — most often by manipulating the axes (a truncated y-axis, mismatched scales) so real data tells a dramatically different story than it should.

Anthony's closing checklist for reading any chart honestly: (1) look for cherry-picking and get a holistic view, (2) inspect the axes for alignment and scale, (3) widen the time series, and (4) layer in real business context tied to operating plans and outcomes.

Forecasting too high pushes you to over-invest ahead of actuals; forecasting too low leads you to over-promise to the market and under-build the infrastructure to support the customers you win. Both directions carry catastrophic downside.

A forecasting philosophy that treats the forecast as an iterative pursuit of directional accuracy rather than penny-perfect precision — each cycle you layer on new information and methodologies to get one step closer to reality.

The three deal milestones that most reliably indicate forecast health: (1) entering the pipeline after real pre-qualification (confirmed intent and budget), (2) proposal/negotiation once commercials are being discussed, and (3) legal or executive approval once the deal leaves the champion for compliance and sign-off.

Name every pipeline stage after the action that has been completed — 'Negotiation Completed,' 'Proposal Sent,' 'Marketing Qualified Lead' — rather than an ambiguous noun like 'Negotiation' or 'Proposal,' so an opportunity's exact position is never in doubt.

Break the pipeline into meaningful segments — deal size/tier (enterprise, mid-market, SMB), geography, product/use case, industry — and measure conversion rates and sales cycle within each segment instead of using one blended rate for the whole business.

Don't layer forecasting technology — including AI forecasting tools — until the underlying process (stages, entry/exit criteria, segmentation) is ready. Once the foundation is set, tooling can enhance accuracy; before that, it just automates a broken input.

Use ChatGPT as the technical collaborator you turn to when a human peer is unavailable — paste a broken formula or a stuck problem and get an immediate diagnosis and a testable fix.

Describe a Salesforce business rule in ordinary human language and let ChatGPT translate it into the validation rule or formula, then review the output for business context before saving.

Paste an existing, complex formula and ask ChatGPT 'what does this formula do?' to get a plain-English explanation you can understand and pass on to others.

A mental model for reacting to disruptive technology: history doesn't repeat but it rhymes, and past waves (like email) augmented and grew work rather than eliminating it.

Marketing plays basketball and sales plays football — two different games with two different scoreboards. Alignment means first getting both teams to play the same sport, then to keep the same scoreboard, so they run in the same direction.

Clearly define your go-to-market lifecycle — the CRM stages from awareness through closed-won — as the foundation for how points are calculated in the game. It's an ongoing tuning exercise, not a one-time setup.

For high-velocity businesses with ~30–60 day sales cycles, tie marketing's measurement to bookings and closed-won deals — the golden stage the whole company drives toward.

For long enterprise cycles (12–18 months) with no shot clock, credit marketing with 'assists' — created pipeline and sales-qualified leads — rather than closed-won, and treat MQLs as leading indicators.

The idea that customer success is the 'front porch' of a business — the surface the customer sees, hears, and feels on a daily basis outside the product — the same way college athletics is the front porch of a university.

The reframe that a company's existing customer base is a 'farm' for growth — a renewable source of expansion revenue, referrals, case studies, and product feedback — rather than a static account you simply try not to lose.

Positioning customer success as the connective tissue between the revenue organization and the product organization — the frontline team best equipped to translate daily customer problems into what product should build next.

An informed estimate of what a usage-based deal will be worth over its first 12 months (or a chosen period), assigned even when zero dollars are contractually committed, so the deal can be reported, forecast, and managed.

A closed-loop discipline of tracking each deal's real consumption against its assigned expected value — daily, monthly, or otherwise, but at least through the first year — to see where estimates over- or under-called.

A method for estimating expected value that starts from a data baseline — usage trends of similar companies and of a customer's first three, six, and nine months — then layers in rep discovery, safeguards, and discounts to land a defensible number.

The anti-pattern of forcing usage into a committed contract by discounting the per-unit price — e.g., committing 25% of expected volume for a 10% price cut — to buy reporting predictability.

Three lenses on crediting a deal: first-touch credits the initial engagement (often an ad or third-party/aggregator site), last-touch credits the final interaction (the dealership conversation that closed it), and multi-touch tries to credit every influencing step in between.

The problem of distributing credit across many touches. You can 'peanut butter spread' it evenly across lead sources, or build a weighting mechanism that assigns more credit to the touches that mattered most.

A staged approach for teams new to attribution: get first-touch and last-touch tracking in place, add detailed campaign data and campaign-influence ('influenced by') reporting in the CRM, and only then reach for a fully weighted model.