Why Most Salesforce Projects Fail Before a Single Line of Code Is Written.

Salesforce runs license audits. When misuse is found, the invoice is backdated for years. The funny part is there's no "we didn't know" discount. Audit bills can exceed the original implementation cost.

License selection is the most underrated decision in any Salesforce implementation. Get it wrong, and no amount of clean code or smart automation will save the project.

After working on dozens of Salesforce implementations, here are the most common architectural mistakes I've seen when it comes to license selection, for both internal teams and external users:

1. Picking the license based on price, not persona

Sales Cloud, Service Cloud, Platform, Experience Cloud, Field Service - each has its own object access, feature set, and limitations. A Platform license user can't touch standard Opportunity records. A guest user session has no concept of "logged in context," so personalization, multi-step flows need custom session handling or a login conversion.. Pick by price and the rebuild starts on day one.

2. Treating all Experience Cloud licenses the same

This one hurts the most. Customer Community, Customer Community Plus, Partner Community, and Customer Community Login all look similar on paper. They're not.

Built a public-facing Experience Cloud site recently? Then you already know the trap. Customer Community can't use sharing rules. No roles. Capped at 10 custom objects on the basic tier. The moment requirements grow beyond a simple self-service portal, the license becomes the bottleneck, not the platform.

3. Login vs member-based pricing without modeling usage

Login-based looks cheap until traffic spikes during a campaign or renewal cycle. That $5/login quietly becomes $40K/month. Member-based is predictable but heavier upfront. Most teams never model both across a 3-year horizon before signing.

4. Misusing Partner Community for end customers

Partner Community is for partners reselling or servicing your product. Not for customers buying it. Salesforce's compliance team catches this in audits. Every time.

5. Ignoring object and feature limits per license

Forecasting, territory management, approval processes, custom object access, API call limits, all vary by license type. Architects often promise features in the design phase that the chosen license simply doesn't support.

6. Skipping the sharing model implications

External user licenses don't behave like internal ones. No role hierarchy for Customer Community users. Sharing sets and sharing groups become the only path. If the sharing logic was designed assuming standard internal behavior, the entire security model needs rework.

7. Underestimating audit risk

A $280K Salesforce audit bill. Two years of license misuse. One wrong choice at the architecture stage.

What actually works:

• Map every persona, internal and external, to a license BEFORE the build
• Read the actual limitations doc, not the sales one-pager
• Model 3 years of usage, including spikes and seasonal load
• For public Experience Cloud sites, validate guest user limits early
• Get the license recommendation in writing from your account executive.

The wrong license doesn't just cost money. It costs six months of rebuild work and the trust of the sponsor.

What's the worst Salesforce licensing mistake you've come across? Drop it in the comments.

Salesforce #SalesforceArchitect #ExperienceCloud #SalesforceLicensing #CRM #SalesforceAdmin #SalesforceCommunity #SalesforcePartner Accenture