This file is the canon page on how B2B differs from B2C structurally. It traces how every layer of AJTBD bends when the buyer is a company: Jobs, Job Graph, Critical Chain of Jobs, segmentation, value creation. A B2B purchase is not one person performing one Job — it is several roles, each carrying two parallel Job Graphs, business and personal. Those roles run a multi-week, multi-handoff Critical Chain of Jobs that must complete end-to-end before any money moves. How much of the page applies scales with deal size. SMB collapses most roles into one person. Mid-market and enterprise separate them (§9).
The page sits on top of Job Structure, used here per role on two parallel graphs, and Critical Chain of Jobs, the operational core. §10 of Critical Chain of Jobs holds the canonical B2B chain as roles × Jobs-per-role. Its §4 and §5 hold the per-role walk dynamics: drop-off as Solution switch, predictions, the break cascade. This page feeds Segmentation, Riskiest Assumption Test §2, and ABCDX Segmentation. B2B interview methodology lives in AJTBD interview guide.
1. The B2B deal is structurally complex for every participant — and that complexity dominates every downstream decision
A B2B deal is not a scaled-up B2C purchase. It is a categorically different structure. It has multiple roles (§7), two parallel Job Graphs per role (§5), multi-week duration, and a chain that can break at any role-to-role boundary. Every other thesis on this page is downstream of this structural complexity.
The recurring patterns that anchor the rest of the methodology:
- Buyers spend a small share of decision time talking to any one vendor. Gartner's B2B Buying Journey research puts it at ~17% of total purchase time across all suppliers combined, so any single vendor gets a sliver. Most of the deal happens outside the seller's view. The machinery you cannot watch is where the deal is actually decided.
- B2B decision-makers often experience the buying process itself as difficult, slow, and politically risky. Alongside evaluating value, the buyer is trying to survive the internal process of buying.
- Deal length is structurally multi-week or multi-month, with a long tail for larger accounts. A same-day B2C funnel is the wrong mental model for B2B.
Three consequences fall out at once. First, most of what determines whether you win happens outside the room. Stakeholders the seller never meets hold veto rights: IT, security, legal, finance, a former implementer of the incumbent. The seller's leverage is equipping the champion with everything those stakeholders will ask, before they ask it (§3). Second, plan acquisition and pricing motions against long buying cycles, not same-day conversion. A B2C funnel optimized for immediate purchase is structurally wrong for B2B. Third, the deal's complexity tax is itself a force holding customers on the incumbent. A B2B customer who paid the tax once won't pay it again unless the gain visibly exceeds it. Switching cost in B2B is not a feature gap. It is a multi-quarter operational disruption, a habit force (Behaviour Change §9) scaled to the company level. The structural response is in §2.
The default outcome of all this complexity is no decision, not a competitor win. The dominant B2B competitor is the null Solution (Critical Chain of Jobs §4). The buyer abandons the purchase and stays with what they already have. The complexity tax plus the personal risk of a failed implementation (§5) makes doing nothing the safe choice. A large share of qualified B2B pipeline dies here, not in competitive loss. So the first job is rarely out-comparing rivals. It is making the cost of the status quo concrete and unavoidable enough that doing nothing stops being safe.
2. Product value doesn't always dominate — sales motion, relationships, and integrator position frequently win the deal
Sometimes product value is the deciding input. Often it is not. In B2B, product quality is one input among several. The others frequently dominate: whether the seller has a working relationship with the buyer, whether the buyer's chain ran cleanly the last time it ran, whether the seller can answer the questions the absent stakeholders will ask. Product quality compounds on top of those. It doesn't substitute for them.
Product value alone dominates in some cases: novel categories where no incumbent exists; deeply technical buyers evaluating like engineers (developer-tools, infrastructure, security primitives); regulated environments where a specific compliance feature is non-negotiable; segments where the buyer's personal Job is itself "pick the technically best option to prove my judgment" (Personal Job 3 in §6). Other forces dominate in mature categories with established incumbents; with risk-averse buyers (most enterprise mid-market); in deals where switching cost is large relative to the value delta; in categories where the analyst landscape and peer-recommendation channel are well-formed.
§2 and §5 are two sides of one mechanism. Relationships and integrator position outperform raw product quality because they address what the product alone cannot: the Decision Maker's personal Jobs (§5). Those are Job-security continuity, a named customer success manager (CSM), predictable account management, and a "we made the safe choice with a known partner" story. A better product with no relationship offers superior business value while exposing the Decision Maker to blame risk on every personal Job at once. So the buyer's brain, scoring the combined business and personal stack (Value Creation §4), picks the relationship.
The integrator model is the structural endgame. Once a B2B vendor clears the first deal cycle with a customer, additional sales become easier, not harder. The integration is already wired, stakeholders already know the vendor, and the salesforce already knows the buyer's roles and budget cycle. The "we already have [vendor X] — what else can [vendor X] do?" conversation becomes a free acquisition channel. This is the mechanism behind cross-sell and expansion revenue compounding faster than initial sales in mature B2B SaaS. It is visible in Atlassian's land-with-Jira-then-expand-to-Confluence-and-Bitbucket playbook and in HubSpot's evolution from a marketing-automation single product to a six-Hub platform.
3. Information that simplifies the deal is one of the highest-leverage acquisition assets — bring it pre-loaded for every absent stakeholder
Sellers who hand buyers useful information on alternatives, objection handling, and stakeholder questions close materially more often. The deal itself also runs materially simpler. This falls out directly from §1. Most of the deal happens outside the seller's view, so the seller's leverage is what they put in the champion's hands before the champion talks to the absent stakeholders.
The catalog of information that actually moves deals:
- Side-by-side comparison with the named competitors the buyer is evaluating, not generic claims of superiority. "Here is how we differ from Stripe Connect, Adyen, and Worldpay on the dimensions your finance team will ask about."
- Stakeholder-specific objection responses. "Your IT director will ask about SOC 2 attestation, single-tenant deployment options, and a service-level agreement (SLA). Here is the one-page answer for each."
- Customer references in the buyer's specific industry and size band. "Three logos in healthcare-payer SaaS at your scale bought this product in the last 18 months. Here are the implementation timelines."
- A pre-built internal business case template, which the champion copies, edits, and forwards to the Approver without constructing the financial argument from scratch.
- A migration and rollout playbook, as proof that the implementation chain (§1's "very complex" finding) has been run before and converges.
Buyer enablement is the most under-invested high-leverage budget line in most B2B marketing teams. Most budget goes to demand generation at the top of the funnel, while the largest leverage often sits at the conversion gate. But this is capture, not creation. Only ~5% of a B2B market is in-market at any moment (the 95-5 rule — Ehrenberg-Bass / LinkedIn B2B Institute). Bottom-of-funnel enablement wins the buyer who is already deciding. Brand and mental-availability work is what lands you in the Consideration Set of the 95% who will buy later. The two do different jobs, and a healthy B2B mix funds both.
The enablement layer itself compounds across multi-touch sales cycles. See Stripe's docs, Notion's templates gallery, and HubSpot Academy. A "deal room" — a single shared URL containing every artifact — is increasingly the operational form of this thesis. That URL holds comparison sheets, stakeholder-specific FAQs, references, the business case, and the rollout playbook. Vendors who give the champion one URL outperform vendors who scatter the same content across PDFs and email threads.
4. Consideration Activators in B2B flow through peer and institutional channels, not consumer-marketing channels
The channels that wake up a B2B Job are categorically different from B2C. A consumer evaluating a personal-finance app responds to landing pages, social ads, and influencer recommendations. A B2B Decision Maker evaluating an enterprise platform does not. They respond to peer stories from competitors, customer-published case studies, conference talks, analytical reports, and what trusted colleagues recommend. The behaviour-change mechanism is identical to B2C (Behaviour Change §5). What differs is the channel: B2B Consideration Activators load Jobs into the Decision Maker's head through channels the Decision Maker trusts as professional-grade signal.
The B2B Consideration Activators channel stack, roughly ordered by per-touch impact:
- Peer stories from companies in the buyer's reference group. A CTO at a Series B SaaS company is told by a CTO friend at a peer Series B company that their team moved from X to Y last quarter, what worked, and what didn't. This is the highest-impact channel by a wide margin. It carries both information (what does the product actually do?) and trust (the peer chose it; if they were burned they'd say so).
- Customer case studies, especially in blog form. The buyer's preferred form is rarely the polished PDF case study. It is a long-form blog post by the customer's own engineering, product, or ops team explaining what they actually built, what surprised them, and what they would do differently. Stripe's customer stories, Notion's customer pages, and engineering blogs at customer companies that mention the vendor by name all carry materially more weight than vendor-produced marketing.
- Conference talks by customers, not by the vendor. A talk titled "How we migrated 50M users from legacy auth to [vendor]" delivered by the customer's senior engineer at a category conference loads Consideration Activators at peer-credible weight. The vendor's keynote at the same conference loads them at vendor-marketing weight. The customer-told version is meaningfully harder to engineer, and it converts better when it lands.
- Analytical and industry reports, of any source the buyer's procurement function accepts as third-party validation. In some categories that's Gartner and Forrester. In others it's IDC, McKinsey vertical-practice reports, Crunchbase market maps, or the buyer's industry trade association. The function is the same: third-party signal that the vendor is "real."
- Trusted-colleague recommendation inside the buyer's own company. A senior engineer the Decision Maker trusts says "I'd pick this one." This is the lowest cost per touch and the highest information-density per touch, and it is impossible to engineer directly. The vendor's lever is to get the senior engineer to evaluate the product first.
- Vendor-produced content (docs, blog posts, technical deep-dives). This doesn't substitute for peer, customer, or analyst channels. It is the substrate the peer-channel signals point back to. The buyer's engineer who hears the peer recommendation googles the vendor, hits the docs, and either confirms or falsifies the peer story. Strong docs make the peer signal stick. Weak docs unwind it.
Most B2B marketing budget over-invests in vendor-produced content and under-invests in peer-channel enablement. The vendor can't write peer recommendations directly, but can make them measurably easier. That means customer-success teams whose explicit Job is to surface customer stories, named-customer reference programs, customer-advisory boards, talk-coaching for customer engineers, and sponsored editorial in industry publications customers actually read. Cold acquisition in B2B is mostly cold Consideration Activators-loading. Inbound paid campaigns work only when there's already a warm channel feeding them: peer talk, an analyst's report, a customer's blog post the prospect found. Cold paid spend without warm Consideration Activators behind it converts weakly in most B2B categories. Against the 95% not yet in-market (§3), its realistic job is building mental availability for a later trigger, not immediate conversion.
5. B2B motivation is mostly personal Jobs, not business Jobs — every role carries two parallel Job Graphs
This is the single most counter-intuitive thesis on this page. Default product-team intuition says B2B decisions are made as professionals, on the merits of the business case, with KPI achievement as the primary driver. Reality reported across multiple B2B research engagements at mid-market and enterprise scale is different. Personal Jobs gate the decision and business Jobs justify it. The business case is necessary. It gets the deal on the table and past finance. But the human in the seat moves on Jobs they perform on their own behalf, with the business KPI as the frame the personal Job runs inside. The exact split varies by industry, deal size, role, and founder involvement. The structural point is that personal Jobs usually decide whether the human moves at all.
Every role in a B2B deal carries two parallel Job Graphs simultaneously:
- Business Job Graph. What the role's KPIs are: hit the sales plan with fewer FTEs; reduce defect rate by 30%; cut customer-support cost by 20%; ship the platform migration by end of Q3. Visible, written down, evaluated in performance reviews.
- Personal Job Graph. What the human in the role performs for themselves: don't get fired; get promoted; speak at a conference; not look incompetent in front of the CEO; not be left holding a failed implementation. Unspoken, rarely written down, usually invisible to vendors who haven't asked.
Two contexts vary the business-to-personal ratio:
- Active founders, with the Decision Maker at CEO or CEO-minus-one, give roughly 50/50. When the company's founders are still active in operations and the Decision Maker sits one or zero levels below them, business motivation is materially stronger. The Decision Maker is being evaluated by people who care about business outcomes directly.
- A Decision Maker two-or-more levels below the CEO, or with founders and owners no longer active, lets personal Jobs dominate. This is the default in most US mid-market and enterprise organizations.
John Maynard Keynes, paraphrased from The General Theory of Employment, Interest, and Money (1936): "The principal personal task of the employee in a company is to reduce the risk of being blamed." Keynes wrote about labor markets in general, but the framing maps directly. B2B decisions are dominated by blame-avoidance. The seller who reduces blame risk for the Decision Maker dominates the seller who maximizes business value.
Communication, demos, and sales scripts must hit personal Jobs explicitly. A landing page that names "sleep at night knowing the audit log is complete" is hitting a personal Job. A page that names "reduce filing errors" is hitting only the business Job. The product itself should be designed against personal Jobs alongside business Jobs. A product that hits the business KPI but exposes the Decision Maker to blame risk — incomplete audit logs, weak SSO, no rollback path — will lose to a product that hits the KPI marginally less well and gives the Decision Maker a defensible "I picked the safe option" narrative.
To surface the personal Job in an interview, climb up from the business Core Job rather than asking for it directly. Asking "what are your personal motivations for this?" almost never works. The respondent has no ready language for the question and answers with the business Job by default. The reliable move is to anchor on the business Core Job the role already named, then climb one rung up into the personal graph with a single question:
"What personal result, as a human, will you get from {Expected Outcome of business Core Job}?"
Anchored to the business Job they're already explaining, this lets the respondent ladder up from familiar ground into the unspoken layer: "I'll get a promotion," "I won't get fired," "I'll get to tell that story at the next conference," "I'll finally feel competent in my role." It is usually a sentence they've never said out loud before. Each answer is a single rung. Repeat the question against each surfaced personal Job ("and what result do you get from getting promoted?") to climb toward the role-holder's life-level needs: status, safety, autonomy, competence. Stop one rung below pure needs. Those are too abstract to design against (Job Structure §1). Interview discipline lives in Job Structure §16 and AJTBD interview guide.
6. The five personal Jobs of every B2B Decision Maker
Across the consulted-expert corpus and Ivan's agency research, B2B Decision Maker personal Jobs cluster into five recurring patterns. Treat them as a starter checklist to validate per segment, not a universal law. The five Jobs below appear in some form in the majority of mid-market and enterprise B2B deals studied. They are Decision-Maker-flavored. Every other role in the chain (§7) carries its own personal-Job profile, and the CFO's, the IT director's, and the champion's differ sharply.
- Personal Job 1 — "I want to make a choice that won't get me blamed or fired" (Job security; colloquial form: "no one will fire me"). The default dominant personal Job. The Decision Maker is choosing a solution whose downside they will be personally accountable for. The worst case is being publicly responsible for an expensive failed implementation. Communication: "Our solution is safe — your KPI will be hit, with no surprises you will have to explain afterward." Operational instruments: SOC 2 / ISO 27001 attestations, named enterprise customers in the same industry, money-back or pilot-period clauses, named implementation manager and CSM, transparent SLA. This is the single most under-invested personal Job for product teams scaling from SMB to mid-market. SMB buyers operate without it; mid-market and enterprise buyers operate with it as dominant.
- Personal Job 2 — "I want to use the same tools the best people in my field use" (status; colloquial: "I'll be with the best"). The Decision Maker wants to operate at the level of the best people in their field with the best tools. Buying a status-loaded product is itself a status-uplift act. Communication: "The leaders in your space already use this — here are the logos." Operational instrument: the customer-logo wall, which almost always works disproportionately to its information content. What matters is which logos sit on it, not how many.
- Personal Job 3 — "I want to build a career-defining story from this implementation" (career upside; colloquial: "my position in the company will grow"). The Decision Maker is performing the business Job partly as a vehicle for their own advancement. A successful implementation produces a story the Decision Maker can tell in performance reviews, conference talks, and the next interview. An expensive product is often a stronger fit for this Job than a cheap one. The price tag itself signals importance and seriousness, and the Decision Maker gets to tell a "we made the right call; we picked the premium solution" story. Communication: "You'll be telling your CEO the story of how this implementation moved the business. Here is the template."
- Personal Job 4 — "I want to offload operational routine" (escape from drudgery, in order to focus on strategic work; colloquial: "I don't want to do boring routine"). A significant share of any Decision Maker's work is administrative routine: running reports, filling tickets, attending stand-ups about backlog grooming. The Decision Maker wants to be working on strategic problems, talking at conferences, leading visible initiatives. Communication: "We take A, B, C, D off your plate so you can spend your week on work that matters." Operational instruments: workflow automation, AI-driven defaults, set-and-forget configuration, escalation paths that don't require Decision Maker attention by default. The HR-function pattern shows this: HR teams accumulate operational task dumps from every other department, and products like Workday and Rippling win HR by performing this Job at scale.
- Personal Job 5 — "I want to pick a vendor who will still support me at year 3" (orphan-implementer avoidance; colloquial: "I won't be left without support"). The Decision Maker has been burned before: buying a solution, justifying the spend, deploying it, then having the vendor disappear, raise prices unexpectedly, or fail to support a critical integration mid-rollout. Communication: "You will have a named CSM, response SLA of X hours, escalation path Y, and our roadmap is public for the next four quarters." Operational instruments: published roadmap, named-rep contact, status-page transparency, written escalation procedures, customer-advisory-board membership. This is also why "we just raised $50M Series B" lands as a positive signal in enterprise sales — it reduces vendor-disappearance risk.
Buyers who perceive personal value are far more likely to purchase, and to pay a premium, than those who see only business value. That is the finding of the CEB / Google From Promotion to Emotion B2B study of ~3,000 B2B buyers. Per-segment effects vary. The durable finding is the direction and size of the lift, not a universal multiplier.
7. A B2B deal is a chain of roles, each carrying veto or veto-equivalent rights
A B2B deal involves not one decision-maker but a chain of roles, each carrying its own pair of Job Graphs (§5) and veto or veto-equivalent rights. SMB collapses several roles into one person. Mid-market and enterprise separate them. Mapping the role chain, and the personal Jobs of every role in it, is the prerequisite for any sales motion that scales. The role names below follow the MEDDIC / MEDDPICC vocabulary standard in US enterprise sales, so most sales orgs will recognize them.
The eight roles
- Executive Sponsor (Business Sponsor) is the role that gets the value. This is the senior leader whose KPIs improve when the product is bought. Examples: a VP of Sales whose plan calls for $50M in annual recurring revenue with the same headcount; a Head of Customer Support whose mandate is "reduce ticket volume 30% without growing the team." Their business Job is the visible motivation. Their personal Job is usually some flavor of "demonstrate I delivered against this mandate." This role is necessary but not sufficient. They rarely have budget authority alone and don't carry the technical or compliance veto rights. In some MEDDIC-aligned orgs this role and the Economic Buyer below are the same person; in others they are separated.
- Economic Buyer (Decision Maker) is the most expensive person on the call, with the final word. This is the role with formal decision authority over the category, often the CEO in startups, the COO or Head of [function] in mid-market, the SVP / EVP in enterprise. They take the recommendation from the Executive Sponsor, run it through absent stakeholders' filters, and either approve or block. MEDDIC: Economic Buyer; everyday usage: Decision Maker. Identifying the actual Economic Buyer — not the role that looks like the Decision Maker on the org chart — is one of the highest-leverage moves in B2B research. A recurring failure mode is interviewing someone called the "Decision Maker" who turns out to be the Executive Sponsor or Champion rather than the budget-signoff authority.
- Approver (Finance / Budget gate) is the formal budget-signoff role, usually the CFO. In SMB and flat orgs, the Economic Buyer and the Approver are the same person. In mid-market and enterprise they are separated to reduce fraud, balance competing departmental wants, and prevent impulse buys. The Approver typically doesn't engage with the product but reviews the business case. Their personal Job is almost always "don't approve a spend that will look stupid in the year-end review." Arm the Economic Buyer with an Approver-ready one-page business case before the Economic Buyer walks into that conversation.
- Technical Buyer is IT, Security, DevOps — the technical-fit gate. This is the role that judges technical fit. Examples: the IT director who has to take the new system into their perimeter and support it operationally; the security officer who reviews data handling, encryption, access controls, breach risk; the DevOps lead who evaluates integration complexity and operational load. In enterprise deals, Technical Buyer veto is the single most common reason mid-market SaaS deals stall above ~$50K in annual contract value (ACV). It typically blocks on missing SOC 2 attestation, SSO/SAML/SCIM, audit log, or role-based admin. Notion Enterprise (2021) launched the SSO/SAML/SCIM/audit-log bundle specifically to unblock enterprise Technical Buyer veto.
- Gatekeeper is Procurement, Legal, Compliance — the process-and-risk gate. These roles judge contract terms, vendor-risk standards, and procurement procedure. Examples: procurement runs the vendor through the standard request-for-proposal, request-for-information, and master-service-agreement cycle; legal reviews indemnification, intellectual-property, and data-residency clauses; compliance reviews regulatory fit (HIPAA, FERPA, SOX, GDPR / CCPA). Gatekeepers have process-veto rights. They don't decide whether to buy, but they decide whether the deal can move through procurement at all. Zoom for Education (2020) launched FERPA-compliant configurations specifically to clear K-12 procurement-Gatekeeper veto.
- Coach is the internal advisor who provides intel and political guidance. A MEDDIC term, distinct from Champion below. This is a person inside the buying org who informally shares context: "the real Economic Buyer is the COO, not the VP"; "your real competitor is the in-house team, not the vendor on the shortlist"; "the Approver hates 3-year contracts." Coaches don't actively push the deal. They reveal the chain. (In looser usage often called "Advisor" or "Recommender"; analysts like Gartner and Forrester play the external-Coach role for the buyer.)
- Champion is the role that puts in active effort to get the deal done. This is the most active form of internal advocate: people whose personal Jobs are served by the deal succeeding, usually because the product hits the career-upside personal Job (Personal Job 3) or the escape-from-routine personal Job (Personal Job 4). Champions do work the seller never asked for: calendar internal meetings, draft business cases, escalate to the Economic Buyer, push back against Technical-Buyer veto. A B2B deal at any meaningful complexity is dramatically harder to close without a Champion. Without one, deals stall while no one inside the buyer's organization spends political capital to move them. But not every willing advocate can move the committee. A friendly Talker who can't drive internal consensus is the most common silent-kill. Recruit the Champion who actually mobilizes the group (the Mobilizer), not the one who is merely warm. MEDDPICC: the "C" in MEDDPICC is Champion.
- Detractor (Anti-Champion / Saboteur) is the covert opposer with personal reasons to block — the mirror of Champion. These are people whose personal Jobs are served by the deal failing. Examples: the Economic Buyer behind a previous implementation of the incumbent, whose prior win is publicly devalued if your product wins; the head of an internal team building a competing in-house solution; the executive whose department headcount shrinks if your product automates work currently done by their team. Detractors are usually invisible from outside the buying organization and rarely surface in the first interview. Surface them on the second or third pass with questions like "who might be against this deal? who could block it? who blocked similar deals in the past?" (Industry terminology varies — "Detractor" and "Anti-Champion" are common in US sales-training contexts; "Saboteur" is also used.)
- User Buyer (End User) is the people who use the product daily — the people whose work changes when the product is deployed. This is the role the product's UX is built for in B2C, and the role with the least purchase weight in B2B (§8 unpacks the exception). User Buyers feed business value into the Executive Sponsor by using the product. Their Jobs matter for activation, retention, and seat-expansion, but rarely for the initial purchase decision.
8. End-user UX is a purchase input when the role is scarce — or when adoption is product-led
The default in B2B is that end-user Jobs don't influence the purchase decision. IT, security, finance, and the Decision Maker hold the veto rights. The end user is the output the product serves, not the input to the decision. Two structural exceptions break the default. The first is labor leverage: when the end-user role is itself a scarce, expensive, hard-to-retain hire, their tooling preferences become a purchase input. The second is adoption leverage: when the motion is bottom-up or product-led, end-users adopt the product themselves and become the buying signal (product-qualified leads), so end-user UX is the acquisition engine regardless of how replaceable the role is. The two often compound (Cursor and Figma below run on both). This section unpacks the labor-market case in depth.
The ex rule: if a role, like an ex, is hard to find, easy to lose, and impossible to forget, they carry purchase weight. Senior software engineers, senior designers, senior data scientists, and top sales reps — roles whose departure is itself a business event — get tooling preferences honored. "I won't work here if you make me use Confluence instead of Notion" is a credible labor threat when the labor market for that role favors the employee. The company gives ground because the cost of replacing the engineer dominates the cost of the SaaS subscription.
The dynamic flips when the labor market favors the employer. Bookkeepers, customer-support agents, and operations associates — roles where the labor pool is deep and the employer dictates terms — get whatever tooling the company picks, and their UX preferences don't move the purchase. This is why mass-market B2B operations software ships with notoriously rough end-user UX: see NetSuite, SAP Business One, and most legacy ERP. The buying decision was made above the end user, against the company's KPI, not against the end user's preference.
Two contemporary US patterns run on this dynamic:
- Cursor's rapid displacement of legacy IDEs (~2023–2025). Senior engineers, currently the scarcest hire in tech, chose Cursor's AI-native editor over JetBrains and VS Code defaults. Companies switched because retaining the engineer dominated the licensing cost. The buying motion is bottom-up, driven entirely by end-user preference at a role where the labor market favors the employee.
- Figma's displacement of Sketch and Adobe XD (~2018–2023). Designers were the scarce hire, designers preferred Figma's collaboration model, and companies switched because designers threatened to leave. Adobe ultimately discontinued XD in 2023 after failing to compete on the engineer- and designer-driven adoption motion.
Categorize your end-user segment by labor-market dynamics before designing the UX investment. If your end user is an in-demand engineer, designer, or data-science role, invest heavily in end-user UX as a purchase input. If your end user is a back-office or operational role, invest minimally in end-user UX for the purchase decision, then re-evaluate for retention and activation downstream. B2B end-user UX is consistently worse than B2C UX, and the gap is not laziness — it is a rational allocation against the actual buyer. Treating this as a problem-to-solve for all B2B segments mis-allocates engineering investment. Treat it as a problem-to-solve for segments where the end-user role is scarce, or where the motion is product-led and the end user is the buying signal.
9. The Critical Chain of Jobs in B2B — roles × Jobs-per-role, breaks at role boundaries, personal-Job failures dominant
A B2B Critical Chain of Jobs is not a linear sequence of Jobs the customer walks (Critical Chain of Jobs §1 for the B2C base case). It is a roles × Jobs-per-role matrix (Critical Chain of Jobs §10), with hand-offs at every role boundary and two parallel Job Graphs per role. The structural property: no money moves until every role's business Jobs and personal Jobs at every step are performed. These per-role Jobs map onto the six non-linear buying jobs Gartner names — problem identification, solution exploration, requirements building, supplier selection, validation, and consensus creation — which the committee loops through rather than completes in order.
Where the chain breaks (canonical patterns from Critical Chain of Jobs §10, refined per the B2B specifics on this page):
- IT security review. Champion wants the tool, Executive Sponsor approves intent, Decision Maker signals go-ahead, and IT blocks on missing SOC 2, SSO/SAML, audit log, or role-based admin. The chain breaks at Executive Sponsor → Technical Buyer, the $50K-ACV stall point (§7).
- Clinical or regulated-workflow integration. CMO approves, IT integrates, and clinicians (or analysts, or operators) refuse because the new tool doesn't write back to the system of record (Epic, Salesforce, NetSuite). The Tax Job the buyer never saw at evaluation time becomes the chain-break at rollout.
- B2B2C marketplaces. Payment platform, marketplace, merchant, consumer. The break at marketplace-to-merchant onboarding shows up as a consumer-side metric drop weeks later.
- Procurement or legal late-stage stalls. Deal closed verbally, then legal refuses to sign on indemnification language or data-residency clauses. The deal slips a quarter or dies.
Most B2B chain-breaks are personal-Job failures at role boundaries, not business-Job failures — the §5 personal-Job dominance applied to role boundaries. The IT director's business Job ("keep the systems running") may be served by your product. Their personal Job ("don't let an un-audited tool into my perimeter — if it leaks, I'm fired") fires the veto. An airtight business case still dies at IT review when the seller never addressed it.
Chain length varies sharply by deal size:
- SMB B2B has 1–2 roles (founder = Executive Sponsor = Decision Maker = Approver; or founder plus one IT-savvy operator). Chain breaks are rare; deals close in days or weeks.
- Mid-market has 3–5 roles (Executive Sponsor, Decision Maker, Approver / CFO, IT, sometimes legal). This is where most deals, most chain breaks, and most leverage from the §3 information-asset thesis sit.
- Enterprise has 7+ roles (champion, Decision Maker, IT, security, legal, procurement, end-user representatives, sometimes a sponsoring executive). Chain breaks are the default state. Expect 3–6+ month cycles. The §3 thesis becomes operationally mandatory.
Map the B2B Critical Chain of Jobs as roles × Jobs per role, not as a linear path. Fix chain-breaks with role-specific evidence and tooling, not better core product. IT directors need SOC 2 attestation and a one-pager their CFO will accept, not a new product feature. Legal needs a master-service-agreement template and indemnification language, not a price cut. Time outreach to predictable chain-receptivity windows (Critical Chain of Jobs §6): Q4 budget cycles, post-incident vendor reviews, new-role onboarding for the Decision Maker, regulatory-deadline windows. The receptivity bar is much lower during these windows than in steady state.
10. Segmentation in B2B — same Core-Jobs-and-criteria root as B2C, with three operational additions
Segmentation in B2B is fundamentally the same as B2C — sets of customers performing similar Core Jobs with similar success criteria (per Segmentation). Industry, company size, and revenue band are refinements. Core Jobs and criteria are the root.
Three operational additions for B2B that B2C doesn't have:
- Map the role chain per segment (§7). Two segments with identical Core Jobs but different role chains — say a founder-led 50-person startup versus a functionally-split 5,000-person enterprise — require different sales motions even if the product is identical. They need different stakeholder maps, different objection handling, and different sales-cycle length.
- Map the deal-approval process per segment. Bottom-up versus top-down purchasing, formal procurement versus credit-card swipe, proposal-required versus purchase-order-issued: each shape needs a different funnel. Slack's bottom-up growth into enterprises and Salesforce's top-down enterprise sale are the two endpoint patterns. Most B2B segments cluster around one or the other.
- Map the budget cycle and budget-holder per segment. A segment whose budget cycle is calendar-Q4 needs Q3 acquisition motion. A segment whose budget is project-based and approved ad-hoc needs always-on motion. The same product sold to two segments with different budget structures can look identical at acquisition and diverge sharply after renewal and expansion.
B2B has lower Job-existence uncertainty than B2C — a useful asymmetry for RAT prioritization. In B2C there is significant uncertainty whether the Big Job exists in the segment at all: dormant Jobs, novel categories, behavior-change required to activate the Job (see Behaviour Change §5 for Consideration Activators load on dormant Jobs and Critical Chain of Jobs §6 for the First-time vs. Nth-time path split). The main B2C RAT risk is is there demand? In B2B there is much lower uncertainty whether the Job exists. At any given moment a company is either already performing the Job with the incumbent solution, or actively searching for a vendor against known criteria. The main B2B RAT risk is can we push our solution through the complexity tax (§1)? Do we know the role chain, the budget, the objections?
For B2B research, build the Job hypothesis list before the first interview and use each interview to confirm-or-falsify rather than to discover from scratch. Recruit the Decision Maker directly, not via an end-user, even when the end-user is easier to find. End-user interviews surface end-user Jobs, often a weak signal for purchase. Decision Maker interviews surface roles, deal process, budget, and objections, a high signal for purchase. Focus interview budget on Problems with the incumbent, not on hypothetical features. A customer fails to perform a Job for only two reasons: it is too hard (a Barrier — Barrier Removal) or not important enough (filtered upstream by past payment — AJTBD key theses §15). In B2B, "not-important-enough" is filtered upstream by past payment. "Hard" is what kills deals, and the source of "hard" is almost always a Problem with the incumbent that the new vendor can solve.
ABCDX-on-B2B is a separate move (per ABCDX Segmentation). Once a B2B base is paying, the per-account margin × satisfaction segmentation produces patterns that often invert team intuition. A recurring discovery shape in boutique B2B-services and SaaS practices: the team assumes the A-segment is mid-market customers in the $100–200K ACV band, but ABCDX analysis surfaces that A is actually the top 10% by margin — a different industry, a different deal-size band, or a different use-case the product was delivering as a side-effect. A deliberate refocus on the actual-A segment routinely produces material revenue lift over the next few quarters. The general principle: ABCDX-on-A/B routinely identifies a segment within the paying base the team didn't realize was the target segment.
11. B2B Job structure — same eight elements as B2C, with two new dimensions inside context
The eight-element structure of a single Job (Job Structure §2–§10) — context, negative emotions, Consideration Set, trigger, expected outcome, success criteria, higher-level Job, positive emotions — applies in B2B without modification. What changes is what sits inside the context element: two new dimensions B2C doesn't have.
- The company's past experience. This is the company-level history that shapes how the current buyer evaluates options. Example: the company missed the mobile transition in 2009–2012 and watched competitors capture market share. Now every new technology category (AI, voice, AR) gets pre-emptively evaluated to avoid repeating the miss. Operational consequence: the prior trauma is itself a lever for loading Consideration Activators. Surface it in interviews ("what category did your company miss in the past, and what did it cost?") and load against the trauma's current shape.
- The company's structural traits. These are hierarchy depth, decision-making centralization, control-vs-trust culture, founder-led vs. professional-management, public vs. private. Examples: a 30,000-person bank requires every vendor through a 90-day procurement process; a 50-person Series A startup runs the entire vendor evaluation on Slack in a week. Same product, two utterly different deal structures, and the difference shows up before the first Personal Job is even surfaced.
The Business Job's higher-level Job is the KPI written into the role's plan. At the top of the business chain, the KPI is itself terminal: no higher-level Job above it inside the company. Above it sits the role-holder's personal Jobs, on the parallel graph. "Hit the sales plan" is terminal for the VP of Sales as a business Job. Above it on the personal graph sits "get promoted to CRO," "not get fired," and "have a story to tell." The two graphs are independent but interact at every node.
A complete B2B Job record contains the eight elements per role twice: once for the business graph, once for the personal graph. Records that only document the business graph are systematically incomplete, and the missing personal-graph side is exactly where the deal stalls. Cross-link the two graphs explicitly. The personal Job at each node is performed in service of the business Job at that node. The business Job is performed because the personal Job is served by performing it. Capture company traits and company past-experience at the segment level, not just the account level. Company traits cluster by industry × size × maturity, so mapping them once at the segment level lets the same trait map apply across all accounts in the segment.
12. Recruiting Decision Makers is structurally a sales activity, not a research activity — account-based marketing as the operational shape
The hardest question in B2B research is not what to ask — it is how to get the Decision Maker on a call at all. Decision Makers are scarce, time-poor, and structurally selective about whom they meet. The B2C recruitment shape — post on a panel, screen for criteria, schedule — does not scale to B2B. The operative shape is to treat recruitment as the first stage of sales and build a multi-touch pipeline that converts contact into conversation.
The reframe: you are not recruiting respondents — you are recruiting potential customers. Every Decision Maker you put on a research call is also a sales prospect. Every interview is both data and demand-generation. This recasts the cost-benefit of recruiting investment. Spending two weeks to land a single 45-minute Decision Maker call is unreasonable as research budget allocation, but entirely reasonable as account-based sales investment, and the call produces both deliverables. Mature research practices commonly decline engagements where the Decision Maker population is small enough (sub-1,000 globally) that the project is structurally sales-and-relationship-building rather than research. In those engagements the right investment is in business-development and account-executive capacity, not researcher capacity.
The mechanics that work for cold Decision Maker recruitment (rough order of conversion strength):
- Warm intros, especially with a calendar handoff. Someone the Decision Maker trusts forwards an intro and offers to set up the call. This is the highest-converting channel, and it multiplies all later channels.
- Value-first outreach. Write to the Decision Maker as Director / VP / Head of X, not as researcher, and lead with value, not a favor. Name the likely Job, the trigger and the Problem with the current way, the value you deliver, then a soft ask. Re-positioning the call from help me with research to here's value you can use materially raises response rate.
- Reference to people already interviewed. "I spoke with [recognizable name at peer company] last week — they recommended I talk with you about [the Job]." This is both a warmth signal and a peer-pressure signal.
- Always ask for two intros at the end of every interview: peer companies on the same Job, or the next role downstream in the chain. Compounding the network is the cheapest acquisition channel for the next round.
- Webinar funnels and the offline-conference circuit. Run a topic-led webinar and track which Decision Makers register, attend, and ask questions. At conferences, sales reps pre-book fifteen-minute slots with target accounts the day-of, exchange cards, and follow up the next week. A two-day conference is a concentrated batch of net-new warm Decision Maker contacts.
- Value-add offers in the intro. "We've just finished a study of 30 companies on [this Job] — happy to share the read in exchange for 30 minutes." The Decision Maker trades time for asymmetric value, which lifts conversion materially.
- Cold LinkedIn in US / Western Europe. Cold LinkedIn outreach converts at meaningful rates when the message is well-written and lands a specific peer reference. Cold outreach conversion varies materially by region and category. Calibrate the channel mix by market.
The account-based marketing (ABM) algorithm (rough seven-step structure standard across mature B2B-sales practices):
- Compile the target-company list against the target segment's ideal customer profile.
- Parse open sources (LinkedIn, Crunchbase, company sites, press releases, podcast appearances) to identify the named Decision Maker at each company.
- Enrich contacts across social channels — LinkedIn, X / Twitter, public Slack communities, conference speaker rosters, podcast guest lists.
- Run topical webinars; track registration, attendance, Q&A engagement per account.
- Send peer-referenced cold outreach with value-add offers; warm intros where available.
- Conference attendance with pre-booked 15-minute slots.
- Continuous list-enrichment as each interview produces 1–2 new peer intros.
A 2–3 person team can run this end-to-end; scale beyond that requires dedicated sales-development capacity. The activity is sales-and-marketing, executed under a research label. The boundary between research, demand-gen, and pipeline-building is intentionally blurred. Don't budget Decision Maker recruitment as a research cost line. Budget it as sales / marketing investment with research as a deliverable. The team that does B2B research well is structurally cross-functional: a researcher, a sales-development rep, and a content-marketing partner working as one pod.
13. The B2B sale doesn't end at the signed contract — a significant share of "won" deals don't make it to renewal
The B2B sale's real deliverable is the renewal in year 2, not the signature in year 1. A first-year contract that doesn't renew often doesn't pay back. You spent the cost to win the customer and to implement them against a single year of revenue, so the deal can end underwater. It isn't always a loss. Sometimes year one alone clears its cost; sometimes the customer comes back later. But non-renewal is the weakest version of a "win," and usually an avoidable one. Many "won" deals don't renew, not because a competitor took them, but because the work after signing broke down. How many churn varies by category, deal size, and economics, and smaller customers churn more than enterprise. Whether the base grows or leaks over time is measured by net revenue retention, the signal that the integrator model (§2) is working. The full unit-economics treatment belongs to a future canon page.
The post-sale chain has its own role chain and chain-breaks, distinct from the pre-sale chain in §7 and §9 but structurally similar:
- Onboarding. Implementation manager, champion, and end users. The chain breaks when implementation drags past the buyer's expected timeline, the champion gets reassigned, or the end users can't get to first value within the activation window.
- Adoption. Champion, end users, and occasional Decision Maker review. The chain breaks when usage doesn't reach the activation threshold the business case was built on, the Decision Maker doesn't see the metric move, or end-user resistance accumulates.
- Expansion. Champion, a new Executive Sponsor in an adjacent function, and Decision Maker. The chain breaks when the next Job in the chain (per Critical Chain of Jobs §9) doesn't materialize, or when an adjacent stakeholder vetoes the cross-function spread.
- Renewal. Decision Maker, Approver, and often a new procurement review. The chain breaks when the business case the deal was sold on can't be demonstrated, when budget is reallocated to a competing priority, or when the original champion has left the company.
The champion-departure failure mode is one of the most under-measured B2B churn drivers. A champion who leaves between sale and renewal takes the institutional memory of why this product was bought with them. The replacement's evaluation starts from zero. The renewal conversation is effectively a new enterprise sale with the existing product as the incumbent.
Teams that run §3-style information enablement at the pre-sale stage often also run it at renewal. The renewal Decision Maker is the same target as the original Decision Maker, just shifted in time. Quarterly business reviews, named-CSM relationships, success-metric dashboards, and documented business-case-vs-realized comparisons are all post-sale-chain instruments analogous to the pre-sale information assets in §3. Treat onboarding as part of the sale, not as something that begins after the sale ends. The unit economics of the deal are determined by renewal, and renewal is determined by what happens between contract signature and the first business-case-vs-realized review.
Cross-references
- Job Structure — the eight-element structure of a single Job; §16 specifically on B2B's two parallel graphs and the two personal-Job interview questions
- Critical Chain of Jobs — the operational core; §10 holds the canonical B2B Critical Chain of Jobs (roles × Jobs-per-role) — referenced and extended here in §9; per-role walk dynamics in §4 and §5
- Value Creation — value mechanics applied per role's business and personal Jobs; §10 on segment criteria-priority orders applied to B2B; §17 on unique value living outside current Core Jobs (the integrator-model substrate)
- Behaviour Change — forces of behavior change at the role level; §4 on Consideration Activators as the loading mechanism; §9 on habit as the company-level switching-cost driver
- Segmentation — segmentation root (Core Jobs + criteria) extended in §10 here with B2B-specific operational additions
- ABCDX Segmentation — ABCDX on B2B paying bases; §10 on marketplace's two-side segmentation
- Riskiest Assumption Test §2 — segments-and-Jobs as the root of the RAT chain; §5 on custom risks specific to B2B (Excel-switching, IT-veto)
- AJTBD interview guide — interview question discipline (recruitment lives here in §12 of this file; question discipline lives in the HowTo)
- AJTBD key theses §25 — business + personal Jobs in B2B chains (short canonical form of §5 here)