Selling to companies changes how Salesforce stores customers, tracks decisions, prices deals and serves accounts after the sale. Below, you’ll find each change in a Salesforce B2B implementation, from the first data model decision to the license bill, with every Salesforce limit and list price taken from Salesforce’s own pages. Choices you can’t reverse later get flagged, because those are the decisions worth making first.
How Salesforce for B2B Differs From Salesforce for Consumers
In Salesforce for B2B, the customer is a company. People sit inside that company as contacts, a single deal can involve several of them, prices come out of negotiation and the relationship carries on through contracts, renewals and agreed service levels long after the first order. That account model comes before any configuration, so it’s the first thing to settle in any Salesforce implementation for a business that sells to other businesses.
Salesforce’s own B2B CRM guide describes B2B CRM systems as built to manage bigger budget sales, “track long-term sales cycles, and facilitate relationships with multiple stakeholders within a business.” Salesforce’s What Is B2B Sales? guide adds that stakeholders from IT, legal, procurement and the C-suite all take part in the purchase, which is why B2B sales take longer to close. Long cycles and multi-person buying drive the changes in the table below:
Area | Selling to individuals | Selling to companies | Salesforce feature |
|---|---|---|---|
Customer record | One person | A company with people attached | Business accounts and contacts |
Company structure | Rarely relevant | Parent companies and subsidiaries | Account hierarchy |
People | Belong to one customer | Some work with several companies | Contacts to Multiple Accounts |
Decision | One buyer | A group with defined roles | Opportunity contact roles |
Sales coverage | One owner | Reps, specialists and executives | Opportunity teams and account teams |
Credit | One rep | Shared or overlay credit | Opportunity splits |
Price | List or promotional price | Negotiated, contract-based price | Quotes, price books and Revenue Cloud Advanced |
After the sale | An order | Contracts, renewals and service levels | Contracts, orders and entitlements |
Channel | Direct | Partners and resellers as well | Partner Cloud and partner licenses |
Most of these rows trace back to one early decision, how you store the customer, so that’s where the build starts.
Business Accounts, Person Accounts or Both?
Business accounts are the default. Salesforce stores companies and other entities as business accounts unless you change it, and contacts sit under each account as the people you deal with. For a company that sells only to other businesses, this is the whole customer model, and lead conversion fits it directly: converting a lead creates an account, a contact and, if you choose, an opportunity.
Person accounts are for individual buyers. A person account combines account and contact fields into one record for a consumer. It can’t take a parent account, can’t appear in an account hierarchy and can’t be a contact’s primary account, and in Lightning a converted lead with no Company value becomes a person account once the feature is on. Even with Contacts to Multiple Accounts turned on, a person account’s links to other accounts are always indirect, so it never anchors a group of contacts the way a business account does.
Decide before you enable. Salesforce’s guide to enabling person accounts is blunt: once the feature is on, it can’t be disabled. It recommends previewing the change in a sandbox and needs an admin with the Customize Application and View All Profiles permissions, and Salesforce’s prerequisites also call for a business account record type plus Contact sharing set to Controlled by Parent. If you sell to companies and to individuals, you’ll need both account types, so answer that question before the first record loads.
Account Hierarchies, Subsidiaries and Contacts Who Span Companies
A large customer can buy through several entities. A parent company owns subsidiaries, each subsidiary may buy on its own terms, and the people you deal with don’t always stay inside one of them. Salesforce builds the account hierarchy from the Parent Account field, and its account hierarchy setup guide confirms the hierarchy view is available from Essentials Edition up.
What you need to model | Salesforce feature | What to know |
|---|---|---|
A parent company with subsidiaries | Account hierarchy | Users can view up to 2,000 accounts from each point where they enter a hierarchy, with up to 15 columns, and Salesforce notes that hierarchies can’t be viewed in the mobile app |
People who work with several companies | The primary account is a direct relationship and the others are indirect; every contact still needs a primary account, and the feature can’t be turned on through the Metadata API | |
Subsidiaries that buy on their own terms | Separate child accounts | Each child keeps its own owner, billing and shipping addresses and opportunities, while its Parent Account field ties it to the group |
New leads from companies you already know | Lead conversion with matching and duplicate rules | Conversion can update the existing account and contact, which keeps duplicates out, and each object allows up to 5 active duplicate rules |
Hierarchies need care during data migration. Parent records have to load before their children so the links survive, and rebuilding parent-child record links is a step of its own in Salesforce data migration services. Decide which account sits at the top of each hierarchy before the first load, because moving it later means changing Parent Account values on records that users, reports and integrations already rely on.
Tracking the Buying Committee and Your Own Deal Team
In B2B sales, several people take part in a single purchase. Salesforce records who’s involved on the opportunity and the account, on the buyer’s side and on yours, so every deal shows who decides and who sells. These 5 features do most of the work:
- Opportunity contact roles. Opportunity contact roles record the part each contact plays in a deal, with roles such as Evaluator or Decision Maker. They’re available in all editions, so even a small team can capture who decides.
- A single primary contact. Salesforce allows only 1 primary contact per opportunity. Triggers and validation rules can control how contact roles are used, for example by blocking a stage change until a Decision Maker is named.
- Opportunity teams. When several reps and specialists work the same deal, an opportunity team records who’s involved and lets them track progress together. Opportunity teams are available in Enterprise, Performance, Unlimited and Developer editions.
- Account teams. Account teams give a key account standing coverage across all its deals. Salesforce’s own examples of team roles include an executive sponsor, a dedicated support agent and a project manager.
- Opportunity splits. Splits share revenue from a Closed Won deal among team members. Revenue and overlay splits come by default, and you can add up to 6 custom split types, choosing for each one whether it must total 100%.
Put the contact-role rules into the build from day 1. A deal with no Decision Maker on record warns a manager about the forecast, and that warning only exists if reps have to fill the role in, which makes these settings central to any Sales Cloud implementation. Plan teams and splits together too, since opportunity splits only work once team selling is turned on.
The role values themselves are yours to set. Salesforce lets you customize opportunity contact roles, so add the roles your buyers actually use, such as Procurement or Legal, and keep the list short enough that reps pick the right one without guessing.
How B2B Sales Teams Split Territories and Forecast Revenue
Territories decide which rep owns which accounts, and forecasts decide how that pipeline rolls up to managers. Set them up in this order:
- Build a single territory model. Sales Territories, formerly Enterprise Territory Management, organizes accounts into territories inside a model, and only 1 model can be active at a time.
- Write account assignment rules. Rules assign accounts to territories automatically, with up to 15 assignment rules per territory, and you can still assign accounts and leads by hand.
- Preview the model in Planning state. Every new model starts in Planning state, which Salesforce says lets you preview its territory hierarchy before deploying it, so the structure gets checked before any rep’s accounts change hands.
- Choose forecast types. Salesforce Forecasting builds forecasts from opportunities, opportunity products, splits, product schedules or territories, with up to 4 forecast types active at once, and territory forecasts follow whichever territory model is active.
- Match splits to forecasts. If overlay reps receive split credit, add a split-based forecast type so their numbers show up in their own forecast, and turn on opportunity splits first, since split-based forecasts depend on them.
Edition limits shape the plan too: Enterprise Edition allows 2 territory models, Performance and Unlimited allow 4, and the standard allocation is up to 1,000 territories per model, so a second model gives you room to plan next year’s territories while this year’s model stays active. One gap needs a decision of its own, because Salesforce notes that filter-based opportunity territory assignment isn’t triggered when an opportunity is created through lead conversion. Decide how those new deals get a territory before reps start converting leads in volume.
Quotes, Contracts and Renewals Now That CPQ Is End of Sale
Standard Salesforce already covers the basic B2B paper trail. Quotes are built from an opportunity and its products, contracts record the agreement with an account and turn read-only once activated, and orders, which Salesforce defines as an agreement to provision services or deliver products, attach to a contract or an account. The bigger decision is what handles complex pricing and approvals, because Salesforce CPQ, its long-standing quoting product, is no longer sold to new customers.
Compared on | Standard quotes and contracts | Salesforce CPQ | Revenue Cloud Advanced |
|---|---|---|---|
Sold to new customers | Yes, with Sales editions | No | Yes |
Status | Current | End of sale with no end-of-life date announced; no new feature development | Salesforce’s named successor to CPQ |
What it covers | Quotes, contracts and orders | Configure, price and quote | Product catalog, pricing, configurator, quotes, orders, contracts and billing |
Price | Included in Sales editions | Not listed, since new sales have ended | $200 per user per month, billed annually, with an annual contract |
Approvals | Flow Approval Processes | CPQ Advanced Approvals | Advanced Approvals |
Salesforce’s CPQ end-of-sale notice confirms that existing customers can keep using CPQ, buy more users, renew and get support, so nothing stops working on a set date. What’s left to decide is timing. Revenue Cloud Advanced sits inside the Agentforce Revenue Management suite, so teams new to Salesforce can implement it directly with Revenue Cloud services, while existing CPQ customers plan a CPQ to Revenue Cloud migration on their own timetable.
Renewals and discount approvals follow the same split. In CPQ, a renewal opportunity is created from the contract and CPQ builds the renewal quote, while in Agentforce Revenue Management, renewing a customer asset generates a renewal quote and then an order. For approvals, Salesforce points core-platform teams to Flow Approval Processes, and in Revenue Cloud Advanced its own Approval Designer example routes quotes discounted at 25% or more to a Sales Manager and adds an SVP of Sales above 50%.
Selling Through Partners, Resellers and Distributors
When partners sell for you, people outside your company need to see leads, opportunities and accounts. That changes which licenses you buy and how sharing works:
- Partner Cloud, Salesforce’s partner suite, brings Partner Ecosystem Management and Partner Relationship Management together, so partners work on the same accounts and opportunities as your direct team.
- Salesforce’s PRM page describes connecting partners to deals through deal registration and lead routing automation, so partners can log the opportunities they’re working and new leads can reach the right partner for follow-up.
- Salesforce’s Experience Cloud user licenses page positions Partner Community for business-to-business sites that need sales data. Customer Community suits large numbers of external users who need cases or knowledge, and Customer Community Plus adds reports, dashboards and standard sharing.
- Partner Community and Customer Community Plus require roles tied to each external user, so partner access follows a role structure you have to design. The partner hierarchy uses Partner User, Partner Manager and Partner Executive roles, and Salesforce’s Help recommends reducing that to 1 role where you can.
- A partner starts as a business account that you enable as a partner account, and each of its contacts becomes a partner user once you enable them. The designated account can then be linked to your partner site.
Role design also decides what each partner manager sees, because partner users can view and edit data owned by or shared with users below them in the partner hierarchy, regardless of the org’s sharing model. If you also serve customers through a self-service site, you’ll run partner and customer access side by side, each on its own license, and both are built as partner and customer portals on Experience Cloud.
When Business Buyers Order Online With Salesforce B2B Commerce
Salesforce B2B Commerce runs on the same accounts and contacts as your sales org, so the account design above carries straight into the store. Each store decision below shapes what buyers can see, what they pay and how their orders reach your back office:
Store decision | How it works in B2B Commerce |
|---|---|
Buyer accounts | You turn a business account into a buyer with Enable as Buyer, then enable its contacts as customer users, so start with the accounts that already reorder most |
Buyer groups | Buyer groups give several accounts the same store, price books and entitlements, and a single account can belong to up to 20 buyer groups, so it can sit in a price tier and a regional catalog at once |
Entitlement policies | Buyer groups and entitlement policies decide which products each group sees and whether it sees prices, which supports buyer-specific pricing and product steering |
Pricing strategy | Best Price shows the lowest price across a buyer’s assigned price books, while Priority Price follows the order you set, so pick one before loading negotiated price books |
Licenses | Buyers who need other buyers’ data need Customer Community Plus or higher; Standalone includes 2 stores and Standalone Plus includes 10, so count your storefronts early |
Checkout | B2B stores use custom checkout only, and Commerce extensions bring in pricing, inventory, shipping and tax services from whichever system owns them, often the ERP |
Not every B2B company needs a store. If buyers still order through reps and email, Sales Cloud with quotes and orders covers it, and a store starts to pay off when buyers want self-service ordering. B2B Commerce is supported on Enterprise, Unlimited and Developer editions, and companies that also sell to consumers can run a B2B store and a D2C store from the same org.
For manufacturers that also sell through dealers and distributors, those portals run on the Experience Cloud licenses covered in the partner section, and our page on Salesforce for manufacturers shows how they sit beside the store.
How Marketing Changes When You Target Accounts
Account-based marketing starts from a list of target companies, then reaches the people inside each one. Marketing Cloud Account Engagement, formerly Pardot, is Salesforce’s B2B marketing automation platform, and it can point that effort at the accounts most likely to buy. When account data sits in several systems, Data 360, formerly Data Cloud, can consolidate those sources into unified profiles of customers or accounts first.
Account Engagement qualifies leads with 2 separate signals. Scoring and grading work as a pair: scoring tracks what a prospect does, grading reflects how well their persona, fit or demographic matches your ideal buyer, and together they tell sales when a lead is ready. That split matters in B2B sales, where a junior researcher can be very active while the person who signs barely clicks.
Account Engagement’s Salesforce connector syncs prospect data in both directions every 2 to 4 minutes. It also syncs opportunities for ROI reporting and can sync with person accounts for companies that sell to both firms and individuals. Agentforce Engagement, formerly Agentforce Lead Nurturing, can now send first-touch emails, follow up and hand interested prospects to reps, and it works best on top of a clean Account Engagement setup with scoring and grading already tuned.
What Changes After the Sale: Service Levels and ERP Data
Service Levels Written Into Contracts
Business customers can buy support on agreed terms, such as phone support with a set response time, and Salesforce’s entitlement management, part of Agentforce Service (formerly Service Cloud), lets you define, enforce and track those service levels. An entitlement is a unit of support such as phone or web support, a service contract records the agreement with the customer, and a milestone such as First Response is a required step that sets the clock on each case. Entitlements attach to accounts, contacts, assets and service contracts, but contacts don’t inherit an account’s entitlements automatically, so decide which record carries the promise.
Keeping ERP and Salesforce in Step
Many B2B companies already run an ERP for orders, invoices, stock and credit, and Salesforce’s integration patterns name the options for connecting it:
- Remote process invocation. Salesforce calls the ERP, either waiting for a reply or firing and moving on. Salesforce’s example creates an order when an opportunity closes, while the back-end ERP stays the data master.
- Batch data synchronization. Records move on a schedule, using an ETL tool that can run change data capture against the source data. It fits data that can arrive on a delay, such as invoice history loaded overnight.
- Data virtualization. ERP data appears in Salesforce screens without being copied into Salesforce. Reps check details such as order history in place, and the ERP keeps the only copy.
Decide which system owns orders, prices, inventory and credit status before anyone builds a connection, then design the Salesforce ERP integration around those decisions. The same ownership map tells you which fields reps can edit in Salesforce and which ones they should only see.
Salesforce Choices You Can’t Undo Later
A few B2B choices lock in once you make them. Each row below comes from Salesforce’s own documentation, and each one deserves a decision before the build:
Choice | What Salesforce says | Decide this first |
|---|---|---|
Person accounts | Can’t be disabled after they’re enabled | Whether you’ll ever sell to individuals |
Multiple currencies | Can’t be disabled once enabled | Which currencies you’ll quote and report in |
Activated contracts | Become read-only | Who activates contracts, and at what point |
Converted leads | Can’t be unconverted, and editing them needs the View and Edit Converted Leads permission | Matching and conversion rules for existing accounts |
Disabling a buyer account | Deletes its buyer-group associations | Buyer-group design before buyers come on board |
Archived territory models | Can’t be reactivated | When to retire the current territory model |
Test each of these in a sandbox first. Each one is quick to do and has no undo button, which is exactly why it needs an owner and a decision date. The first 2 rows matter most for B2B companies that also sell to consumers or quote across borders, and both questions can surface after go-live if nobody raises them during discovery.
Multiple currencies needs extra planning because it changes reporting as well as quoting: Salesforce converts amounts to your corporate currency using conversion rates that admins maintain, and dated exchange rates need Advanced Currency Management.
What a B2B Salesforce License Stack Costs
A B2B org can need more than sales seats. The worked example below uses list prices from Salesforce’s Sales pricing page and its other product pages as of October 8, 2026, all billed annually and subject to change. It models a hypothetical company with 50 sales users, 40 partner users and 10 of those sales users who also build quotes, so swap in your own counts:
- Sales seats: 50 users on Core at $195 per user per month comes to $117,000 a year. Core sits between Pro Suite at $100 and Advanced at $395 per user per month, so check which features your team actually needs before picking a tier.
- Partner access: 40 members on Partner Relationship Management, the PRM edition of Partner Cloud, at $25 per member per month comes to $12,000 a year. Login-based pricing starts at $10 per login per month.
- Marketing: Account Engagement Growth+ at $1,250 per org per month comes to $15,000 a year, with 10,000 contacts included.
- Quoting: 10 Revenue Cloud Advanced users at $200 per user per month come to $24,000 a year. Revenue Cloud Growth lists at $150 per user per month if Advanced is more than you need.
- Total: $168,000 a year at list price, before Agentforce add-ons, discounts, taxes or implementation services. The same Sales pricing page lists Agentforce for Sales from $125 per user per month if you add AI agents later.
B2B Commerce isn’t in the total because Salesforce doesn’t publish its price: it’s licensed by gross merchandise volume or order count and quoted directly. Feature availability is the other thing to check. Salesforce positions Core, Advanced and Max against the legacy Enterprise, Unlimited and Agentforce 1 editions, but Help pages still list features such as opportunity splits and Sales Territories under the legacy names, so confirm each feature against the edition on your order form.
Services are a separate line. HyphenX’s Salesforce implementation cost guide gives planning bands of $15,000 to $40,000 for a focused rollout, $50,000 to $200,000 for a mid-market program and $200,000 to $1 million or more for an enterprise transformation.
A Pre-Build Checklist for Your Salesforce B2B Implementation
Answer these before configuration starts. Each one maps to a decision covered above:
☐ Do we sell to individuals as well as companies, now or in our plans?
☐ Which accounts are parents, and who maintains the hierarchy?
☐ Which contacts work with more than one company?
☐ Which buying-committee roles must every deal record?
☐ How is credit split between reps and overlay specialists?
☐ Are territories set by region, industry or named account?
☐ Who approves discounts, and at what level?
☐ Do partners sell for us, and which license do they need?
☐ Which system owns orders, prices, inventory and credit status?
☐ Will we quote and report in more than 1 currency?
☐ Do any buyers need to browse and reorder online?
☐ Which service levels do our contracts promise, and to whom?
☐ Will marketing qualify leads by account fit as well as activity?
Any question without an answer yet is a scope risk, so settle it early, while a change of mind still costs only a meeting. Together the answers decide the account model, the licenses on the order form and the integrations in scope, and any estimate made without them rests on assumptions you haven’t agreed to.
B2B Salesforce Specialists for Every Part of the Build
B2B builds touch more moving parts than most: account hierarchies, territories, Revenue Cloud quoting, partner portals and ERP links. HyphenX Solutions has 250+ Salesforce professionals, so each area gets a specialist who has configured it before. Choices you can’t undo, such as person accounts and multiple currencies, get a senior review before anyone switches them on. Read more about HyphenX Solutions.
Case Study
Here’s how matching and source-of-truth rules, part of the account model above, played out on a real HyphenX Sales Cloud project for a B2B sales team.
B2B SaaS Sales Team: Clean Account Data From 3 Prospecting Tools
A B2B SaaS company running a structured outbound motion sourced prospects through Apollo, Lusha and Hunter, and none of the 3 tools connected to Salesforce. Reps searched, copied, pasted and deduplicated records by hand, while leadership forecast from a pipeline nobody fully trusted. HyphenX connected all 3 tools to Sales Cloud through their APIs, with real-time deduplication against existing records, Hunter email verification before each record was written and a field-level source-of-truth policy.
Key takeaway: B2B prospect data arrives from several sources at once, so matching and source-of-truth rules belong in the account model from the start.
Read the full case study: From Swivel-Chair Prospecting to Single-Click Pipeline
Frequently Asked Questions
What is a Salesforce B2B implementation?
It’s the work of configuring Salesforce for a business whose customers are other companies. That covers the account model, buying-committee tracking, territories, quoting and approvals, partner access and post-sale service levels, with B2B Commerce and account-based marketing added when buyers order online or marketing targets named accounts.
How is Salesforce set up differently for B2B and B2C?
A consumer-focused org can store each buyer as a person account and sell at list or promotional prices. A B2B org stores companies as business accounts, models parent and subsidiary relationships, records buying-committee roles on each opportunity and prices through quotes and contracts. Service levels and partner channels are common B2B additions.
Should a B2B company enable person accounts?
Only if it also sells to individuals. Person accounts can’t be disabled once enabled, they can’t sit in an account hierarchy, and they change how leads without a company name convert. If individual buyers are a real part of your business, enable them after testing the change in a sandbox.
Can a contact belong to more than one account in Salesforce?
Yes, Contacts to Multiple Accounts relates 1 contact to several accounts. The contact keeps a direct relationship with its primary account, which every contact still needs, and indirect relationships with the others. It suits advisors, board members and people who work across a parent company and its subsidiaries.
How do account hierarchies work in Salesforce?
Each account can point to a parent through the Parent Account field, and that chain of parents forms the hierarchy. A Lightning user sees at most 2,000 accounts from any entry point into the hierarchy. Hierarchies don’t display in the mobile app, and person accounts can’t take part in them.
How do you track a buying committee in Salesforce?
Add each person to the opportunity with a contact role, such as Evaluator or Decision Maker, and mark 1 primary contact. Validation rules can require key roles before a deal moves to the next stage, and the standard Opportunities with Contact Roles report type lets managers review who’s recorded on each open deal.
How does Salesforce handle territories for B2B sales teams?
Sales Territories, formerly Enterprise Territory Management, groups accounts into territories using assignment rules inside a territory model. A single active model applies at any moment, each territory supports up to 15 assignment rules, and territory-based forecasts can roll pipeline up through that structure.
Is Salesforce CPQ still available?
Only to existing customers. New customers can’t buy Salesforce CPQ, and it gets no new features, though current customers keep their licenses, support and the option to add users. New buyers start on Revenue Cloud Advanced, which Salesforce names as CPQ’s successor.
Do I need Salesforce B2B Commerce or just Sales Cloud?
Sales Cloud handles rep-led selling with quotes and orders. B2B Commerce adds a store on the same accounts, with buyer groups and entitlement policies controlling which products and prices each buyer sees, and Salesforce prices it on gross merchandise volume or orders placed, so it fits once self-service ordering is part of the plan.
What license do partners need to work in Salesforce?
Partners who need sales data such as leads and opportunities use the Partner Community license, which Salesforce positions for business-to-business partner relationship management. It requires a role for each partner user, so plan the partner role structure alongside your internal one. Salesforce also sells partner access through Partner Cloud’s PRM edition, listed at $25 per member per month.
How does account-based marketing work with Salesforce?
Account-based marketing picks target companies first and then runs campaigns at the people inside them, and Salesforce’s B2B marketing automation for it is Account Engagement, formerly Pardot. Grading checks how well each prospect fits your ideal buyer while scoring tracks their activity, so a target account’s contacts can show up as fit but quiet or busy but junior. The connector keeps prospects and opportunities in sync with Salesforce every 2 to 4 minutes, so sales and marketing work from the same account data.
How do service-level agreements work for business customers in Salesforce?
Entitlement management defines the support a customer is owed, service contracts record the agreement, and milestones such as First Response track the clock on each case. Entitlements can attach to accounts, contacts, assets or service contracts, and the feature needs Agentforce Service.
How does Salesforce connect to an ERP in a B2B setup?
Salesforce’s integration patterns include one where Salesforce creates the order at Closed Won and the ERP stays the master for orders, invoices and inventory. Decide which system owns each piece of data first, then choose a pattern that fits, such as real-time calls or batch synchronization.
How much does Salesforce cost for a B2B company?
Paid Sales editions list from $25 per user per month for Starter Suite to $550 for Max, with Core at $195. A B2B org may add partner licenses, Account Engagement and Revenue Cloud Advanced, and the worked example above, with 50 sales users, comes to $168,000 a year at list price before services.
Which Salesforce settings can’t be undone?
Person accounts and multiple currencies are both permanent once enabled. Activated contracts turn read-only and converted leads can’t be unconverted, and in B2B Commerce, disabling a buyer account deletes its buyer-group memberships. An archived territory model can’t be reactivated either, so preview each change in a sandbox before production.
