Skip to content

Odduel

We put the odds in your favour

Insights

How to build internal tools for your business

A vendor-neutral guide to building internal tools: which processes are worth it, low-code or custom development, the steps, timelines, cost drivers and keeping the tool healthy.

An operations desk with a hand-drawn process map on paper, sticky notes and a laptop, two colleagues seen from behind discussing the steps

To build internal tools well, start from one painful, frequent process, map exactly how staff do it today, then choose the lightest approach that fixes it: a spreadsheet improvement, a low-code tool or custom software. Build a small first version with the people who will use it, connect it to the systems that already hold your data, and measure the time and errors it saves before you extend it.

Last updated: 15 November 2026.

This guide is vendor-neutral: it explains what an internal tool is, how to choose between low-code and custom development, the steps to build one, how long it usually takes and how to keep it healthy afterwards.

What is an internal tool?

An internal tool is software used by a company’s own staff to run its operations, rather than software sold to or used by customers. Typical examples are an approvals queue, an order back office, a stock and returns screen, a customer support console, a scheduling board, a reporting dashboard or an admin panel for a product.

Most companies already have internal tools, even if nobody calls them that. They are the shared spreadsheets with locked tabs, the forms that feed an inbox, the macros one person understands. They work until volume grows, the person leaves or a mistake costs real money.

At Odduel, a creative and technology agency in Barcelona and São Paulo, we design and build internal tools through our application development service, and the first question we ask is always which process is costing the most.

In short: an internal tool replaces a manual or fragile process with software built for it. Choose low-code when the process is standard and the data is simple; choose custom development when the rules are complex, the data is sensitive, many systems must connect or the tool will grow for years. Start small, with real users, and measure.

Which processes are worth an internal tool?

Not every irritation deserves software. The best candidates share several traits:

  • the process happens many times a week;
  • it involves copying data between systems or re-typing it;
  • mistakes are costly or embarrassing;
  • only one or two people know how it really works;
  • managers cannot see its status without asking.

Score your candidate processes on frequency, time per instance, error cost and risk, and start with the highest score. A process done twice a year, however annoying, rarely pays back a tool.

Should you use low-code or custom development?

Low-code platforms let you assemble screens, forms and workflows on top of a database or existing systems, with little code. Custom development builds the tool as ordinary software, designed and coded for your process. Both are legitimate; the right choice depends on the process, not on fashion.

FactorLow-code platformCustom development
Speed to a first versionFastSlower to start
Complex rules and calculationsPossible, gets awkwardNatural fit
User experiencePlatform components, limitedDesigned for the task
IntegrationsBuilt-in connectors; others harderAny system with an interface
Data location and security controlThe platform’s terms and hostingYour choice of hosting and controls
Cost profilePer-user or per-app subscriptions that growBuild cost, then hosting and maintenance
Lock-inHigh: logic lives in the platformLow, if code and data are yours
Who can change itTrained staff, within limitsDevelopers
Low-code and custom development for internal tools compared

When low-code is the right answer

Low-code suits simple, standard processes: request forms, approvals with a few steps, lists and dashboards on top of data you already hold. It also works well as a prototype that proves the process before a custom build.

When custom development is the right answer

Custom development suits tools with complex rules, heavy use by many people each day, sensitive data, demanding integrations or a long life ahead. It is also the answer when per-user subscription costs would grow beyond the cost of owning the software. Our guide to choosing an app development company covers what to ask a partner before a custom build.

What are the steps to build internal tools?

The steps are the same whichever approach you choose.

  1. Pick one process. The highest-scoring candidate, with a clear owner on the business side.
  2. Map the process as it is. Sit with the people who do it. Record every step, system, exception and workaround, including the ones nobody wrote down.
  3. Define the outcome. What should be faster, safer or visible, with today’s figures recorded: time per case, error rate, backlog.
  4. Design the data model. The records the tool manages, their fields and states, and where each piece of data lives today.
  5. Decide on the approach. Spreadsheet improvement, low-code or custom, using the factors above.
  6. Design the screens with users. Simple sketches first, tested with the real users on real cases. Internal users are experts in their work and spot problems fast.
  7. Build a first version. Only what the core process needs. Leave reporting, extra roles and nice-to-haves for later.
  8. Connect the systems. Read from and write to the systems that already hold the data, instead of creating another copy to keep in sync.
  9. Set permissions and audit. Who can see and change what, with a record of who did what and when.
  10. Pilot, then roll out. A small group uses it on live work for a few weeks; fix what they find, then extend it.

Our MVP development guide explains how to decide what goes into a first version and what waits.

What should every internal tool include?

Whatever it does, a good internal tool has a few things in common.

  • Clear roles and permissions, managed in one place, ideally through your company sign-in.
  • An audit trail of changes to important records.
  • Search and filters that match how staff look for things.
  • Bulk actions for repetitive work.
  • Sensible defaults and validation, so mistakes are caught on entry.
  • Exports for the reports nobody planned for.
  • Security of processing proportionate to the data: under the GDPR, internal tools that handle personal data need appropriate technical and organisational measures, such as access control, encryption and backups.
The pages list in the admin panel of the Nothing To Eat website by Odduel, an example of a screen designed for staff

How long does it usually take?

A low-code tool for a simple process can be in use within days or a few weeks. A custom internal tool for a single process typically reaches a first usable version in weeks, and a broader back office that connects several systems takes a few months, delivered in stages.

Two things stretch timelines more than the build itself: unclear processes that only become clear during development, and access to the systems the tool must connect to. Mapping the process properly and arranging access early saves the most time. Our article on app development timelines breaks down each phase.

What drives the cost of an internal tool?

The main cost drivers are the complexity of the rules, the number of integrations, the number of roles and permissions, the volume of data and the level of security required. Design and testing with users take a real share and are worth it: a tool staff avoid is the most expensive kind.

For low-code, look at subscription costs over three to five years at your expected number of users, plus the time of whoever builds and maintains it. For custom development, look at the build, then hosting and maintenance. A fixed quote follows a short brief describing the process, the systems and the users.

How do you keep an internal tool healthy after launch?

Internal tools fail slowly: a missed update here, an unowned feature there, until people drift back to spreadsheets. Prevent that from the start.

  • Give the tool a business owner and a technical owner.
  • Keep a short backlog of requests and review it monthly.
  • Apply security and dependency updates on a schedule.
  • Document how it works, how to deploy it and how to restore it.
  • Review permissions when people join, move or leave.

How do you measure whether it worked?

Compare against the figures recorded in step 3.

  1. Time per case for the process.
  2. Error and rework rate.
  3. Backlog and turnaround time.
  4. Adoption: the share of the process that now runs through the tool rather than around it.
  5. User satisfaction, asked simply and regularly.

If adoption is low, the tool usually misses a step of the real process. Go back to the people using it before adding features.

Questions people ask

What is an internal tool?

An internal tool is software used by a company’s staff to run operations, not by customers. Examples include admin panels, approvals queues, order back offices, support consoles, scheduling boards and reporting dashboards. Many companies run these processes on spreadsheets and email until volume, errors or staff changes make dedicated software worthwhile.

Should I use low-code or custom development for internal tools?

Use low-code for simple, standard processes and quick prototypes, where speed matters most and the data is not complex. Choose custom development when rules are complex, many people use the tool daily, data is sensitive, several systems must connect or subscription costs would grow beyond the cost of owning the software.

What are the steps to build internal tools?

Pick one costly process, map how staff do it today, record current figures, design the data model, choose the approach, sketch screens with real users, build a small first version, connect existing systems, set permissions and an audit trail, then pilot with a small group before rolling it out more widely.

How long does it take to build an internal tool?

A low-code tool for a simple process can be ready in days or weeks. A custom tool for one process usually reaches a first usable version in weeks, while a back office connecting several systems takes a few months in stages. Clear process mapping and early access to systems keep timelines short.

How do you know if an internal tool is worth building?

Score the process on frequency, time per instance, cost of errors and dependency on a few people. A process that runs many times a week, involves re-typing data and causes costly mistakes is a strong candidate. Record today’s figures so you can compare time and errors after the tool is in use.

Choose the one process your team complains about most, sit with the people who run it and write each step down. If you want help turning that map into a tool your staff will actually use, see our application development service or tell us about the process.

More articles

More from our Insights.

Explore all insights

Get in touch

Let’s change your odds.

Odds do not change on their own. If you have something to build, launch or fix, tell us about it and we will show you how we would approach it.

    Need an NDA before you share details? Start a project

    Chat with us