Blog

Internal tools: the apps you already use, and how to connect them into one system

Benjamin · · 13 min read

Most growing businesses have plenty of tools. The problem is the gaps between them. A research-backed guide to internal tools, the products that build them, and how to connect what you already pay for.

Most growing businesses don't have a tools problem. They have plenty of tools: an accounting package, a CRM, Google Workspace or Microsoft 365, a few spreadsheets, a WhatsApp group, maybe Airtable or a scheduling app. Each one does its own job well. The problem is the space between them, where a person reads something in one tool and types it into the next.

Internal tools are the software your team uses to run the business: dashboards, admin screens, approval flows, job boards, trackers. This guide maps the tools that already do this job, explains how each one works and where it stops, and shows how to connect the tools you already pay for into one working system without replacing any of them.

What the research says about disconnected tools

The cost of the gaps between tools is well measured. A few of the more careful studies:

  • 60% of time goes on "work about work". Asana's Anatomy of Work Index found that people spend about 60% of their working time on communicating about work, searching for information, switching between apps and chasing the status of work, rather than on the skilled work they were hired for. (Asana)
  • Nearly seven hours a week lost to complexity. Freshworks' 2025 Cost of Complexity Report surveyed 706 practitioners and decision-makers in six countries, mostly at larger firms. Employees juggle about 15 software tools and four communication channels, and lose nearly seven hours a week to complicated processes and fragmented tools. Respondents estimated that 20% of software budgets go on tools that are underused, poorly integrated or never fully implemented. (Freshworks)
  • Even large companies connect less than a third of their apps. MuleSoft's 2025 Connectivity Benchmark, a survey of over 1,050 IT leaders, found that only 29% of a typical enterprise's applications are integrated, and 90% of organisations say data silos create business obstacles. (Salesforce / MuleSoft) If companies with dedicated integration teams manage less than a third, most small businesses connect far less.
  • Spreadsheets carry hidden errors. Raymond Panko's review of field audits of real business spreadsheets found that the audits using the most thorough methods found errors in at least 86% of the spreadsheets they checked. (Panko, Spreadsheet Errors: What We Know. What We Think We Can Do)
  • Even technical teams spend heavily on internal tools. In Retool's 2022 survey of 2,285 developers, respondents spent about a third of their time building internal tools, most often for operations teams. (Retool)

The pattern is consistent: buying more tools doesn't remove the work, because the work moves into the gaps between the tools.

What counts as an internal tool?

An internal tool is any software that helps your team do its own work: entering, finding, checking, approving or reporting on the information the business runs on. Customers never log in to it. Common examples:

  1. Operations dashboard. Every open job, order or case on one screen, with what is late and who owns it.
  2. Admin panel. A safe way for staff to edit customers, products, prices or bookings without touching the database.
  3. Approval workflow. Purchase requests, expenses, discounts or leave routed to the right person, with a record of who approved what.
  4. Job and dispatch board. For trade and field businesses: which engineer is where, what they need, what is done.
  5. Onboarding tracker. For staffing agencies and HR teams: documents collected, checks complete, start date confirmed.
  6. Reconciliation screen. For finance teams: invoices matched to purchase orders and payments, with only the exceptions left for a person.
  7. Quote builder. Prices and rules pulled from one place, so every quote is consistent.

Most businesses already have all of these. They are just spread across a spreadsheet, an inbox and someone's memory.

The tools that already do the job

There is no shortage of good tools for building internal tools. They fall into five groups. Each works well up to a point, and it helps to know where that point is.

1. Spreadsheets: Google Sheets and Microsoft Excel

How they work: a grid of cells with formulas, shared with your team. Nearly everyone can use one, and you can change it in seconds.

Where they shine: early stages, one-person processes, analysis and quick lists.

Where they stop: permissions are coarse (protected ranges help, but anyone who can edit can usually still break the sheet), version history shows what changed but not why, rules are only enforced if nobody overwrites the formula, and anything automatic needs scripts someone has to maintain. As the Panko research shows, errors creep in quietly. A spreadsheet becomes risky when several people depend on it to run a process every day.

2. Spreadsheet-databases: Airtable

How it works: Airtable looks like a spreadsheet but behaves like a database. Data lives in bases and tables, and records in one table can link to records in another, such as a job linked to its client. Its Interface Designer builds simpler screens on top of the data for particular people, with their own permissions, and its automations react to changes. (Airtable)

Where it shines: turning a messy sheet into structured, linked data, fast, without code.

Where it stops: it becomes one more place where data lives. Your invoices are still in the accounting package and your deals are still in the CRM, so someone still keeps them in step. Complex rules and heavy use get awkward, and it is priced per user. We compare options in Airtable alternatives.

3. No-code app builders: Glide, Softr, AppSheet and Power Apps

How they work: you point the builder at data you already have, and it generates screens you can arrange.

  • Glide turns spreadsheets and databases (Google Sheets, Excel, Airtable, SQL databases or its own Glide Tables) into mobile and desktop apps. (Glide)
  • Softr builds client portals and internal tools on top of Airtable, Google Sheets, Notion, SQL databases or its own database, with logins and permissions. (Softr)
  • Google AppSheet is Google's no-code app builder, closely tied to Sheets, Gmail and the rest of Google Workspace. (Google AppSheet)
  • Microsoft Power Apps builds apps on Microsoft's Dataverse or on data in SharePoint, Microsoft 365, Dynamics 365, SQL Server and other sources, through connectors. It offers drag-and-drop "canvas" apps and data-first "model-driven" apps. (Microsoft Learn)

Where they shine: giving a clean front end to a spreadsheet, especially on phones, inside an ecosystem you already use.

Where they stop: the app is only as good as the data underneath, which is often still one spreadsheet. They work best inside one ecosystem. Connecting Google, Microsoft, your accounting package and an industry tool together is where they start needing workarounds. And everything you build lives on their platform.

4. Low-code internal tool builders: Retool, Appsmith and Budibase

How they work: a developer drags components (tables, forms, buttons) onto a page and wires each one to a query against your database or an API, using JavaScript for the logic.

  • Retool connects components to your databases and APIs, adds Workflows for scheduled jobs and alerts, and can run in Retool's cloud or on your own servers. (Retool docs)
  • Appsmith is open source (Apache 2.0) and works the same way: widgets, data sources and JavaScript, and you can host it yourself. (Appsmith)
  • Budibase is an open-source platform with a built-in database, automations and self-hosting. (Budibase)

Where they shine: admin panels and dashboards on top of a database you already have, built by a technical team.

Where they stop: they are low-code, not no-code, so someone technical has to build and maintain each tool. They assume your data already sits in a database or behind an API. If it lives in five SaaS products and three spreadsheets, the hard part, joining it all up, is still yours.

5. Automation tools: Zapier, Make and n8n

How they work: "when this happens in app A, do that in app B". A new form entry creates a CRM contact. A won deal creates an invoice. A new invoice posts to a Slack channel.

Where they shine: quick, simple handoffs between popular apps, set up in an afternoon.

Where they stop: each automation fixes one handoff, and none of them sees the whole process. After a year, many businesses have dozens of automations that nobody fully understands, logic scattered across tools, and failures that happen quietly until a customer notices. We compare two of them in Zapier vs n8n.

The tools at a glance

  • Spreadsheets (Google Sheets, Excel). Best for early stages and analysis. Stops at coarse permissions, rules that are easy to break, and hidden errors.
  • Spreadsheet-databases (Airtable). Best for structuring messy data quickly. Stops when it becomes one more place data lives.
  • No-code app builders (Glide, Softr, AppSheet, Power Apps). Best for clean screens on existing data, and phones. Stops at the edge of one data source or ecosystem.
  • Low-code builders (Retool, Appsmith, Budibase). Best for admin panels on an existing database. Stops because it needs developers and assumes your data is already joined up.
  • Automation tools (Zapier, Make, n8n). Best for simple one-step handoffs. Stops at one handoff at a time, and failures are easy to miss.

All of these are good tools. Notice what is missing from every one: none of them is responsible for the whole process across all your tools.

Where the gaps actually are: one job, six tools

Here is a typical week in a growing trade or services business. Every tool in it is a good choice on its own:

  1. An enquiry arrives by email or WhatsApp.
  2. Someone adds the customer to the CRM (HubSpot, Pipedrive or similar).
  3. The quote is worked out in a spreadsheet, because the pricing rules live there.
  4. Once it's accepted, the job goes onto a scheduling app or a whiteboard.
  5. When it's done, someone creates the invoice in the accounting package (Xero, QuickBooks or Zoho Books).
  6. The manager asks in the group chat what is still open, because no single screen shows it.

There are five handoffs, and a person carries each one: copying details, checking they match, chasing the next step. Add a Zap here and there and some of the copying goes away, but nothing knows that the job quoted on Monday is the job invoiced on Friday. Nobody can answer "what is stuck, and why?" without asking around.

Your tools are not the problem here. The missing piece is the system that connects them.

What a connected system looks like

The answer is not another app to replace the ones you have. It is a thin layer that ties them together. In practice that layer has five parts:

  1. One shared record of the work. Each job, order or case exists once, with its status, and links to the customer in your CRM, the quote, the schedule and the invoice in your accounting package. Your tools stay the place where each kind of data lives. The shared record knows how the pieces relate.
  2. Two-way connections to the tools you keep. The system reads from and writes back to your CRM, accounting package, calendar and spreadsheets through their own connections (APIs), so information is entered once and appears everywhere it is needed. Every sync is logged, and failures alert a person instead of disappearing.
  3. Screens for the work that falls between tools. The quote builder with your real pricing rules, the approval step, the dispatch board, the exceptions list. These are the internal tools, built around how your team already works, on phones as well as desktops.
  4. The rules in one place. Who can approve what, what must be checked before an invoice goes out, what happens when a job runs late. Written once and enforced everywhere, not spread across a dozen automations.
  5. One view of status. A dashboard built on live data from all your tools, so "what is stuck?" takes one look instead of six messages.

Applied to the week above: the enquiry creates the customer and the job once. The quote uses the pricing rules and goes out from the system. Acceptance books the job and notifies the engineer. Completion raises the invoice in Xero or QuickBooks automatically, and the payment status flows back. The manager's dashboard shows everything open, late or waiting on a person. The team keeps using the CRM, the accounting package and the calendar they know. The difference is that nobody carries information between them any more.

This is also where AI earns its place: reading the details out of an enquiry email or a supplier PDF, or flagging an invoice that doesn't match its quote. It works because it is connected to your real data, and a person checks what matters.

How to choose the right approach

Use this to decide what your workflow needs:

  • One person, one process, still changing every week: a spreadsheet is fine for now.
  • Messy data needs structure, a small team, few connections: Airtable, or a no-code builder on top of it.
  • Everything already lives in Google Workspace or Microsoft 365: AppSheet or Power Apps.
  • You have developers and a database, and need admin screens: Retool, Appsmith or Budibase.
  • Two popular apps need one simple handoff: Zapier, Make or n8n.
  • The process runs across several tools, many people depend on it, and mistakes cost money: a connected system, built around the tools you keep.

The last situation is where most growing businesses end up, usually after trying several of the others. That's not because those tools failed. Each solved its own piece, and nothing solved the whole.

Before you build anything: map your stack

You can do this in an hour with a pen, and it is useful whichever route you choose:

  1. List every tool that touches one core process, including spreadsheets, inboxes and chat groups.
  2. For each one, write what it is the source of truth for: customers, prices, jobs, invoices, hours.
  3. Draw the handoffs. Wherever information moves from one tool to another, note who moves it and how often.
  4. Mark the retyping. Every place the same information is typed twice is a cost and a source of errors.
  5. Mark the questions nobody can answer quickly, such as "what's overdue?", "who approved this?" or "did we invoice it?"
  6. Pick the one handoff that costs the most time or causes the worst mistakes. That is your first build.

How we build it at Lephlo

At Lephlo, this is most of what we do for growing businesses. We don't ask you to replace the tools your team already knows. We connect the tools you already pay for so information moves between them on its own, and we build the internal tools for the work that falls between them.

We start with a free consultation about how the work happens today, often with the stack map above. Then we scope the first version around one process, give you a fixed price for it, and build it in short steps you can see and try. You own the code and the data, fixes are free during the fix period after launch, and we stay on hand as it grows.

One example is our own shift cover and leave app, built in-house for staffing companies. It takes staff records from the company's existing HR system rather than replacing it. When a worker doesn't show up, it offers the shift to everyone who is free, qualified and within working-hour limits, instead of a coordinator phoning people one at a time. Read how it works in the case study.

To see what a sensible first version looks like for you, try the Build Scope Planner, or see what we build. When you're ready, book a free consultation and bring the spreadsheet you most want to retire.

Frequently asked questions

Do we have to stop using our current tools? No. In most cases the opposite: your CRM, accounting package and calendar stay where they are, and the system connects them. We only suggest replacing a tool when it is genuinely holding the process back, and then we move your data across.

Isn't this just Zapier with extra steps? Automation tools move data across one handoff at a time. A connected system keeps one record of the whole process, enforces the rules in one place, shows the status of everything, and tells a person when a sync fails. Many of our clients keep a few simple automations alongside it.

Is Retool or Power Apps a good alternative to custom software? They can be, if you have someone technical to build and maintain the tools and your data already sits in one database or ecosystem. When the process spans several SaaS tools, many people use it, or you want to own what you build, a custom system is usually the better long-term fit.

What if one of our tools has no API? Most modern accounting, CRM, HR and scheduling products have one. Older systems sometimes don't. Then there are other routes, such as scheduled file exports, email parsing or the system's own database. We find this out during scoping, before anything is priced.

How long does it take? It depends on how many tools are involved and what the process has to do. A first version that connects two or three tools around one process is a much smaller job than a system for a whole department, which is why we scope before we price.

Sources