The Three Whys
A simplified qualification framework of three open-ended questions: why buy anything, why now, and why this vendor.
Go-to-market strategy is how a company reaches, wins, and expands customers — the ICP, segments, motions, pricing, and positioning that fit together. Strong GTM narrows focus, matches the motion to how customers buy, and stays tightly instrumented.
A go-to-market strategy is the plan for how a company reaches, wins, and expands customers — the ICP it targets, the segments and motions it uses (product-led, sales-led, partner-led), its pricing and positioning, and the operating model that ties them together. Strong GTM strategy narrows focus to a defensible niche, matches the sales motion to how customers actually buy, and stays tightly instrumented so the company can tell what is working.
Original research touching GTM Strategy. Each study states its sample and method.
A B2B SaaS benchmark is only comparable when the denominator, the panel, the statistic and the time basis all match. Run these five checks in order — …
Most "state of the stack" reports are self-reported surveys. This one is reconstructed from what these companies actually operate — and adjusted for a…
The market sorts by altitude — from high-margin strategy/IP at the top to commoditized ops delivery at the bottom. Altitude predicts M&A destiny: the …
All figures from our own reconstruction of SEC Form D filings, 2014–2026. Cohort-level results use Series A vintages 2014–2019, which have 78+ months …
Series B vintages 2014–2019 (n = 645), each observed for 78+ months. Median detected Series B is $25.9M and median graduating Series C is $55.0M — bot…
How LeanScale runs delivery where GTM Strategy is involved.
Most playbooks are heaviest in Build. This one is heaviest in Blueprint — by a mile. Plan your time accordingly. 1 Blueprint Mine their systems for ev…
Every GTM Lifecycle project moves through the same four phases. Know what you produce in each one. 1 Blueprint Research their systems & company. Surfa…
Light on meetings, heavy on up-front analysis. Most of the value lands before the discovery call. 1 Blueprint Research inside + outside their systems;…
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…
Alignment between sales and marketing requires a shared vision, common goals, and an agreed way of measuring success. The recurring obstacles are conf…
Marketing operations is the function that makes marketing measurable: it owns the systems, the data definitions, and the reporting that connect spend …
Most sales and marketing conflict traces to process rather than personality. The recurring faults are inconsistent data definitions and unclear routin…
Alignment is a hiring outcome as much as a process outcome. The people who sustain it bring the functional skill, the experience of operating against …
Alignment is built in five steps, in order: reporting structure, the right people, a clearly defined Go-to-Market process, an incentive structure that…
Interviewing a sales or marketing leader for a Go-to-Market role means testing cross-functional ability, not just functional depth. The questions prob…
In marketing, an SQL (Sales Qualified Lead) is a prospect judged to be a good fit for the product and ready for direct sales engagement. The definitio…
Customer lifecycle stages track the relationship after the deal closes, through onboarding, adoption, expansion, and renewal. As with the earlier stag…
The Go-to-Market lifecycle is the full customer journey expressed as one connected set of stages, from first touch through renewal. It works when ever…
Lead lifecycle management tracks a potential customer's progress through the top of the funnel. Their value comes entirely from entry criteria: a stag…
Lifecycle measurement is what turns stage definitions into a working system. Once every stage has entry criteria, conversion rate and time in stage ca…
A proof of concept is a lifecycle stage with its own entry criteria, not an informal trial. Running one well means designating which prospects qualify…
Sales stages are the backbone of forecasting and pipeline reporting. Each needs explicit entry criteria and a qualification methodology behind it, so …
There are three ways to build a growth model. Top-down starts from a market or board target and works down; bottom-up starts from rep capacity and wor…
A growth model is only as good as the assumptions inside it, so those assumptions are captured explicitly rather than buried in formulas. The method i…
Segmentation determines whether a growth model reflects the business or averages it away. The usual cuts are firmographics, geography, sector, and pro…
A growth model works backward from a revenue target through bookings, pipeline, leads, and awareness, so each layer states what the one above it requi…
A customer success plan sizes the retention side of the growth model. It starts with customer segmentation, then sets service level agreements, health…
Jack Jackson on building and sustaining culture through hyper-growth — what holds as headcount compounds, what breaks first, and how operating norms h…
Justin St. Louis Wood, an operator who has built and scaled Go-to-Market functions, on the path from foundational operations to an AI-driven motion — …
A conversation on building a growth plan a board will actually accept: how to construct the model, which unit economics carry the argument, and where …
A conversation on Go-to-Market strategy when every competitor has the same AI tooling — where differentiation actually comes from, and which sales and…
Anthony Enrico, a RevOps leader turned founder, on Go-to-Market strategy in the AI era: how the role of RevOps is changing as AI absorbs execution wor…
Guy Rubin, founder of Ebsta, on the benchmark data behind sales and RevOps performance — what the annual report reveals about pipeline, conversion and…
Theo Pavlich on RevOps talent and hiring philosophy: what to look for in a fast-growing Go-to-Market environment, how to sequence the first hires, and…
Steve Denner, VP of RevOps at Owner.com, on running a lean RevOps function with globally distributed contractor teams, and where AI genuinely accelera…
Sophie Buonassisi, a marketer turned venture investor, on how Go-to-Market strategy is evaluated from the other side of the table — what investors loo…
The CEO dashboard answers whether the business is on plan, in as few numbers as possible. The core set is ARR, new business bookings, SQL volume again…
The customer success dashboard measures the health of the base and the capacity of the team serving it. Customer health by segment shows where revenue…
The executive dashboard puts marketing, sales, and customer success on one surface so the leadership team reads the same numbers. Closed won new busin…
Funnel analytics exposes where deals stall by measuring conversion at each step — MQL to SAL to SQL to Closed Won — rather than looking at the endpoin…
The marketing executive dashboard connects activity to pipeline. Conversion rates, created pipeline, and MQL, SAL and SQL volume by region show whethe…
The sales executive dashboard is built for the forecast conversation. Aggregated metrics and goal tracking give the top-line position, pipeline overvi…
Fair territories come from valuation, not from geography. The sequence is: define the Ideal Customer Profile, identify data sources to score accounts …
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…
The RevOps Flywheel is LeanScale's operating loop, run in four steps: adjust the growth plan, augment the growth infrastructure to support it, analyze…
Real engagements involving GTM Strategy.
A software company with a customer base in the thousands wanted to know where expansion revenue actually comes from. Four analysis waves across CRM, p…
A growth-stage cybersecurity vendor had no rigorous way to tell reps which accounts to work. LeanScale built an account priority score, a competitor-d…
A growth-stage AI company had no scored view of its market, so reps picked accounts on instinct. LeanScale built a weighted ICP matrix, the enrichment…
A financial-services technology company had a mature CRM in which the fields that actually predicted deal size were mostly empty, and was pushing into…
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.
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.
As AI-generated content becomes indistinguishable from human work, buyers trust less of what they see and move toward signals that are harder to fake and more authentic.
The domain is the one brand asset a business fully controls that connects its website, email and advertising, so it is the point where customers can check who they are dealing with.
Content published on a platform subdomain, social page or deploy link builds the platform's brand equity and search presence. Content on a domain you own builds yours and can't be taken away.
A short, concise, memorable domain is the best way to move someone from a physical touchpoint, such as a billboard, invitation or subway ad, to your site.
With hundreds of extensions, a registry's channel job is to surface the relevant extension at the moment a buyer is making a related choice, not to compete with .com on the homepage.
A channel-only go-to-market for a large portfolio of products: hundreds of SKUs sold through a limited set of storefronts, where the work is merchandising, co-marketing and promotion at the partner's point of sale.
Trust in a sales or partnership relationship requires a person on each side who is accountable for making it work. It can't be one human trusting an AI or a nameless entity.
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.
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.
In an agentic stack, systems of record that hold critical context become infrastructure that agents use, and tools that exist only to make other tools easier for humans to use disappear.
Phase one was broad experimentation with pilots, tools, models and home-built agents, ending in a token bill nobody could tie to output. Phase two is a governed control tower that executes a small set of hero workflows.
A layer that connects the best LLMs with an enterprise's process, brand context, guardrails, tools and integrations so agents can execute the workflows teams spend time on today.
Avoid committing to a single model provider for the same reason large companies avoid a single cloud: the best model for each task keeps changing.
Design AI access in three layers from day one: shared organizational context everyone can see, permissioned layers within it, and individual data that is not shared.
A tool that stores critical business context has staying power. A tool that exists only to make another tool easier for a human to use does not.
Using AI without guardrails pushes review and standard-setting onto whoever is downstream, creating a tax on the organization's time and on the brand.
Founders who take on hard problems succeed at a higher rate than those chasing easy ones, because easy problems attract saturated competition.
As AI fatigue grows, people will pay more for human interaction on things that matter, and AI's role shifts to the operational work behind the human relationship.
Three conditions that must all hold before a business can sell: the business is ready to be sold, the market is ready, and the seller is ready. The seller's readiness is the most important and the most often missing.
Every owner leaves their business eventually, through one of five doors: pass it to their kids, give or sell it to employees, sell to a third party, shut it down, or go bankrupt.
A business is transferable only when its relationships, decisions and daily work belong to the business rather than the owner. If the relationships sit with the owner, it is a job, not a business.
The most expensive employee is one who shares the owner's strengths and blind spots. Hire for the gap instead.
Translate an income goal into an hourly value and judge every task against it. N3 coined the phrase for its own team.
A business is sold once to the buyer and again to the buyer's lender, and the lender requires clean books.
A buyer pays for what the business will do after the handover, so past profit counts only as far as it predicts future profit.
A transaction creates value only if the combined company is worth more than the two apart, through shared customers, sales effort or assets.
The buyer acquires a majority stake and the seller rolls the remainder back into the business, sharing in the growth and in a later sale.
N3's sequence for selling a company: screen the client, populate the data room, write the confidential information memorandum and a blind teaser, approach a pre-screened buyer pool, sign confidentiality agreements, run buyer meetings, collect and compare offers, then complete due diligence.
Every delay between LOI and close raises the chance that a deal falls apart, so sellers should prepare documents in advance and protect the timeline.
Ask whether the business would run for 90 days with the owner away and without a phone or laptop. Since almost nobody can, take one week off under the same conditions and fix whatever stalled.
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.
Frontier AI models are a Formula One engine every company rents on equal terms. Competitive advantage comes from the map, a company's own definitions, owners and connected data, not from horsepower.
Measure the revenue a go-to-market organization produces per unit of what has already been spent on it, and improve it through conversion and cycle time rather than new headcount, pricing or leads.
A company's business logic written down in plain English in one place AI can read: what win rate means, how bookings are counted, what qualified means.
Every metric gets exactly one owner, a named human rather than a team: whoever has to defend the number in the board meeting.
The connections between a company's data: contracts to the right opportunities, to the right accounts, with the right people on them.
Never let the model author business logic. People write definitions in plain language and AI converts them into structured formats such as YAML.
A zero-budget start: write down the 20 definitions every reported number depends on, put one name against each, and write down where each number comes from.
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.
Rather than hiring a single go-to-market engineer, find a naturally curious problem-solver in each department and give them the tools, a shared context layer and a builder's playbook. Together they form a tiger team that builds from inside the problems.
An AI-native go-to-market approach: build and validate the context layer (the ground truth) before generating any artifacts from it. Model quality is not the constraint; the context the model operates from is.
A step-by-step build for teams with little AI or engineering background. Audit the content, determine what is true today, organize what survives into markdown files, have an AI restructure it into a knowledge graph with keywords and relationships, then host it as a custom connector the team can plug into.
An operating rhythm that keeps a context graph accurate: ingest skills that stage new material as nodes, a graph-health skill that checks every node, a health dashboard, a weekly Friday cleanup and a bigger monthly truth pass.
AI adoption should follow the customer lifecycle in waves: account intelligence first, then deal acceleration, then pipeline monitoring, then post-sales. It should not start with content generation.
Build the small, purpose-built tools that only work with your own stack and that no vendor would ever put on a roadmap. Buy, and keep, the compliant systems of record the rest of the stack integrates with.
Make the case for tools or headcount the way a rep sells a deal: multi-thread across department leads, find cross-department value and overlap with the current stack, and build the business case and ROI story before presenting.
Before backfilling a seat, ask whether you have adequate coverage and activation across a finite market. If you do, invest in enablement and pipeline for the people already performing instead of adding more of the same role.
Model intelligence and business context are separate problems. Vendors keep adding horsepower; only the company can supply the map. Anthony's summary: more horsepower won't build the map, more intelligence won't give you the context, and making Usain Bolt faster won't fix the toddler leg.
You are effectively hiring your AI models every day, and each day is their first. Without a persistent foundation, teams are stuck re-onboarding them over and over.
The most effective way to get more out of a go-to-market investment is to raise yield: increase conversion rates and reduce time in stage. Small gains compound, and they are the business case for investing in the data model.
Connecting the dots across and within systems, so the AI knows which records belong together when it looks at a person or account. The crawl-walk-run starting point is to make the CRM your first context graph.
Measure AI by output relative to tokens spent, not by volume of usage, and design the data so agents can hop between connected records instead of indexing whole databases.
Humans write definitions in plain English. AI may format them (Google Doc to YAML to GitHub), but it must never decide what a metric or a good renewal means.
Define first the metrics you'll have to defend in the board meeting this quarter, and make the owner of each metric the person who has to speak to it there.
A four-level progression. (1) Centralized: warehouse and BI layer in place. (2) Resolved: identities deduplicated to one canonical key per account across systems. (3) Defined: 20 to 30 key metrics defined, agreed and version-controlled, each naming the column and filters to use. (4) Retrievable: clean associations and distilled data give quick, cheap retrieval.
Build the data model once so any agent can run on it. Starting with the agent means reverse-engineering a bespoke data model for every agent you build.
A roughly ten-week deployment staffed by five roles: an executive sponsor (usually the CRO, possibly the CEO), RevOps, an analytics engineer, a platform engineer, and whoever runs the CRM. More than half of the time goes to alignment before engineering and agent building.
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.
The default event motion: attend because you have always attended or because you think you have to be in the room, and expect the value to come to you.
Size the format to the share of attendees who are your buyers or customers: at roughly 10% or more, show presence is worth it; at three or four percent, skip the booth and run a targeted suite off-site.
Match the seniority and the specific people you send to the audience that will be there, using CRM data to pick reps by the pipeline that will be in the room rather than by event skill.
Replacing the common 3x event ROI target with an 18x or 20x bar, measured against closed-won booked revenue rather than pipeline.
Measuring an event over the six-to-eighteen-month period in which its true impact actually lands, instead of on booth leads scanned during the show.
Vendelux's data thesis: build the most robust data set of where people and companies are going to be, combining confirmed attendee data with a predictive engine, then overlay a customer's CRM on top of it.
Treating a multi-day event as a set of activations, each with a stated goal and a defined audience, staffed by the right internal people and scheduled around the event's own agenda.
Every buyer relationship at an event has to survive three phases — reaching out and booking before the show, showing up prepared during it, and following up after. Failing any one produces zero value from that buyer.
As AI avatars become convincing, being physically in a room is the only way to verify that the person you are buying from is who they say they are — making in-person the channel that carries trust.
Map the big tentpole events that matter to your market first, then work down and fill the remaining calendar with roadshows and local activations.
A machine- and human-readable description of what is in your data, deployed alongside the data itself: a SQL model definition plus a YAML file carrying the meaning, provenance, calculation choices and enumerated values for every field.
If you read your own semantic data and don't get clarity from it about what the data actually is, neither will your AI.
A way of organising a data warehouse in three layers. Bronze is a raw one-to-one copy of source data. Silver is cleaned and sanitised — fields extracted from JSON strings, readable date formats, human-readable column names, only the columns you need. Gold combines multiple tables into the final artifact used for tracking and reporting.
Living mostly in the silver layer, producing artifacts freely, and letting an artifact's survival through real business change decide whether it earns a place in gold.
The recognition that an AI pipeline is mostly traditional software: a query handler script, an entity lookup, graph traversal, packaging — and only at the end a model call.
Sequencing infrastructure by maturity rather than building it all at once: hard-code context into skills while proving value, add a vector database when unstructured volume grows, and consider a graph database only when your semantics are held together by brute force.
Choosing models by what task they are fine-tuned to do well rather than ranking them on a single intelligence axis.
Structuring a combined data and revenue operations team so each ops head operates as a product owner, with analysts who are AI engineers and other technical people at their disposal, plus the business strategy and context from the sales or CS leader they partner with.
Replacing the sprint bucket with a triage question asked before anything is scheduled: what is the likelihood that this can hurt anything or cause any permanent damage? The assessment is done agentically and its output routes the request to one of three delivery tracks.
Track one is an experience-layer skin change on a custom app that touches no metadata, flows or business logic, creates no security or performance issue, and can go straight to development and out. Track two is a small metadata update that still needs a human in the loop but runs on demand. Track three is project work that resembles the agile process the team already runs.
Gate one is an agent modelled on the teammate who is best at interrogating a brief — trained on that person's comments and transcripts of them ripping briefs apart — which forces a request back to the underlying why and the value. Gate two is the architect reviewing the solution design.
Giving each role — SDR, BDR, account executive, launch specialist, integration specialist, strategic CSM — a fully custom experience layer that can be modified without touching metadata or business logic.
Holding business logic, automations and plumbing under tight control while deliberately experimenting with ways to open up the experience and application layer — including hosting internally built user creations the way Vercel hosts small projects.
A baseline ratio of go-to-market headcount to RevOps headcount used as the starting point for an investment conversation, with any deviation from it tied to particular metrics.
Deliberately making your first dollars-and-cents conversation with finance one where you protect budget — flagging a cheaper software swap, consolidating contracts — so the relationship is established long before any request for resource.
Converting declarative Salesforce configuration to Apex on the belief that it is easier for an LLM to manage the whole system the way it would a code base, replacing flow diagrams with SOPs and generated Mermaid diagrams as the documentation layer.
Writing down the tactical detail of how you personally do the job — call volume, timing, follow-up, organisation, the funnel and its conversion rates — until what looked like personality turns out to be a repeatable recipe someone else can run.
The point, usually three to six months in, where a rep stops obediently executing the playbook and says: I get it, I know how to do this, and I'm going to bring myself to the job.
An exercise in which a rep writes what their manager, peers and customers will say about them when they leave the job — and then works backwards to the behaviours that would earn it.
Translating the qualitative reputation you want — responsive, honest, knowledgeable — into stated numeric service levels, then publishing them to the people who will judge you by them.
The table-stakes contract Cole gives anyone on a revenue team he leads: know what good and bad performance look like and be aligned with your manager on it; be compensated fairly; be treated with respect; have the tools necessary to execute the job.
Running strategy by objectives at the leadership level — four to six priorities aligned to the founder's vision, reviewed with leaders every two weeks — while getting far more prescriptive about activity expectations at the individual rep level.
Proactively catching a high performer's base and OTE up to what the role is now worth, rather than waiting for them to lobby or for a competitor's offer you would then match.
Cole's rule for maturing leaders: people will roll problems to your feet, and the moment you pick one up you own it — so choose deliberately rather than reflexively.
The moment a career stops being a ladder of obvious next steps and becomes a set of trades — once basic needs are met, every promotion is a compromise between satisfaction, impact, title and compensation rather than a straightforward step up.
The five ingredients Cole weighs in any job — compensation, title, industry, leading people, and impact — tested by asking whether more money, a better title and a different industry would make you happy if you led nobody and felt no impact.
Joey's view that the live conversation is the most valuable unit in go-to-market. Data and dialers are the subatomic particles, and the conversation is the atom you have to stack to build anything valuable. He also calls cold calling 'conversational advertising' — delivering a tailored ad to an intended target and getting a reply.
Outbound succeeds or fails on four things: the list (right accounts, right contacts, good data), the messaging (right message to the right contacts), the rep (ramped, trained, doing the right inputs) and the follow-up (systematic circle-backs on conversations that did not convert).
A cold call structure where the first gate is an honest opener that signals a cold call and asks for help, and the second gate declares the reason for the call. It then offers two buckets of pain for the prospect to self-select into, followed by a tight pitch, a call to action and a correct disposition.
An idea Joey credits to Ryan Reisert: a rep doesn't need to be memorable on early cold calls, but must not be forgotten when it is time to be remembered.
The ceiling of any outbound effort is the quality of the list — primarily the targeting of accounts and titles, with accurate contact data as a subcategory — so list building must pass a quality assurance check before it reaches the floor.
Account research from AI and third-party signal tools, compared with an intel-gathering (IG) report built from real conversations with people across the target organisation.
A shift away from large, low-paid, high-volume SDR teams toward teams half or a quarter of the size, made up of highly paid specialist conversationalists who stay longer because they are more effective.
A role Joey has run for about two years: an SDR who can book meetings from intercepted inbound but may not book meetings on outbound. Their outbound job is to have conversations below the decision-maker level inside target accounts and gather intel for the AE.
The share of a prospect list you will ever reach by phone if you keep calling it. Joey says for 1,000 prospects it usually never exceeds 200, no matter how many rounds you dial.
TitanX's model triangulates telecom and carrier, consumer and professional data to answer three questions about a number: is it the prospect's, is it active, and how does it respond when unfamiliar numbers call it?
Voicemail rules that depend on answer intent: skip voicemail on high-intent prospects, leave voicemails and AI-screener messages on low-intent prospects, and point voicemails to the email you sent.
Joey's position that outbound itself works and a failing motion reflects execution, because outbound is continuous experimentation — much like a PLG motion — run inside the four containers of list, message, rep and follow-up.
Automate the back of the house — administrative, repeatable, rule-bound work — and keep humans in the front of the house, where the business touches customers, prospects and the market.
When channel headwinds reduce effectiveness — blacklisted email domains, LinkedIn throttling, spam-flagged phone numbers — teams try to make up for it with effort, raising volume to recover their previous results.
Power dialing places one call from one number to one person. Parallel dialing places several calls at once, connects the rep to whoever answers and hangs up on the rest.
Carriers such as AT&T, T-Mobile and Verizon share data and score outbound numbers, which rise or fall with dialing behaviour — much as Google and Microsoft blacklist spam email domains.
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 more a team automates a channel — content packs, personalised cold email at scale, AI-written comments — the less trust it builds, because the patterns become recognisable and the audience discounts them.
Because Reddit's revenue depends on the quality of human content rather than on ads, pressure to keep content human runs through three layers: the company, the moderators who can lose their subreddits, and the members who leave when quality drops.
Prioritise a small number of high-value threads — large subreddits, fast-moving discussions likely to be referenced by search and AI assistants — and write genuinely human content, instead of commenting at volume.
Building karma and credibility by browsing relevant subreddits and commenting only when you have genuine value, a take or advice to share — and saying nothing otherwise.
The karma threshold — typically around 50 to 100 — that most subreddits require before an account can post, earned when people upvote its comments and posts.
Never share links or products until people ask; when you post, write about the problem you solve with real insight, then follow up by direct message with the people who engage.
Lila's model for where SaaS goes when anyone can build a product: win on distribution, deliver at a fraction of what it would cost the buyer to build, and produce value quickly without a steep learning curve.
SaaS companies are increasingly service companies: they turn hard-won domain expertise into something repeatable, much as a consultancy builds frameworks, because the software itself is no longer hard to build.
Replacing expensive frontier-model calls with small, task-specific models — such as quantized open models — that cost a fraction as much while retaining most of the intelligence for that task.
There is a ceiling on how much more efficient a process can become, but almost no ceiling on how much more effective it can be — so the bigger prize from AI is doing the work better, not just cheaper.
Scenario selection, product configuration, commercial terms, and a locked review step — designed around what the front-end user must do rather than how the plumbing works.
Treat guided selling design the way you would treat replicating any top performer: go into conversation intelligence, break down how the best sellers actually sell, and encode that rather than an idealised process.
The binding constraint on out-of-the-box quoting is not what it can produce but what it fails to prevent. Restrict the options a scenario allows rather than correcting errors after the quote goes out.
Before recommending anything, map CPQ, contract lifecycle management and billing/subscription — plus ERP or accounting where relevant — and confirm they can communicate flawlessly.
Automate granular alerts for the things you expect to go wrong — an invoice schedule that has not appeared, a billing date that has slipped — instead of reconciling on a quarterly cadence.
Running founder-led demos primarily for product feedback and word of mouth rather than for the revenue they close, on the basis that the calls simultaneously generate top-of-funnel, brand and a build loop with the product team.
Bring in the sales leader before the first reps, because founder win rates reflect easy early adopters rather than a repeatable process, and the leader is the one who can build the process and hire against it.
Hiring people who have personally lived the customer's problem, so their story lands on every call and their judgement about the space is earned rather than briefed.
Community fails when it is treated as a category rather than an offer. It needs specific value props and rituals — a recurring event, an outcome, a transformation — designed the way you would design any other business.
An audience is a one-to-many following measured in followers and engagement. A community is the down-funnel subset that pays and connects with each other, and it is usually where the actual business lives.
Renaming RevOps to reflect what the work has become — building agentic workflows and infrastructure across the company — rather than keeping a title that no longer describes the job.
Surfacing context (information you could gather yourself, more slowly), process (an end-to-end workflow the skill now owns entirely), and infrastructure (maintaining the terminal, folder structure and the system itself).
If a process requires more than three tools, rethink the workflow. If more than one person follows it, it has breadth worth capturing. If you say or do something more than three times, it should be a skill.
The stated problem and the real one differ. Nobody says they cannot get follow-ups out on time; they say they are up late on email and always feel behind. The second is the pain point to build against.
For each CRM field, the agent returns bullet points of times someone explicitly said the thing, written so it cannot be copy-pasted, with a rule preventing it — the human rewrites the entry.
If you removed AI from a workflow and would still get the same output, AI only made it faster — you have not redesigned anything.
A wrap skill that summarises decisions, updates a cache and writes a compact handoff file at the end of a session, paired with a pickup skill that resumes exactly where it left off after clearing context.
The single-player experience — one person with a folder, a harness and full access — is already excellent. The multiplayer experience, requiring governance, permissioning and personalisation at scale, barely works.
Individual agents and skills recreate the pre-SaaS spreadsheet problem: everyone with their own formulas, their own data, arriving at meetings with different numbers.
Children in an unfenced schoolyard stay close to the building; children with a fence range all the way to the boundary. Constraints expand exploration rather than limiting it.
Push centrally-controlled skills out like a web deployment, but have them live inside each person's own harness, so central updates land without overwriting accumulated personalisation.
Agents with a name, a job description, a defined skill set that can run on a schedule or a trigger, and capability tiers — rolled out to managers like a new hire class.
Review the actual day in the life of sellers across the last hundred meetings and threads, identify the missed moments, derive the recognition insight, review the automation granularly, then deploy edits across every personal harness at once.
The large stack decisions are determined by company characteristics rather than chosen — headcount decides the CRM, the pricing model decides whether metering exists.
Enterprise Salesforce suite; HubSpot growth stack (the all-in-one default under 200 people); modern AI-native lean stack (deliberately thin, Clay and a warehouse doing the work); dual CRM in transition (Salesforce and HubSpot in parallel, mid-migration or permanently split after an acquisition); and the consumption stack (usage billing wired to real metering).
Tier one — CRM, marketing automation, enrichment — table stakes at any stage. Tier two — sales engagement, CPQ, warehouse, routing — added when the motion demands it. Tier three — next-gen CRM, AI agents, usage metering — the frontier.
Prioritise the unglamorous systems between revenue and the invoice — metering, quote-to-cash — over more visible tooling, because those are the ones nobody funds until they break.
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.
A product-led company can layer an enterprise motion on top of an existing consumer-grade acquisition engine relatively easily; a sales-led company attempting the reverse faces cultural, financial and capability barriers that compound.
Holding the point of data capture justifies expanding into every downstream step that capture enables — enrichment, routing, segmentation, payments.
Reserve for enterprise the things only an enterprise genuinely needs — data centre location, security and privacy, scale, administration and SSO — rather than the things that are simply most valuable.
Fence off a defined budget, state up front what success looks like and how it will be measured — usually recognition rather than new business — run it, then hold an honest review including the option to stop.
Hiring a credentialed practitioner from the buyer's own world — a discipline PhD, or someone who held the exact job at a target account — to act as a consultative partner across pre-sale and post-sale.
Invest against demonstrated signal in increments rather than scaling ahead of proof — the opposite of hiring fifty AEs as a growth strategy.
When output metrics — forecast, ACV, deal velocity, quota attainment — fall short, the cause is almost always upstream, so the reporting must reach pipeline generation at rep and campaign level.
The connective tissue agents run on — definitions, data model, skills and workflows — built and maintained as an operating function rather than assembled per project.
An agent pointed at a new client's connected data on day one, running the full teardown — funnel conversion by stage, stalled deals, rep coverage, quietly dead pipeline — and writing it up against the playbook in brand voice.
A quarterly review where unanticipated client questions are answered live from the client's own data and definitions, rather than deferred to a follow-up.
Three background agents operating the delivery business itself: project management turning call transcripts into scoped tasks, customer health reading transcripts and Slack for account signals, and team evaluation watching delivery quality and coaching needs.
Build the context graph first — the semantic layer resolving definitions, motion, plan and identity across systems — then build the skills, plugins, workflows and interfaces on it.
Measuring a customer-facing agent by how many people it prevented from reaching a human, rather than by the outcome the interaction exists to produce — satisfaction, conversion or revenue.
A layer that classifies and analyses every customer-facing conversation across email, chat, text and voice, used as an observability tool before any agent is built and as the foundation the agent stack sits on.
Voice realism is commodity and improving on someone else's release schedule; behaving like an effective operator, learned from a specific company's own conversations, is the durable differentiator.
Identifying the highest-performing reps automatically from conversation data, extracting their playbooks — jokes, analogies, phrasing for complex products — and reproducing those tactics in the agent.
Eighty percent of the work produces an impressive demo; the remaining twenty is unglamorous edge-case handling that only experience and failure supply.
Agents running the work that used to be non-humanly possible — the analysis nobody had time for and the answers that took a data team three sprints — on demand, in plain English.
ICP analysis cross-referencing deal size, sales cycle and six-month retention; a messaging teardown against recorded sales calls; and a live pipeline diagnostic run inside the forecast meeting.
Shared definitions, identity resolution, the plan, and memory — the four absences that make raw AI on a CRM return confident wrong answers.
Competitive advantage comes from constant recalibration during the quarter rather than from headcount or tooling — discovering you were wrong while it can still be changed.
Multiply each possible outcome by its probability and sum them: a $100k bet with a 50% chance of $500k and a 50% chance of zero has an expected value of $250k. Then check it against opportunity cost and against whether losing is survivable.
Judge a decision by the quality of the reasoning available at the time rather than by how it turned out — while treating an improbably long losing run as evidence the process itself is broken.
A decision has broadly known outcomes — eggs or yoghurt, water or coffee. A bet has material variables outside your control. Most business calls are bets that were never priced as such.
Master the basic disciplines first — they make you better than ninety-five percent of beginners — and only then work on reading signals, which is genuinely advanced and does not matter until the fundamentals are automatic.
Cost of the investment plus a rough estimate of the time it consumes, against a target number of leads at a target ACV. Three or four significant figures is close enough, and the model takes about ten minutes.
Declining to act is itself a bet, carrying the consequence that a competitor takes the opportunity you passed on.
The roughly twelve-month window — eighteen at the outside — between a Series A closing and the company being back out raising, in which the outcome of the Series B is determined.
The three sequential builds that fill the Capital Clock window: instrument every motion before scaling it, multiply the performance of each motion with technology, then prove the result on a segmented scoreboard.
Three layers of context every go-to-market decision runs on: Performance (all GTM data normalised into one semantic layer and tied to goals), Market (ICP, messaging, market conditions), and Process (a living repo of playbooks, hypotheses and decisions).
Efficiency saves money by removing effort; effectiveness wins the market by lifting the win rate, conversion and performance of each motion. At this stage, only the second one matters.
CAC, payback, conversion and sales cycle reported by channel, by motion, by customer segment and down to the individual rep and CSM, rather than blended across the business.
A government-wide set of security and compliance controls a technology company must meet before U.S. federal agencies are allowed to put government data into its system. FedRAMP High carries ~425 controls (versus ~95 for SOC 2) and requires a separate enclave, encryption in transit and at rest, FedRAMP-only subprocessors, and assessment by an accredited third-party assessor.
After a 3PAO assessment, a company must find a federal sponsor — a CISO or CIO within an agency (or the DoD/DoW) willing to underwrite its cyber risk and grant an Authorization to Operate. This is the step where a senior official stakes their reputation and job on the vendor.
Every part of FedRAMP can be solved with enough money and time except getting the sponsor — paying for that is bribing the government and is illegal. Sponsors are won through funded mission owners, program budget holders, networking, and combined top-down (political appointees, agency secretaries) and bottom-up pressure.
FedRAMP is annually re-audited and requires monthly continuous monitoring: a check-in with the government across CVEs, misconfigurations, and overall security posture, with strict remediation SLAs (30 days for high-criticality findings, 90 days for medium).
Doing FedRAMP alone is like buying land in the most exclusive zip code and building your own house (permits, architects, supplies, inspection, forever). Knox instead runs the 'luxury condo building' on Main Street: customers move into a single-tenant floor, bring their own furniture (CI/CD, APM, hyperscaler), and inherit ~80% of the 425 controls plus Knox's agency sponsors.
In an authorization-gated market, the fastest (if not cheapest) route to FedRAMP can be to acquire a company that already holds it, then build on that boundary — rather than pursue a multi-year organic authorization.
Because so few vendors clear FedRAMP, entire federal software categories run on one or two authorized options — ITSM has only ServiceNow and Salesforce; the OMB HRIS RFP came down to Oracle and Workday. Monopoly/duopoly conditions push prices up and product quality years behind commercial equivalents.
The federal government rarely buys anything for under $1M — the contracting overhead makes smaller deals uneconomic — and it purchases for 10,000–100,000 users at a time, favoring vendors already proven at commercial scale.
Before spending a dollar on federal, ask whether you've proven yourself at enterprise scale commercially — the one gate that can't be spun up. Commercial-first companies typically qualify around ~200 people / ~$50M revenue with a few enterprise logos; defense-tech, government-first companies can pursue it as early as 50–75 people.
FedRAMP acts as a pre-diligenced, CYA-grade trust signal in commercial regulated markets. After a certification announcement the first inbound is often a financial-services or healthcare buyer, not a government agency — so FedRAMP behaves like a 'super SOC 2' that differentiates and closes commercial deals.
Defend content investment internally on three fronts: (1) it outperforms traditional marketing on cost per qualified lead, (2) it generates earned-media value the company would otherwise pay Meta and Google for, and (3) it reframes and lowers the cost of the top of the funnel.
Build media brands as verticals that each map to a product hub (marketing, sales, entrepreneurship, AI), starting from a customer pain point and using TAM plus coverage gaps as the signal to add a brand or channel.
For each media vertical, decide whether to build a brand from scratch, partner with existing creators/journalists, or acquire an established brand — driven by the pace of change in the category and whether trusted voices already exist.
After acquiring a media brand, never meddle with the editorial. Meddle with the editorial → meddle with the audience → meddle with the trust. Instead, arm the brand with insights, production, distribution, and growth capital while leaving the content itself alone.
Produce video first, then repurpose the single asset: video → transcript → audio podcast, newsletter, short-form clips, and SEO/AEO blog post. A human owns the original idea at the start, AI compresses the middle (scripting, outlining, clipping, localization), and a human quality-gates the output before it publishes.
Start and perfect your video strategy on YouTube, where scale gives you the richest early signal on what audiences like, then treat platforms like LinkedIn as new distribution for that content — not as derivative afterthoughts — via a data-trained clipping strategy.
At scale, media can sit under a media-believing CMO. But early-stage media should report to the founder/CEO, not marketing — the founder best knows what the brand needs to be, and marketing ownership risks flattening editorial into product-marketing nobody wants to watch.
HubSpot's replacement for inbound marketing: a way to drive compounding growth in partnership with AI that constantly learns and compounds across paid media, creators, and content, rather than relying on keyword-ranking and hand-raiser capture.
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.
Design monetization in sequence: packaging first, then pricing structure, then the pricing metric (what you charge on, and whether forward- or backward-looking), and the price point dead last.
Bundle features around the outcomes a customer is trying to achieve, not around a product-team ranking of which features get used most.
The amount of pricing/packaging complexity a business can carry is capped by its ACV and the type of customer it sells to — high ACV can absorb complex enterprise pricing; low-ACV startup sales demand simplicity.
Classic SaaS had near-zero marginal cost and 80–95% margins; AI reintroduces a real, usage-driven cost to serve that most SaaS-native companies can't even measure, so pricing that doesn't follow cost loses money.
Outcome-based is what you price on; usage-based is how you meter it — and they can combine. Outcome pricing fits vertical products with a uniform outcome and is a trap for horizontal products where the same usage means different things to different users.
You're a candidate for outcome-based pricing only if: (1) you can clearly define one outcome across your customer base; (2) customers agree to and accept that exact definition; and (3) the value of that outcome is similar across all customers.
Make usage-based pricing palatable by combining a recurring base fee with usage on top, wrapped in real-time visibility, per-team spend controls, caps/notifications, and token-level billing traceability.
De-risk migrating your most important customer by working backward: test new pricing on the least-important segment or market, then new business, then run validation interviews with your 2nd–5th customers, plus internal validation with the sales team, before migrating the anchor account.
Treat pricing and packaging as a living product surface, revisited every product-release cycle or sales cycle (whichever is longer) — not set once and left for five to seven years.
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.
A three-layer split of GTM ownership: executives (CEO, CRO) own the WHY (market, category, how we win); the VP of RevOps owns the WHAT (processes, business and operating strategy, scalable design); GTM engineers own the HOW (enrichment, automation, ICP plumbing, execution).
The RevOps role is splitting from a generalist (decent at business and systems admin) into two lanes: the deeply technical GTM-engineering lane, and the strategic decision-maker accountable for the GTM infrastructure overall.
Effective AI transformation must change all three legs at once — people (how teams work and are structured), process (re-architected end-to-end), and technology (AI-first infrastructure and data) — not just automate external workflows.
The central tension for a RevOps leader: keep running the non-stop operating machine (forecasting, pipeline, QBRs, territory and account planning, comp) while simultaneously leading an AI-first transformation — usually with the same headcount and a mandate to use fewer people.
Tessa's methodology scores an operator's or org's AI adoption from 0 to 5 — where 0 or 1 is basic use (asking questions, rewriting an email) and higher levels reach standardized workflows and autonomous agents.
Sort work by urgency and importance: do the highly-important-and-urgent first, delegate the urgent-but-low-importance, and protect time for the highly-important-but-not-urgent — always weighing level of effort per initiative.
Start in 'analog mode' — write your own thoughts, plan, and hypothesis manually using your own judgment — then use AI to find examples, metaphors, and crunch data to back it up and level it up.
A tactical first step for any operator: open a Google Sheet, list the core tasks you do daily, weekly, monthly, and quarterly, mark the level of effort and whether each is manual or automated, then map where AI or an agent could help — and how peers in your role are doing it.
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.
Spend the opening months of a new role absorbing information from two sources — the people on the ground doing the selling and implementing, and the available data — then marry those perspectives into a working theory of what's actually happening before setting priorities.
When you miss a quarter, an intellectually honest post-mortem usually ties the miss to a planning or strategy assumption you weren't honest about — not to near-term deal execution.
Charge only when the AI agent completes the entire job correctly (e.g., reads and infers every field on a document 100% right), so price tracks roughly one-to-one with the value delivered.
Report usage-based revenue to the board by stacking two clearly labeled layers: contracted ARR ('take it to the bank') plus a conservative fraction of the forecasted amount booked as 'estimated ACV' (EACV).
Start with a small, high-confidence use case you know you can nail, prove value fast, and use that win to earn the right to the next project — becoming the customer's primary consideration for what's next.
Qualify and sell the deal first, then run the POC only to confirm the solution works and the teams click — never as a desperate Hail Mary to generate intent that isn't there.
Before offering a POC, square away the MSA, legal and security, and budget, and get both IT and operations (the business side) at the table and excited. The POC then only validates the solution and the working relationship.
Have the implementation / agent-PM team scope the work during the sales cycle, so the buyer meets who they'll work with, gains confidence, and sellers can't over-promise.
Build the revenue plan so every channel has its own win rate and ASP and new-logo ('NUCO') plugs the gap to the number — robust enough that a missed quarter can be traced to a specific assumption that broke, with leading indicators warning you a quarter or two out.
Leadership sets a non-negotiable number; what's up for debate is only the resources required to deliver it. The exercise is iterative and cross-functional, and pairs with a proactive 'what would it take to 10x my org' model run before the CEO asks.
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.
Each new media/computing paradigm — radio, TV, web, social — builds a wholly new advertising infrastructure around it, and advertising never disappears. AI is the next paradigm and will get its own reinvented ad stack.
Instead of one agency-created, brand-approved ad shown to everyone, every person is served an ad generated specifically for them — the long-sought 'holy grail' that AI can finally deliver at scale.
A ladder from a fixed banner to fully generated advertising: start with dynamic text generated to match the conversation, move up to generated assets, then to dynamic UI — the ad format and interface generated per user and per brand.
The publisher's surface area is treated as sacred, and the ad platform optimizes for the end user first, the publisher second, and the advertiser third — because end-user value drives engagement, which in turn makes advertisers happy.
Click-through rate is a misleading success measure because users can click without converting; the right target is the advertiser's actual objective (conversion/value), which should hold steady rather than decay if the ads are genuinely relevant.
The early assumption that 'user asks about shoes → show a shoe ad → they buy' is wrong; buyers research with an LLM but still purchase elsewhere to price-shop and earn rewards. Closing that behavior gap takes time, not just better technology.
The more expensive or complex a purchase, the more a buyer researches first — so AI ads convert best for high-consideration, financial categories (taxes, student loans, credit cards), amplified by seasonality like tax day.
A north star of returning advertising to craft — the era when a Got Milk campaign or a full-page New York Times ad was a genuine piece of art — using generative tools to produce brand-true experiences people admire rather than block.
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.
For AI products, the old default channels — performance marketing and SEO — give way to two new engines: social video that demonstrates the product's output, and visibility inside LLMs (ChatGPT, Claude).
A hyper-compressed planning rhythm: weekly planning against a monthly calendar, no plans beyond the month, and an annual North Star kept as a vision rather than a locked-in plan.
A three-part decision model for a fast-moving market where clean data lags reality: use data where it exists, intuition to see patterns beyond the numbers, and how fast you can learn as a tie-breaker — preferring to go, do, and learn over planning to perfection.
Get surfaced inside models by writing intent-based 'how-to' content built around how a real user searches, in longer formats (a rough 30,000-character bar), and by building presence in the forums LLMs read — Reddit first.
Start with a branded subreddit treated like any social account, then engage authentically in relevant subreddits — see what people ask, help them, and inject product info where genuinely useful. Avoid the 'cheating farm' of over-promising, irrelevant subreddits, and pushy advertising.
The trap of chasing growth without delivering value — reframed as: a KPI to grow by X really means figuring out how much value (Y) you must create to earn it.
Rebrand only when it's existential — required to capture a market you must be in — not because a name feels sexier or slightly clearer. Then sequence the rollout: decide, warn loyal users early, switch the domain silently, then announce.
The three things a startup CEO looks for when hiring from big tech: ability to be hands-on (even C-level does the work), courage to own decisions personally, and agility to change direction fast.
Demystification of the vocabulary: a 'repository' is a folder, and an 'agent' is a folder containing a set of instructions saved as a file. You 'program' or 'train' the agent by writing its SOP in natural language and triggering it with an automation.
The operating system is built on four repos/folders: (1) transcript warehouse (raw call input), (2) customer warehouse (per-account intel and context), (3) GTM library (in-depth playbooks), and (4) company context (brand guidelines, customer avatars, pain points).
A relay where each agent prepares data for the next: a transcript agent annotates and routes calls, a customer-warehouse agent enriches account files from those notes, and a working agent (e.g., territory design) consumes the pre-built context to do real GTM work.
A body of enriched files — per-customer context, playbooks, company avatars and brand — authored so agents can inherit memory. The documents are written for agents to read, not humans: 'made by agents, for agents, used by agents.'
The agent platform (Claude Code, Claude Cowork, OpenAI Codex, Google Antigravity) becomes the central interface for the whole organization because, via MCP, it is tool-agnostic — pulling from and writing to HubSpot, Salesforce, Google Drive, Snowflake, and Intercom.
Because agents can write back into files, every implementation can update the source playbook with new learnings, so the system improves itself with each customer and prospect rather than staying static.
Each major lab (OpenAI, Google, Anthropic) ships three distinct products: the model (baseline infrastructure — GPT-5.2, Gemini 3, Claude Opus 4.5), the consumer app (the browser chatbot for general-population Q&A), and the agent platform (for professionals to get work done).
The capabilities that only agent platforms have and consumer apps lack: a persistent internal to-do list (so the agent works 10–40+ minutes autonomously), the ability to launch sub-agents, reading and writing files on your local machine, permission/plan modes, queued messages, and context compaction.
A repeatable structure for building agent prompts: (1) supply context files, (2) instruct it to launch sub-agents, (3) have it maintain a to-do list, (4) tell it to be token-efficient, (5) direct it to write outputs to files, and (6) frame it to think like a strategist / thought partner.
A token is the atomic unit of how AI thinks (~3–4 characters). The context window is finite working memory holding all inputs and outputs (e.g., 200K for Claude 4.5, 1M for Gemini 3); once full, the agent forgets earlier context. 'Compacting' summarizes the current context and hands it off to a fresh agent with a clean window.
A skill is a folder of files that teaches an agent how to perform a task (make a PowerPoint, an SOP, a PDF, wireframes). The labs adopted a shared skills standard, so you can download skills from the internet or build your own and point the agent at the skill's path to execute it.
Getting an agent platform running in ~5 minutes: (1) download VS Code, (2) install the official Claude Code extension from Anthropic, (3) log in with a $20/month Claude subscription. Restart, click the orange icon, authorize, and the agent is enabled.
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.
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%.
In an AI world, the cost of being wrong has collapsed, so iteration velocity — not first-time correctness — is the dominant competitive advantage in go-to-market.
Do the reps yourself with an AI-built tool and an expert on call, so you compress the failure that an outside agency would spread over months into a couple of fast, cheap weeks.
Any task that looks like one step ('start Google Ads') is really dozens of steps, and not knowing where to start — or which step is next — is what actually stops people, not the tool.
Reverse-engineer every revenue goal from the sales cycle and pipeline coverage, then act with the urgency that math demands.
For AI-native companies at scale, the customization math tips from buy to build once one engineer can build the tool in a month and any coding agent can maintain it.
The durable value in a GTM tool isn't the code — it's the product manager's hard-won knowledge of what people actually do with it: the workflows, sequence, guardrails, and integrations.
Get a paying customer on an MVP or front-end-only demo before building the real product, so you validate that someone will actually pull out a credit card.
AI gets you ~99% of the way, but the final mile still takes human taste, focus, and follow-through — a six-month project becomes four days, not four minutes.
You can only automate a motion well if you understand it cold — which is why AI SDRs built by people who never ran a sales process miss the mark.
The quality of any tool reflects how core its job is to the business that built it — so for jobs that matter, choose the obsessed point solution over the all-in-one chasing more NRR.
Match every hire, tool, and system to your actual stage instead of copying what much larger companies do.
The best GTM advice is focus — narrow the ICP and the product, and get comfortable saying no early.
Since go-to-market process breaks whenever it depends on human compliance, the fix isn't more enforcement (mandatory fields, stage gates) but removing people from the data-capture loop entirely — letting AI listen and populate the system automatically.
Once AI captures CRM data automatically, the salesperson stops being a producer of data (data entry) and becomes a consumer of it — served a prioritized view of what's healthy, what's slipping, and what to work on next.
Adopt in stages: crawl (RevOps connects CRM, call recorder, Slack/Teams, and email, sets team structure and field mappings for a two-way sync), walk (auto-create and enrich records, remove humans from data entry), run (deal-health analysis, agents, and cross-functional data products).
Plot every opportunity on two axes: horizontal = how healthy the deal is (likelihood to win), vertical = how likely it is to close when the rep expects. The quadrants surface safe bets, acceleration opportunities (will close but not this quarter), and firm-decision-date deals where you may not be selected.
A full-reasoning agent wired to every captured touchpoint plus external research tools that executes deal tasks — building a custom ROI calculator to the prospect's own metrics, pulling industry benchmarks, and drafting the decision-maker email.
A per-contact score from -10 to +10 that identifies champions and blockers at a glance, with the reasons and specific quotes behind each. Filtering contacts by ICP persona and a high promoter score produces a live, shareable list of advocates.
Product roadmap signal should come from live sales conversations with the market — use cases, friction, competitors mentioned — not primarily from customer success and existing customers, who are biased because their problem already feels solved.
RevOps problems are hard to solve but remarkably consistent across similar-stage companies — a Series B sales-led company has the same problems and the same fixes as its peers — which is why the function outsources well while sales and product must stay in-house.
As AI and no-code make building products easy, the hard problem shifts from creation to distribution — getting a great product in front of its rightful customers in an attention (eyeball) economy.
An outbound platform architected for AI from the ground up as a multi-agent system — each agent using the model it's best at — rather than a pre-AI product with AI 'slapped on top' via chatbots or plugins.
A workflow where you paste a domain, the system scrapes it, infers your ICP and buyer personas, writes them out as reusable context files, and converts them into a targeted lead list that also powers copywriting and qualification.
Use intent signals (job changes, hiring, department growth, 10-K priorities, life events) to decide who to contact and when — but keep them out of the message. Mentioning the signal wastes scarce email real estate and doesn't impress the buyer.
Replace the standard chain — Sales Navigator for lists, Apollo and other enrichment tools, a verifier, and ChatGPT deep research — with a single AI-native system on a fair, usage-scaled credit model.
Bridge the gap between sellers who understand angles but not tooling and 'GTMEs' who understand tooling but not selling by giving one strategy-fluent operator an easy-but-sophisticated execution system.
Before feeding anything into AI, do the old-school work of identifying your audience and nailing your ICP and personas; AI is an accelerant layered on top of that bedrock, never a substitute for it.
A mid-market-to-enterprise deal has 11–15 stakeholders: the executive sponsor (C-suite), the director-level champion who discovers and evaluates vendors, the end users, and the technical implementers who hold integration veto power. You must speak to every one.
A range from shallow (know the main persona in the buying committee) to deep (true one-to-one: identify a website visitor, enrich them in Clay, pull public psychographics, and send a personalized message).
Research a target account's public data, draft an insight-rich 'we admire you' breakdown, have the founder refine it in their voice and post it, then let the AE reference it live in the deal to accelerate the cycle.
Rather than over-engineering an attribution model, ask 'how did you hear about us?' on the request form, in the disco script, and again in the first or second demo — capturing self-reported touchpoints across the funnel.
Three curated NotebookLM knowledge bases: (1) competitive research (~90 competitors' value props), (2) product docs, release notes, and analyst reports, and (3) ICP/persona research plus Gong pain-point call transcripts.
Pull close-won/close-lost call transcripts into an LLM, extract pain points, convert them to topics, cross ~82 personas by ~50 topics into hundreds of monitored prompts, and let each prompt seed a blog post, white paper, or ad/email copy.
First do the blocking-and-tackling (know your customer, produce content, know your channels and measurement); only then 'abstract' into distinctive, delightful, B2C-style campaigns that break through the noise.
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 three-stage progression: prove genuine product-market fit once (a real problem, consumer-first), then achieve go-to-market fit by making the motion repeatable, then scale it into a 'dynasty' rather than a single lucky win.
Build around a real consumer problem and behavior, deliberately not leading with the novel technology (crypto/blockchain) or a get-rich-quick token.
A trading mechanic where a player offers unwanted items for a desired one; the system real-time-buys the target from one seller and real-time-sells the offered items to multiple buyers worldwide, netting a cashless swap.
Layering successive, lower-friction on-ramps into the economy — crypto, then credit card, then cashless quick trade, then an AI NPC negotiator — so each new rung pulls a broader persona into trading.
A staged handover of asset control from the studio to the player: start closed (assets exist but access is tightly controlled), move to shared responsibility ('you have a key, I have a key'), then to full player control (take it and go, even revoke the game's access).
When AI is integrated properly into how code is deployed and how engineers work, each person effectively gains a code reviewer, a junior programmer, and a security analyst — roughly tripling their output.
Using different AI models to challenge each other's work — e.g., writing a piece of code with Claude and having ChatGPT analyze it in the role of a security compliance officer.
Mythical's build sequence: (1) economic tech — changing the economies inside games; (2) social interaction — new ways for players to compete and play together (Pulse Arena tournaments); (3) open platform — letting outside studios build on Mythical's stack.
A reframe of investor rejection: a no usually reflects the VC's own vision or their LP-mandated 'deal box,' not a flaw in the idea — 'it's not a bad idea, it's just not the idea they have.'
Data silos are structural, not attitudinal: product and billing data sit with engineering or a data team, RevOps sits under go-to-market, and as long as they're distinct teams the data stays separated from the people who need it.
The data-team gatekeeper who deprioritizes RevOps requests as mundane while, in reality, those requests are the highest bottom-line-impact work at the company.
A 'data model' is a curated, reusable catalog of source fields you green-light (authorize) for syncing — built from a database table, a custom SQL query, or a spreadsheet — that anyone can then grab from to sync anywhere.
The single simplest usage field — the date a customer last logged in — predicts churn better than most sophisticated composite product signals.
Segment accounts by product engagement in the CRM and route the play accordingly: heavy users get an immediate upsell script, light users get an education pitch rather than a sales pitch.
A reframe that evaluates every data request by its revenue dimension — collections, overage monitoring, churn avoidance, or upsell — instead of by the data itself.
The practice of breaking cross-team silos by leading with curiosity about the other side's priorities — RevOps asking to be educated on the data team's world, and technical teams asking who's affected and why a request matters — in both directions.
A composite health metric combining the number of deals a rep works, the average deal size (ACV), the win rate, and the length of the sales cycle. Ebsta uses it to quantify the gap between top and average performers.
A seller who influences top of funnel, generates their own opportunities, and continues to own the relationship after the deal is signed — the opposite of the single-purpose-vehicle / hunter-farmer model where customers are handed from one specialist to the next.
A relationship-health score built from observable transactions — meetings, email traffic (inbound worth more than outbound), and call data (longer calls worth more) — deliberately excluding intent and sentiment analysis.
The difference between a firmographic, one-line ICP ('Series A–C startups') and a layered one that adds persona, buyer maturity, investors, and growth rate — and never confuses ICP with TAM.
Requiring every opportunity to carry written, scored qualification, with explicit gates and triggers to move from one stage to the next — and not allowing sellers to skip stages or self-score their own qualification.
The top-performer discipline of converting the fewest opportunities out of discovery on purpose — ruthlessly killing deals that won't close so time and resources flow to deals that will.
AI crawlers split into three types: retrieval bots (take a live user prompt, fetch your content, and pull the answer back — RAG-style), training bots (crawl broadly to train a model over time), and traditional index bots (classic search indexing like Google).
Reframing AI retrieval bots not as noise but as human buyers acting through a machine: the person sends the LLM to read your site on their behalf and receives the answer inside the chat.
Serve two versions of your website: the visually rich experience for humans and a separate, machine-optimized version for AI bots — clean markdown/JSON, schema markup, and supplemental content like extra FAQs — delivered by intercepting bot traffic at the CDN.
AI Engine Optimization (also called GEO) is the practice of optimizing how LLMs retrieve, represent, and cite your brand — a successor discipline to SEO that targets AI answers rather than search-result rankings.
Win the AI channel by creating content for long, specific, bottom-funnel prompts that only your brand (or a very few players) can credibly answer — instead of chasing high-awareness, top-of-funnel keywords.
A two-step operating loop for a brand-new channel: first establish a measurement baseline (which bots, which pages, which prompts, cited or not, versus competitors), then start making and testing changes to learn what moves visibility and conversion.
A growth-marketing foundation — merging the analytical, data-driven side (attribution, reporting, infrastructure) with the creative side (offers, channels, audience) — as the strongest stepping stone to running all of marketing.
Model your target as current ARR + new ARR + expansion − churn/contraction. New ARR is new logos (and new contracts with existing customers); expansion and churn both come from the existing base.
Take the macro ARR goal and reverse-engineer it top-down through funnel metrics (net retention, SQL-to-close, sales cycle, MQL-to-SQL, average ACV) and bottom-up through the resources and team (CS capacity, quota/performance, ramp time, cost per SQL, salaries) required to hit it.
When executives challenge the outputs (reps, budget, pipeline required), don't defend the outputs — send them back to the inputs and ask which specific assumption they'd change: conversion rate, sales cycle, MQL-to-SQL, expected performance.
Because deals don't close the month a lead arrives, the length of the sales cycle dictates when pipeline must exist. A two-quarter cycle means the pipeline for Q3 bookings has to be built in Q1.
A rep is 'ramped' only when building pipeline and closing at full productivity — not when training ends. Ramp time should never be shorter than the sales cycle, which forces you to hire ahead of the number.
The board evaluates the plan not as a sum of initiatives but as unit economics balanced against growth, judging whether the company can graduate to the next funding stage. If it fails that test, the CEO and CFO reject it back to you.
Because you invest in SaaS before results arrive, unit economics degrade when you invest and improve as ROI lands. Plan a trend that grows into the economics the board wants — not a perfect green line every quarter.
Anchor and stress-test assumptions against VC/PE-published benchmarks (win rate by ARR band and deal size, quota-to-OTE ratios, funnel conversion rates) so the conversation becomes 'you vs. the market' instead of 'you vs. the person.'
Replace the static spreadsheet with scenario modeling for sensitivity analysis, live progress-to-target reporting, a core-vs-new-bets split, and a daily sales-tracker email that becomes the company's single source of truth.
There are no silver bullets. Compounding small, daily improvements — messaging, coverage, demos — is what drives real growth: 1% better every day is roughly 37x over a year, while 1% worse is a ~97% loss.
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 founder raises capital only three to five times in a lifetime while an investor does it every single day — so the founder is structurally the amateur. Closing that gap with structure, data, and network intelligence is the mission.
Flowlie's positioning: a behind-the-scenes operating system for a raise — not a marketplace, broker, or middleman — that helps founders uncover the right investors and the right people in their own network to reach them.
The two pillars of Flowlie: a predictive fit-scoring model (version five) that ranks how likely a firm or partner is to be interested, and a network-analysis engine that maps warm-intro paths and ranks each with a 'path impact score.'
The core fundraising philosophy: the outcome is decided mostly by the preparation — target lists, investor updates, relationship-building, and warm-path lining-up — that happens before you ever say you're raising.
Deliberately forward-loading warm-intro requests — scheduling connectors to introduce you weeks out — so investor meetings cluster into a single window instead of trickling in one at a time.
Valley's model for a full outbound loop: (1) find high-intent leads, (2) research them across 60–70 data points, (3) score them for ICP fit, (4) craft messaging in your voice, and (5) send it on LinkedIn autonomously at scale.
V1 outbound: take a filter-based list, enrich the contacts, drop them into an email or LinkedIn sequencer, and wait for meetings at the bottom of the funnel. V2 outbound: intent signals, warm outbound, and enrichment/research/qualification — send 30 hyper-relevant messages and book 10 instead of blasting 30,000.
A converting outbound message must make the recipient feel two things: relevance (it's clear why you reached out to me specifically, not the person next door) and investment (that real time was spent on me, not a one-to-many blast).
Person-level website-visitor identification is only valuable when paired with a layer that researches, personalizes, and sends. Intent should be weighted by visit frequency (repeat visitors over single visitors) and by high-intent pages like pricing, customer, and case-study pages.
Run Valley on autopilot (fully autonomous research, drafting, and sending) for broad, high-volume ICPs and transactional sales; run it as a copilot / human-in-the-loop 'AI SDR intern' (research and drafting, human approves send) for narrow, high-value, account-based motions.
Because LinkedIn caps monthly message volume, the only levers to improve outbound results are acceptance rate and reply rate — which forces teams to improve the relevance of their prospects and their messaging rather than sending more.
A hiring filter that prioritizes innate curiosity and a demonstrated desire to learn over tool-specific experience or a pedigreed, linear resume. Hard skills on the go-to-market side can be taught; curiosity and teachability can't.
Define revenue and go-to-market operations by the actual work someone does, not by whether their job title said 'RevOps.' Many strong operators have the skills and experience under unrelated titles.
Hire for familiarity with the general tool landscape and a proven knack for learning new tools, rather than deep fluency in one platform — because the stack turns over constantly (~3 new MarTech tools a day).
A stage-specific set of interview questions that surface curiosity, resourcefulness, and problem-solving. Baseline: excitement about systems. Specialist: 'a time you used a tool in an unconventional way' + 'the last time you troubleshot an issue.' Manager: 'a RevOps project or tool you're curious about but haven't done.'
LeanScale's two hiring profiles — architects (strategic, engagement-facing) and systems engineers (technical system owners) — plus a live exercise for engineers: after baseline Salesforce/HubSpot certifications, build any go-to-market tool in Lovable or Bolt, time-boxed to a couple of hours.
A tooling discipline: before buying a new tool, ask whether the job can be done with what you already own. Weigh the full cost — operational overhead, cognitive load, and integration risk — not just the monthly fee.
Borrowing theater's 'notes' ritual — where the director publicly lists everyone's mistakes after a rehearsal — as a model for building the thick skin to say 'I don't know' and 'I got this wrong,' then fix it fast.
Because every public SaaS company answers to the same SEC rules, quote-to-cash should be a standardized, out-of-the-box process — not a uniquely engineered snowflake per company. A 'unique' process is a problem to fix, not a competitive advantage.
Instead of a separate CPQ, billing system, and revenue-recognition system integrated between CRM and ERP, run a single platform that handles CPQ, AR/billing, and ASC 606 rev rec — sitting between the CRM and the GL with no reconciliation and one product catalog.
An AI agent that lets any seller generate a compliant quote by typing a plain-English request into Slack (or mobile, email, or the CRM). The agent parses the request, asks for any missing policy-required inputs, applies product rules, and returns a quote PDF.
A business-focused Q&A layer that asks a seller simple questions (where is the customer located, what segment) and converts the answers into the right products, compliance, and discounting — instead of making the rep understand how the CPQ is configured.
Usage/consumption billing comes in distinct models: pure pay-as-you-go (no commitment, invoice on actual use), pre-committed plus overage (commit to a volume like 200,000 API calls/month, pay extra above it), and credit pools (buy a $100k pool and draw down across products, AWS/GCP-style).
A policy-driven method for turning variable consumption into a defensible ARR: for pay-as-you-go, take average consumption over a trailing 3-6 months and recognize a set percentage (e.g., 80%); for committed-plus-overage, the commitment is fixed ARR and overage recognition depends on how straight-line it is and what the auditor will accept (from ~95% down to ~20%).
When a customer adds licenses and renews early, you cancel the current term (crediting the unused period, like dropping a car lease) and restructure into a new term. Done right it's one opportunity, one order form, with credits and proration auto-calculated and reporting that shows it as upsell — not churn plus a new deal.
The design principle that the primary consumer of a CPQ should be the seller, not deal desk or RevOps. Reps should be able to run even complex deals (multi-year ramps, partner margins, special payment clauses) and the entire post-signature lifecycle themselves.
The seller creates an 'order' (draft during the sale cycle, confirmed once closed) and that same object generates the invoice and feeds finance. There's no separate quote-to-invoice re-keying, so numbers can't diverge between what sales sold and what finance bills.
A staged operating model for taking a company from nothing to a running revenue engine: first establish foundations and first principles, then instrument and stabilize, and only then layer in advanced and modern techniques (including AI) to sprint.
On joining, learn the existing systems by using and pushing them to their breaking point, then ship a working V0/V1 before soliciting input — collaborating afterward to fill in scope and context.
A CRM-based revenue-intelligence system resting on three pillars: (1) volume/activity — meeting depth and self-sourced pipeline; (2) accounts — tiering and account quality; and (3) accuracy/validation — clean, correctly-tagged data with automated backstops.
A single consolidated system — often an automated spreadsheet with 50-60 metric tiles rather than a visual 10-12-metric dashboard — organized in three levels: North Star KPIs (board/investor), functional KPIs (six to ten per team, in lockstep), and hyper-specific activity metrics.
Measure sales on the inverse of marketing's volume: only opportunities that pass a hard gate from discovery into 'prove value' count — deals genuinely closeable, and closeable within the quarter — and marketing's targets are pegged to that same gate.
Build custom, proprietary 'hubs' from scratch (e.g., in Replit) that solve a precise business problem and eradicate vendor spend; then transform their outputs into an agent-readable format (JSON) so agent 'spokes' (n8n, Manus, computer use) can run the downstream mission — with a human at the tail.
For any process, first ask whether AI can do the entire thing (path one: hardest but most efficient). If it can't be done cleanly, default to human-first with AI as augmentation (path two).
A GTM platform should be designed from the ground up as one system spanning data, engagement, and machine learning — not assembled by bolting point solutions together — the way a self-driving car is engineered whole rather than by strapping cameras and radar onto an ordinary vehicle.
AI augments the seller rather than replacing them. Duo, launched September 2024, is a human-in-the-loop companion — the rep's Pokemon or Iron Man suit — that learns each individual through reinforcement learning and grows with them.
Amplemarket is 'in the business of matchmaking' — connecting buyers who have problems with sellers who have solutions, so that every time a problem exists the buyer is made aware of the best possible solution.
In non-transactional, high-consideration buying, the purchasing experience — the craft, the care, the reverence for the product — is part of the value itself, and that care transfers to the buyer.
AI lets far more people build, so there will be more companies ('planets') to connect, each with smaller sales teams, and the space between them grows more opaque as creating information drops to near $0.
Every 24 hours the rep lands on a fresh feed of the most relevant accounts and buying signals in their book of business (the Spotify Daylist), paired with a recommended action for each — swipe the lead in or out (the Tinder system of action).
Low-quality, high-volume outbound is not a small positive but an active negative — it burns your domain, your leads, and your single chance at a first impression, signaling that your company doesn't care.
The highest-value trigger is timing — reaching a buyer when the problem you solve is already the last thing on their mind before sleep. You find that moment by composing signals (e.g., 100%+ team growth plus ten open AE roles) rather than relying on any single one.
The intelligence layer is a paradigm shift bigger than the internet, but it's raw power like the discovery of fire. Value comes only when you invent the 'pan' — thoughtful, purpose-built tooling — to cook something with it.
Vendors sell inside-out ('what I know, therefore you must know, therefore I'm best'), but buyers grade you outside-in through their own set of lenses — their pain, prior tools and research — most of which you can't see.
A B2B buyer moves from curiosity/pain through searches, forums, reviews and peers, forming impressions the whole way. Around 60–70% of the journey they build a shortlist of 3–4 vendors, and the best-impression 'number one' vendor at that point wins ~84% of the time.
Two obstacles to becoming number one: marketing complexity — the buyer is anonymous and you can't see when or where their journey starts; and sales complexity — by the time they engage they're highly informed on problem, solution and competitive landscape.
A large language 'thinking' model trained to think like a specific customer's buying committee, wrapped in a synthetically generated company, org hierarchy and pain scenario — a high-fidelity representative of your real buyer.
A buying journey of ~400–600 touch points is organized into discrete 'episodes' (a Google search, asking the community, exploring a vendor website, reading a testimonial); episodes roll up into a journey, and journeys attach to a buying persona.
A sales manager coaches to internal process ('you forgot to book the next meeting,' 'you skipped MEDDIC'); the buyer scores you on impression, not process. Dodging a pricing question the buyer just saw a competitor answer is what actually costs the deal.
AdamX's three products. TopJourney scores your buyer journey episode-by-episode against competitors; TopRep has the synthetic buyer analyze every recorded sales call for patterns; RolePlay lets reps practice live against the trained synthetic buyer.
The moments buried in call recordings where buyers express what they love ('sold on the solution,' 'this beats your competition hands down'). The synthetic buyer captures, de-dupes and ranks them, filtering out noise like 'thanks for waiting' or 'love your Zoom background.'
Reject the freshman-classroom model where every rep takes the same required courses. Coach like athletics: don't teach a strong server to serve — drill each rep's actual weakness (the 'backhand').
Your buyer journey score only matters relative to competitors in the same shortlist. An average journey wins if everyone else is worse; a good journey loses if a rival is better. Winning is measure-improve-measure-improve against the competition.
Reframe underperformance as a people problem, not just a revenue problem: focus on the individual rep and their manager, and stitch together the data (calendar, CRM, enablement) that reveals where each is struggling.
PeopleLens' four-step loop: (1) unify siloed rep-touchpoint, org, and people data into one connective tissue; (2) run proprietary models over structured and unstructured data; (3) render a persona-specific lens (exec, manager, rep); (4) push personalized performance nudges and agents to the front line.
The same underlying data rendered three ways — an exec lens for strategic bets and stack-ranking, a manager lens that diagnoses why a specific rep is struggling, and a rep lens that gives each seller a 360 view of their own outcomes, competencies, time allocation, and nudges.
For decades GTM data centered almost entirely on the customer (spouse's name, pet's name, endless fields). True first principles put the customer on one side, the product at the center, and the rep on the other — bringing the 'forgotten' rep into the equation with their own data lens.
Grow-or-go decisions are usually driven by anecdote in a QBR, not by facts about where a seller breaks down. The biggest, cheapest ROI is the 'massive middle' B-pool; because letting a rep go is roughly 18 months of revenue, personalized coaching that lifts the middle beats cutting.
Attio's product philosophy: the CRM should adapt to how your organization already does business, not force you to change your process to fit the tool.
By syncing your inbox and calendar on signup, Attio auto-builds your network of companies and people, enriches it, and layers on last-touch, contact ownership, and relationship strength — with no separate tool.
A custom record attribute powered by an AI prompt: you write your ICP in plain language and Attio evaluates every inbound lead against it, flagging fit for the rep.
Five standard objects plus unlimited custom objects and attributes, including Workspaces and Users objects that pull product data in, so the schema mirrors your actual business.
An automated workflow that, on every new signup, uses a research agent to summarize and ICP-tag the company, then routes: enterprise to round-robin, non-ICP to self-serve, and ambiguous mid-market/startup leads to a Slack channel for a human to route via buttons.
Attio is both where customer data lands and where you take action on it — you can report on live data, drill into the underlying records, and immediately sequence, task, list, or route them without leaving the tool.
Train a single AI model on a company's own data, then deploy it across every channel a buyer wants — chat, email, and voice — so context and quality carry seamlessly between modalities.
As more teams use AI to send high-volume 'fake personalized' outbound, each individual email becomes less effective — a network effect that runs in reverse, degrading the whole channel as adoption grows.
Remove the email-first form gate from website conversation. Provide genuine value and answer questions first, then weave pre-qualification into the conversation — 'give to get,' classic sales.
The specific questions a buyer asks are first-party intent data that reveals what they care about and are trying to solve — a 'roadmap to close' you can't buy from any data vendor and can only earn by opening the conversation.
Respond to buyers in real time in whatever channel they're using — chat, email, or voice — because the latency in most GTM motions is the human, not the medium. AI can reply within seconds and continue the buyer's exact conversation.
Run qualification logic live in the conversation and route each buyer to the right next step: a highly qualified buyer to an AE calendar, a mid-tier buyer to an SDR, a low-tier buyer to self-service.
Use AI voice around the human moment, not in place of it: after a buyer books a demo, an AI call gathers a few tailoring questions so the human demo is more valuable to the buyer and the rep is better prepared.
Train the model on data a company already has — website, docs, academy, good call transcripts, sales-training material — then refine it in a testing interface where you role-play your own customer and thumbs-up/down responses to tune tone and accuracy.
'Lean' should mean intentional, agile, right-sized structure for your stage — not the scrappy, disorganized, under-structured state most early teams actually describe when they say they're lean.
Import product engineering's agile operating system into RevOps — standups, definitions of done and ready, boards, user stories, QA and UAT stages — as the default way the team works.
A documented onboarding 'course' — tech stack, who-owns-what map, the agile working agreement, definitions of done and ready, systems, and roadmaps — that makes an incoming contractor or agency productive on day one.
Because RevOps has no fixed blueprint and fits differently into every company, assemble your function by borrowing proven patterns from more mature functions.
Divide the customer journey vertically into segments (four, from growth/brand marketing through sales, onboarding, CS, and support) and give each a product owner who obsesses over improving that stretch for customers, the company, and employees.
Dedicate a help-desk-and-comp role (backed by contractors) to absorb the daily end-user questions and recurring commission/quota cycles so developers and admins stay focused on the roadmap.
The recurring cycle where point tools proliferate around the CRM, category winners emerge and go vertical, the stack consolidates into a few big players — and then a new layer (now AI) fractures the ecosystem again.
Own the company growth model and go-to-market performance-to-plan — fully segmented, every way the business can be cut — as the source of strategic leverage that earns RevOps a seat in the room.
A short list of the company's top 'must-be-true' initiatives that the RevOps leader relentlessly surfaces cross-functionally — in every doc, roadmap, and prioritization call — to keep the whole organization aligned.
The career path out of the RevOps 'yes-too-much / no-too-much' trap: treat high-quality technical work as table stakes and win the next level on leadership — building a function that runs without you controlling every part of it.
Structure B2B support around the account as the centerpiece — its timeline, sentiment, history, and stakeholders — rather than around individual, disconnected tickets the way horizontal ticketing platforms do.
In B2B, AI's role is to assemble and surface the full context of an account — pre-sales data, call recordings, CRM history, previously-approved human answers — rather than to generate a single reply to a single question.
For technical, high-context B2B questions, AI should draft a documentation-grounded suggested response that a human reviews and sends — keeping a person in the loop instead of auto-replying.
Automatically convert existing Loom (and demo) videos into complete, screenshot-rich documentation, turning the thin, unowned docs AI draws from into high-quality source material — closing the data loop that makes AI answers good.
A workflow engine (triage, condition-based routing by time zone and ticket type) combined with AI-driven workflows (sentiment-based escalation, SLA-breach alerts) — the layer Tony argues actually constitutes a B2B support system.
Measure the business by revenue per full-time employee rather than by headcount hired or money raised. Top performers run $500K+ per head (versus an old $150–200K benchmark), driven by AI-leveraged operators.
Build marketing, brand, a reliable pipeline channel, and your own sales process before hiring a salesperson. Reps are harvesters of pipeline and closers — not creators of demand.
Land your first sales inside your existing network, then narrow to a hyper-specific micro-niche for whom the product is an absolute no-brainer, and make the economics the best deal of their lives early on.
In an AI-driven sea of sameness, brand generates demand. Aesthetics signal seriousness and a content strategy (written, tutorials, or podcasts) is the modern equivalent of commercials and billboards.
Start on HubSpot as an affordable, pre-built, scalable CRM; stand up Snowflake as the data warehouse for sales, product, and financial data; and report from there (e.g., Looker) rather than overloading the CRM.
Before buying any onboarding or CSP tooling, define exactly what first-time-to-value is for your product and sprint to reach it as fast as possible.
Let AI take work to roughly 90% and reserve the last mile for a human, so output sounds authentic and nothing goes out that doesn't resonate. The goal is producing better, not just producing more.
Treat go-to-market like health and fitness: track leading-indicator 'biomarkers' (onboarding speed, churn by segment, new-rep ramp, pipeline created, conversion) instead of reacting to lagging results after they break.
Each stage of growth — validation, product-market fit, product-channel fit, scale — is exponentially harder than the last, and you can lose product-market fit at every technology wave (on-prem to cloud, cloud to SaaS, SaaS to AI-native).
Design your offering as the thing you personally wished existed in your prior role, then scale the 'love' by hiring people better than yourself, guarding culture and integrity, and getting process and finances tight early.
RevOps is the business's family-clinic generalist — no single specialty, but a stream of problems from every function daily. Its job is to diagnose root causes by stepping into each function's shoes, not to treat the presenting symptom.
Take a reported symptom and break it into workflows and steps from first principles — for a conversion drop: lead source, count, region/quality, marketing activity, routing, scoring, and product pitch — then benchmark whether it's isolated (~20% of reps) or across the board.
Step 1: give the person comfort and let them talk (avoid seeding your bias). Step 2: validate the hypothesis quietly against the data in the background. Step 3: talk to other stakeholders of the platform, process, and functions to triangulate where the problem truly lies.
RevOps solutioning is a blend of people, process, and platform — never numbers alone. The revenue outcome can come through personal relationships, process, or systems, and usually a combination.
Four defenses that stop problems before they surface: (1) automation and AI to keep leaders out of low-value work, (2) learning and development so the team understands how the GTM machine fits together, (3) data hygiene with restrictive write-access to core systems, and (4) weekly/biweekly checks with real-time reports and fix-on-the-spot remediation.
A deliberate, agenda-less block of time spent exploring the data — the opportunity module, lead behavior, Slack signal — just to sense how the business is behaving, without a specific question to answer.
The two skills that carry a RevOps career: being a genuine people person who can build relationships with extroverted sellers and senior cross-functional leaders, and curiosity paired with a doer attitude — because the problems are new every day.
Prioritize RevOps work by identifying the few major 'pillars' or 'boulders' that create the biggest business impact for a given week, month, and quarter, and aligning them to the company roadmap and OKRs.
Most refusals aren't a hard no but a 'not yet or not now' — the request is acknowledged, logged into OKRs and weekly planning, and sequenced behind what the revenue-generating teams need right now.
An informal personal scale that rates each task by how easy or hard it is for you specifically to address, used alongside deadlines to decide what to work on and when.
Do the hardest, biggest task ('the frog') earliest in the day, so the rest of the day is easier to navigate.
The scoreboard isn't tasks completed but tasks completed that have purpose — work tied to a real company or RevOps priority.
Design departments and systems that run self-sufficiently without you — reducing your role to maintenance — so the business survives your absence.
Stand up a good-or-great process quickly and iterate on it, rather than trying to architect a perfect one up front.
Effective RevOps leadership requires all three at once: having strong opinions, voicing them, and having good opinions backed by data and field experience.
Direct disagreement at the plan and the best direction for the organization, never at the individual — because you're all on the same team.
Treat initiatives as calculated risks with an explicit hypothesis, a plan B/C, and a shared understanding of the odds — so a failed experiment that proves something still counts as a win.
RevOps is the kingmaker, not the king: the person who sees the entire big picture and moves everything forward through influence, without ever making the final decision or owning a department outright — regardless of whether they report to a CRO, CFO, or CEO.
Build trust with the executive you report to by knowing the entire business — every team, not just your function — better than they do, so that when they raise something you're already on the same page instead of catching up.
A daily operator ritual: wake up and scan a set of dashboards the way a fan checks their sports team — is anything broken in Salesforce, is pipeline building as expected, which reps are up or down — paired with a heavy cadence of one-on-ones.
Decide whether you're a very-early-morning worker or a late-night worker and commit to it, because the best, needle-moving work happens in an uninterrupted 'power hour' — not in the middle of a day full of meetings, Slack, email, and context-switching.
During business hours the operator is like a firefighter at the station — present and unpreoccupied because anything can happen — and does deep work outside that window. It's effectively an on-call role without necessarily being more stressful.
Rather than trailing a single executive from company to company, build a reputation within one or two industries where professionals and executives talk to each other, generating better referrals than personal loyalty ever could.
Treat your RevOps seat the way you'd treat a company: an inception phase where you build process, a growth phase where you scale it, and a deliberate exit strategy for growing out of the role toward the next level.
When asked something you can't answer, never say 'I don't know' or signal indifference; always respond 'let me look into it' and ask what resources might help — staying the approachable, curious person who will find the answer.
Build a private company's systems, data, and controls to a post-IPO enterprise standard before any event — so a pre-IPO startup already operates the way a public company must.
The three questions the IPO process forces a revenue org to answer over and over: Can we evidence for this? Are we SOX compliant? What is our system of record?
Move quoting, discounting, approvals, signatures, and revenue recognition from a manual, cross-team process into a formal, controlled CPQ engine (e.g., Salesforce CPQ) with product and discounting rules.
A way to slice a growing RevOps team into its core components: systems and tooling, enablement, compensation/commission, and data.
A documented, evidenced process for changing your systems of record: make changes in sandbox before production, log who deployed what and when, then sample and pressure-test those changes against the system on a recurring cadence.
Evaluate current-state process as if a skeptical outsider had just walked in and must independently verify it — at a tactical level: how would they know what changed, where would they look, and how would they trust it's accurate?
Sales velocity = (number of deals x average deal value x win rate) / time to close, expressed as a normalized dollars-per-day contribution per seller. The velocity delta is the multiple separating top performers from B/C players (11x in the 2025 report).
A view of the revenue motion where the left side is acquisition (lead to close) and the right side is post-sale retention and expansion. The insight: the right side must be multi-threaded and instrumented as deliberately as the left.
Compare the average number of days a deal spends in a stage when it wins versus when it loses. Once a deal exceeds ~14 days in a stage, win rate drops sharply; by four weeks it falls to about 5%.
Top performers close off roughly 30% of opportunities at the discovery stage, refusing to advance deals that were never properly qualified on budget, stakeholders, timeline, mutual close plan, and security/legal review.
Quantify what top performers do (e.g., six engaged stakeholders and a finance persona above a set engagement score by stage two), visualize it simply, and enforce those benchmarks as gates a deal must clear and triggers that prompt sellers and managers inside the CRM opportunity record.
A machine that connects to email, calendar, and phone systems to reconstruct every customer relationship, create and maintain CRM contacts, score engagement out of 100 (with trend and relationship-owner), and write it all back to Salesforce automatically.
Divide marketing and go-to-market into commoditized components (asset production speed, message scaling, channel operation, lead flow) that any marketer can run, and the non-commoditized secret sauce (the story you tell, one-to-one personal interaction, and how your audience feels) that is genuinely differentiated.
Technology makes the pipes that reach an audience faster and more efficient, but you and your team decide what flows through them. Because attention can't be bought — only earned — an efficient pipe carrying a boring payload still fails.
Q1: 'How do we feel about the way we brand ourselves and interact with the market today?' Q2: 'What do you really want to be known for?' The gap between leadership's private answers and what the market actually perceives defines the brand problem to solve.
A single-page document capturing 'this is who we are, this is how we want to be perceived in the market, and this is what we want people to know about us,' agreed by everyone with a stake in the brand before any external-facing work begins.
Three barriers keep companies from investing in brand: (1) trust — it's hard for a founder to let a newer leader or agency lead a transformation of their baby; (2) the brand-vs-growth tension — a ~6-month brand bet competes with demand channels that pay back today; (3) scar tissue from agencies that over-promised and under-delivered.
Bring in an agency when (1) they have specific expertise you lack in-house and you want to capture that knowledge, (2) you simply need helping hands and bandwidth you can't hire fast enough, or (3) you need a credible third party to validate a strategy you're pitching to an executive or founder.
You cannot look like, market like, act like, and operate like every other company and expect outsized (10X) results. The size of the outcome you want dictates the size and non-obviousness of the investment you must be willing to make.
Split marketing spend into three distinct buckets: a one-time brand revamp (tuning the 'Formula One car'), ongoing brand marketing (billboards, out-of-home, high-funnel video with no direct-response path), and demand gen (PPC, SEO, conversion-driven paid social, outbound SDR).
Spend nearly all your budget on demand while more dollars still pay back through payback period, CAC, and CLV:CAC. When additional demand spend stops producing proportional value — you've maxed the intent that exists in the market — that's the signal to invest higher-funnel in brand to grow total searches and eyeballs.
After a successful brand overhaul, three things are true every time: (1) internal excitement spikes — employees advocate and share; (2) recruiting efficacy jumps — inbound interest in working there rises; (3) core marketing metrics get more efficient — more direct traffic, higher conversion, higher funnel velocity and close rate.
Outsized outcomes come from luck multiplied by preparation. You can't will the lucky break, but you don't get the fortuitous opportunities without having done the work that makes you ready to seize them.
Sum, across all possible outcomes, of each outcome's probability times its value: EV = P(outcome1) x V(outcome1) + P(outcome2) x V(outcome2) + ... . A positive EV is a good bet; a negative EV is a bad one.
From Annie Duke's book: judge choices by the quality of the bet given what you knew, not by whether the single outcome was good or bad. A good decision can lose and a bad decision can win.
A core value of Spencer's company: constant, incremental self-improvement — applied here to decision-making, by reviewing whether a choice had positive expected value regardless of how it turned out.
The ratio of the amount you must call to the total pot you stand to win, expressed as the minimum win probability that justifies calling. Call $100 into a pot that becomes $400 and you have 25% pot odds.
Model each go-to-market segment as a bet: win rate (probability) times ACV (value) gives per-deal EV; then layer in deal volume, fully-loaded rep cost, and marketing cost to get the true expected value of investing in that segment.
A calculated field in Salesforce or HubSpot — built from custom properties and workflows — that outputs how much a given account or open deal is 'worth' by expected value, so reps can filter to the highest-EV deals.
Build territories and quotas from expected value — TAM and account valuation weighted by expected conversion rate — rather than gross dollar value.
The replacement for servant leadership: lead from the front, believe no job is too small, and do the high-context work yourself instead of managing away from it.
A lens (adapted from Ben Horowitz's peacetime/wartime CEO) that treats the last 12 zero-interest-rate years as peacetime — stable, predictable, growth-at-all-costs — and today as wartime, defined by speed, precision, and survival.
A change-management ritual: every team member keeps a Post-it on their main screen that reads 'How can AI help me do what I'm about to do?' — retraining individual behavior before restructuring the org.
The missing middle between micromanaging and absentee leadership (credited to Rippling COO Ian McInnis): get close to a work stream to build context and coach, then step back and grant autonomy once you see consistency.
Michael's operating equation for trust: consistency over time equals trust. You earn the right to grant autonomy by observing consistent delivery, not by title or tenure.
Jim Collins's Good to Great bus metaphor (get the right people on the bus, in the right seats), extended with Michael's addition: you must design the seats themselves — the actual jobs — not just fill them.
A mentor's rule that a new leader has roughly 100–120 days to make their people and structure decisions; after that window, the team's output is the leader's own fault or benefit.
Taste is the human judgment to know whether AI's output is actually good. AI takes prompts and shows you a thing; determining if that thing is good is a nuance and sophistication AI doesn't have.
A model for what to outsource: well-defined work is a neatly wrapped present you can hand to an agency (or junior talent); ambiguous, high-context work is a plate of spaghetti where the noodles are snakes and you need the plate back.
Career market fit is the idea that the market may see your value more clearly than you see it yourself (Michael leads go-to-market but the market thinks of him as a marketer). Paired with it: know the neighborhood you're heading toward, not the exact destination, and take any avenue pointed that way.
A three-layer operating system: quarterly OKRs with an above/below-the-line priority cut and built-in slack time; two-week to-do/doing/done sprints with a Monday plan, Friday check-in, Thursday review + retro, and a Friday 20% block; and a monthly company-wide all-hands to prove what shipped.
A phrase from Rita McGrath's Seeing Around Corners: those closest to the work make the best, fastest decisions, while decisions made far from the work are colder and slower.
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 time it takes a new user to 'get it' after logging in — a core PLG success metric Ocean actively drives down by putting the product's aha moment directly on the landing page.
Vectorize both companies (65M) and LinkedIn profiles (230M), then combine them in one search: input an example person's LinkedIn handle and find lookalike people, by role and context, inside the lookalike companies of a target account.
Target by a contextual understanding of what an individual actually does for a company, not by their title — because titles vary with company size (CMO vs. head of growth vs. VP marketing) for the same real role.
Build, filter, and preview the target list in Ocean without spending a single credit; export to Clay for enrichment only once the list is validated.
Gen 1 is an LLM wrapper around an analog/non-normalized database — a pretty face on messy data with broad, imperfect targeting. Gen 2 models the actual GTM process and automates the flow end-to-end, with human validation between steps.
Automation's real strength is micro-targeting: overlay intent and third-party data on a tightly defined audience so every message is highly relevant, producing 5–10% conversion instead of 0.1%.
The core BCG method: read a broad problem statement closely to extract its keywords and clues, branch into a small set of hypotheses using judgment and calculated guesses, then validate or nullify each with data, experiments, and conversations — under real time and resource constraints.
Treat the stated problem as a symptom. Bring the right functional owners into the room, go deliberately broad first, and pull several years of historical data so the true root cause reveals itself layer by layer before you narrow.
Before analyzing, classify the work as either a backward-looking diagnostic (what went wrong?) or a forward-looking strategy question (how do we grow or break into a new segment?). The mode changes which hypotheses you form and how much value the analysis returns.
A small-and-mighty RevOps team protects strategic bandwidth by interrogating every meeting invite, pushing back on low-value asks, leaning on leadership for air cover, and delegating only when it serves the team — freeing time (and AI-reclaimed minutes) for deep thinking.
There are seasons to accelerate the business and seasons to maintain — to hold the speed limit rather than push the gas. Sustainable performance requires knowing when to brake, because it's genuinely hard to stand still and all-gas/no-brakes leads to disaster.
GTM Fund's early-stage evaluation model. The wave is the macro trend / 'why now' (falling AI costs, regulatory tailwinds, distribution shifts); the surfer is the founder's skill, vision, and tenacity; the surfboard is the product — important but the most flexible because it evolves.
A deep, non-obvious insight into a problem space that gives a founder an unfair advantage. It comes from either lived experience (having operated in the space and felt the pain intimately) or obsession (diving so deep into the problem you discover truths others miss).
A way to read early traction that ignores headline revenue in favor of predictive signals: concentrated, evangelical customers; enterprise validation; founder-led sales; usage depth and retention; and shipping velocity. The real question is never 'how much revenue?' but 'does this traction predict you'll find product-market fit?'
Fundraising is go-to-market pointed at investors. How a founder runs the raise — target lists, warm intros, tailored pitches, a disciplined intro-to-close funnel — is treated as direct evidence of how they'll run sales, partnerships, and customer acquisition.
Sophie's personal method for finding fulfilling work: reflect on what you keep returning to with curiosity and what consistently energizes you, write it down, look for patterns, and identify the two or three core forces (a 'triangle') that keep pulling you back. Aim for a role at the center of all of them.
Luster's core operating loop: first diagnose proficiency at the atomic skill level, then predict where a lack of proficiency is about to impact performance in the next 24–48 hours, then prescribe the specific practice or content to close that gap in real time.
The principle that you must objectively measure a team's competency gaps before deploying any learning, development, or training — otherwise the enablement is a waste of time and money.
The failure mode of the consultant-led skill audit: after three-to-four months and hundreds of thousands of dollars analyzing the team on poor CRM data and self-reported interviews, the firm 'plops' a diagnosis with no mechanism to fix it — and it's already last quarter's problem.
Grounded in behavioral and cognitive psychology, Luster offers two practice modes: full-call simulations that mimic an entire sales conversation (prospecting, discovery, QBR, proposal, negotiation), and isolated skill drills with a built-in AI coach that repeatedly tests one skill such as objection handling.
Two ways to build an AI product. 'Quick tech' is a user interface layered on a single shared LLM instance — fast to demo, but unable to control data sharing, latency, or per-customer context. The 'platform' approach builds a trained, closed-off instance per customer behind proprietary layers, trading feature speed for control, security, and stability.
Luster's proprietary stack that sits between the raw LLM and the user interface. Layered bottom-up: a per-customer trust-and-security layer, a custom ingestion model of the org's people and behavior, a company-specific insights/persona/goals layer trained on first-party plus third-party web data, a conversational-AI layer (latency, personality, context), and an output layer of predictive skill insights and prescribed actions.
Instead of sending from a massive shared server (a shared IP pool) full of thousands of unvetted senders, give each user an isolated mini-server ('cluster') with its own IP address so one sender's behavior can't affect the others.
Regularly send emails from a customer's mailboxes to known reference mailboxes to observe where they actually land — inbox, spam, promotions, or undelivered — as the true indicator of email infrastructure health.
Simulate natural, two-way activity across real corporate mailboxes to balance the unnaturally low response rates of cold outreach, so email service providers don't flag the account.
Cap daily send volume per mailbox to what platforms now tolerate (15–25/day, down from hundreds), have the platform control the cap rather than the rep, and scale volume only after messaging is validated on a small sample.
Treat cold outreach like a paid-ad platform: give the system many message variations, test each against a small subset of the audience, and scale only the versions that generate positive engagement.
Use reinforcement learning — a distinct branch of AI from LLMs — as the optimization layer that looks at what has and hasn't performed to predict which hooks, lead magnets, and offers will resonate, and recommends new variations over time.
Blend autonomous AI (which ingests large data sources) with human review checkpoints — a sales rep reviews certain AI-generated copy before it reaches a prospect, and an admin reviews certain content before it reaches the rep.
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%.
The consistent core set of capabilities the market keeps asking to have in one place: sales engagement (cadences and sequences), conversation intelligence, data and enrichment, and predictable forecasting.
Bernardo's three equally-likely scenarios for these platforms: (1) consolidation and rebranding succeed into specialized all-in-one platforms; (2) vendors can't escape their legacy branding and stay boxed into what they were known for; (3) a platform becomes the ecosystem — builds a CRM and takes on Salesforce and HubSpot directly.
A re-evaluation discipline: dust off a structured scorecard and grade every vendor across its full, current feature set — not just its original category — and refresh it far more often than quarterly or annually.
The core buyer decision: assemble best-in-class point solutions for each category, or align the whole go-to-market operation on a single consolidated platform. As tools commoditize, the pull is toward picking one 'pony,' driven by cost, bundling economics, and current negotiating leverage.
A minimal scorecard for any partnerships team: (1) production to goal — pipeline sourced and revenue won, segmented by partner; (2) cost-to-carry ratio — fixed overhead plus variable cost per partner; and (3) cannibalization rate — direct deals that moved to a partner channel and what that cost.
Set production goals both overall and segmented by partner, and match the goal type to the partner type: a channel reseller carries a closed-won production number, while a referral partner (or one that risks cannibalization) carries a sales-qualified-lead goal for leads handed to the sales team.
The cost of running the partnerships motion, broken into operational overhead you can't easily influence and the variable cost per partner — events, sales, marketing, and partner-manager resources — that you can, expressed against the production that spend generates.
The share of deals that would likely have closed direct but moved to a partner channel — tracked by counting opportunities already registered in the direct channel that shifted to a partner, and the discount or referral fee paid to do so.
The cross-functional plan RevOps builds and owns, tying sales, marketing, customer success, and partnerships to one set of goals — and the first thing you measure RevOps against by asking whether the teams are actually achieving it.
A structured feedback loop that treats the departments and individual contributors RevOps serves as its customers: weekly one-on-ones with functional leaders, an IC 'champion' for day-to-day signal, and a formal RevOps satisfaction survey sent to everyone served.
The data-driven half of measuring RevOps: every operational initiative should show up as improving funnel metrics — rising conversion rates (e.g., SQL to closed-won) and falling cycle times — as a direct correlation to the work completed.
The idea that small adjustments to conversion-rate or cycle-time assumptions in a capacity plan or growth model compound into outsized, exponential gains as the business scales.
A defensive dimension of the RevOps scorecard that measures the issues the team prevents — for example, how many days you've gone without a serious priority-zero tech-stack incident or a serious data error in a board meeting.
Measuring RevOps's tactical and operational projects on budget and expected completion time — staying under budget and on schedule for work like a CRM implementation or a new set of board/offsite metrics.
Treat gross revenue retention and net revenue retention as a single paired metric. NRR sums churn, contraction, and expansion; GRR strips out expansion to isolate how much of the starting book remains. Reading only one lets expansion mask underlying churn.
Pick your health-scoring method based on your motion. High-touch, low-account-count books use sentiment-based human judgment (green/yellow/red from the CSM who lives the account). Low-touch, high-volume books use systematic signals (utilization, penetration, login/usage drops).
Capture customer sentiment through two surveys. NPS measures likelihood to refer — a directional proxy for renewal. CSAT measures satisfaction, read through specific engagements, journey milestones, or the overall relationship. Survey on the right cadence, across a representative cross-section, without pestering.
Marketing carries a quota of sales-qualified leads and created pipeline, set jointly with sales and interlocked with the bookings and revenue plan on both volume and timing, then tracked per channel.
Judge every marketing channel by concrete dollar efficiency — cost to create an SQL and cost to create a closed-won deal — alongside the differences in deal size, conversion rate, and sales cycle by channel.
A 2x2 visualization that matrixes two channel metrics — most usefully conversion rate against production (volume) — to gauge the efficiency of each lead source and rank high- versus low-performers.
Coverage of pipeline to quota where each deal is discounted by a stage-based probability weight (ideally drawn from your own historical closed-won rates) plus a deal-health or subjective adjustment for finish-line risk.
The rate at which sales-qualified opportunities become closed-won, calculated only on closed deals (never open ones) and segmented by product, business unit, region, and firmographic segment.
Systematic review of why deals are won and lost, using close reasons that are relevant and actionable, then hunting for overall trends and anomalies that fail a common-sense check.
The defining skill of a great RevOps leader: stepping in to get tactical for a specific business outcome when needed, then expanding back out to the overall strategy — while prioritizing the big-picture work.
The VP of RevOps is the cross-functional glue — a conductor who plays no single instrument but keeps sales, marketing, CS, partnerships, finance, and product aligned and producing one coherent strategy.
The VP of RevOps' single most important deliverable: a data-driven go-to-market operating plan — goals, assumptions, capacity planning — that is then monitored against actuals through the quarter and year.
A nested rhythm: annual planning; monthly plan/forecast tracking and internal board dry runs; weekly 1:1s with every functional leader; and a daily 'morning coffee dashboard.'
A blunt litmus test for the role: if you are not leading (not merely attending) the annual planning process and not in the board room, you're operating at a director level, not VP.
When RevOps enters a company and what the first roles are: it typically starts from a systems need, so the first hire is a dedicated systems admin (CRM plus connected tools), followed quickly by a second, more strategic skill set focused on process, analytics, and reporting.
A ranked preference for where RevOps should report: first a true, full-scope CRO; if none, a COO; if none, a strategic (not accounting-led) CFO who owns corporate planning.
A distinction between a true CRO who owns the entire revenue organization — marketing, sales, and customer success/account management — and a 'CRO' who is really a VP of Sales moonlighting in the title, focused mainly on the sales motion.
The principle that RevOps needs to sit under an executive with scope over the entire GTM lifecycle so it has unbiased authority over every lever — and that placing it under a single-function leader strips that authority.
The sequence of roles a RevOps org adds as it scales: systems owner(s) → a manager/VP-level strategic leader with a seat at the table → a dedicated reporting-and-analytics owner → enablement → per-function RevOps PMs across marketing, sales, and CS.
A maturity model for the function. RevOps 1.0 is the tactical, reactive service center — implementing the tech stack, formatting sales calls, planning territories, comp plans, and CS playbooks, and managing requests. RevOps 2.0 is an internal management consultant that participates in corporate planning, sits shoulder-to-shoulder with finance on the board plan, and leads with insights and recommendations.
A planning discipline in which the analyses behind each metric, the plan assumptions themselves, and actual performance against those assumptions are all kept visible and updated in real time — rather than being computed once for the annual plan and filed away until the next board meeting.
The set of five or six drivers a well-built revenue waterfall contains — normalized prospect volume, sales cycle, time-based conversion distributions, close-won production, SQLs and MQLs — that you should have a pulse on at all times and be able to segment 20–30 ways (enterprise vs. SMB, region, product line, service center).
A five-part checklist for a trustworthy CRM: (1) enable field history tracking, (2) timestamp critical stage and status changes with custom fields, (3) freeze closed-won data, (4) flow lead data into every object on conversion, and (5) put validation rules in place.
Turning on Salesforce field history tracking to record how data evolves over time, providing an audit trail for diagnosing issues and a historical snapshot for admins, users, and downstream tools.
Dedicated custom fields that capture the date each important status or stage changed — lead status, lead lifecycle stage, opportunity stage, customer stage, or proof-of-concept stage — so change data is directly reportable.
Locking closed opportunity data so it can't be edited after the deal closes — restricting changes to a super admin and reinforcing it with validation rules, automation, and weekly backups.
Ensuring that when a lead converts, its important fields — lead source, lead source detail, owner/SDR, and lifecycle timestamps — carry across to the account, contact, and opportunity records.
Rules that block records from saving unless they meet your business process — from simple checks (required amount, no past close dates) to methodology-driven requirements that ask for the right data at each stage.
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 mistake of misperceiving whether your highest value is functional or emotional and then stacking it incorrectly across messaging, content, and sales training — leaving real value unclaimed in the buyer's mind.
A shift from measuring value in price (the only conventional unit) to a broader unit Miller calls 'worthiness,' since price answers none of the buyer's real questions about effectiveness or how the offer will make them feel.
A metaphor treating value exchange between vendor and customer as gravitational attraction — heavier objects (more mass) pull lighter ones toward them — used to deconstruct why some offers pull customers and others don't.
The first source of gravity: how valuable an offer is innately, before the market perceives it at all — a breakthrough technology is extremely valuable sitting in the lab before anyone knows it exists.
The second source of gravity: getting an offer close enough to the customer that they know about it and can be pulled toward it — high-touch for enterprise, low-touch volume for SMB.
The third and most-overlooked source of gravity: the opposing pull of competing options that holds the customer in place and prevents a value exchange — the gravity of the next best alternative.
An occasional, outsized, nonlinear payoff that occurs when timing or the sudden significance of a job-to-be-done causes value to compound rather than add.
The single element of value that is most strongly connected to your brand — unique and special to you. Tom also calls it your superpower, and cites data that it can represent as much as 70% of perceived value.
A triangle whose three sides are the ways humans subconsciously perceive value: functional, emotional, and economic. In any value exchange the brain stacks one element as primary — up to ~70% of the perception.
Products are tools that help customers get jobs done. Whether a customer acquires a tool depends on the job they're trying to do and how functional or emotional that job is.
A maxim Tom credits to Kellogg's MBA program: the primary job of a marketer is to lower the cost of customer thinking. Adding feature on feature or benefit on benefit dilutes rather than compounds perceived value.
Tom's metaphor for RevOps: the 'plumbing' is instrumenting, maintaining, running, extracting, and visualizing the data; the 'poetry' is interpreting that data into a performance narrative. The combination is the value.
The main lenses for cutting a sales team's territories: (1) geographic — international/domestic regions, time zones, states; (2) product or service specialization; (3) industry/vertical; (4) firmographic tier — enterprise / mid-market / SMB; and (5) a fair round-robin or named-accounts approach when the others don't apply.
Balancing territories is not only a morale-and-attrition safeguard; it's a pure-business lever. Equalize a strong territory and a weak one and, in aggregate, the same sales headcount produces more revenue.
Design territories from evidence: mine historical SQLs and closed-won deals sliced by each segmentation bucket, backfill any data you failed to capture, and gather feedback from reps, product, and marketing before drawing the lines.
Roll new territories out at natural calendar breaks (a new quarter or month) and define explicit holdover criteria governing which prospects a rep can keep working after the reshuffle.
Anthony's go-to sequence for a typical B2B SaaS company: start firmographic (enterprise vs. SMB motions need different sellers), then geographic by time zone (buyer availability), then product or industry only if they genuinely differ, and fill the rest with round-robin or named accounts inside bigger buckets.
The most fundamental aspect of any business: an entity capable of creating a value exchange event. Until value is exchanged, an organization — however well-funded or well-intentioned — is not yet really a business.
The idea that winning in business — high performance that is predictable, repeatable, and inspires investor and board confidence — can be codified into a framework and 'bought' like any other service, rather than left to luck.
An operator who masters the science of value exchange and imprints a predictable, repeatable operating framework onto a business — calling, and hitting, their shots rather than making it up as they go.
The failure mode where a company diligently executes a systematically flawed system — practicing a bad golf swing. You may improve incrementally, but you only ingrain bad habits and will invariably 'hit the wall.'
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.
Three lenses on crediting a deal: first-touch credits the initial engagement (often an ad or third-party/aggregator site), last-touch credits the final interaction (the dealership conversation that closed it), and multi-touch tries to credit every influencing step in between.
The problem of distributing credit across many touches. You can 'peanut butter spread' it evenly across lead sources, or build a weighting mechanism that assigns more credit to the touches that mattered most.
A staged approach for teams new to attribution: get first-touch and last-touch tracking in place, add detailed campaign data and campaign-influence ('influenced by') reporting in the CRM, and only then reach for a fully weighted model.
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
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
Matt Overman on the trust recession, why you can vibe code a website but can't fake a domain, what publishing on someone else's platform costs you in SEO and AEO, the .agent round coming in 2028, running 270 TLDs as a channel-only business, and why AI pushed his team back to in-person events
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
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
Anish Chadalavada on why phase one of agentic AI ended with a token bill nobody could explain, what an enterprise AI harness is, model lock-in as the new multi-cloud problem, multiplayer governance, which martech survives, and why the premium is moving back to humans
Nitin Khanna on 100+ exits: the three things that must be ready before a business sells, why owner dependency makes a company untransferable, return on time, why every business sells twice, rolled equity, and the one-week test that shows where the owner is still the bottleneck
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
Anthony Enrico, solo, on why everyone rents the same Formula One engine and what actually separates you: the semantic layer, the context graph, the one-owner rule, never letting the model write your business logic, and three things to do on Monday
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
Ryan Vanshur on finding one builder inside each department, why the context graph matters more than the model, the content audit that threw out 75% of what he had, the wave theory of AI adoption, and going from 12 account executives to 8 without a backfill
Jake Toepel and Anthony Enrico's Updata Partners CEO Summit talk on why a smarter model will never draw you the map: the semantic layer, the context graph, the four-level maturity curve, tokenomics, and a ten-week roadmap that is more than half alignment
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
Alex Reynolds on the $10 million booth with thirty reps on their phones, why 3x event ROI is a terrible bar, badge scans as a vanity metric, half of all tickets selling in the last two weeks, and proof of humanity in the age of AI avatars
Kushal Sharma on the data layer underneath AI — what a semantic layer actually is, what a context graph actually does, when a vector database is worth buying, and why almost none of it is an LLM
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
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
Clearbox co-founders Shawn Tenam and Lila Rest on why Reddit rewards the human effort automation can't fake, how to earn your way past the karma gate, and the cost engineering behind a $75-a-month product
Derek Mogar on quote-to-cash in the AI era: the four-step build, the guardrails, and why trust in the data is where most projects fall short
Andy Guttormsen on demos as a product and brand engine, hiring the leader before the reps, and why Circle renamed RevOps the internal AI team
Sarah Madden (Smadds) on the three buckets every skill falls into, the rule of three, and the infrastructure discipline underneath it
Day AI's Christopher O'Donnell on the folder every RevOps team is quietly building, and why multiplayer mode barely works
Anthony Enrico on a field study read from live systems rather than a survey — and why your headcount picks your CRM
GTM Council co-founder Noah Marks on why software is becoming a services industry, and how to become the pipeline czar at your company
Typeform CRO Bryce Winkelman on running self-serve and enterprise at once, fighting for brand budget, and the industry-expert hire most teams miss
LeanScale CTO Jake Toepel opens the hood on the agent fleet behind a whole portfolio — and why one company's messy definitions become thirty boards' worth of wrong answers
Dvir Ginzburg of Encore AI on the metric that tanks revenue, why 'acts human' is the real moat, and the customer who lied to an AI agent
LeanScale CTO Jake Toepel runs an agent through ICP, messaging and pipeline diagnosis — then shows why it breaks on your own CRM
Yishi Zuo of Tavus on poker, expected value, and why the right go-to-market call can still lose
Anthony Enrico on the 12-month window between your Series A and the go-to-market machine your Series B is actually buying
Irina Denisenko on FedRAMP, the federal sponsor bottleneck, and turning a 3-year, $3M gauntlet into 90 days
Jonathan Hunt on owned media, the build-vs-partner-vs-acquire playbook, the video-first flywheel, and why HubSpot is officially calling time on inbound
Mica, founder & CEO of Amplemarket, on agentic GTM — building outbound agents that research, personalize, and run while you sleep
Roee Hartuv on pricing & packaging, the jobs-to-be-done approach, and how AI broke SaaS unit economics
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
Tessa Whittaker on the strategic layer AI can't automate, and leading enterprise AI transformation
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
Andrew Geisse (CRO, Pallet) on honest GTM planning, POCs that actually convert, and selling AI into a $12T industry
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
Mike Choi on building Koah, the monetization layer for AI apps, and why every paradigm shift reinvents advertising
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
Leysan Zigangirova (CMO, Async) on marketing AI products, getting visible inside LLMs, and surviving the Podcastle → Async rebrand
Yasin's build-along on the folder-and-file architecture behind LeanScale's agentic operating system
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
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
Alex Shartsis on why speed beats perfection, the eroding CRM moat, and building GTM for an AI world
Robert Moseley on why CRMs break, and how AI removes humans from the data
Christian Peverelli on AI-native outbound, the death of spam, and putting agency-grade prospecting in one operator's hands
Benjamin Hoehn on ICP-first content, founder-led marketing, and using AI to accelerate — not replace — the fundamentals
Andy Mowat on where scaling companies neglect the fundamentals — enablement, data foundations, GTM tooling, and the RevOps career
John Linden on player-owned economies, product-market fit, and building with AI from day one
Polytomic founder Ghalib Suleiman on breaking the data–RevOps silo, syncing product and billing data into your CRM without engineering, and why empathy is a revenue lever
Ebsta founder Guy Rubin on the 2025 B2B Sales Benchmark Report — sales velocity, deep ICP over TAM, and ruthless qualification.
Kevin White on AI bot traffic, AEO, and the future of digital marketing
Anthony Enrico (LeanScale) and Guillaume Jacquet (Vasco) on reverse-engineering ARR, unit economics that pass the board, and killing reforecast hell
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
Vlad Cazacu on building Flowlie, running fundraising like a real process, and why raising is 80% preparation
Zayd Ali on building Valley — the AI SDR for LinkedIn — and the shift from V1 blast outbound to V2 relevance
Theo Pavlich on hiring RevOps talent for curiosity over pedigree, why an unconventional background is an edge, and taming GTM tool sprawl
Prakash Raina on unifying CPQ, billing, and rev rec — and letting reps quote straight from Slack
Justin St. Louis Wood on building revenue systems from first principles — then rebuilding them AI-first
Amplemarket founder Micael Oliveira on building a consolidated, AI-plus-human GTM platform — and why signals and timing beat volume
Neel Kamal on the synthetic buyer, the 84% shortlist rule, and seeing your go-to-market through your customer's eyes
Yogi Punjabi on building PeopleLens — an AI layer that makes every rep a better performer and every manager a better coach
Zev Lebowitz demos Attio — the AI-native CRM that molds to your motion instead of forcing you into someone else's
David Walker on why outbound is losing signal, and how one multimodal AI layer — chat, email, and voice — converts the inbound traffic every buyer already generates
Steve Dinner on running a high-output RevOps team with zero in-house admins or devs — agile, structure, specialist contractors, and AI
Tony Tom on Orca's account-first, AI-powered approach to B2B customer support
LeanScale co-founder Anthony Enrico on the Traction podcast — the modern, revenue-per-FTE GTM playbook for AI-era startups
Shaadik of LambdaTest on treating RevOps like a general physician — root causes, not symptoms
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
Mario Paganini on brand as the last non-commoditized advantage, the two questions that start every rebrand, and how to split budget between brand and demand
Spencer Hodgson on betting on channels and reps with expected value
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
Ocean.io founder Michael Heiberg on vector-based lookalike targeting, micro-targeting over mass outreach, and the two generations of GTM AI
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
Luella's Mustafa Saeed on AI guardrails, email deliverability, and keeping humans in the loop in GTM
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 and Cameron Legge join Anthony Enrico to unpack what the Clari–Groove deal means for the sales tech stack and how RevOps should respond
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 Alves on the three metrics every customer success team must measure — gross vs. net retention, customer health, and voice of customer
Anthony Enrico and Bernardo on the three marketing metrics that tie demand gen to the bookings plan
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
Alex Brower on graduating RevOps from a ticket-taking service center to the strategist in the planning room — and running planning as a real-time closed loop.
LeanScale Chief Architect Henrique Sakai on the five CRM foundations that make your revenue data trustworthy
Tim White on why partnerships are a give-to-get game, a strategic-acquisition on-ramp, and a relationship business you can't fake
Thomas Miller on value misstacking, worthiness over price, and gravity as the universal law of business
Thomas Miller on the inner core, the value triangle, and why RevOps needs plumbers and poets
Cameron Legge on designing fair, efficient sales territories for B2B SaaS
Tom Miller on the value exchange event, operating plans, and engineering repeatable winning
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
Bernardo Alves on what actually makes multi-touch attribution difficult — and the pragmatic first steps most teams should take instead