How to Evaluate Salesforce for Your Business

If you’re considering Salesforce for your organization — or you’ve already signed a contract and are wondering what you’ve gotten into — this guide is for you. After years of working with the Salesforce ecosystem, I’ve seen companies thrive on it and others drown in licensing costs and misconfigured orgs. The difference almost always comes down to how well they evaluated the platform before committing.

This is the first in a series where I break down everything you need to know about evaluating Salesforce, from picking the right edition to negotiating your contract.

What is Salesforce?

At its core, Salesforce is a cloud-based Customer Relationship Management (CRM) platform. But calling it “just a CRM” is like calling AWS “just a server.” Over the past two decades, Salesforce has evolved into an entire ecosystem of products covering sales, service, marketing, analytics, integration, app development, and more.

The platform runs on a multi-tenant architecture — meaning all customers share the same underlying infrastructure, but each org’s data is isolated and secure. This is what enables Salesforce to push three major releases per year (Spring, Summer, Winter) to every customer simultaneously.

Key concepts to understand upfront:

• Org — Your company’s dedicated Salesforce instance. Think of it as your tenant in the multi-tenant building.
• Objects — Database tables (e.g., Accounts, Contacts, Opportunities). Salesforce provides standard objects out of the box, and you can create custom ones.
• Records — Rows in those tables. A single Contact or a single Opportunity is a record.
• App Exchange — Salesforce’s marketplace for third-party apps and components that extend platform functionality.
• Apex — Salesforce’s proprietary programming language (Java-like) for server-side logic.
• Lightning Web Components (LWC) — The modern UI framework for building custom frontend components.
• Flows — Salesforce’s no-code/low-code automation tool that replaces the older Workflow Rules and Process Builder.

If you’re coming from a traditional software engineering background, think of Salesforce as a Platform-as-a-Service (PaaS) with a pre-built data model, UI layer, authentication, and business logic engine — all configurable through a browser.

How to Set Up a Free Salesforce Org

Before you spend a single rupee, get your hands on a free Developer Edition org. This is non-negotiable. You cannot evaluate Salesforce by reading documentation alone.

Option 1: Developer Edition (recommended for learning)

1. Go to developer.salesforce.com/signup
2. Fill in your details and sign up
3. You’ll receive a verification email — click through and set your password
4. You now have a fully functional Salesforce org with most features enabled

Developer orgs are free forever, have limited storage (5MB data, 20MB file), but include access to almost every platform feature. They’re perfect for prototyping and learning.

Option 2: Free Trial (recommended for business evaluation)

If you’re evaluating Salesforce for purchase, request a 30-day free trial of the specific edition you’re considering (Sales Cloud, Service Cloud, etc.) through salesforce.com. This gives you a more realistic picture of what you’ll actually get.

Option 3: Trailhead Playground

Salesforce’s learning platform Trailhead automatically provisions playground orgs when you start hands-on challenges. These are great for structured learning but less suitable for open-ended evaluation.

Pro tip: Create at least two Developer orgs — one for clean experimentation and one that mirrors your actual business scenario. Orgs are free; time spent debugging a polluted environment is not.

How to Log In to Your Salesforce Org

This sounds trivial, but there are nuances worth knowing:

• Production login: login.salesforce.com
• Sandbox login: test.salesforce.com
• Custom domain (My Domain): Once configured, you’ll log in via yourcompany.my.salesforce.com

Salesforce enforces Multi-Factor Authentication (MFA) as a requirement. You’ll need the Salesforce Authenticator app or a compatible TOTP app on your phone.

Things that trip people up:

• Logging into a sandbox with the production URL (or vice versa) — you’ll get a cryptic error
• Locked accounts after failed login attempts — an admin needs to unlock you via Setup
• IP restrictions — if your org has IP whitelisting enabled, you can’t log in from an unrecognized network without a verification code

If you’re managing multiple orgs (which you will be), I strongly recommend using a browser with profile support (Chrome profiles, Firefox containers) to keep sessions separate.

Picking the Right Org Edition

This is one of the most consequential decisions you’ll make, because switching editions later is painful and expensive. Salesforce offers several editions, each with different feature sets and price points:

Salesforce Editions Overview

My Recommendation

For most businesses seriously evaluating Salesforce, Enterprise Edition is the sweet spot. Here’s why:

• API access — If you need to integrate Salesforce with anything (and you will), you need API access. Professional Edition doesn’t include it natively.
• Apex and LWC — Custom development capabilities are essential for anything beyond basic CRM. Professional Edition locks you out.
• Advanced automation — Enterprise gives you Flow orchestration, approval processes, and platform events.
• Custom objects and fields — Higher limits than Professional.

Avoid Essentials unless you’re a team of five using Salesforce purely as a contact database. The limitations will strangle you within months.

Consider Unlimited only if you have a large org with heavy support needs and complex customization requirements. The price jump from Enterprise is significant, and you should quantify exactly what additional features you need.

How to Choose the Right User License Types

Salesforce licensing is where things get expensive — and confusing. There are different license types that determine what a user can access, and getting this wrong means either overspending or under-provisioning.

Core License Types

Salesforce License (Full CRM)

• Access to standard CRM features: Accounts, Contacts, Opportunities, Cases, etc.
• Required for sales reps, service agents, and anyone who needs full platform access
• This is the most expensive per-user license

Salesforce Platform License

• Access to custom objects, custom apps, Apex, and Flows
• Cannot access standard CRM objects like Opportunities or Cases
• Significantly cheaper than a full Salesforce license
• Ideal for users who need a custom app built on the Salesforce platform but don’t need CRM

Identity License

• Single Sign-On (SSO) only
• The user can authenticate through Salesforce but has no access to the platform itself
• Used for Identity-as-a-Service scenarios

Community/Experience Cloud Licenses

• For external users (customers, partners) accessing portals
• Come in multiple tiers: Customer Community, Customer Community Plus, Partner Community
• Pricing can be per-user or per-login (important distinction)

Chatter Free

• Free collaboration license for users who only need Chatter (Salesforce’s internal social tool)
• No access to CRM data or custom objects

License Strategy Tips

1. Audit who needs what — Not every employee needs a full Salesforce license. Map out user personas and their actual needs.
2. Use Platform licenses aggressively — If 30% of your users only interact with custom apps, you could save 40-60% on those seats.
3. Community licenses for external users — Never buy full licenses for partners or customers. Community licenses exist for this.
4. Per-login vs. per-member for communities — If external users log in infrequently, per-login pricing can be dramatically cheaper.
5. Factor in add-on costs — Many features that seem included actually require additional licenses (e.g., CPQ, Einstein AI, Data Cloud).

An Overview of Every Major Salesforce Product

Salesforce has grown into a constellation of products. Here’s a practical overview of each and when you might actually need it:

Sales Cloud

What it does: Core CRM for managing leads, accounts, contacts, opportunities, and the sales pipeline. When you need it: If you have a sales team. This is the bread and butter. Verdict: Essential for any sales-driven organization.

Service Cloud

What it does: Customer support platform with case management, knowledge bases, omni-channel routing, and service-level agreements. When you need it: If you have a support/service team handling customer issues. Verdict: Excellent for structured support operations. The omni-channel capabilities are genuinely best-in-class.

Marketing Cloud / Marketing Cloud Account Engagement (Pardot)

What it does: Email marketing, journey building, advertising, social media management, and B2B marketing automation. When you need it: If you’re doing sophisticated marketing campaigns that need to tie back to CRM data. Verdict: Powerful but expensive. Evaluate whether HubSpot or Mailchimp meets your needs first.

Commerce Cloud

What it does: E-commerce platform for B2B and B2C storefronts. When you need it: If you’re running an online store and want it deeply integrated with your CRM. Verdict: Strong for enterprise e-commerce. Overkill for small shops — consider Shopify first.

Experience Cloud (formerly Community Cloud)

What it does: Build portals, forums, and microsites for customers, partners, or employees. When you need it: When external users need to interact with your Salesforce data through a branded portal. Verdict: Good for partner portals and customer self-service. Template quality has improved significantly.

Data Cloud

What it does: Customer Data Platform (CDP) that unifies customer data from multiple sources. When you need it: If you have customer data scattered across multiple systems and need a unified profile. Verdict: Relatively new and evolving. Evaluate carefully — the promise is bigger than the current reality for most use cases.

Einstein AI / Agentforce

What it does: AI-powered features including predictive lead scoring, opportunity insights, next-best-action recommendations, and now autonomous AI agents. When you need it: When you have enough data volume for AI predictions to be meaningful and want to augment human decision-making. Verdict: Lead scoring and opportunity insights work well with sufficient data. Agentforce (autonomous agents) is still maturing — pilot cautiously.

Tableau / CRM Analytics

What it does: Business intelligence, data visualization, and advanced analytics. When you need it: When you need dashboards and analytics beyond what native Salesforce reports offer. Verdict: Tableau is world-class BI. CRM Analytics (formerly Einstein Analytics) is powerful for Salesforce-specific insights.

MuleSoft

What it does: Integration platform for connecting Salesforce with other systems via APIs. When you need it: If you have complex, enterprise-scale integration requirements. Verdict: Excellent integration platform, but expensive. For simpler integrations, consider native Salesforce Connect or middleware like Workato.

Slack

What it does: Team communication and collaboration (acquired by Salesforce in 2021). When you need it: If your team needs a messaging platform integrated with CRM workflows. Verdict: Great product, but the Salesforce integration story is still evolving. Most teams use Slack independently.

Ranking Salesforce Products: Best to Worst

Based on my experience, here’s how I’d rank the major products by value for money and execution quality:

1. Sales Cloud — The core product. Mature, well-documented, and genuinely useful. The foundation everything else builds on.
2. Service Cloud — Robust case management and omni-channel routing. If you need structured support, it delivers.
3. Tableau — Best-in-class BI tool. Worth it if you’re serious about data-driven decisions.
4. Experience Cloud — Solid for portals. Templates have gotten much better. Good ROI for partner management.
5. MuleSoft — Powerful integration platform. Ranked mid-tier only because of price — if budget isn’t an issue, it’s excellent.
6. Marketing Cloud Account Engagement (Pardot) — Good B2B marketing automation, but the UX lags behind competitors like HubSpot.
7. Commerce Cloud — Strong for enterprise e-commerce, but the learning curve and cost are steep.
8. Marketing Cloud — Powerful but complex and expensive. The B2C journey builder is impressive; the overall platform cohesion is still a work in progress.
9. Data Cloud — Promising concept, still maturing. Early adopters report mixed results.
10. Einstein AI / Agentforce — Predictive features are useful with enough data. Agentforce is too new to rank definitively.

Your mileage will vary based on your specific use case. This ranking reflects general enterprise value, not niche scenarios where a lower-ranked product might be exactly what you need.

Tips for Negotiating Your Salesforce Contract

Salesforce is one of the most negotiable enterprise software vendors. The list price is a starting point, not a final number. Here’s what I’ve learned:

Timing Matters

• End of Salesforce’s fiscal year (January 31) — Sales reps have quotas to hit. You’ll get the best deals in December and January.
• End of quarter — If you can’t wait for fiscal year-end, negotiate in the last two weeks of any quarter (April, July, October, January).
• Multi-year commitments — Salesforce heavily incentivizes 3-year and 5-year contracts. You’ll get deeper discounts but lose flexibility.

Negotiation Tactics

1. Never accept the first quote — Standard discounts of 15-30% are common. Push for more.
2. Bundle products — Buying multiple clouds together gives you leverage. “We’ll add Service Cloud if you discount the bundle by X%.”
3. Get competitive quotes — Having a real alternative (HubSpot, Dynamics 365, Zoho) gives you leverage. Sales reps can see when deals are at risk.
4. Negotiate user count carefully — Over-provisioning licenses is the #1 cost mistake. Start conservative and add later.
5. Cap annual price increases — Standard contracts include 7-10% annual escalators. Negotiate these down to 3-5% or flat.
6. Include sandbox and storage — These are often add-on costs that can be bundled in during negotiation.
7. Ask for Premier Support — If you’re signing a large deal, Premier Support (or Premier+) can sometimes be included at no additional cost.

Red Flags

• Being pressured to sign quickly — a legitimate deal will still be available next week
• Vague descriptions of what’s included — get everything in writing with specific SKU codes
• “We can add that later” — if you need it, get it in the contract now

How to Properly Staff a Salesforce Org

A common mistake: buying Salesforce without planning who will manage, configure, and develop on it. The platform doesn’t run itself.

Key Roles in the Salesforce Ecosystem

Salesforce Administrator

• Manages day-to-day org configuration: users, profiles, permission sets, page layouts, reports
• Builds automations using Flows, approval processes, and validation rules
• First line of support for user issues
• You need: At least one dedicated admin for every 50-75 users. For smaller orgs, this can be a part-time role.

Salesforce Developer

• Writes Apex code, Lightning Web Components, and integrations
• Handles complex business logic that can’t be done with clicks
• Manages deployments and version control
• You need: One developer for orgs with custom development needs. Complex orgs may need 2-5+.

Salesforce Architect

• Designs the overall technical strategy: data model, integration patterns, security architecture
• Makes build vs. buy decisions
• Reviews code and configuration for best practices
• You need: One for large/complex implementations. Can be a consulting engagement rather than a full-time hire.

Business Analyst

• Translates business requirements into Salesforce solutions
• Manages user stories and acceptance criteria
• Bridges the gap between business stakeholders and the technical team
• You need: One for any org undergoing active development or process change.

Release Manager / DevOps

• Manages the deployment pipeline: sandboxes, CI/CD, version control
• Coordinates releases across teams
• You need: One for orgs with multiple developers or frequent releases.

Staffing Models

Tip: For initial implementation, consider a Salesforce Implementation Partner (SI). Build your internal team in parallel so you’re not dependent on consultants forever.

Section Notes

A few things to keep in mind as you work through this evaluation:

• Salesforce is not a silver bullet. It’s a powerful platform, but it requires investment in people, processes, and ongoing maintenance. A poorly implemented Salesforce org is worse than a spreadsheet.
• Total Cost of Ownership (TCO) is more than licenses. Factor in implementation costs, ongoing admin/dev salaries, AppExchange subscriptions, data storage overages, training, and integration costs.
• Start small, expand later. Don’t try to implement every cloud on day one. Start with one use case, prove value, and grow.
• The ecosystem is your friend. Trailhead for learning, the Trailblazer Community for support, and AppExchange for pre-built solutions. Leverage them.
• Data migration is always harder than you think. Plan for it, budget for it, and allocate more time than you expect.

Project: Determine the Right Licenses and Org Type

To put this knowledge into practice, here’s an exercise. For each of the three fictional clients below, determine:

1. Which org edition they should use
2. Which user license types they need (and how many of each)
3. Which Salesforce products they should evaluate
4. An estimated annual licensing cost (use list prices as a baseline, then apply a reasonable discount)

Client A: TechStart Solutions

• 12-person SaaS startup
• 5 sales reps, 3 customer support agents, 2 founders, 1 marketing person, 1 operations
• Currently using spreadsheets and Gmail
• Budget-conscious, needs basic CRM and support ticketing
• No custom development needs yet

Client B: Meridian Manufacturing

• 200-employee manufacturing company
• 30 field sales reps, 15 inside sales, 20 service technicians, 10 customer support agents
• Currently using an on-premise CRM that’s end-of-life
• Needs integration with their ERP system (SAP)
• Partners and distributors need portal access (approximately 150 external users)
• Has one IT person who can learn Salesforce administration

Client C: Nexus Financial Group

• 2,000-employee financial services company
• 200 relationship managers, 100 service agents, 50 marketing team, 30 compliance officers, 500 back-office users who need limited access
• Strict regulatory requirements (data residency, audit trails, encryption)
• Existing investments in Tableau and MuleSoft
• Needs AI-powered lead scoring and next-best-action recommendations
• Multiple business units with different processes

Try working through these scenarios before looking at existing solutions online. The act of mapping business needs to Salesforce capabilities is the most valuable skill in this ecosystem.

This is Part 1 of a series on evaluating and implementing Salesforce. In the next installment, we’ll dive deeper into Salesforce’s data model, security architecture, and how to plan your first implementation.

If you’re going through a Salesforce evaluation right now and want to bounce ideas, reach out — I’m always happy to help fellow engineers navigate this ecosystem.