Customer-Facing or Internal? Where a New App Creates the Most Value

Most software decisions start with the wrong question, what should we build?, when the question that matters is where does the pain live?

A new app earns its keep in one of two places. It can make your own operation faster and steadier, or it can make your customer's experience easier. Both are worth doing, but they are not the same thing, and treating them as interchangeable is how teams build the wrong tool well.

Where does software create value?

Software creates value in two distinct places: inside your operation, and at the edge where you meet your customer. Internal software — line-of-business applications, internal portals, dashboards — cuts the cost of running a process. Customer-facing software — client portals, self-service tools — improves the experience of dealing with you. Knowing which one you are building keeps you from solving the wrong problem.

The split matters because the two pay back differently. Internal tools pay back in saved hours, fewer mistakes and less reliance on the one person who knows how things work. Customer-facing tools pay back in retention, reduced inbound chasing and, sometimes, a reason a client chooses you over a competitor. Build for the wrong payoff and a technically good app still misses the mark.

What is internal software for?

Internal software exists to make a repeated operation cheaper, more consistent and less fragile. A line-of-business application is internal software built to run one core process — quoting, scheduling, case management, stock control — used by your team rather than your customers. Its job is to take a process that currently lives in spreadsheets, inboxes and someone's head, and give it a single, reliable home.

The pains it removes are operational:

• Process cost — hours lost to re-keying data, copying between tools and doing by hand what software could do once. The McKinsey Global Institute's 2017 automation research found that 60% of occupations have at least 30% of their activities technically automatable with current technology, and much of that is the repetitive internal admin a line-of-business tool removes.
• Key-person risk — the bus factor problem, where a process only works because one person remembers the steps. Encode the steps and the risk drops.
• Manual chasing — the internal version of drift, where work stalls because nobody can see what is waiting on whom until it is late.

If the cost of your pain is internal time and internal error, internal software is where to look first.

What is customer-facing software for?

Customer-facing software exists to improve the experience of dealing with you and to take routine work off both sides. A customer portal (or client portal) is a secure, self-service area where clients do for themselves what they would otherwise email or phone you for: check status, upload documents, approve work, see their data. It moves the interaction from your inbox to their screen.

The pain it removes is usually the client visibility gap — the moment a client cannot see where their work stands, so they email to ask, and someone on your side stops what they are doing to answer. A portal that shows status the client can read whenever they like removes that exchange entirely. Customers reach for self-service readily: a 2024 Gartner survey found that 73% of customers use self-service at some point in their service journey. A portal meets that habit instead of fighting it, but the same research is a warning: self-service only pays off when clients can actually find what they came for.

Customer-facing software can also do something internal tools rarely can: differentiate you, or open a new line of revenue. A self-service experience that is genuinely better than a competitor's becomes a reason to stay.

"Internal software is felt by your team; customer-facing software is felt by your client. Build where the pain is felt, not where it is easiest to imagine." — The Control Standard

Internal or customer-facing — how do you choose?

Choose by asking two questions: where is the pain felt, and who pays for it? If the cost shows up as your team's time and your team's mistakes, build internal. If the cost shows up as clients chasing you for status and visibility you already hold, a customer portal often removes that chasing on both sides at once — which is why it can pay back faster than it looks.

It helps to name what kind of innovation each one is. The Doblin Ten Types of Innovation model, developed by Doblin and now part of Deloitte, separates innovation into ten categories rather than just "product". Internal tooling tends to be Process and Structure innovation — doing the work better and organising it more reliably. Customer-facing software tends to be Channel, Service and Customer Engagement innovation — changing how clients reach you and what it feels like to deal with you. The same lens that tells you what you are improving tells you who will feel it. Our guide to the ten types of innovation walks through the full model.

A practical way to settle it: score the pain before you commit. How often does it happen? How much time does it cost each month? What goes wrong when it fails? How many people — your team, your clients, your suppliers — does it touch? The pain with the highest frequency, cost and reach is the one to solve first, regardless of which side of the line it falls on.

Should you build it at all — and build or buy?

Deciding which app rarely settles whether you should build it. Before committing to either an internal tool or a customer portal, work the build vs buy software decision: an off-the-shelf product may already cover most of the pain, and custom software only earns its cost where your process is genuinely your own. The cheaper path is often business process automation — automating the repeated steps inside an existing process before reaching for a whole new application.

And before any of that, make sure the process is worth fixing in software at all. Many pains that look software-shaped are really unclear processes wearing a software costume. Systemise first: give the process a clear owner, defined steps and good stakeholder management, then decide what to build. The systemising pain hub covers the full sequence from messy operation to the right tool.

If you are weighing a new app right now and want to know whether your pain is internal, customer-facing, or not ready for software yet, the free Pain Automation Score below scores it in a few minutes — and points you to the right next step.