Customer Portals

Salesforce Customer Portal
without a licence for every customer.

Their opportunities, quotes and orders, and the full history on every case, on a login you own. It reads live from Salesforce, so your customers see the same records your team is already working in rather than a copy beside them.

Where Experience Cloud genuinely fits, we will say so rather than quote. Where it does not, you get a fixed-price scope, an Australian team and support after launch.

On your domain, in your branding, and yours at the end of it.

  • No per-user fee Portal logins do not cost Salesforce seats
  • 18+ yrs Building business software
  • Fixed Price scopes, no surprises
  • You own it Code, docs and credentials
Australian owned and operated

Built here. Your data stays here.

  • No offshore development. Everything is written by our own team in Australia. Nothing is subcontracted overseas.
  • Your data stays onshore. Hosted in Australia, on infrastructure you own, under Australian law.
  • Every state, not just ours. Perth, Melbourne, Sydney, Brisbane, Adelaide and everywhere between.

What your customers see

What your customers see in a Salesforce portal

Every screen reads live from Salesforce, so the figures match because they come from Salesforce rather than from a copy somebody refreshes.

  • Their opportunities, quotes and orders
  • Cases and the full history on each
  • Contracts and documents shared with them
  • Forms that write back to the object they belong to
  • Account details they maintain themselves

Who logs in

  • Customers
  • Partners
  • Suppliers

What people ask us for

Start with the job your Salesforce portal has to do

The same portal gets asked for in six different ways depending on where you are up to. Select any one to read how we approach it.

Salesforce customer portals

Salesforce customer portal and client portal

A customer portal for Salesforce is a login you own, on your domain, where your customers see their own account. A client portal for Salesforce is the same build under the name professional services tend to use. Either way it is not the Salesforce login: your customers never get access to Salesforce, and you do not buy them a seat.

The portal reads live from Salesforce through the API, so what a customer sees is what Salesforce says right now rather than a figure somebody exported on Friday. A Salesforce customer self-service portal removes the calls asking where things are up to.

Salesforce customer portals

Salesforce customer portal development

We are a Salesforce customer portal development company, and this is custom work rather than a product with your logo on it. Salesforce portal development starts with what your customers should see and what they should be able to do, because that decides everything after it.

A custom Salesforce customer portal is worth building when an off-the-shelf tool cannot model how you actually work: partner hierarchies, multi-contact accounts, or approval steps that would need heavy configuration. Where a product would genuinely do the job we will say so rather than quote.

Salesforce customer portals

Build a Salesforce customer portal, or a customer app

Some clients want a portal on the web, others want a Salesforce customer app their customers keep on a phone. The data layer is the same; the difference is how it is delivered and what it costs to maintain, and it is worth deciding deliberately rather than by default.

Either way it is a Salesforce customer portal solution scoped and fixed-price before anything is built, running in parallel with how you work now until you agree it is right.

Salesforce customer portals

Salesforce customer portal integration

Salesforce portal integration is the part most projects underestimate. Connecting a customer portal to Salesforce means deciding which system is authoritative for each field, how a portal login maps to exactly one Salesforce record, and what happens when two things change at once.

Salesforce has its own portal product in Experience Cloud, and where that fits your needs we will say so rather than build. The reason clients come to us is usually licensing or fit: a custom portal reads through the API and costs nothing per external user, which changes the economics entirely once you have more than a handful of them.

If you already have a portal or a website, we integrate the customer portal with Salesforce rather than starting again. If you have neither, we build both.

Salesforce customer portals

Invoice, payment and account portals

Most Salesforce portals start as a Salesforce account and case portal: their opportunities, quotes and orders. From there it usually grows into cases with full history, contracts, and a document area.

A Salesforce customer account portal and a Salesforce customer billing portal are the same build seen from different angles. The work is making sure anything done in the portal lands against the right record, first time, without anybody reconciling it by hand.

Salesforce customer portals

Orders, quotes, documents and dashboards

This is the alternative to licensing Experience Cloud per external user, which is why most clients come to us for it. A Salesforce customer order portal, a Salesforce quote portal for approvals and a Salesforce customer document portal are all the same portal with more of the account exposed. A Salesforce client dashboard on the front page answers the question before they go looking.

What Salesforce does not hold, we fetch from wherever it does live. That is usually the job system, the CRM or a database, and joining those is the same work as any other integration.

One place, one view

Your customers should not need three logins

Salesforce holds part of the picture. The rest is in the job system, the CRM, the payment gateway and wherever your documents live. A portal that only reads Salesforce hands your customer a fragment and sends them back to the phone for the rest.

We join them. One login, designed to your brand, showing a complete account view built from every system that has a piece of it.

  • Your accounting system, so invoices and payments sit beside the account
  • Your delivery or job system, for what happens after the sale
  • Payment gateways, so paying in the portal reconciles where the money is tracked
  • Document storage, including anything held outside Salesforce
  • Your website or app, so the login is part of your brand rather than beside it

How it works now

Every question lands on your desk

  • Customers ring or email to ask the same questions
  • Somebody exports from Salesforce and sends it out
  • Chasing takes a person the best part of a day a week
  • No record of who was told what, or when

After

Customers look it up, straight from Salesforce

  • Available any time, straight from Salesforce
  • Nothing rekeyed, because it is read rather than copied
  • Anything they submit posted back where you want it
  • An audit trail of who saw what and when

Scoped and quoted before you commit. You own the code, the documentation and the credentials at the end of it.

Get a fixed-price scope
Common questions

Questions owners ask about a Salesforce portal

Is this the Salesforce login?

No. The Salesforce login is where you and your staff work. This is a separate portal you own, for your customers, that reads and writes your Salesforce data. Your customers never get access to Salesforce itself.

What can customers actually see?

Typically their opportunities, quotes and orders, cases and the full history on each, contracts and documents shared with them. What they cannot see is anything else, because the portal only ever requests the records belonging to that contact.

What is the hardest part of Salesforce portal work?

Salesforce has its own portal product in Experience Cloud, and where that fits your needs we will say so rather than build. The reason clients come to us is usually licensing or fit: a custom portal reads through the API and costs nothing per external user, which changes the economics entirely once you have more than a handful of them.

Do we need a licence for every portal user?

No. The portal reads through the API under one connection, so the number of customers logging in does not change what you pay Salesforce. That is usually the reason a custom portal costs less than the alternative once you have more than a handful of users.

Will it slow Salesforce down or put our data at risk?

The portal reads through the API rather than touching your system directly, so day-to-day use is unaffected. Writes are limited to what you approve, and everything is logged so you can see what changed and when.

How long does it take?

A straightforward portal over Salesforce is usually weeks rather than months. We scope it and quote fixed-price before starting.

Tell us what your customers keep ringing about

Which Salesforce edition you are on, roughly how many customers would use it, and what they most often ring about. We will come back with a straight answer and a fixed-price scope.

Prefer a quick chat? Call 0425 531 127. We answer the phone in Perth.