The CRM stays. The waste goes.
A portal can simplify selected CRM workflows. First establish which licences each user still requires: API access is not a substitute for user entitlements. Compare native seat options, permitted portal access and the full ongoing cost before proposing a change.
12–18% of what we free up
The proposed one-time build fee is a share of estimated first-year savings, subject to an agreed scope. Maintenance, hosting, API access and any retained licences are separate costs and belong in the same business case. Estimates are verified after rollout.
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.
The CRM stays the system of record
The portal is designed around your CRM as the system of record. Define any caching, logging and retention requirements before implementation.
Pilot first, always
Agree a small pilot group and test its actual workflows, access controls and support needs before wider rollout.
Timed to your renewal
Plan rollout against contractual notice and renewal dates. Only include seat reductions that your agreement permits, with transition and ongoing costs included.
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.
Choose the right access model
Stage 00 is a 30-minute qualifying call at no cost. If the timing or the estate does not justify an engagement, we say so on that call.