Salesforce Platform License vs. Custom Portal

When you realize you’re overpaying for light users, Salesforce gives you a legitimate middle option: the Platform license, a limited-access seat that costs a fraction of a full Sales or Service Cloud license. So the real question for most teams isn’t “full seat or nothing” — it’s full seat vs. Platform license vs. a flat-fee custom portal. Here’s how the three compare.

The three options at a glance

Option	Typical list price	Scales with headcount?	Best for
Full Sales/Service Cloud seat	~$150–$165/user/mo	Yes — per user	Power users who live in the CRM
Salesforce Platform license	~$25–$30/user/mo	Yes — per user	Staff who need custom objects, not full CRM
Flat-fee custom portal	One flat monthly fee	No — same at any headcount	Light users: sellers, ops, partners, customers

Prices are publicly listed ranges as of this writing, not quotes — confirm current pricing with Salesforce. Even the cheapest per-seat tier still bills per person.

Full Sales/Service Cloud seat

The full platform. Worth every dollar for power users who run pipeline, build reports, and live in the CRM all day. The problem is only that it’s priced for those people — and most orgs assign it far more broadly than that profile justifies.

Salesforce Platform license

A genuine saving for the right user: it grants access to custom objects, Chatter, and core platform features without the full CRM app pricing. If someone needs to work with your custom data model inside Salesforce but doesn’t need Leads, Opportunities, and Cases, a Platform license can be the correct call. The catch: it still bills per user, it still caps what you can expose, and it doesn’t fit external users well.

Flat-fee custom portal

For the users who touch the CRM for a narrow set of tasks — a custom portal gives them a purpose-built tool wired live into Salesforce, on one flat monthly fee regardless of how many people use it. It isn’t limited to Salesforce’s component set, it’s shaped to your exact workflow, and it’s ideal for external users (partners, customers) you shouldn’t be paying internal seats for. As user counts grow, the flat fee increasingly wins.

How to choose

• Power user, lives in the CRM? Full seat.
• Needs your custom data inside Salesforce, occasionally? Platform license.
• Light or external user doing a handful of tasks? Custom portal — especially at scale.

Most mid-market teams end up with a mix. The point isn’t to pick one globally — it’s to stop assigning full seats by default. For the complete framework, see how to cut CRM licensing costs, and to spot which users belong in which bucket, read how to tell which CRM users you’re overpaying for. To model the portal option against your seat count, use the savings calculator.

Frequently asked questions

Is a Platform license enough to fix our CRM costs?

Often partially. It’s the right move for staff who need custom-object access but not the full CRM. It won’t help external users, and because it still bills per person, it doesn’t stop your cost from scaling with headcount — which is where a flat-fee portal comes in.

Can a custom portal and Salesforce licenses coexist?

Yes — that’s the normal setup. Power users keep full seats, some staff sit on Platform licenses, and light/external users move to a portal that syncs with the same Salesforce records. One source of truth, three access models matched to actual need.

Do we lose data ownership with a portal?

No. Salesforce stays the system of record; the portal reads and writes the same records in real time. You also own the portal and its IP.