Client portal — external users, self-serve access
Built for people outside your company (clients, partners) to see their own status, documents and messages — see Client Portal Development.
Dashboard — display and analysis, mostly internal
Built to show data — charts, metrics, status — to your own team, primarily for viewing and filtering rather than taking action or entering new data. See Dashboard Development.
Internal tool — internal users, taking action on data
Built to replace a manual process — your team enters, updates and acts on data, not just views it. See Internal Business Tools.
Where they overlap, honestly
Many real products are a blend — an internal tool often includes a dashboard view; a client portal often includes status displays similar to a dashboard. The distinction matters most for scoping who the primary user is and what they're there to do, not as a rigid category boundary.
Questions
Can one product be all three?+
In practice, yes, often — but scoping starts by identifying the primary user and primary action, then layering the others in as needed.
Which is usually built first?+
Whichever addresses the highest-friction current problem — often an internal tool (replacing a spreadsheet) or a client portal (reducing status-check emails).
Is a dashboard always the cheapest of the three?+
Often, since it's display-focused rather than action-taking — but this depends on data-source complexity, not a fixed rule.