Sales Leadership

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.