Enterprise & Public-Sector Sales

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.

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 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.

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.

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.

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.

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.

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%.

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.

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.

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.

Partnerships require giving value — and making concessions — before you get anything back, in contrast to the common approach of building a channel purely to sell more of your own product.

A partnership program must be sponsored from the board and executive leadership down, because early concessions and delayed ROI can't survive quarter-to-quarter decision-making.

Treat your strategic partners as potential acquirers, using a multi-year partnership to build relationships, test integration and cultural fit, and position for a strategic exit.

Concentrate limited bandwidth on a select few high-conviction partnerships where the combination is disproportionately valuable, rather than spreading thin across many low-producing relationships.

Build trust so high that a partner would call your personal phone at 3am on a Sunday and know you'll pick up and problem-solve as eagerly as they need.

Deliberately weight travel and face-to-face time above other activities to win partners' hearts and minds and to harvest the off-the-record intelligence that never surfaces on a recorded call.

Give every partner equal access to support, technology teams, and roadmap, and hold commercial terms you'd be comfortable exposing to a partner's competitor — the foundation for managing channel conflict.

Tie the partnership team's KPIs to overall company revenue rather than channel-only revenue, so channel and direct teams succeed together.

Make an honest assessment of whether a partner motion fits your GTM, then either fully commit the resources or don't start — no one-foot-in, one-foot-out programs.

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

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

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

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

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

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.