Internal tools
Replace the spreadsheet everyone edits and nobody trusts
We turn the spreadsheets and shared documents that run your back office into small, reliable apps: one set of data, clear rules, approvals where they matter and a history of who changed what.
Work orders
OrderOwnerDueStatus
WO-218 CuttingIvanTodayDone
WO-219 WeldingMarkoTodayIn progress
WO-220 CoatingAnaTomorrowBlocked
WO-221 AssemblyPetraFridayPlanned
WO-217 CuttingIvanMondayDone
What it is
The same work, without the fragile file
A spreadsheet is the right tool until several people edit it at once, a formula is overwritten, or a decision depends on a column someone forgot to fill in. An internal tool keeps what worked, the columns and the logic your team already understands, and adds what a spreadsheet cannot: required fields, permissions, approvals and a record of every change.
- Starts from the spreadsheet you use today, including its data
- Rules are enforced by the tool, not remembered by people
- A person approves wherever a mistake would be costly
- Connected to the CRM, ERP and accounting so nothing is typed twice
Purchase request
- FormRequest submittedItem, quantity, job reference
- RulesBudget and supplier checkedOver the limit: needs a manager
- ApprovalManager decides
- ERPPurchase order created
What we deliver
Tools we are most often asked for
Scheduling and dispatch
Jobs, teams, vehicles and dates on one board, with conflicts shown before they happen.
Approvals
Purchase requests, discounts, leave and expenses routed to the right person, with the decision recorded.
Registers and records
Equipment, contracts, certificates and deadlines in one place, with reminders before something expires.
Dashboards and reports
Figures pulled from your systems on a schedule, so the monthly report is opened and not assembled.
Quality and checklists
Inspections and handovers filled in on a tablet or phone, with photos, and stored against the job.
Integrations
Data read from and written to the CRM, ERP and accounting software, so the tool is not another island.
How a project runs
One spreadsheet at a time
- 01
Map the process
We sit with the people who use the spreadsheet and note what each column means, who fills it in and what goes wrong.
- 02
First tool
We build the core screens, import the existing data and put the tool into use with the team that owns the process.
- 03
Extend
Approvals, notifications, reports and integrations are added once the basics are in daily use.
- 04
Care
We fix what comes up, keep the software current and adjust the tool as the process changes.
What we build with
- Application
- Next.js, React, TypeScript, PostgreSQL
- Connected to
- Google Workspace, Microsoft 365, Odoo, Pipedrive, HubSpot, Your accounting software
- Around it
- Single sign-on, Role-based access, Audit log, n8n
Is an internal tool worth building?
A good fit when…
- A shared spreadsheet runs a process that several people depend on
- Mistakes come from missing fields, overwritten formulas or old copies
- You need to know who changed or approved something, and when
- No off-the-shelf product matches the way the process works
Probably not for you when…
- One person uses the spreadsheet and it causes no trouble
- An existing product covers the process and you can adapt to it
- The process changes every few weeks and is not settled yet
- A setting in a tool you already pay for would solve it
Use cases
Where internal tools are used
Problems an internal tool is often part of solving.
An assistant that answers from your documents
Staff or customers ask in plain language and get an answer drawn from your documents, with the source shown.
Open use case OperationsBusiness automationCustom softwareNew colleagues ready on day one
Accounts, equipment, documents and first-week tasks set in motion from one form.
Open use caseQuestions about internal tools
Why not keep the spreadsheet?
Often you should. If one or two people use it and it causes no errors, a spreadsheet is the right tool. It stops being right when several people edit it, when a mistake in it costs money, or when you need to prove who changed what.
Why not a no-code tool?
For simple cases a no-code tool can be the better answer, and we will say so. We build custom when the rules, the permissions or the integrations go beyond what those tools handle well, or when you want to own the code and the data without a per-user platform underneath.
Can you import what is already in the spreadsheet?
Yes. We clean the data, import it and check it with the people who know it, so the tool starts with your history and nobody retypes anything.
How do our people log in?
Usually with the Google or Microsoft account they already have, so there is no new password and access ends when the account is closed.
Can it be used on a phone or tablet?
Yes. Screens used away from a desk are designed for a phone or tablet first. If the work needs offline use or the camera, a mobile app may suit better.
Who owns it?
You do. The code is in your repository, the database in hosting you control, and the documentation is written so another developer could continue the work.
Show us one process. We will show you what it could look like.
The analysis is free, takes about an hour of your time, and ends with a written summary you keep.
Prefer to read first? See examples