For operations teams

Build an internal tool with AI, on the data you already have

An internal tool starts from the sheet or the API you already run, not from a blank canvas. Eqlo writes the screens, the roles, and a Postgres database you can see. You pick the European Union, the United States, or the United Kingdom at creation. Five projects stay free, with one seat and no card.

  • 2 to 5 minFirst draft
  • 80People in the example
  • 1 / 3 / 10Seats by plan
  • 3Regions to pick
Internal expense approval tool with a four-step chain and a total
The approval screen after the first draft: a submitted expense, a manager step, then finance above a threshold.

The internal tools people ask for most

Expense reports

A submit screen, a receipt, a manager step, then finance above a threshold you write in English. The claimant sees the status without chasing mail. CSV export keeps the old sheet as an export, not as the system. The first draft lands in two to five minutes. The afternoon is for the threshold only you know.

Production tracking

A list of jobs, a status, a person on the next step. Built for a phone, because that is where the work is. Offline mode keeps the last list open. You do not rebuild an ERP. You retire the tab that sat beside it.

A supplier portal

A login for people who are not on your payroll. They see their orders, not the whole company. Invitation goes out by email. Reader, editor, and administrator stay on your side. The supplier stays a reader.

Leave requests

A form, a calendar, a name on the approval. The people directory can sit in the same project. You do not mail a spreadsheet named FINAL. When someone leaves, you remove the seat.

Illustrative scenario

A worked example

This is an illustrative scenario, not a named client. An 80-person company still runs Friday expenses in a sheet. The operations lead pastes the columns and writes that managers approve first, then finance above 300 dollars, with a receipt required. Eqlo builds a submit screen, a queue, and a status the claimant can see. They import the existing sheet as CSV. They pick the United States region at creation. In the first month the team files through the tool instead of the tab. Finance stops chasing missing receipts in email. The sheet becomes an export.

  • 80people in the company
  • $300finance threshold, assumed
  • CSVimport of the old sheet
SSO and audit settings on an internal Eqlo tool
The access screen: company sign-in, an access log, and the region chosen at creation.

Connect to what you already have

An internal tool that invents a second source of truth will lose on the first Monday.

An existing database

Eqlo creates a Postgres database from the description, with a schema you can see and change. Direct read access is there for developers. If you already run a database, say so. A very specific trade will still need a developer to take over.

A shared spreadsheet

CSV import and export are product facts. Google Sheets can be asked for in one sentence. Keys are stored encrypted. You start with an import and a gap you name, not with a promise that every legacy cell has an API.

Trade tools through an API

Stripe, Google Calendar, Google Sheets, Notion, Slack, Brevo, HubSpot, Twilio, Google Analytics, and Supabase are the named connectors. Asked for in one sentence, errors handled. Not every old system has a clean API. When it does not, you keep the import and you write the hole.

Security, access, and a trail

An internal tool fails the first security review when it invents its own login.

Single sign-on

Email, Google, and Apple sign-in exist on the public plans. A company identity provider is an enterprise conversation. Write to hello@eqlo.app. Until then, people open the tool with a mailbox they already control. You do not mail a password.

Roles and permissions

Reader, editor, administrator. Free is one seat. Plus is three. Team is ten. A commenter is not an editor. When someone leaves, you remove the seat. A forwarded URL is not a control.

Access log

Who changed a status, when, from which seat. Encryption at rest and in transit. A full access log. Daily backups, 30-day retention. A full export whenever you ask.

Hosting region

European Union, United States, or United Kingdom, chosen at creation. No silent move. Read the residency page before you paste addresses or a passport tab you should never have imported.

Frequently asked questions

Can it talk to the tools we already pay for?

Often, yes, through the connectors you enable. Spreadsheets, a calendar, a payment account. We do not pretend every legacy system has a clean API. If it does not, you start with a CSV import and a gap you name.

Where does the data sit?

In the region you pick at creation: European Union, United States, or United Kingdom. Read the residency page before you put personal data in.

Do we need engineering on day one?

No. You need a clear loop and someone who owns the first version. Engineering comes in when you outgrow the first connections or want the repository in your own pipeline.

Is this a replacement for our ERP?

No. It is a way to stop running a second system in a sheet. If a vendor already does the job, keep them. Eqlo is for the gaps that never got a ticket.

What does a first internal tool cost?

Free is $0, one seat, five projects, no card. Plus is $19, three seats. Team is $49, ten seats. SSO beyond the public sign-in options is a conversation at hello@eqlo.app.

Describe the loop. Put it in front of the team this week.

Five free projects, one seat, no card. The repository is yours when engineering has to come in.