Turn the spreadsheets that run your business into tools you own.
We build order desks, approval panels, client portals and KPI dashboards in weeks, on platforms such as Supabase and Retool or as custom web apps. Each has logins, roles and a history of every change. The code, the data and the accounts are yours.
The same work, in one place.
- Before: Orders arrive by email and phone, and someone retypes each one into a shared spreadsheet.
- After: Orders are entered once in an order desk that checks stock, prices and credit limits.
- Before: Purchase approvals are chased in chat, and nobody can say who agreed to what.
- After: Requests go through an approval panel with limits per role and a record of every decision.
- Before: Stock lives in several files, and each one shows a different number.
- After: Everyone sees one stock view, refreshed from your systems on a schedule you set.
- Before: Clients email to ask where their order is, and someone looks it up by hand.
- After: Clients log in to a portal and see their own orders, documents and invoices.
- Before: The Monday report takes hours to assemble from exports and pasted figures.
- After: A dashboard is ready each morning, with a written definition behind every number.
What replaces the spreadsheets.
Every tool ships with logins, roles, an audit trail (a record of who changed what, and when) and backups.
Order desks
Orders from every channel are entered, checked and tracked on one screen. Stock, prices and credit limits are verified as the order is typed, then it flows on to accounting and the warehouse.
Approval panels
Purchases, discounts, refunds and leave requests go to the right approver for the amount. Reminders go to whoever is holding a request, and each decision is stored with a name and a time.
Stock and job views
The view shows stock, jobs in progress and what is due to ship, read straight from the systems you already run. Nobody copies figures into a spreadsheet first.
Client and supplier portals
Clients get a login to check orders, download documents and invoices, or reorder. Suppliers can confirm delivery dates the same way. Each account sees only its own records.
KPI dashboards
The numbers you review each week sit in one place and refresh on a schedule. Every metric has a written definition, so sales and finance read it the same way.
AI steps inside the tool
A tool can read an attached order and fill the form, suggest a product code or summarise a long thread. The person using it sees the suggestion and decides.
Three tools in daily use.
Three tools for a 60-person wholesaler, with the arithmetic behind each number.
-
Example scenario
An order desk in place of the order spreadsheet
A customer emails an order, phones it in or hands it to a sales rep on a visit.
- The sales office enters it once, or uploads the customer's PDF and checks the fields read from it.
- The desk checks stock, the customer's price list and their credit limit as the order is entered.
- Orders over the credit limit wait for approval from finance, inside the same tool.
- Approved orders go to the accounting system and appear on the warehouse pick list.
About 3 hours a day back for the sales office, and one record per order that sales, finance and the warehouse all see.
Assumes 60 orders a day, 4 minutes each to retype and check by hand and 1 minute in the order desk. That is 4 hours a day down to 1.
-
Example scenario
Purchase approvals with limits and a trail
Someone needs to buy something above their own spending limit.
- They fill in a short request in the approval panel and attach the supplier's quote.
- The panel sends it to the right approver based on the amount and the cost centre.
- The approver sees the budget left and past purchases, then approves or rejects it on their phone.
- Each decision is stored with a name, a time and a comment. Approved requests go to purchasing.
Every request has a status, an approver and a history. Finance sees who approved what and when, without asking around.
Assumes three approval levels set by amount, for example team lead, operations director and owner. You choose the levels and the limits.
-
Example scenario
A Monday dashboard in place of the Friday report
The management team meets every Monday to review last week's sales, orders, stock and cash.
- Overnight, the dashboard reads the week's figures from accounting, the CRM and the warehouse system.
- Each figure is checked against simple rules, and gaps or sudden jumps are flagged before the meeting.
- Every metric links to its written definition and to the records behind it.
- Actions agreed in the meeting are noted on the dashboard and reviewed the next Monday.
Everyone opens the same numbers before the meeting. The 4 hours someone spent building the report each Friday go to other work.
Assumes 4 hours each Friday to export, paste and check the figures by hand: 184 hours a year over 46 working weeks.
Platforms you can keep.
Low-code platforms assemble standard screens quickly, and custom code covers what they can't.
- Low-code platforms
- RetoolAppsmithBudibasePower Apps
- Custom web apps
- ReactNext.jsNode.jsTypeScript
- Data and sign-in
- SupabasePostgreSQLMicrosoft Entra IDGoogle Workspace
- Dashboards
- MetabaseLooker StudioPower BI
We choose the platform for each project, often one you already pay for. The accounts, the code repository and the database are all in your company's name.
From spreadsheet to daily tool.
Audit
We watch the spreadsheet in use, list who needs to see, change and approve what, and choose the platform with you.
Pilot
We build a first version on your real data. A small group uses it next to the old spreadsheet, so the figures can be compared.
Deploy
We add roles, the audit trail, backups and sign-in with your company accounts, then train your team. The old spreadsheet is retired once the figures match.
Operate
We fix, extend and add screens as the business changes, or hand the code and documentation to your own developers.
Questions about staying in control.
Why not buy an off-the-shelf system instead?
Sometimes you should, and the audit will say so. A custom tool earns its place when the process is specific to you or the data sits across several systems. It also helps when you need permissions a packaged product doesn't offer.
Who owns the code and the data?
You do. The code sits in a repository in your name, the data in a database in your account, and platform accounts are registered to your company. Each tool comes with documentation good enough for another developer to pick it up.
What if the platform raises its prices or shuts down?
We plan for it. Where we can, data lives in a standard database you own, such as PostgreSQL, and the business rules are written down. Moving the screens to another platform is work, but your data and your rules move with you.
Can different people see and change different things?
Yes. Roles decide who can view, edit and approve each record. A sales rep sees their own customers, finance sees every invoice, and a client in the portal sees only their own orders. Every change is logged with who made it and when.
Will it work with our accounting system or ERP?
If the system has an API (a built-in way for other software to read and write its data) or a scheduled export, yes. We check how yours connects during the audit, before you commit to a build.
How long does a first tool take?
We plan 2–4 weeks for a first version on your real data, then 2–6 weeks to make it ready for daily use. A single dashboard can be quicker. A portal used by people outside your company needs more security work, so plan for the longer end.
Bring us the spreadsheet everyone depends on.
In the audit we map who uses it and how, then propose a first tool with a fixed scope and a fixed price.