Create, edit and publish, then run your website and your app from their own dashboard. Every feature shown in real screenshots.
See the features
A Next.js project in React and TypeScript, sent to your GitHub repository. A spec change made in the repository comes back to Eqlo.
See the developer page
Paste a URL. In thirty seconds you see exactly what Google receives before any JavaScript runs.
Check a URLA spreadsheet that four people edit at the same time always ends the same way: two versions, a missing row, and nobody who can say who did what. To build an operations app with AI, you describe your process in plain English, and Eqlo sets up the tables, statuses, roles and automations, then imports the data from your spreadsheet.
Before anyone tries to build an operations app with AI, this is the step they skip, and it decides whether the tool is adopted or bypassed. A poorly described process yields a tool that makes people tick false boxes to move on, and the spreadsheet is back within a month.
Describe each step with a verb. Not “file in progress”, but “the manager checks the receipt”. A step you cannot phrase as an action is really a wait: it does not need a screen, it needs to go. Each step that survives becomes a value of the status field.
Give each step to a role, never to a person. “The branch manager”, not “Sophie”. When Sophie changes jobs, the tool carries on. The exercise also exposes steps with no clear owner, which is common and costly. In the admin, each role gets its own tabs and, for every table, precise rights from read-only up to export.
Write down the thresholds and the exceptions. Above a certain amount, one more approval. In an emergency, act first and tidy up later. Exceptions are what sink rigid tools, and each fits in one sentence that the AI turns into a condition: greater than, less than, equal, empty or contains.
Measure the waiting before the work. In most processes the real work takes minutes and the total delay takes days. The cost lies in the moment a file sits unnoticed, and the tool has to tackle that moment first.
Two versions float around, a row vanishes, and nobody knows who removed it. Everyone keeps a private copy “just in case”, which makes things worse. In Eqlo, every record has its own history: who changed what, whether it was the team, a member, an automation or a visitor.
The ERP holds the accounts, another tool holds the stock, and one person copies from one to the other. Eqlo does not plug straight into those systems, but their CSV or Excel exports import into an existing table, and an automation can send a signed webhook that Make, Zapier, n8n or your server picks up.
The file waits for a signature, nobody is told, and it only moves when someone remembers. The delay comes from silence, not from work. An automation triggered by a status emails the record’s values to the right person, which is the quickest win of the whole project.
Three tools the team builds by itself, starting from the internal tool project type. None needs engineering work.
A table of files with an amount, a receipt and a status for each step, shown as a kanban board. Rules are written in plain English: “when a manager approves a claim over $300, move it to finance and email them”. Action buttons approve one file, or a batch of them.
Jobs, stations and their status, with a photo field, a date-and-time field and a calendar or kanban view. A dashboard shows the indicators, how they moved since the previous period and progress toward a target.
Suppliers become members of the site, signing in with a one-time email code. They upload a document or report a delay through a moderated form, and a members-only list shows them their own submissions. Pages reserved for members are never indexed by Google.
This is what sets operations apart from other roles. The tool is used standing up in a workshop, a warehouse or a van, usually between two jobs, rather than at a desk.
Signal comes first. Installed on the home screen, the app keeps screens already opened readable offline, but entering data needs a connection. If an area never has signal, plan for entry on the way back and say so plainly: a tool that promises more than it delivers gets dropped.
Input comes next, and it should be rare and simple. Lists and statuses rather than free text, and a photo whenever possible: snapping a meter takes three seconds, retyping it takes thirty and adds mistakes.
Last, a status beats a declaration. Asking for start and end times gets rounded, hopeful numbers. Moving a status with one button is enough, because the record’s history keeps every change and nobody has anything to report.
This scenario describes no real company. For four years, the eighty employees of a firm have logged their expenses on one shared sheet. Three weeks pass on average between submission and repayment, nearly all of it waiting.
Drawing the process shows the real problem before anything is built: of three weeks, the actual work takes under an hour. The rest is waiting, because nobody learns that a file is sitting with them.
The tool takes in four years of history through an Excel import, sets the four statuses, the $300 rule and the receipt photo. Above all, each status change emails the next person in line. The old sheet remains open in read-only mode for a fortnight, then falls out of use.
Eqlo neither replaces it nor tries to. ERP exports feed your tables by import, and the tables go back out as CSV or SQL. The tools you build sit beside the ERP, never in its place.
A seven-day invitation link opens this one project and nothing else in your Eqlo account. The admin keeps the last fifteen sign-ins with their method and any refusals. On the Team plan, company single sign-on protects access to the studio.
Every list exports as CSV and every table as SQL. Finance keeps working in its own tools, pulling current data when it needs it instead of waiting for a weekly copy by email.
Describing a process, setting statuses, roles and automations, then changing them as you learn: that is your job, and you need nobody for it. “Add a Suppliers tab with an automatic reminder” is enough for the AI to create the tab, the fields and the automation. Deleting data asks for confirmation, and one click undoes a change.
The limit comes with company systems. Eqlo has no public API and no direct database connection, so reading from or writing to an ERP is a developer’s job. Once the tool becomes critical, developers can pick it up from a GitHub repository holding the specification and the Next.js source.
For the full internal tools guide, or the other teams that use Eqlo.
That page covers the build: spreadsheet import, tables, roles and security. This one covers operations work itself: the process, the steps, the waiting and the realities of the floor.
Not directly. An automation can call a signed webhook to Make, Zapier, n8n or your own server, which then writes to the ERP. That bridge is something to build with your technical team.
Not day to day: adding a step, moving a threshold or editing an email takes one sentence. Owners and admins can also have the AI change the admin’s code, reviewing the modified files before they accept.
Partly. Installed on the home screen, it keeps screens already opened readable. Entering data needs a connection, so in a dead zone, records are added on the way back.
Describe them as rules with conditions on fields. In an emergency, an admin moves the status by hand, and the record’s history shows who did it. A tool that ignores exceptions ends up bypassed.
Yes, as members of the site. Once signed in, they send documents through a form and see only their own records.
Compare total elapsed time before and after, not typing time. The work takes minutes and the delay takes days, so the gain shows up in the waiting. Record histories show where files stall.
Push the project to GitHub, where your developers get standard Next.js code to run in their own setup. If they change the specification in that repository, the change returns to Eqlo as a new version.
Start without a card, with five projects and one seat for free. Connections to company systems stay with your technical team.