Choosing Between an Internal Tool and a Customer Portal
Internal systems and customer-facing portals solve different problems and get built differently — here's how to tell which one you actually need.
They look similar from a distance
'We need a web app' can mean two very different projects. An internal tool is built for a known set of staff, used repeatedly, and optimized for speed and control. A customer portal is built for people outside the organization, used occasionally, and optimized for clarity and trust on a first visit. Building one when you actually need the other is one of the more common — and most expensive — planning mistakes.
Questions that tell them apart
Who's actually using it, and how often? Staff using a tool eight hours a day will tolerate a denser interface in exchange for speed; a customer visiting once a quarter needs it to be obvious. Does it need to represent your brand to an external audience, or just get a job done internally? Does it need to scale to thousands of external accounts with self-service password resets and support flows, or a few dozen staff logins managed by an admin?
The answers usually make the direction clear well before any development starts — which is exactly why this decision belongs in the planning and architecture stage, not after the first version is half-built.
A staged approach works for both
Regardless of which one you need, starting narrow works better than starting broad: one core workflow built well, released to a small group, and expanded once it's proven — rather than a wide feature set that takes twice as long to reach anyone's hands.