What we do · Internal tools and portals
Internal tools and portals, built in 3 to 8 weeks
Admin panels, operations views, approval apps and portals for clients, partners and suppliers, so the work happens on one screen instead of across a spreadsheet, an inbox and a chat thread.
- Price
- From $3,000 one-time; multi-module systems from $5,000
- Time
- 3 to 8 weeks
- For
- Teams running the business from spreadsheets and inboxes, or sending customers and suppliers status by email.
- You own
- The code or the app, in your repository or workspace
Internal tools and portals give your team and your customers a proper screen for the work: admin panels, operations views, approval apps, and portals for clients, partners or suppliers. We build on Retool, Softr, Supabase or Next.js, chosen by who uses it and how much it must scale, with roles and permissions enforced on the server. Builds start at $3,000, one-time, and multi-module systems with portals at $5,000, at a fixed price set after the audit.
A proper screen for the work
Admin panels, approvals and portals, with permissions on the server.
-
Operations views
The team works from one screen, not five tabs.
-
Approval flows
Requests, approvers and an audit log of changes.
-
Portals for clients and suppliers
Each one sees only their own records.
-
Roles checked on the server
Not just hidden in the interface.
Before and after
Today
- The team works from a shared spreadsheet with no permissions
- Approvals happen by email and get lost
- Customers or suppliers ask for status because they cannot see it
- A no-code app has hit its limits on users, records or speed
- New staff need a week to learn where everything lives
With Internal tools and portals
- The team works from one screen built for the job
- Approvals are tracked with a log of every change
- Clients and suppliers serve themselves in a portal
- Permissions are enforced on the server
Out of scope: a public product you plan to sell to many customers; a tool designed before the process is agreed.
Internal tools and portals, step by step
- Week 1
The screens are sketched with the people who will use them. Roles, permissions and the data model are agreed and written down.
- Weeks 2 to 3
The first module runs on real data. Your owner and two or three users try it and their feedback goes into the next sprint.
- Weeks 4 to 6
We add further modules, approvals, notifications and the integrations to your other tools, with training as each piece lands.
- Go-live
The tool is rolled out to everyone, and the old sheet or inbox stays read-only until the new tool has handled real work. Hypercare begins.
Measured in production
“A good internal tool is one people open without being told to, so we design it with the people who will use it.”
A tool to replace the spreadsheet
Show us the spreadsheet or inbox your team lives in. We will sketch the tool that replaces it and who sees what.
Show us the spreadsheet
What you get
- The tool or portal, in production, on your accounts and domain
- Roles and permissions checked on the server as well as in the interface
- Approval flows, notifications and an audit log of changes
- Integrations to the systems it reads from and writes to
- Documentation and training recordings
How we know it is done
- Each role sees and changes only what it should, tested for every role
- The people who use it daily have signed off each module
- The spreadsheet or inbox it replaces is no longer needed
What you own
- The code or the app, in your repository or workspace
- The database, in your tenancy
- The domain and user accounts
- The documentation
of small and mid-size business leaders feel overwhelmed by too many business tools
Source: Salesforce SMB Trends, 6th editionWhat people ask about internal tools and portals
Retool, Softr, Supabase or Next.js?
Retool for internal admin panels where speed matters more than looks. Softr for simple portals on data you already keep. Supabase with Next.js when the tool faces customers, needs custom design or must scale. The reasons are written into the blueprint.
Can customers or suppliers log in?
Yes. Portals give each outside user their own login and show only their records: their orders, their documents, their approvals. Access is gated so only approved accounts get in.
Will we pay per-seat licence fees?
It depends on the platform. Retool and Softr charge per user; a Supabase and Next.js build does not. Running costs for each option are set out before you choose.
What happens if the scope changes mid-project?
We agree the change in writing before doing the work, with its price and its effect on the timeline. You decide whether it is worth it. We do not absorb scope quietly and present a larger invoice at the end.
Who owns the code, the workflows and the accounts?
You do, from the first sprint. Tools, automations and databases live in accounts in your name, code sits in your repository, and documentation is part of the deliverable. If you stop working with us, it all keeps running.
Reading
- Security
Your Lovable app is probably public
Over 170 Lovable-built apps had open databases in one disclosure. How the leak works, the three named breaches of 2026, and the twenty-minute check to run.
- Strategy
Task automation vs AI systems: how they differ
What task automation and AI systems each are, when each one fits, and how their cost and risk differ, with the five layers an AI system needs.
Also what we do
Automate
Teams re-typing data between tools, chasing status by hand, or waiting a day for a report.
Modernise
Companies running a $5M to $100M operation on spreadsheets, a legacy ERP or a tool nobody dares change.
Advise
Founders and COOs making technology decisions without anyone senior to check them.
Forward deployed engineers
Leadership teams that expect AI and automation to change how the company runs and want engineers working in the room with their teams.
Extend
Teams that already run a platform but are out of capacity, or need a skill they do not have in-house.
Harden
Founders who shipped an app with an AI builder and now need it to hold up for customers, investors or an audit.
Zapier to n8n migration
Teams whose Zapier bill grows with task volume, or who need code, self-hosting or AI steps that Zapier makes hard.
Airtable to Supabase migration
Teams whose Airtable base is slow, near its record limits, hitting API rate limits, or now used by outside people who must see only their own data.
AI agents
Teams with a multi-step task that needs reading or judgement, a clear goal and a person willing to approve the outcome.
Integrations
Teams whose tools each hold part of the picture and who re-key data between them daily.
Dashboards and reporting
Teams that export, clean and paste reports every week, or argue about whose number is right.
Related: Modernise, Dashboards and reporting, Build
Every project starts with an audit
We spend one to two weeks with the people who do the work and give you a costed blueprint, ordered by payback. The $500 is credited in full to the build.
- Audit1 to 2 weeks. $500, credited to your build.
- BlueprintIncluded in the audit’s second week. Included with the Audit; quoted separately for multi-phase programmes.
- Build2 to 8 weeks. From $1,000 one-time; internal tools from $3,000.
- Run60 days of hypercare, then monthly. Hypercare included; care plans from $50/month.

















