Service 02 · The portal

The CRM stays.The wastegoes.

Light users don't need a $2,000 seat to read a record and update a field. The portal gives them exactly the access they use — read and light-write, live against your CRM — while their seats come off the contract.

How it's priced

12–18% of what we free up

Not a day rate. Not a license. A one-time build fee set as a fraction of the first-year savings your audit proves — so the project can only exist if the math works. Everything else is yours: every year, forever.

Your admin's take

Your Salesforce admin keeps their org exactly as it is — same objects, same automations, same reports. What they lose is the seat-count headache: the provisioning churn, the license spreadsheet, the renewal scramble. The admin is the hero of this story, not the casualty.

How the build works
01

The CRM stays the system of record

The portal is a pass-through access layer. Every read and write happens live in your CRM through its API. Nothing is migrated, duplicated, or synced to a second database.

02

Pilot first, always

50 light users move first. Your team runs on it, kicks the tires, and signs off before anyone else transitions. Risk is front-loaded and tiny.

03

Timed to your renewal

Full migration lands before your contract renews, so removed seats come off the bill the day they stop being used. Zero coverage gap, zero double-paying.

04

Maintained under SLA

Every build includes a maintenance retainer — monitoring, API version updates, and support under a service-level agreement. One agreement, one accountable party.

Cheaper seats still cost forever.
A 600-seat org burns ~$169K of seat waste every quarter it waits.

Zero seatsdon't