A large company's customer app is usually designed with care: clean screens, smooth flows, regular updates. The portal its dealers use to place orders often looks exactly as it did the day it launched, ten years ago. So do the HR screen where people request leave and the app on the field team's phones. Enterprise application design is about that second group: the software people inside the company use every day.
Short answer: The cost of a badly designed internal app never shows up as a line on an invoice. It shows up in training, in support tickets, in lost time and in systems nobody uses. You can make that cost visible, and you can redesign in small, measurable steps. This article explains how.
Why do internal enterprise apps get overlooked?
There are a few familiar reasons internal apps end up last in line. None of them is any one team's fault; the structure of a large company simply pushes this work to the back.
Users "have to use it anyway". A customer who dislikes an app leaves. An employee or a dealer can't. So problems in internal apps don't arrive as complaints; they pile up as quiet inefficiency. The work gets done, and the cost appears in nobody's report.
Nobody clearly owns the budget. A customer app has an owner and a goal. An internal app sits between departments: HR uses it, IT maintains it, sales feels the results. Nobody sees it as their own priority.
There's no measure of success. Customer apps are judged by conversion. Internal apps are often not measured at all, and it's hard to show that something unmeasured has improved. When a manager asks for a redesign budget and can't answer "what are we losing today?" with data, the request slips to next year.
Fear of the legacy system. Internal apps have usually grown over years and been wired into other systems. The worry that "if we touch it, something will break" keeps postponing change.
What does a badly designed internal app cost the company?
Most of this cost is hidden inside other budgets. You can fill in the list below for one internal app in your own company. The goal isn't to produce a number; it's to see what you need to measure.
INTERNAL APP HIDDEN COST CHECKLIST
App: ______________________
[ ] Training: How long until a new user can work in the app on their own?
[ ] Support tickets: How many are "where is it, how do I do it" questions?
[ ] Workarounds: Does the work run through spreadsheets, phone calls or chat instead of the app?
[ ] Double entry: Is the same information typed by hand into more than one system?
[ ] Errors: How often are wrong entries corrected, and who does it?
[ ] Waiting: How long do people wait for someone else's approval or help to finish a task?
[ ] Unused features: Are there screens you maintain that nobody uses?
[ ] Satisfaction: How do dealers or employees talk about the app?
[ ] Security: Because of workarounds, is data moving through uncontrolled places?
[ ] Measurement: Can you answer any of these questions with data today?
The last question is often the most important. If your answers are guesses, the first job of a redesign is to start measuring. We explain how to audit an existing product in should you redesign or audit first.
Let's find your internal app's most painful flow together: send a short note to hello@things.ist and we'll get back to you within 48 hours.
How do HR, dealer and field apps differ?
All three count as "internal apps", but their users and conditions are very different. Design starts with that difference.
| HR app | Dealer portal | Field app | |
|---|---|---|---|
| Users | All employees, the HR team | Dealer owners and their staff | Field teams, technicians, sales reps |
| Context | At a desk or on a phone, now and then | At the counter, mid-shift, every day | On site, on mobile, often with a weak connection |
| Most common problem | Relearning it every time because it's used rarely | Orders placed by phone instead of in the app | Small screen, gloves, sunlight, dropped connection |
HR apps. Most employees open this app a few times a month, for leave, payslips or expenses. In an app people use rarely, they relearn it every time, so simplicity and familiar patterns matter more than anything. A good employee experience starts with an app that needs no training. HR apps also serve a very wide range of users: the same screen is used by a specialist at headquarters and by a shift operator at a factory. Design for the user with the least time and the smallest screen, and it works for everyone.
Dealer portals. Dealers use the portal in the middle of their work, often with a customer in front of them. If an order takes several minutes, the phone is faster, and the portal is slowly abandoned. A dealer is also an independent business. The portal should give them more than an order screen: stock, pricing and campaign information they can use to run their own business. A portal that helps the dealer's business gets used without anyone pushing it.
What is a dealer portal?
A dealer portal is the web or mobile app a manufacturer or distributor uses to work with its dealers. Dealers place orders, check stock and prices, and follow invoices, campaigns and support requests. It's the digital channel for B2B (business-to-business) sales; designed well, it replaces work that otherwise runs on phone calls and email.
Field apps. Field teams use the app standing up, on the move and often with a poor connection. Large tap targets, offline mode and short flows aren't nice-to-haves here; they're requirements.
In a basement, on a construction site or in a rural area, the connection drops, and if the app loses what was entered, the team stops trusting it; the work goes back to paper or chat. That's why a field app has to be tested in the field, not in the office: in real light, on a real connection, at the real pace of the job. In field apps, the best design is often the one with the fewest screens; the team should spend its attention on the work, not on the app.
How do you design enterprise applications with AI in four stages?
We do this work with an AI native process. AI native means a studio that builds AI into every step of the process. At each stage, AI speeds up the heavy lifting and people make the decisions. Here's how the four stages adapt to internal apps.
Discover. AI groups support tickets, usage logs and interview transcripts into themes. Our team goes into the field: we talk to dealers, employees and technicians in person and watch them while they work. The gain: the real source of the problem becomes visible through evidence rather than guesswork. We cover the methods for this stage in how to do UX research with AI.
Define. AI quickly produces alternative versions of the existing flows. The team decides with you which flow to move first, usually the one used most or the one causing the most trouble. The gain: you approve a small, measurable first step, not the whole system. The chosen flow is prototyped and tested with the people who use it every day.
Deliver. The design system and the code are produced by the same team, and integration with legacy systems (APIs, the data model) is solved by that team too. AI generates code tied to the design system; our engineers review it. The gain: you have one point of contact, and nothing gets lost between design and code.
Grow. AI summarizes usage data and feedback. The team decides with you which flow comes next. The gain: the budget grows step by step, based on measured results.
Can you redesign an internal app without replacing the legacy system?
Yes, and that's usually the right way to do it. Rewriting an internal app from scratch in one go is the riskiest approach, and it's exactly what justifies the fear of the legacy system.
Instead, you move flow by flow. The most painful flow moves to a new interface first, while it keeps talking to the old system in the background. If needed, old and new run side by side for a while and users switch over gradually. Each flow is measured before and after, and the next step is chosen based on that result.
The most critical part is having design and back-end integration in the same team. A flow's new interface is designed with full knowledge of what the old system can and can't provide, so surprises turn up at the design table, not during development. We go deeper into phased migration in how enterprises should approach a product redesign.
From a dealer portal: "Without needing a manual"
"Five thousand dealers use the product they built every day, without needing a manual. That's the quietest compliment software can get." — Head of Digital Channels, Energy
Said about a dealer platform in the energy sector, this sums up what a good internal app looks like: nobody talks about it, because the work just gets done.
How do you start an internal app redesign?
You don't need to set up a big program. You can start with five steps:
- Fill in the checklist. Complete the list above for one of your internal apps, using what you know today. The questions you can't answer are findings too.
- Pick the most painful flow. One flow where support tickets, complaints and workarounds pile up the most.
- Talk to the users. Interview a few people who use that flow every day, or watch them at work.
- Bring IT and procurement in early. IT knows from day one what data the legacy system can provide and where integration hits its limits; that knowledge needs to be on the table before design starts. Procurement can run contracts and security review in parallel, so the project doesn't wait for weeks.
- Write a brief. Describe the problem, the users, the legacy system's constraints and how you'll measure success. Your checklist answers will be the strongest part of the brief.
FAQ
How do you do UX research for internal apps? Because the users are employees or dealers, they're easy to reach; the hard part is seeing what they really do. The best results come from watching people while they work. We explain how to choose a method in which usability testing method when.
Should we turn our dealer portal into a mobile app? It depends on where and how dealers use it. If they're at a computer behind the counter, a good web interface may be enough; if they're in the field or on the move, mobile comes first. Make this call based on what you observe during discovery, not on assumptions.
How should personal data be handled in an internal app? Employee and dealer data is personal data. Which data is collected and why, who can see it and how long it's kept should be handled as part of the design, in line with the data protection laws that apply to you. This isn't legal advice; for a definitive answer, work with your company's legal team.
How long does a redesign take? It depends on scope. Most projects take 10–16 weeks from kickoff to launch; when you move flow by flow, the first improvement can go live sooner.
Let's look at your internal app together
In short, here's who we are: a studio that works with AI and does design and development in one team. Things is one of the pioneering and leading companies in AI-driven design in Turkey. Since 2018 we've brought more than 50 products to life, and our work has won a Red Dot award.
Let's find your internal app's most painful flow together: send a short note to hello@things.ist and we'll get back to you within 48 hours. You can also reach us through our contact page.
Design. Engineering. Mastery.