Internal tools

The internal tools builder with AI, on the data you already have

A useful internal tool starts from what already exists, usually a spreadsheet that has grown too big. With Eqlo as your internal tools builder, you import that file, describe the process in plain English, and get screens with roles, approvals and a history of every change. The code can go to your GitHub repository whenever you want.

20,000rows per CSV or Excel import
15field types in the admin editor
300automation runs a day per project
$49a month for the Team plan

Internal tools builder screen showing expense claim EX-1042 for $389.50, approved by the manager and waiting for finance under the over $300 rule — An expense claim above $300: the rule sends it to finance after the manager has approved it.

Replacing a shared spreadsheet without breaking what works

Most internal tools start the same way. A spreadsheet works well for two years, then four people write in it at once, two versions circulate by email, and a row disappears without anyone knowing who deleted it.

The safest path is not to replace everything in one go. It works best in three stages, and Eqlo is designed for that progression.

First, import the file as it is

Bring in your spreadsheet saved as CSV or Excel, within 5 MB and 20,000 rows, and your data appears in a list screen of the admin. You retype nothing, and the original file stays where it was.

Then, add what the spreadsheet lacks

A history showing who changed what, read rights for some people and write rights for others, a status that cannot be skipped, an email when a row waits for approval. Those gaps are usually why you started looking for a tool.

Finally, move one team at a time

Keep the spreadsheet available in read-only mode for two weeks while habits change. Migrations fail when access to the old file is cut before the new tool has proved itself.

The internal tools people ask for most

Four kinds of tools come up in almost every company, whatever its size. Each one has its own tricky part.

Expense reports

An employee fills in a form with the amount, the reason and a photo of the receipt, and the claim reaches their manager, then finance. The tricky part is the rule, not the form: above a set amount, another approval is required. You write that rule in a sentence, and an automation applies it.

Production tracking

A list of jobs, a status for each station and a photo at each step, shown as a kanban board in the admin. Workshops often have weak signal, so keep in mind that the installable app only keeps pages already opened readable offline. Entering new data needs a connection.

Supplier portal

Suppliers create a member account on your site, which you approve before they get in. They then send documents through a form and find their own submissions in their member dashboard. They never see the data of other suppliers.

Time-off requests

A request form, a calendar screen for the team and an approval status for each request. An automation can email the employee as soon as their manager approves, so nobody has to chase an answer in the hallway.

Illustrative scenario

An example from start to finish

Nothing here describes a named client. For the past four years, the expense claims of an eighty-person company have lived in one shared spreadsheet. The office manager describes the current process in three sentences: who submits a claim, who approves it, and above which amount finance must review it.

4 yearsof history imported from a CSV file
$300threshold that adds a finance approval
3roles: employee, manager, finance

The import brings in four years of history with the original column names, so nobody has to learn new vocabulary. Three additions make the difference: the receipt photo attached to the form, the $300 rule, and a history showing who approved each claim. The spreadsheet stays readable for two weeks, and after that nobody opens it again.

Admin team settings with a custom finance role, read and edit rights on the expenses table, and a log of the last 15 sign-ins — Access to the tool: a finance role with its rights on each table, and the list of recent sign-ins.

What the internal tools builder connects to

A tool that creates a second source of truth wastes time instead of saving it. The aim is to bring your data in once, then send it where your other tools need it.

Your spreadsheets

A one-time CSV or Excel import is almost always the right choice. Keeping a spreadsheet in sync means keeping the problem that brought you here. Data leaves the tool just as easily, as a CSV or SQL export.

Your everyday software

Slack, Google Sheets, Notion, HubSpot, Brevo, Twilio and Stripe connect in a few clicks, each with a test button and a log. Secrets such as API keys are encrypted with AES-256.

Your in-house systems

An automation can call a secure webhook when a record changes, and a signed webhook can feed Make, Zapier, n8n or your own server. That is how the tool hands data to an ERP or an internal service.

Security, access and a trail

An internal tool handles data you do not want circulating freely. These points are set when the project is created, not after the first incident.

Company sign-in for builders

On the Team plan, the people who build and edit tools sign in to Eqlo through Google Workspace, Microsoft Entra or Okta. You can make that SSO mandatory for every address on your domain.

Roles for each table

In the admin of the tool, a custom role sets which tabs appear and, table by table, whether someone may view, add, change, remove or export records. A manager can approve for two teams while an accountant reads everything and changes nothing.

A history on every record

Each record shows who changed what, whether it was a colleague, a member, an automation or a visitor. The admin also lists its last 15 sign-ins, with the method used and any refusals.

Invitations limited to one project

You invite a colleague to the admin of a single tool with a link valid for 7 days. The rest of your Eqlo account stays closed to them.

See how Eqlo protects your data

Eqlo, Retool, Airtable or building it in-house

Here are the four usual ways to build an internal tool, compared on what really changes. Competitor details were checked in September 2026, so look at each vendor’s current prices before deciding.

Comparison of Eqlo, Retool, Airtable and an in-house build
Criterion	Eqlo	Retool	Airtable	In-house build
Starting point	a description and a spreadsheet	components to assemble	a base to structure	a specification
Mobile version	installable app from the same project	limited	limited	separate project
Company SSO	Team plan, for the workspace	depends on plan	depends on plan	to be built
Code you can take away	Next.js on GitHub	no	no	yes
Price	$49 a month for the Team plan	per user	per user	salaries
Who changes it later	anyone, by writing in the chat	a developer	a power user	a developer

Retool remains excellent for a developer assembling an interface on top of existing databases. Airtable fits well when the need is close to a structured, shared spreadsheet. An in-house build makes sense when the tool sits at the heart of your business. As an internal tools builder, Eqlo covers the most common case: a known process, a team that cannot wait, and no developer available this quarter.

Pick the page that matches the team involved and how demanding the project is.

Frequently asked questions

Can the tool connect to a database we already run?

Not directly. You bring the data in with a CSV or Excel import, then keep other systems informed through webhooks to Make, Zapier, n8n or your own server. Exports to CSV or SQL are available at any time.

Who can sign in to the tool?

Colleagues you invite to the admin, each with a custom role, and members who register on the site if the tool has a public side. The admin keeps a log of its last 15 sign-ins.

Do we need a developer to change the tool later?

Not for everyday changes. Adding a field, changing a threshold or adding an approval step is done by writing a sentence, such as "add an Invoices tab with an automatic reminder". Bringing in a developer only makes sense once the rules become intricate.

Is this a replacement for our ERP?

No. Eqlo builds the tools missing around the ERP, such as what lives today in a spreadsheet, a paper form or an email thread. The two work side by side, with webhooks carrying data between them.

What happens when someone leaves?

You remove their role in the admin of the tool, and their access ends. The history of each record still shows what they changed. For the Eqlo workspace itself, mandatory SSO on the Team plan blocks an account disabled in your directory.

Can we bring the tool in-house later?

Yes. The GitHub connection pushes the complete React and TypeScript code of the Next.js project, together with the specification. If someone changes the specification inside the repository, Eqlo picks it up as a new version, and your developers keep working in their usual tools.

Can suppliers use the tool?

Yes, as members of your site. You approve each registration, and each supplier only finds their own submissions in their dashboard.

How many seats does the Team plan include?

Ten seats in the Eqlo workspace, for the people who build and edit tools, at $49 a month. For a yearly invoice or a purchase order, write to hello@eqlo.app.

Describe the process and put the tool in front of the team this week

Open a free account with five projects, no card needed. Import your spreadsheet, describe the steps, and share the admin with the colleagues concerned.

Build an internal tool See pricing