The Three Whys
A simplified qualification framework of three open-ended questions: why buy anything, why now, and why this vendor.
Sales leadership is the craft of building, coaching, and scaling revenue teams. A recurring theme across the podcast: the best CROs often don't come from a pure sales background, leaders win on trust and operating rigor, and AI changes the tooling but not the fundamentals of leading humans.
Great sales leaders are defined less by personal selling ability than by their capacity to build repeatable systems, coach teams, and earn trust across the organization. Many of the strongest CROs come from operations, marketing, or cross-functional backgrounds rather than pure sales, because modern go-to-market leadership is about orchestrating an entire revenue engine — process, data, enablement, and people — not just closing deals.
How LeanScale runs delivery where Sales Leadership is involved.
Territory design is unusual: almost all the work lands in Blueprint. If you do that part right you can one-shot the whole plan and get a green light i…
A board deck that holds up follows a fixed structure: executive summary, financial performance, strategic goals, company operations, risks and opportu…
Dashboards fail when one view tries to serve everyone. The working pattern is a separate dashboard per audience — CEO, executive team, sales, marketin…
The period after a raise is when Go-to-Market debt becomes expensive. The work is to convert new capital into a revised growth model and the operating…
A sales commission plan is where the growth model meets individual behavior. It should pay for the outcomes the plan depends on, stay simple enough fo…
A simplified qualification framework of three open-ended questions: why buy anything, why now, and why this vendor.
An experienced sales leader joining an early company starts in the SDR seat, feeds the founder meetings, watches how the founder closes, then closes, then hires behind themselves.
Run two outbound clocks at once: a long-term play that gets buyers into your network to see your content over time, and short-term manual touches to get in front of them now.
Treat revenue as a failing statistic and capture structured reasons and requested features for every lost deal, so the losses can be retargeted once the product or timing changes.
To get a founder past founder-led sales, lay out two concrete options with their outcomes and risks, say which you lean toward and why, and let the founder choose.
The revenue leader pushes the rock uphill while the CEO works on product, budget and engineering so that the rock itself gets smaller.
A process that took you from zero to one should be tested for how far it bends. Past that point, reinforce and extend it like an old building being remodeled, or start from scratch.
Past $5M, calculate the ACV each segment needs, how long it takes to close and the payback on seller, ad and SDR spend, and route anything under the floor away from a human.
When competitors catch up on product, differentiation comes from a brand built on named people, each with a recognizable lane, rather than on the company logo.
Founder content should mix expertise with why the founder is in the space, what they have lived through and what motivates them, chosen to resonate with the buyer being targeted.
Applying AI to make an existing process faster instead of redesigning the systems, job descriptions and ways of working around it.
Redesign the SDR role so reps are trained to connect emotionally and look different from the AI buyers encounter, rather than doing the same job louder.
Point AI at understanding the industry and the person you are reaching, and keep the outreach itself human.
A loop in which candidates use AI to apply at volume, recruiters use AI and ATS tools to screen that volume, and the AI favors AI-written resumes, forcing every candidate to use AI.
The cycle that over-applied efficiency creates in hiring: poor-fit candidates get placed, fail, and return to the job market, with both sides losing time and money.
Evaluate candidates on a variety of signals that demonstrate skill rather than relying on the self-reported resume.
Give a candidate a scenario and have them solve it in front of you, with AI allowed, so you can observe how they think rather than grade a finished asset.
By the time a buyer arrives as an inbound lead, they have done their research and decided, so influence has to start well before the funnel.
A leadership balance that holds people accountable with clear expectations while creating an environment where they want to make you proud, instead of relying on fear.
A survey run at the beginning of each quarter that asks sellers how confident they are on what enablement rolled out, creating a leading measure enablement can influence and connect to revenue results.
People need to be hit seven ways with seven different messages before something sinks in.
Managers should never be surprised by what enablement is rolling out, because that is something enablement can control.
Standing meetings and communication channels that happen on a known cadence, so reps and managers know why they are showing up and what they will take away.
Slot an ad hoc enablement need into an existing ritual and frame it under a common theme so people see the why and what's in it for them.
Have a sales process that is both written down and taught, so the team produces more predictable outcomes.
The behaviors, outcomes and activity that have to happen at each stage, drawn from the signals that move deals to the next stage the quickest.
Forums that bring managers together to talk through the management framework in practice and learn from each other.
Agents and alerts in a manager's daily flow that flag the specific coaching opportunity for a rep.
Capture a leading metric enablement can change and correlate it with the revenue outcomes leadership wants.
Translate enablement into plan math: a small change in yield on the same pipeline has a large revenue effect, in both directions.
Measure how often the same or similar questions appear in internal channels, before and after a training.
Track how long a new rep takes to reach a fourth or fifth deal to see whether they are creating momentum, rather than stopping at time to first deal.
Build onboarding around the stages of the sales process rather than a sequence of content, so a rep can recall what to do at each point in a deal.
Replace "how do we get there?" with "what needs to be true for this to happen?", list every condition without limiting yourself to current resources, then decide which are worth pursuing.
Take the target as given, spell out what it would require, and move the debate to the inputs rather than the outcome.
If a revenue leader is spending too much time learning infrastructure or how to do the RevOps job, it is time to bring someone in, and probably past time.
RevOps keeps its mission of giving the go-to-market organization leverage, but builds the technical infrastructure and guardrails that let others build, rather than building the castle for everyone to look at.
A CRO needs to be able to carry a number and build the systems behind it, and financial literacy rounds out the role.
Study one line of the company's financial model each day: its benchmarks, what good looks like, what great looks like, and where your own number sits.
Endurance, one of the Marine Corps leadership traits in the JJ DID TIE BUCKLE acronym, is underrated in growth roles and depends on being on a mission you never question.
The framing Nick attributes to an Altos Ventures article: the firm invests in hedgehogs, long-term people about the mission rather than about just chasing an outcome.
Evaluate a business within a fixed window, then give executives three distinct paths rather than one recommendation: invest and bring in growth leaders, take it private with private equity, or sell to named acquirers.
When a competitor's brand is too strong to beat head-on, concede the business it is known for and take a larger adjacent pool of spend.
Instead of winning thousands of logos individually, integrate into a handful of key software platforms in the right industries, where you aren't competing against name brands, so each partnership reaches many potential customers.
Evaluate pipeline coverage separately for SMB, mid-market and enterprise, and read it alongside each segment's conversion rate rather than in aggregate.
Know how much pipeline is in each stage and each stage's conversion rate, then ask why deals fail between specific stages, using MEDDPICC gaps to find the cause.
Anthony's metaphor: investing in go-to-market without telemetry is like spending tens of millions on mining equipment with no idea what the machines are yielding.
After a raise, a company hires salespeople to replace founder-led selling, the founder's process fails to replicate, conversion falls, and the founder returns to selling to hit the committed number.
When the plan is out of reach, tell the CEO and board why you are in this spot and what happens if nothing changes, then lay out scenarios supported by historical data.
If you had to leave a sales presentation for an emergency, the colleague beside you should be able to run it just as you would, because the message is the same.
Choose where you work by who you get to sell to, not by which product is hottest, because the buyer is who you will spend eight to ten hours a day with.
Before you can hire the team, decide what the team will look like, and collect today the data you will need to route and forecast for it.
Whoever sets the pricing and positioning for a flagship launch should sell it first, starting with existing customers, before rolling it out to the sales org.
When an executive joins a sale, the AE owns discovery and the executive takes the presentation and pricing, then the roles shift over time.
Include AI in every package and differentiate tiers by feature versions, available models and the rate card for tokens, with token top-ups on top.
Assess AI margin across the whole customer distribution of heavy, middle and light token users instead of looking only at those who use everything.
Hire the leader for a new motion, then have them do the individual work personally until it is proven, before building the team around them.
Pair a rep who is weak in one part of the sale with the colleague who is strongest at it, so both sides improve.
Go-to-market AI can come from leadership-designed infrastructure or from reps experimenting on their own, and Triple Whale has tried a little of both.
Basic personalization no longer works, so outbound has to go far beyond it with research-driven gifts, in-person events and tailored artifacts.
The most important thing in sales is hitting numbers. The second most important is being right about whether you will or won't.
Give each go-to-market function a different focus mandate: sales narrows on closing, CS expands across clients and products, and solutions sits in the middle.
When a high-energy setting wears you down, decide on a character, which is yourself, and play that character rather than asking what you would do.
Before any interview or important conversation, decide on three things you want to get across, and for every question find a way to bridge back to one of them.
With no SDR team, the revenue leader commits to being the team's best SDR, with leader-generated leads ideally covering half of each rep's number and the rep responsible for the rest.
AI can do research and help edit, but the story and the ultimate decision should be made by a person.
Use AI where the work is bounded by fixed functionality and packaged products, and keep the link between the solution and the client's business with the person who knows the client.
Keep process out of a small company until you can no longer avoid it, because speed is the main advantage a small company has over a large one.
No formal deal desk at or under roughly $20M ARR, a light email-based review around $50M, and forms and documentation as more approval layers appear.
Reps get a BDR after consistently booking a set number of meetings themselves, not as a prerequisite for booking them.
Allocate additional resources to proven performers, and coach up or coach out the rest.
A commission curve steep enough that top performers can't afford to leave and low performers can't afford to stay.
Evaluate reps against the team's average production as well as against quota, and let a tiered plan push that average up over time.
Accept a semi-improvised CRM early on, but go back and fix it while it is young rather than after years of growth.
Choose your first operations hire based on how strong finance already is.
Set up prospects on trial exactly like paying customers, tell them so, and invite them to test your support as well as your product.
Walk away from deals where matching a lower price destroys margin, provided you have differentiation and an objective way to show performance and ROI.
Leave fixed price increases out of the contract and set renewal price according to how much value each customer got.
Run the company on one durable rule, earning more than you spend and treating it like a real business, instead of whichever venture metric is in fashion.
Go-to-market is a math equation with fixed laws: know your inputs, outputs and conversions. But no go-to-market tactic overcomes a bad product, and the CRO owns retention as well as new revenue.
Define a future state that has nothing to do with your product, orient all messaging around helping the buyer reach it, and present the product last as the only way there.
Find a niche inside your vertical where buyers share events, consultants and technology, and surround a couple of hundred logos through partners, community and fit-for-purpose product.
Every partner has a motivation, but it may not fit a programmatic tier-and-incentive model. Find the 20% of partners who produce 80% of the output, learn what a win looks like for each, and deliver it.
Once partners have referred enough business, the partnership becomes a retention and expansion channel, and partner-managed customers need an excellent support and enablement experience.
Let high-agency people take on the next large problem, and when they solve it, put them in charge of it.
Treat every donor as a sample of one, borrowing the medical-research idea of designing treatment around an individual patient, so each donor gets an individualized experience.
Competitive differentiation sustained by four owners rather than a battle card: product marketing keeps positioning and competitive material current, enablement turns it into something sellers can use, leadership buys in, and frontline managers reinforce it.
An AE's job in a demo includes directing the buyer's attention to what is genuinely different, explicitly, and an enablement team's job includes teaching AEs how to do that.
Split the 'why not just use Claude' problem into a sales-execution question (are we sharp about our differentiation and consistently teaching the buyer what to notice?) and a company-strategy question (where can a specialist product create value a general-purpose product is less designed to deliver?).
Bring practitioners from the buyer's industry, such as lawyers for a legal AI product, into the sales process for credibility, and pair them with a management structure or coaching that teaches them how to operate in a SaaS sales environment.
The higher the average contract value, the lower the SE-to-AE ratio: roughly one-to-one at seven figures, two-to-four AEs per SE at six figures, and pooled SE coverage below that.
Rather than importing a playbook from a previous company, identify which selling principles transfer to the new motion and which assumptions to throw away.
In an AE interview, have the candidate pitch or demo, ask for a self-evaluation, give one piece of feedback, observe how they receive it, and have them do it again. The second attempt matters more than the first.
For sales-leader interviews, hand over a data set, encourage the candidate to use any AI they like, and then have them explain and defend each choice in their analysis.
Coach a rep on one theme at a time, measured weekly against a defined framework, until they hold the target consistently, then move to the next.
Interim or fractional go-to-market leadership fits three situations: a leadership gap during a search, leave or transition; a founder or first-time CRO who needs a senior pair of hands; and an important project with no obvious owner that doesn't yet warrant a permanent executive hire.
A replacement for always be selling: approach every opportunity with an open mind and do the work on the problem, the business case, ROI measurement and the value proposition from the start, rather than arriving with a product to push.
Treat discovery as a way to learn about the customer's challenge, why it matters and why now, not as a way to find out what to show in the next meeting.
Approach every meeting from first call to signed contract with a discovery mindset. Early calls focus on the solution; late calls on the organizational setup and how the project will start.
The discovery question Julie rates highest: ask what the pain the customer is trying to solve really means to the business, rather than which revenue number they want to move.
Before a proposal goes in front of a customer, the rep should be able to explain why the project matters to them, how they will use the solution and what success looks like, as if they were the customer.
Account executives run solution-led discovery and give demonstrations in the customer's context; sales engineers come in later for custom demonstrations, POCs and deep-solutioning workshops.
Staff post-sales mainly with technical account managers who each own a small book of six to eight accounts, work on the customer's initiatives and run projects, rather than a renewals-focused CSM team.
Good solutioning before the sale creates the blueprint for expansion, which the technical post-sales team then executes, rather than the deal being thrown over the wall to customer success.
A new CRO should help enough but not too much: equip the team, stay out of most calls, and be brought into a deal when it will make a difference.
Make decisions quickly with limited data, commit to them with conviction, and pivot without drama if they prove wrong. Aiming to be right about 70 percent of the time, rather than 100 percent, is what makes speed possible.
Peak performance is not being productive from eight to five. It is finding the specific periods of the day when you do your best work and spending them on the hardest task.
If everything in your day goes to your job, team and other people and nothing fills you back up, you are setting yourself up for a crash.
Instead of rigid boundaries that sales will force you to break, commit to doing whatever the number requires and, in the same breath, commit to the recovery you need.
Build pipeline by proactively sending a specific buyer a written point of view (what you think, how you can drive value for them, and proof points), rather than running high-volume sequences.
Every QBR presentation starts with the presenter reflecting on what happened in the quarter, why it happened and what they will do better.
The risk leader is measured on enabling durable growth, finding ways to say yes safely within a stated risk appetite, rather than on minimizing losses.
Each function tracks the leading indicators it controls, while both leaders share accountability for one outcome. At Imprint that outcome is company profitability and partner growth.
A partner program is judged on whether it changes the partner's key business behaviors and whether it does so at a scale that matters to the partner's business.
The team that lands a partner also launches and grows the program, and specialist functions such as risk work alongside from the first day instead of receiving the account later.
Invest centrally in standardized data access, permissions, controlled deployment and observability before teams build specialized AI workflows on top.
Whoever puts their name on a document, recommendation or partner communication is accountable for every word, whatever tool helped produce it.
Each go-to-market channel decays through fatigue: it works while it is new, everyone adopts it, and prospects stop paying attention. The time a channel stays effective is getting shorter.
Run a standing portfolio of eight to ten go-to-market experiments sized to team capacity, expecting most to fail and one or two to succeed.
The only go-to-market investments Shani considers lasting are content and human connection. Their formats change, but the pillars remain.
Start from how attendees feel at a conference (cold, alone, approached by strangers) and design a booth experience that feels warm and different, with something they take home and a hook for follow-up.
Use a designer to set the homepage direction, then use AI to build animations, extend the template to every other page, and make SEO and AEO edits against competitor sites before migrating.
The question Shani wants sales candidates to ask: it shows whether deals are lost to product, competitiveness or pricing, which decides whether the job is winnable.
Beyond salesmanship, hire reps who can learn quickly, who solve problems creatively, and who are T-shaped enough to create missing assets and build their own pipeline without blaming other teams.
The CRO owns both sales and marketing, and every team shares one revenue number instead of marketing owning MQLs and sales owning pipeline.
When weighing a career decision, separate the doors that will stay open from the ones that are closing, and walk through the closing door while you still can.
Shared experience and unit economics. US companies selling at home share context with their buyer and price against US labor costs, and neither carries over to international markets.
APAC is more than 50 sovereign countries with their own tax codes, laws and leadership, so entry decisions should run through three checks: is the problem regulated, which segment do you serve, and what cultural nuance applies.
In a new region, the partners worth having won't give you meaningful mindshare yet, and many of those eager to partner are arbitrage plays, so prove a direct business first.
AI will be incremental for digital go-to-market, which was already instrumented, and transformative for real-economy businesses that are still digitizing, because the digital and AI adoption curves overlap for them.
Sell one broad set of capabilities by packaging a subset into a solution with a tangible business benefit and ROI for each industry or function.
Siro's model for an end-to-end sales performance system: record every conversation, then use AI to run, evaluate and improve the business.
The point, usually in a rep's one-on-one after a training, when the rep asks their manager whether a new initiative is really required. Whether the business change sticks is decided there, by the first-line manager.
A sales leadership framework: recruit great people who want to learn, retain them by developing their skills and careers, and help them bring revenue across the line as a value-adding partner.
Evaluate sales candidates on intelligence, character, credibility and experience, weighting intelligence, character and credibility above experience.
Off-script interview moments designed to reveal coachability and character, because candidates rehearse answers to direct questions.
Run each one-on-one from the rep's data, pipeline generation and qualified opportunities, measured against leading indicators that make quota likely if hit consistently.
Start enablement with RevOps: map the conversion funnel, find where the business model is broken, and align revenue, sales leadership and enablement on moving one or two metrics at a time.
Keep complex reporting logic out of vibe-coded front ends and put it in a solid data layer between the CRM and the app.
Four deliberate changes after the 2016 layoff: narrow to one industry, take only revenue that can be a going concern, invest in proprietary IP, and rebuild the sales narrative around speed to market.
Before taking an engagement, ask whether it can become an ongoing investment for the client, ideally one that generates measurable revenue, so the work can stack and scale instead of ending in a cliff.
Build a core code library every engagement starts from, license it to each client perpetually without transferring ownership, and keep the rights to client-funded customizations so the IP grows with every engagement.
Replace a credentials pitch with a narrative about the buyer's market that makes time to market the deciding criterion, then win on that criterion.
A niche is narrow enough when your whole marketing budget can reach it through the same events and partners. If a second segment would need different trade shows, wait and expand into it later as an adjacency.
Tier one partners go to market with you and get major conference investment; tier two get quarterly business reviews, account planning and close sales relationships with little investment; tier three are utility tools worth including but not strategic.
In a services business, manage to utilization as the master metric and plan capacity from pipeline scenarios, hiring lead time and ramp time so supply matches demand.
Instead of chasing work-life balance, plan the limited time you have at home as deliberately as your work week, be mentally present in it, and use systems and rituals so you don't have to rely on discipline.
A forecast built by finance without a bottoms-up roll-up from the field may land on the number, but it can't explain churn, downsell, where deals are being won or what is happening with customers.
Revenue operations sits alongside finance and translates sales data into the financial plan that rolls up to the board, and also supplies the metrics leaders use to coach.
If reps enter opportunities only once they know they have the deal, the CRM is recording orders, not supporting a forecast.
Start with strategy and the outcomes you want, explain the why, write a communication plan and an input plan, give frequent transparent updates, and iterate, including admitting when a call was wrong.
There are only so many ways to organize a team. Returning to an earlier model is fine when it carries what you learned from the detour.
End every roundtable or listen-and-learn by asking: if you were running sales and CS, what one piece of advice would you give yourself?
For a specific change, pick a cross-functional group with mixed experience and backgrounds, have a neutral leader run it with senior leaders absent, script what you need from it, respond openly, then have members collect feedback from their own teams.
Give the organization an overarching AI strategy (purpose, approved tools, intended uses), basic training such as prompting and limiting context, and governance, instead of leaving everyone to work it out.
Before applying AI, ask whether the process is right. Design from the AI lens (how AI would do the work) rather than the current-process lens (how AI could patch it).
Write down what each term and KPI means, such as new logo, win rate, MQL, bookings and ARR, assign an owner, and get everyone at the table, finance included, to agree, even when the definition is a compromise.
Use outside firms for outside thinking, unbiased data analysis and challenge to your org design, but keep the change management plan and the decisions in-house, because the operator lives with the results.
Before and while adding sales to a PLG motion, prove that sales adds growth rather than collecting commission on revenue self-serve would have produced anyway.
Keep small accounts self-serve and put enterprise-wide administrative features in a SKU that can only be bought through sales, so sales attribution is unambiguous.
Set aside a book of accounts that no rep may touch and measure the sales team against it as a control group.
Invest in search (SEO, now AEO), then a growth team that speeds visitors to value, then paid campaigns with known unit economics, and only then sales.
A new sales rep should return four times their base and variable compensation in their first year.
An early, quantitative RevOps person or team that stands between the exec team and sales leaders to measure whether the sales effort is truly incremental.
Benchmark RevOps headcount at about one RevOps hire per six sellers early, easing to about one per 30 sellers once a company has hundreds of sellers.
Make the first RevOps hire a former investment banker or management consultant with a couple of years to fill before business school.
Run the early sales process in a spreadsheet, watch what reps log on their own, add what leadership needs to measure ROI, and use the combination as the CRM v1 design.
Integrate an acquisition starting with the easiest, fastest-value step and work back to the heaviest: marketing cross-sell, overlay sales support, enablement, CRM migration, then shared authentication and billing.
A CRO coming in from the outside to turn around a revenue organization has to get three things right, in order: culture first, then structure, then operations.
A north-star vision to double the size of a business (2X) over two years (2Y).
Senior leaders go to customer meetings, ask the tough questions and learn the customer and the data firsthand, without overshadowing the account owner.
You don't need to be a buyer's top priority, only above the line of what they will actually fund this year.
Once the buyer says yes, stop selling. Continuing the pitch can only add reasons to reconsider.
A revenue-call technique: for each deal, imagine looking back at month-end after it failed to close, name the reason, then keep asking "what else?" until every risk is on the table.
Trying something new and paying attention to the team can lift performance even when the experiment itself fails.
The metrics a leader visibly inspects are the ones the team respects and moves.
Anthony Enrico's way of grouping RevOps work: first, GTM telemetry (can you measure what you report to the board?); after that, every project should improve conversion rate or velocity.
Split the revenue team to match a keep-grow-add strategy: one team defends and grows the largest and mid-sized customers, another hunts new logos.
Every behavior the strategy needs should be economically incentivized, so a rep unsure of the strategy can read it from the comp plan: if it pays you, do it.
Whatever a company spends on RevOps, the team should at least pay for itself annually — through reduced expense, a more productive sales team, or better decisions from better reporting.
Size a RevOps team by the capabilities the business is missing, not by a target headcount.
Aim a finite go-to-market budget at the specific places with the most defensible return instead of spreading it thinly across every product, segment and team.
Small percentage improvements in conversion or retention, applied to a large go-to-market base, are worth more than they look — and small slips cost as much.
The route from RevOps to the C-suite: own the reports and the numbers, and be able to explain how A connects to Z across every function, until you are a required seat in executive meetings.
Two ways a RevOps leader earns a board-meeting invitation: ask to sit in once trust is established, and debrief every board meeting with the CRO to prepare for the next one.
C-level seats tend to open during transitions and turmoil; the people who get them keep doing good work, build relationships, and volunteer when the moment comes.
A strong RevOps leader already carries the number in practice — at the CRO's hip, crossing the T's on every deal — even if the comp plan never had a quota.
The head of RevOps runs the pipeline and forecast calls in the CRO's stead, asking the questions the CRO would ask and taking the answers as the boss would.
Build storytelling by first practicing non-business stories — your own career — with your team and your CRO, then turning that practice into telling stories with numbers.
In software there is no critical event that ages on its own, as a candidate on the job market does in recruiting. The seller must find one inside the buyer — ideally a personal stake, such as a promotion or the risk of being replaced — and keep every conversation anchored to it.
The reason most enterprise deals are lost to no decision rather than to a competitor: the buyer isn't afraid of missing out, they're afraid of messing up.
High-velocity sellers are revenue athletes: many at-bats, fast learning, losses that don't sting. Enterprise sellers are chess players: strategic, but without natural urgency, so they drift.
Take fear out of an enterprise deal by acting as an advisor who has seen this situation many times, rather than prescribing urgency or piling on ROI.
The pipeline bunches up at the technical deep-dive stage because sellers rush discovery and then hand the buyer everything. Slow down early, earn each stakeholder, and ration information stage by stage.
Tie the critical event to a date, work backwards through legal and every step to go-live, and turn the buyer's org chart into a power chart of influence and authority.
No deal enters best case or most likely without a credible compelling critical event. If the event can move by weeks, it counts; if it can move by quarters, it isn't a critical event.
Present the enterprise forecast to the executive team as a shared call, asking for their read on each deal, rather than defending it as the CRO's own.
RevOps as a systems-thinking force multiplier: replace long deal-desk meetings with a Slack approval flow, and measure the seller's own organization — such as legal request response time — not just the buyer.
Data without a story gives people nothing to grab onto, and a story without data isn't relevant. Pair them, form several hypotheses, pick the one with the shortest learning cycle, and agree up front on the metric and the time horizon.
An agent workflow that pairs a listener agent, which proposes updates from recorded calls and messages, with a scrutinizing agent that rejects weak items before anything reaches a human.
Curate choices down to a few. Buyers don't want more information; they want to make the right decision.
A diagnostic distinction between a demand engine that functioned and then degraded, and one that was never actually built — where years of virality quietly substituted for an acquisition motion nobody ever stood up.
Before optimizing a go-to-market process — routing rules, tooling, channel spreadsheets, conversion tuning — check whether there is any volume in the calendar to optimize. If the calendars are empty, optimization is not possible.
Positioning rule, credited to 37signals co-founder Jason Fried: use the language your customers use about you, not the language you want to use about yourself.
Job number one is finding the port in the storm and establishing yourself firmly in one spot. Only once you are out of the water do you get to choose whether to go deeper into that territory or wider across more of it.
Identify the places the business wins without effort — organic evangelism, a segment that keeps showing up — and invest there first, instead of building a new motion somewhere you are weak.
A reframe Jason was given for the CEO job: much of the work is not figuring out how something gets done but figuring out who is going to own it.
Earning every rung in sequence rather than being handed a jump, on the theory that the skipped levels catch up with you later.
Sequencing an impossible-looking list of work one item at a time, from Anne Lamott's book on writing — where a boy panicking over an overdue report on birds is told by his father that he'll get it done bird by bird.
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.
Writing down the tactical detail of how you personally do the job — call volume, timing, follow-up, organisation, the funnel and its conversion rates — until what looked like personality turns out to be a repeatable recipe someone else can run.
The point, usually three to six months in, where a rep stops obediently executing the playbook and says: I get it, I know how to do this, and I'm going to bring myself to the job.
An exercise in which a rep writes what their manager, peers and customers will say about them when they leave the job — and then works backwards to the behaviours that would earn it.
Translating the qualitative reputation you want — responsive, honest, knowledgeable — into stated numeric service levels, then publishing them to the people who will judge you by them.
The table-stakes contract Cole gives anyone on a revenue team he leads: know what good and bad performance look like and be aligned with your manager on it; be compensated fairly; be treated with respect; have the tools necessary to execute the job.
Running strategy by objectives at the leadership level — four to six priorities aligned to the founder's vision, reviewed with leaders every two weeks — while getting far more prescriptive about activity expectations at the individual rep level.
Proactively catching a high performer's base and OTE up to what the role is now worth, rather than waiting for them to lobby or for a competitor's offer you would then match.
Cole's rule for maturing leaders: people will roll problems to your feet, and the moment you pick one up you own it — so choose deliberately rather than reflexively.
The moment a career stops being a ladder of obvious next steps and becomes a set of trades — once basic needs are met, every promotion is a compromise between satisfaction, impact, title and compensation rather than a straightforward step up.
The five ingredients Cole weighs in any job — compensation, title, industry, leading people, and impact — tested by asking whether more money, a better title and a different industry would make you happy if you led nobody and felt no impact.
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.
Joey's view that the live conversation is the most valuable unit in go-to-market. Data and dialers are the subatomic particles, and the conversation is the atom you have to stack to build anything valuable. He also calls cold calling 'conversational advertising' — delivering a tailored ad to an intended target and getting a reply.
Outbound succeeds or fails on four things: the list (right accounts, right contacts, good data), the messaging (right message to the right contacts), the rep (ramped, trained, doing the right inputs) and the follow-up (systematic circle-backs on conversations that did not convert).
A cold call structure where the first gate is an honest opener that signals a cold call and asks for help, and the second gate declares the reason for the call. It then offers two buckets of pain for the prospect to self-select into, followed by a tight pitch, a call to action and a correct disposition.
An idea Joey credits to Ryan Reisert: a rep doesn't need to be memorable on early cold calls, but must not be forgotten when it is time to be remembered.
The ceiling of any outbound effort is the quality of the list — primarily the targeting of accounts and titles, with accurate contact data as a subcategory — so list building must pass a quality assurance check before it reaches the floor.
Account research from AI and third-party signal tools, compared with an intel-gathering (IG) report built from real conversations with people across the target organisation.
A shift away from large, low-paid, high-volume SDR teams toward teams half or a quarter of the size, made up of highly paid specialist conversationalists who stay longer because they are more effective.
A role Joey has run for about two years: an SDR who can book meetings from intercepted inbound but may not book meetings on outbound. Their outbound job is to have conversations below the decision-maker level inside target accounts and gather intel for the AE.
The share of a prospect list you will ever reach by phone if you keep calling it. Joey says for 1,000 prospects it usually never exceeds 200, no matter how many rounds you dial.
TitanX's model triangulates telecom and carrier, consumer and professional data to answer three questions about a number: is it the prospect's, is it active, and how does it respond when unfamiliar numbers call it?
Voicemail rules that depend on answer intent: skip voicemail on high-intent prospects, leave voicemails and AI-screener messages on low-intent prospects, and point voicemails to the email you sent.
Joey's position that outbound itself works and a failing motion reflects execution, because outbound is continuous experimentation — much like a PLG motion — run inside the four containers of list, message, rep and follow-up.
Automate the back of the house — administrative, repeatable, rule-bound work — and keep humans in the front of the house, where the business touches customers, prospects and the market.
When channel headwinds reduce effectiveness — blacklisted email domains, LinkedIn throttling, spam-flagged phone numbers — teams try to make up for it with effort, raising volume to recover their previous results.
Power dialing places one call from one number to one person. Parallel dialing places several calls at once, connects the rep to whoever answers and hangs up on the rest.
Carriers such as AT&T, T-Mobile and Verizon share data and score outbound numbers, which rise or fall with dialing behaviour — much as Google and Microsoft blacklist spam email domains.
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.
The legacy identity model: verify once that a person is who they say they are, then trust their judgment for everything that follows.
A way to picture declining visibility as access is delegated outward: the person acting directly at the centre, then agents with delegated access, then the subagents and recurring or scheduled actors those agents spawn.
The three ways vulnerabilities surface with AI agents: credential theft, prompt injection, and rogue behaviour.
Repositioning the CISO from a blanket stop sign on AI adoption to the function that green-lights tools, because guardrails, attribution and data controls make adoption defensible.
Giving every agent that acts on a person's behalf its own unique, downscoped, time-bound identity instead of letting it inherit that person's credentials, with each agent attributed back to a human or team owner.
Continuous verification attached to every action of whether an identity, human or non-human, has the permission to act and should have it — with everything downscoped by default.
Counter-controls are what allow speed: a car without brakes cannot safely open up its engine.
Mark's term for the AI outreach power tools now in the hands of every employee, dangerous without a sense of skepticism about how they are used.
Treating each prospect interaction as a request for a small, incremental investment — reading the next two lines, opening a relevant white paper — rather than a single ask for a meeting.
Building new-logo pipeline only from a starting point of corroborated trust — a customer anecdote, a warm intro, a common employer or investor, or a credible voice vouching for the product.
The part of selling AI cannot replace: showing up with deep, earnest empathy for how a problem is hurting a specific customer.
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.
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.
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.
Agentic GTM is composed from a few interchangeable building blocks: a very smart intern (the LLM), web search, a data platform, and a workflows agent that can take or suggest actions on your behalf.
A maturity ladder for AI in GTM: using skills (precise, installable instruction sets) puts you in the top 1% of users; using scheduled tasks (routines that run agents on a cadence) puts you in the top 0.1%.
A research-and-enrichment agent (running in the LLM, plugged into the web) hands its output to an engagement agent living inside the GTM platform (harnessed to owned channels and CRM), which has its own instructions for how to act.
Personalization that generates a bespoke sequence per person: the agent knows whether you're connected, whether you emailed or cold-called before, and what the CRM says, and decides both the copy of each step and the channel each step starts on.
To design agentic flows, ask what recurring work you would hand a very smart intern you just hired — then build agents around that answer, letting the LLM interview you and write the instructions.
Across Amplemarket customers since January 2026, opportunities generated by channel split roughly 40% email, 40% calling, and 20% social — evidence that multi-channel, contextual outbound still works.
AI creates a widening productivity gap between adopters and non-adopters, but market pressure keeps teams employed: if you can go faster, competitors force you to reinvest that speed rather than fire people to move at the old pace.
A working test for whether a target segment is narrow enough: do a significant number of people in the target actually know your brand? If awareness stays at zero as you spend, the niche is still too broad.
Build brand equity in one absurdly narrow niche first, then expand to the next adjacent niche one at a time, repeating the awareness-building motion in each.
A principle Anthony credits to Radian Capital's managing director: operate the business as if you'll own it forever — 'or else you will,' meaning if you won't make long-term bets you'll never build anything worth selling.
The counterintuitive claim that narrowing to the right small group of customers — rather than chasing a bigger TAM — produces more durable revenue, because a resonant niche will sell your product for you into tertiary markets.
Frazier's stance that building brand and building demand are not different activities to be traded off in a budget; done right, they are the same effort, with brand equity as the foundation.
The framework in Frazier's book 'Marketing and Channel Management for Low Brand Equity Firms' — 21 marketing and channel principles that build on each other, aimed at small and mid-sized firms trying to build awareness from zero.
The classic marketing framework (attributed to E. Jerome McCarthy) — product, price, place, and promotion — the levers a marketing manager coordinates to take a brand to market.
A move away from many-layered specialist orgs (SDR, AE, SE, closer, CSM, plus tiers of managers) toward flatter structures staffed by fewer, more experienced reps who carry unique knowledge and real authority.
Assign the best, highest-potential territories and accounts to proven top performers, and weaker territories to beginners who must prove themselves — matching account potential to rep capability rather than dividing the world evenly.
A two-part explanation for marketing's declining influence since ~2000: universities shifted from teaching marketing management toward buyer behavior and analytics, and marketing managers in companies rarely carried profit-and-loss responsibility — so finance and founders stopped trusting them with budget.
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.
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.
Invert the usual order of operations: instead of perfecting audience cohorts and reusing one asset, start with what you're trying to say and the mindset you're reaching, then treat every ad as a blank canvas customized to that audience and context.
For one-to-many media like DOOH, target the location and mindset of the screen rather than the individual, and vary the creative per venue-context so it feels relevant to many without being invasive.
Bring a new product line to market in three moves: assess and wire up supply/partners, launch as a high-touch managed service with trusted betas to 'fail and win, fail and win,' then open self-serve, and finally close the measurement loop to prove impact.
Design channels to reinforce each other in sequence — a brand seen on a digital-out-of-home screen is retargeted on mobile — so the story continues across screens rather than each channel running in isolation.
Before opening a new channel to market, educate and certify the internal team so everyone can represent it consistently — treat internal readiness as a prerequisite for external demand.
Put three parties in the room together — the agency (strategy and deployment), the brand (positioning and creative appetite), and the platform (the creative that lands) — each owning a distinct role, compounded by shared measurement.
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 fear that native-AI companies will displace SaaS incumbents that bolt AI onto legacy architecture — and the buyer's inability to tell a truly native-AI product from a SaaS wrapper.
Meet the customer in the middle by proving value in their own environment through a proof of concept, sharing risk, then expanding — making the POC the default go-to-market move rather than a concession.
AI deals require selling horizontally across the functional buyer (HR generalists, HR ops, HR leadership), IT, an AI committee, and security — any of whom can veto or delay the deal.
The economic buyer — the person with discretionary authority to say yes and move budget — has gone horizontal in AI deals; IT is often the new economic buyer even on an HR purchase.
Embedding technical forward-deployed engineers into the implementation team to manage LLM change, build guardrails against hallucination, and hand-hold customers through early adoption — modeled as an accounts-per-FDE/CS gearing ratio in headcount planning.
An implementation philosophy (borrowed from Indiana football coach Curt Cignetti's 'stacking days, stacking wins') of engineering a continuous drumbeat of provable metrics and success stories the champion can tell internally.
Extending the go-to-market engineer role beyond top-of-funnel prospecting into mid-funnel deal execution — automated SOWs from call transcripts, company-specific deal coaching, and CRM-plugged GTM diagnostics.
The enterprise qualification methodology Scott helped develop; in AI's chaos the two most decisive elements he stresses are Champion ('no champion, no deal') and Decision Criteria — the capability shopping list a buyer uses to evaluate vendors.
Rather than extracting the buyer's decision criteria, supply it: an editable, weighted, unbranded capability scorecard that lets the customer objectively compare vendors for the problem they're solving.
Auto-fill MEDDPICC in the CRM from Gong call transcripts while also keeping rep-entered MEDDPICC, then compare and contrast the two to triangulate what's actually happening in accounts.
When a company hires a go-to-market leader, RevOps and enablement are the first two hires; the ecosystem is built before AEs so reps ramp fast into a well-oiled machine.
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.
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.
A go-to-market model with no contracts and no renewals — pure pay-as-you-go, even on multi-million-dollar enterprise deals — so the customer can leave at any time and the company effectively re-earns the business every single day.
Anthony's framing for the startup-vs-scale-up choice: a big ship already has a direction and goes far; a jet ski is nimble and yours to steer. Oliver's corollary: at early stage you work ON the company (creating its DNA), and at scale you work IN it (executing).
Define ARR by taking collected revenue and extrapolating it forward twelve months, then stacking disciplined, repeatable consumption projections — derived from a customer's telemetry data or their prior-vendor usage — on top of the extrapolated actuals.
Pay commissions up front on a projected ACV — the customer's estimated one-to-three-year spend — protected by security-margin haircuts, a two-person review of the estimate, a rep-adjustable projection, and a consume-to-earn provision that only fully vests the commission once the customer actually consumes.
A comp plan surfaces problems but rarely causes them. If deals collapse at scale, the root cause is bad hires or a product that isn't doing its job — not the incentive structure, which only mitigates or escalates the underlying issue.
Staff a company in waves: SEALs first (operate confidently without supervision in uncharted terrain, mission evolves as they gather intel in the field), then Marines (build the foundation), then infantry (scale once the foundation exists).
Motivation is why someone joined your cause — intrinsic, and not the leader's job to install. Morale is how someone feels in a given moment — situational, and squarely the leader's job to manage by supporting people through hardship without removing it.
The real leverage from AI isn't the model — it's the discipline of organizing and maintaining company knowledge so an agent has clean, current context to draw from, turning a one-hour subject-matter meeting into a five-minute prompt that's 95% right (plus a ten-minute human review of the output).
AI Engine Optimization (AEO/GEO): the discipline of improving how a brand is ranked and cited inside LLM recommendations. The defining stat is that up to 85% of what AI recommends comes from third-party content, not your own website.
The categories of off-site content LLMs weight most: review sites (e.g., G2), small influencers and YouTube, digital publications and blogs covering your category and competitors, and integration content co-published with partners.
Run an AI-visibility analysis to surface the URLs you should be working with and the content types you lack, then use those two outputs to build the partnership and content roadmap.
There's no universal first step; you diagnose your existing content baseline and attack your biggest gap — whether that's missing technical FAQs, a better-ranked competitor, negative brand sentiment, or a story that's stale after a pivot or new product.
Model partnerships like any other channel: TAM, then persona overlap, then a per-quarter penetration assumption, pipeline conversion, and win rate into new bookings — the same funnel logic marketing and outbound use.
Partner-involved revenue retains and expands better than direct: PartnerStack benchmarks show ~130 NDR on partner-managed revenue vs. ~105 on the core business (and ~108 partner-sourced), plus better gross retention and lower cost-to-serve.
Zero-to-five (pre-PMF): usually no partnerships hire. Post-PMF: invest early but patiently, sizing partnerships as a third GTM pillar alongside sales and marketing, targeting 30-40% of total revenue over time.
The defining shift from a sales org (where you sell the vision and the full range of what's possible) to a customer-success org (where you have to deliver on promises that are sometimes bigger than reality).
The discipline, on every promotion, of deliberately stepping back to relearn a department and role rather than carrying your previous job forward under a new title.
As the cost to build applications collapses and AEO churns like the SEO-algorithm era, durable defensibility comes less from product and more from a broad, diverse ecosystem of partner-evangelists.
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.'
In a world of unlimited information and opportunity, the scarce edge is clarity — the ability to focus on the few highest-priority problems and not over-index on the feeling of stress. Individual clarity and organizational clarity move together.
A concept coined by a16z's Martin Casado: unlike product-market fit (fitting a product to existing demand), market annealing means shaping the market itself — educating buyers, defining the demand, and shaping the product in parallel.
The platform is a world-class kitchen that can prepare any 'meal' (extract value from any image or video data). Rather than acting as waiters serving every hungry customer a different dish, you build one focused 'hamburger stand' — a single killer app sold 100% outbound — to prove a restaurant can be built on top of the kitchen.
A powerful platform doesn't create instant value on its own; it needs a killer application that lets customers get value immediately — the way Databricks needed notebooks before people could realize its value.
Instead of marking up hyperscaler infrastructure and competing on its margin, pass that cost through at parity and charge on the usage or value delivered on top of it.
A weekly leadership operating cadence with no fixed agenda or set times: the team gathers to solve the hardest problems and works until the set of things is finished, ordering pizza along the way.
A progression of accountability: an IC empowers themselves; a head of sales empowers through people and owns a team; a CRO takes accountability for the whole company — vision, strategy, fundraising, and product influence.
Just as engineering accrues technical debt, an organization accrues partner debt, customer debt, and employee debt by taking on too many things at once and failing to fulfill the promises made.
With only 53 roster spots, do two jobs no single specialist can combine — freeing a roster spot for the team — and you convert yourself from a fringe cut candidate into an indispensable asset.
Continuously stack differentiating skills and credentials so you always have another 'arrow' to shoot when the terrain changes — an NFL player who is also a finance/marketing undergrad who also has an MBA.
Instead of building a broad network, go deep on four to six relationships, serve first, buy the lunch, and never ask for jobs or favors — let value compound until the other person decides to help.
Refuse to let a past role become your identity; you never run your fastest looking backward, and everyone — including you — is replaceable, so keep facing forward.
Respect how hard it is for a consumer to pull out a credit card, meet them as close to their ideal situation as possible, and map the distinct pressures on all three actors — consumer, purchaser, and the retailer/customer in between — to remove friction from every 'yes.'
To break into a niche, endemic category, prove genuine investment in the sport to earn credibility with its passionate core, then layer elite talent on top — going high (star pros) and low (grassroots) at once.
Never overextend or drift downstream from what your product actually delivers; a broken promise breaks the value proposition, and a burned consumer is nearly impossible to win back.
Measure whether your brand truly resonates by tracking what share of business comes from referral (via post-purchase survey): ~20% is a strong signal that others are marketing for you; mid-single-digits is a problem.
Radical self-honesty and accountability: the film (and the truth) always comes out, so acknowledge mistakes fast rather than hedging or claiming undue credit.
Plans matter, but reality diverges from them; align the team candidly around the terrain in front of you instead of defending the map you drew.
Encourage full disagreement before a decision, then demand total commitment after it — once the play is called the debate is over, and nobody half-asses it to protect a personal escape hatch.
Coach the process — preparation, technique, brand, culture, team, sound assumptions — and treat results as a signal (distorted by external forces) for whether the process is broken, not as the thing you optimize.
Building a company is like building a house: you can go fast, but you can't skip steps — if the stair needs four nails, drive four fast rather than two.
Founders and owner-operators develop tunnel vision from sheer passion; an experienced outside advisor adds peripheral vision to spot the pothole — or the eight-figure unlock — sitting just off to the side.
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%.
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.
Andy's written checklist of the go-to-market foundations fast-growing (roughly Series A) companies forget: the data foundation, GTM tooling, the right metrics to track, efficient processes, CPQ, and enablement.
Build formal enablement when you start cloning sales teams and multiplying products and complexity. Below that — one manager, fewer than ~10 reps — the manager owns enablement and rep ops themselves.
Enablement hires come in two shapes — the former rep you train up, and the teacher-type with an ops mind. Either succeeds only if they partner with sales leaders as the prioritization function and hold an opinion on what to train.
You're a passive job-seeker — always with a role lined up or recruiters chasing you — until you get 'punched in the face': laid off, in conflict with a boss, or at a company that ran out of money, forcing a proactive, jarring search.
At the VP/C-level, the odds of a role being publicly posted are low; it's whispered to you through the network. Whispered captures the confidential company insight execs gather while interviewing (and then normally throw away) into a durable edge.
A resilience test for data architecture: if we deleted your CRM instance today, how exposed are you? Teams with a true data warehouse as source of truth could bolt on a new front end and be fine.
The core RevOps mindset: configure systems to fit the business rather than deeply customizing them into brittle, un-maintainable states. Paired with a data skill set (SQL, which AI now makes easy).
Put the GTM engineer role inside the RevOps org: first build the data foundation, then build AI agents on top of it. Keep it aligned so automation solves root problems, not just the surface problem in front of it.
RevOps spans six functions — sales ops, marketing ops, CS ops, GTM systems, strategy, and enablement. You won't be great at all of them, so build a full-funnel operator by rotating across them, ideally under a leader who moves you around.
A 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.
The organizational cancer where no one is empowered to make a decision — approval chains, forms, and red tape turn every needed action into a slow, frustrating reaction that bleeds talent, customers, and revenue.
Jack's practical blueprint 'from the janitor to the CEO' for building a high-performance, innovative culture by empowering every level of the org to decide, take initiative, and add value.
Every role, from CEO to individual contributor, gets a clearly defined 'fence' — a sphere of influence — inside which they can innovate, fail, and decide without asking permission.
Empower frontline people to act in the customer's interest without asking permission — do what you'd do for your grandma — and keep asking 'how do we do better?' to surface and implement their solutions.
Culture compounds from what you reward, formally or informally. Reward outcomes and customer-proud work and you spin a flywheel of initiative; reward hours and optics and you manufacture performative productivity.
Model your own mind as a large language model: a database with a learning layer whose training data is the people you interact with. The more people you meet, the richer the dataset and the better your predictions, analysis, and instincts.
Because your brain-as-LLM has no safety team to filter bad inputs, deliberately curate what you consume: stay away from the noises of no's and stay close to the noises of yes, filling your dataset with people who believe things are possible.
Any capacity you stop using atrophies — a finger immobilized for months, eyes covered for a year, and the brain the same way. Offloading creative and critical thinking to AI quietly weakens the very muscles you depend on.
The outreach-spam era is a supply glut: pre-2019, ~50 companies chased ~100 US/Europe customers; the tech boom pulled ~500 sellers from across the globe toward a shrinking buyer base, so desperate automated outreach was inevitable.
There are only two ways to succeed: consistent, disciplined long-term work, or compromising ethically to appear successful overnight. Growth hacks are nonsense; you have to move through the natural process with patience.
Modern life moves people between three boxes — office, home, and club — which caps thinking and energy. Humans were designed for the outdoors, so escaping into nature once or twice a month restores perspective, energy, and ideas.
A VC framework Anthony relays: evaluate a startup on the wave (market), the surfboard (product), and the surfer (founder) — and the surfer matters most, because a great surfer finds the right wave even on mediocre equipment.
Treat your network as a decade-long asset instead of a job-hopping byproduct. Build history with people and do it with integrity, and those relationships become your most durable, lowest-cost pipeline.
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.
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).
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.
'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.
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.
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.
A research-derived methodology that distinguishes two selling environments — low-complexity/transactional and high-complexity/enterprise — and, in the complex environment, wins by Teaching the buyer something new, Tailoring it to their situation, and Taking Control from an advisory, expert frame.
The Challenger research profiled sales-rep archetypes and measured which won. Weiss names four: the Hard Worker (outworks everyone), the Challenger (teaches and pushes change), the Relationship Builder, and the Lone Wolf.
Neil Rackham's 1970s discovery framework: understand the buyer's Situation, the Problems inside it, the Implications of not solving them (cost of inaction), and the Need-payoff of solving them, to drive urgency around why change now.
A riff on SPIN designed to combat product-led, feature-and-benefit selling by first understanding the buyer's problems before offering a solution — best used to help a buyer see a problem they didn't know they had.
The discipline of reading where a buyer is in their own process and matching your motion to it: a mature buyer knows the problem, the solution criteria, and the competitors; an immature buyer knows little and needs co-creation.
A holistic system organized around engaging the buyer, qualifying, and closing — including 'upfront contracts' (pre-agreeing to a next step) and 'pain funnels' that probe first-, second-, and third-level pain.
The view that sales mastery is the deep execution of a full set of fundamentals — hunting, reaching decision-makers, discovery, creating needs, business-case building, presenting, multi-threading, negotiating, handling rejection — assembled in your own way, rather than any single methodology.
Gartner's framework, rooted in research on buyer decision fatigue and decision confidence, in which the seller's job is to help an overwhelmed buyer make sense of an overload of information and competing options so they can decide with confidence.
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.
Define the company by the customer's problem — for Moxie, 'I want to start, grow, run, and stay compliant as a med spa' — and solve it with whatever works: software, a delivered service, a content library, or AI, without insisting every solution be a classic high-margin SaaS product.
Instead of shipping a tool so the customer can do a job, actually do the job for them — run the ads, write the message, run the A/B test, place buy-now-pay-later at the right touchpoints — with the customer's awareness and approval.
Deliberately pick a micro-niche — a TAM probably too small on its own to build a big business — and win an outright high double-digit share of everyone making that decision before broadening to the next category.
Hire more senior than the stage seems to require — people two steps further in their careers, still hungry and high-capability — pay roughly 50% more, and bet the business grows into that seniority.
Treat go-to-market efficiency as an outcome of product strategy: solve the whole customer problem so you aren't in feature bake-offs, then run sales and marketing at a fraction of normal headcount — Moxie at ~8–9 people out of ~144, under 10%.
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.
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.
Partnerships require giving value — and making concessions — before you get anything back, in contrast to the common approach of building a channel purely to sell more of your own product.
A partnership program must be sponsored from the board and executive leadership down, because early concessions and delayed ROI can't survive quarter-to-quarter decision-making.
Treat your strategic partners as potential acquirers, using a multi-year partnership to build relationships, test integration and cultural fit, and position for a strategic exit.
Concentrate limited bandwidth on a select few high-conviction partnerships where the combination is disproportionately valuable, rather than spreading thin across many low-producing relationships.
Build trust so high that a partner would call your personal phone at 3am on a Sunday and know you'll pick up and problem-solve as eagerly as they need.
Deliberately weight travel and face-to-face time above other activities to win partners' hearts and minds and to harvest the off-the-record intelligence that never surfaces on a recorded call.
Give every partner equal access to support, technology teams, and roadmap, and hold commercial terms you'd be comfortable exposing to a partner's competitor — the foundation for managing channel conflict.
Tie the partnership team's KPIs to overall company revenue rather than channel-only revenue, so channel and direct teams succeed together.
Make an honest assessment of whether a partner motion fits your GTM, then either fully commit the resources or don't start — no one-foot-in, one-foot-out programs.
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.
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.
Conversation, not measurement — quotable, but weigh it accordingly.
“If I hire an AE that makes 140, 150 in the SMB segment, they can't be touching deals less than 15 to 20K.”
“And a lot of people don't realize like, that's what it takes is taking a couple steps back to perfect the process to go 10 steps forward.”
“I made the joke that when I first came in, their meetings were with everyone's mothers and their grandmothers, 'cause I'm like, this title would never buy.”
“If I could produce the result, you couldn't deny me the seat in the room.”
“It's the way you get in the room. It's also the way you get asked to leave the room.”
“The average tenure right now of a CRO and a CMO in the industry is 18 months. It's not long enough to get anything done.”
Keegan Otter on taking the SDR seat first, cutting qualification to three questions, the closed-lost process that resurfaced deals every quarter, pitching founders on the first hires with two paths on a whiteboard, the routing and ACV math past $5M, and why he told Warmly's executive team to build the brand or die
Melissa McCann-Tilton on why a number is the one credential nobody can argue with, what keeps women out of the CRO seat, AI-written resumes screened by AI, why almost half of hires fail, testing candidates in the room, and why your inbound lead is already an order
Chad Trabucco on the quarterly rep-confidence survey he calls the voice of sales, why enablement has to invest in frontline managers, deal green lights and coach camps, the leading metrics that tie training to conversion, ACV and win rate, what a ramped rep actually looks like, and AI role play as the warm-up before a live call
Nick Reyes on going from the Marine Corps to first salesperson at PushPress, the RevOps hire he wishes he'd made years earlier, why RevOps now builds guardrails instead of castles, the 5 a.m. habit that taught him the financial model, and the one question that changed how his team solves problems
Christian Miller on why a CRO missing from the board meeting is a red flag, the 60-day diagnosis of a hidden payments business, reading pipeline coverage by segment and stage, the founder-led snapback, and keeping AI from turning your message into 50 versions of the same deck
Zach Rego on starting Triple Whale's sales team from an Airtable of 2,000 names, why a CRO should still sell every flagship launch, moving AI pricing from credits to good-better-best, why first managers should do the job first, and taking personalization to the craziest degree
Xander Kotsatos on running sales, CS and solutions under one leader for the first time, why being right about the number matters almost as much as hitting it, narrowing sales focus while widening CS, growing new business with no SDRs and no marketing team, why slop raises the value of curation, and why his sales reps don't use AI to write proposals
Ari Greenberg on what to leave out at each stage: why a deal desk can wait until about $20M ARR, BDRs as a reward for reps who already book meetings, a tiered commission plan that lets the rest leave on their own, the proof of concept that crashed and won the customer, letting the cheap guy win, and selling when the buyer has AI too
David Cady on ten-plus years running go-to-market at Virtuous: one financial rule that outlasts every venture metric, why spray-and-pray stopped paying back, category creation with Responsive Fundraising, why the SaaS partner program missed, and promoting high-agency people into the problem they just solved
Simon Kirk on why selling against Claude is the Lattice problem again, teaching buyers what to notice, bringing lawyers into the sales process, SE ratios and win-rate lift, why no playbook survives a copy-paste, and how to interview AEs and sales leaders now that every candidate has Claude
Julie Mall on her one-word edit to always be selling, discovery as learning rather than demo scoping, the question that asks what a pain really means, the solutions-engineer edge in the CRO seat, technical account managers over CSMs, and AI for deal patterns and board prep
Miles Kirkpatrick on the panic attack that changed how he works, finding a 45-minute peak window, decision velocity versus flip-flopping, promoting a commercial roofer to run customer success, and building pipeline with points of view instead of sequences
Lalitha Rao (Chief Risk Officer) and Tyler Dibble (Chief Revenue Officer) on running risk and revenue at Imprint off one profitability target: partner data as underwriting signal, the risk leader in the sales room, no handoffs across seven-year partnerships, and owning every word your AI helped write
Shani Shoham on why every GTM channel has a half-life, running eight to ten experiments at once, conference booths people remember years later, an AI-run website migration with zero traffic drop, what 90% of sales candidates skip, and why the CRO should own sales and marketing
Bhavik Vashi on opening APAC twice for Anaplan and Carta, the two things US companies miss abroad, why the best partners won't take your call yet, reversible and irreversible career doors, and why AI will transform in-person selling in the real economy
Ally Combs on why every GTM change lives or dies in a rep's one-on-one, the three R's of sales leadership, interview tests for coachability and character, leading indicators that make quota inevitable, and the enablement stack she vibe coded on top of Salesforce
Kevin Rice on the four bets that turned Hathway around after a 2016 layoff: one industry, only revenue that can stack, IP that sells speed, and partners that put you in every room, plus utilization, a deal that died the night before signing, and what the climb cost at home
Susan Rothwell on rebuilding the revenue engine at a fifteen-year-old company: a finance-built forecast that was blind rather than wrong, RevOps as the interpreter, a CRM used as an order system, reversing an inherited reorg in the open, the AI test she applies to every process, and the one job consultants can't do for you
Dan Cook (CEO, PDQ) on testing whether sales is accretive or just cannibalizing self-serve, the 4x payback rule, a 6:1 seller-to-RevOps ratio early, a first CRM built in a Google spreadsheet, and an M&A playbook worked backwards from the easiest step
Chris Adamkowski on walking into a sales team that was churning more than it sold, the three pillars of a turnaround (culture, structure, operations), 2X2Y, the slowest camper, stop at yes, a revenue call built on "what else?", and putting churn in the comp plan
Thurman Sneed on going from auditor to Chief Revenue Officer, the rule that RevOps should pay for itself every year, the power of one percent, how to get invited to the board meeting, volunteering for interim CRO and being made COO, and why the answer to "COO or CRO?" flipped in the last ten years
Tim Yandel on the personal consequence hiding behind every compelling event, why fear of messing up kills more enterprise deals than competitors, forecasting when every deal slips, and why the best RevOps metric in an enterprise motion has nothing to do with the buyer
Jason Tatum on inheriting a 12-year-old product with real product-market fit and no acquisition motion underneath it, the empty-calendar test, describing yourself in your customers' language, and getting an impossible list done bird by bird
Steve Dinner on why the two-week sprint is finished, the three tracks and two gates replacing it, the 29:1 RevOps ratio he had to right-size, and why an LLM should manage your CRM like a code base
Cole Gillespie on writing the recipe for a sales rep, turning "responsive" into a three-hour SLA, the four things every person should expect off the elevator, and why the leader who has to be asked for the raise already lost
Joe Mosely on the day the grind broke, the three tactics that stuck, why RevOps people fail by over-indexing on the wrong things, and running ad hoc and roadmap work as two streams
Joey Gilkey on the reach rate almost nobody measures, the four pillars of outbound, an SDR who isn't allowed to book meetings, and why AI belongs in the back of the house
Aimee Menne on the two-question FDE test, knowing when customers are pulling you into services, the maturity curve from first hire to P&L, and how Sourcegraph packages implementation, hours and outcomes
Cheyenne Griffith on the three conditions a company has to meet before enablement can work, why the SKO launch is the smallest part of the job, and why maintenance is the AI problem that keeps her up at night
SecureAuth CRO Mark van Oppen on the three ways agents cause incidents, continuous authority, turning the CISO into the department of yes, the spam cannon on every desk, and building pipeline on trust
Luke Hoffmeister on internal attrition, why 20% is life-changing to them and a rounding error to you, and culture as follow-through rather than snacks
Day AI's Christopher O'Donnell on the folder every RevOps team is quietly building, and why multiplayer mode barely works
GTM Council co-founder Noah Marks on why software is becoming a services industry, and how to become the pipeline czar at your company
Mica, founder & CEO of Amplemarket, on agentic GTM — building outbound agents that research, personalize, and run while you sleep
Former USC Marketing Chair Gary Frazier on brand, niche, the flattening sales org, and why the CMO lost the C-suite
Alex Wakefield on scaling AcuityMD from $2M to $50M ARR, when to bring in RevOps, the overhiring trap, and breaking the 'AI-first' mental wall
Michael Kiernan on 'Human + Agentic GTM' — where AI belongs in the revenue motion, and where it doesn't
Chris Heller (CRO, Place) on M&A integration, talent as the ultimate leverage, and the career moves that actually compound
Jerry Brooner on four exits, the secret pre-IPO roadshow, the truth about startup equity, and why every revenue leader should be building their own agents
Gabby Stoller of Big Happy on creative-first ad tech, building a digital-out-of-home division from scratch, and the GM-to-CRO leap
Joshua Trott on selling in heavy industries, RevOps as the operational backbone, and why delivery — not the deal — is the real contract
Leigh Gross (CRO, Synctera) on 20-person fintech deals, why RevOps is your first GTM hire, and the mid-funnel AI use case nobody talks about
Scott Sinatra on MEDDPICC, the new multi-threading, why POCs are the default, and building go-to-market for enterprise AI's chaos
Guy Rubin on the $78B revenue benchmark, the ICP-vs-TAM trap, and why AI on a broken GTM makes everything worse
Pete Shelton (CRO, Fullcast) on the CRO Dilemma, continuous planning, and becoming the operator your CRO can't run the business without
A live build-along: AI agents for sales, sales management, marketing, customer success, and RevOps — plus the 2026 agent-platform landscape
Oliver Manojlovic (CRO, Dash0) on pure pay-as-you-go GTM, ARR without contracts, consumption comp, hiring SEALs, and motivation vs. morale
PartnerStack CRO Mike Head on AEO, why LLMs trust third-party content, and how partnerships became the highest-leverage growth channel
Alex Loktev on scaling P2P.org through five GTM pivots — who controls the client, the Golden Era trap, and going AI-native
Tom Witte (CRO, Upflex) on hybrid work, AI-orchestrated culture, and becoming an AI-first revenue leader
Brett Kelly on the RevOps-to-CRO path, leading 20-year veterans through reinvention, and why AI means producing more — not cutting staff
Josh Heller (Coactive AI) on market annealing, the CRO's real job, and why clarity beats doing more
Ryan Kuehl on survival math, winning the tastemakers, and building fast without skipping steps
Tyler Molinaro on compressing government sales cycles, hiring for problem-solving over pedigree, and using AI agents to make a lean team outbuild a funded one
Maranda Dziekonski on tying CS to revenue, comp plans, NRR, brand, and real AI use cases
Andy Mowat on where scaling companies neglect the fundamentals — enablement, data foundations, GTM tooling, and the RevOps career
Ebsta founder Guy Rubin on the 2025 B2B Sales Benchmark Report — sales velocity, deep ICP over TAM, and ruthless qualification.
Jack Jackson on performative productivity, spheres of influence, and empowering every level to act
VinnCorp co-founder Khurram Kalimi on why authenticity beats automation, treating your brain like an LLM, and building a network that opens doors
Theo Pavlich on hiring RevOps talent for curiosity over pedigree, why an unconventional background is an edge, and taming GTM tool sprawl
Justin St. Louis Wood on building revenue systems from first principles — then rebuilding them AI-first
Yogi Punjabi on building PeopleLens — an AI layer that makes every rep a better performer and every manager a better coach
Ebsta's Adam Roberts on the data foundation behind revenue intelligence — relationship scoring, AI qualification, pipeline visibility, and bottoms-up forecasting
Steve Dinner on running a high-output RevOps team with zero in-house admins or devs — agile, structure, specialist contractors, and AI
James Kase on ruthless prioritization, protecting focus, and why saying no is a RevOps power move
Vish on being the Hand of the King — how RevOps operators win on trust, structure their days, and grow toward the corner office
Stephanie Ucko on taking RevOps from a pre-IPO startup to a public company — SOX, quote-to-cash, and building to a post-IPO standard
Guy Rubin on Ebsta's 2025 GTM Benchmark Report — ruthless qualification, the 11x velocity delta, expansion revenue, and why you fix dirty data with a machine, not sellers
Michael Preuss on active leadership, AI-first teams, and building in the wartime era
David Weiss on matching the methodology to the motion — and why fundamentals beat silver bullets
Pratz (Origin) on bringing consultant-grade hypothesis-driven problem solving to RevOps
Sophie Buonassisi of GTM Fund on the surfer/wave/surfboard framework, earned secrets, what real traction looks like, and the fundraise red flags investors can't unsee
Christina Brady on how Luster diagnoses and predicts sales-team skill gaps before they erode revenue
Dan Friedman on building Moxie as an all-in-one, running a sub-10% go-to-market team, and winning an embarrassingly small TAM
Bernardo Alves on the three numbers every partnerships team has to measure — production, cost-to-carry, and cannibalization
Anthony Enrico on the layered scorecard for judging whether a RevOps team is actually working
Bernardo and Anthony Enrico on the three metrics that tell you if you'll hit your number — and how to calculate them without fooling yourself
Anthony Enrico and Bernardo Alves on what a VP of RevOps actually does — strategy over firefighting, owning the operating plan, and the cadence from annual to daily
Cameron Legge and Anthony Enrico on when to start RevOps, the first hires, and which executive it should report into
Tim White on why partnerships are a give-to-get game, a strategic-acquisition on-ramp, and a relationship business you can't fake
Cameron Legge on designing fair, efficient sales territories for B2B SaaS
Tom Miller on the value exchange event, operating plans, and engineering repeatable winning
Bernardo Alves on chart crimes, cherry-picked metrics, and why data lies the moment you look at it
Anthony Enrico and LeanScale engagement managers Bernardo and Cameron on why most forecasts are wrong — and the simple fixes that get you one step closer to the truth.
Cameron Legge uses a basketball coach's playbook to explain why sales and marketing keep two scoreboards — and how to merge them into one
Cameron Legge on why customer success is your business's front porch — and its most underrated growth engine