Custom internal tools built around the way your team works
We design and build custom web applications and internal tools for the processes that spreadsheets, email and generic software no longer handle well.
When a custom tool makes sense
Custom software isn't always the answer — but these are common signs that it might be.
Spreadsheets used as a database
Several people edit the same files, versions multiply and nobody is sure which one is correct.
Processes run by email
Requests, approvals and updates are scattered across inboxes, so things are missed and hard to follow up.
No overview
It's difficult to see the status of orders, jobs or requests without asking around.
Generic software that doesn't fit
Off-the-shelf tools force workarounds or include far more than you need.
Double entry and manual checks
Staff re-enter or re-check the same information because there's no single reliable source.
No audit trail
You can't easily see who changed what, or when.
What we build
We focus on tools that are simple to use, solve a defined problem and can grow over time.
Business web applications
Browser-based applications built for a specific process, usable on desktop and mobile.
Tracking systems
Tools to track orders, requests, jobs, assets or stock, with clear statuses and history.
Workflows & approvals
Structured forms, assignments and approval steps that replace email chains and paper.
Portals
Secure areas where staff, customers or suppliers can view information and submit requests.
Admin panels
Simple interfaces for managing data that currently lives in spreadsheets or raw databases.
Integrations
Connections to your existing systems so the tool fits into your wider processes.
Start with a clear, fixed-price package
Defined scope, delivered in days, no calls required.
Examples of internal tools
Tools sized to the problem — from a single team's tracker to a multi-user system.
Small and local businesses
- A simple web app replacing a shared booking or job spreadsheet
- An internal tool to track repairs, orders or equipment
- A request form with automatic notifications and a clear status for each request
Professional firms and growing teams
- An internal tool replacing an important multi-user spreadsheet
- A request and approval system with roles and an audit trail
- A supplier or customer portal connected to existing systems
How we approach an internal tool
Start with the smallest version that solves the real problem, then improve it with the people who use it.
- 01
Understand the process
We map how the process works today, who is involved and where the friction is.
- 02
Define a first version
We agree the smallest useful version of the tool, so it can be used — and improved — early.
- 03
Prototype
We build working screens for the key tasks and refine them with the people who will use them.
- 04
Build & test
We develop the application with permissions and data validation, and test it with realistic data.
- 05
Launch & support
We help migrate existing data, document the tool and agree how fixes and new features will be handled.
Technologies we may use
We favour well-established, maintainable technology over novelty.
Application
- TypeScript
- React
- Astro
Data & back end
- SQL databases such as PostgreSQL or SQLite
- APIs and serverless functions
- Authentication and role-based access
Hosting
- Cloudflare
- Other cloud platforms, depending on your requirements
Before recommending a custom build, we check whether an existing product could meet your needs at a lower cost. Custom software also needs maintenance — we discuss this openly from the start.
Internal tool questions
Is custom software worth it compared with an off-the-shelf product?
Sometimes, not always. A custom tool makes sense when a process matters to your business and existing products don't fit without heavy workarounds. If we think an existing product is the better choice, we'll say so.
Can we start small?
Yes, and we recommend it. A focused first version that solves the main problem can be in use sooner and gives you real feedback before investing further.
Who owns the code?
Ownership of the source code and documentation is agreed in writing before the project starts, so it's clear from the outset.
Will the tool work on phones?
Yes. We build browser-based tools that work on desktop, tablet and mobile, so there's nothing to install.
Can you import our existing spreadsheet data?
In most cases, yes. We review the data, clean it where needed and import it as part of the launch.
Has a process outgrown its spreadsheets?
Tell us how the process works today and what's going wrong. We'll suggest the simplest tool that would help.