Trusted by clients from global brands to local charities
What changes when the work moves into a system built for it
Most of our builds start in one of three places: software bought off the shelf that never quite fitted, spreadsheets the business has outgrown, or an older bespoke system that can't keep up. The jobs are the same whichever it is.
Today
With a web app built for you
Today: The package covers most of the job, so the rest lives in spreadsheets beside it.
With a web app built for you: The system follows your process, so the workarounds go.
Today: An order arrives by email and gets typed into two spreadsheets.
With a web app built for you: It's entered once, and everyone who needs it sees it straight away.
Today: The old system only runs in the office, and one person really knows how it works.
With a web app built for you: It runs in the browser and on a phone, laid out so anyone on the team can use it.
Today: Approvals sit in someone's inbox until they get chased.
With a web app built for you: Requests go to the right person and move on the moment they say yes.
Today: Engineers on site ring the office to find out the job details.
With a web app built for you: They open the job on their phone and close it off there.
Web app development
Software in the browser, on every screen your team uses
A web app is software people sign in to and work in, rather than a site they read. It runs in the browser, so there's nothing to install in the office. On a phone it installs straight from the browser and works like an app. One build means one set of data and one thing to look after.
At a desk
Full screens for the people who live in the system all day.
On the road
Today's jobs, checklists, photos and signatures, on the phone in their pocket.
Updated for everyone at once
A new release reaches every screen when it goes live, with nothing for anyone to install.
What's included
- A workshop and a clickable prototype
- Screens designed and built by one team
- Connections to the tools you already use
- Support from the day it goes live
Built from the inside out
Build the system your team runs on first. Once orders, jobs and customers live in one place, the same data can serve the people you work with: customers check and manage their own orders in a portal, suppliers confirm deliveries, and a quote tool on your website feeds straight in. Every outside view comes through the same sign-in and access rules, held in the database, so each customer sees only their own records. And a portal that saves your customers a phone call becomes part of why they choose you.
- OperationsOrders, jobs and stock in one place
- ApprovalsRequests that move on without chasing
- Your team on the roadToday's jobs on their phone
- Customer portalCustomers check and manage their own ordersTheir own orders only
- Supplier portalSuppliers confirm orders and deliveriesTheir purchase orders only
- Tools for your customersQuotes and calculators that feed straight inPrices out, enquiries in
What we build
Four shapes our web apps take, from the systems inside the business to the portals outside it, often in one build.
The system for the people out of the office: today's jobs, checklists, photos and a signature, installed from the browser.
The stack behind every web app
Every web app we build runs on two platforms that between them do the work of ten or twelve separate cloud services. Vercel runs the screens and stops attacks before they reach your system. Supabase holds the data, sign-in and files in the region you choose, with the rules about who sees what built into the database. Aikido checks every change for security issues. So the first weeks of a project go on what your team will use.
Secure and connected from the first release
The parts that take weeks on a bare build come ready on our stack, so your budget goes on your screens and your rules.
- Work-account sign-in
Your IT team stays in control
Staff sign in with their Microsoft work account. When IT switches an account off, that person can't sign in again.
- Access rules in the database
People see only what they should
The rules hold in the app, in reports and in every integration, because they live with the data.
- Your choice of region
Your data is held where you need it
The database, user accounts and files sit in the region you choose, the UK included.
- Independently audited platforms
Security a single build couldn't buy
Vercel and Supabase are independently audited to SOC 2 Type 2 and ISO 27001, and your data is encrypted at rest and in transit.
- Point-in-time backups
A bad day can be undone
On our standard set-up, if something goes wrong with the data, it can be wound back to a moment before it happened.
- Connected to your tools
It works with what you already use
Alerts land in Teams and Power BI reads the figures. Finance software and your CRM connect wherever they offer a way in.
What goes into the first release
We don't rebuild everything at once. The first release takes over the two or three jobs the business leans on hardest, wherever they live today, so it's in use within weeks. Each release after it comes from what your team learns using it.
Today
- Orders
- Stock
- Quotes
- Jobs
- Invoices
- Suppliers
- Rota
- Pricing
- Contacts
- Returns
- Deliveries
- Timesheets
- Purchasing
- Reports
- Holidays
Your new system
- Orders
- Stock
- Quotes
- Jobs
- Invoices
- Suppliers
- Rota
- Pricing
- Contacts
- Returns
- Deliveries
- Timesheets
- Purchasing
- Reports
- Holidays
Everything else keeps running as it is, fed from the new system until its turn.
How a build runs
Short loops, real feedback, and something in use early.
What clients say about working with us
Questions about web app development
A website tells people about your business. A web app is where the work gets done: people sign in, enter and find information, and act on it. We build both, and they often share the same data.
We build web apps that install on a phone straight from the browser and work like an app. We don't build App Store apps, by choice: one build means one set of data, and every release reaches everyone at once.
You'll click through a prototype before the build starts, and the first release is usually in use within weeks, because it covers the part of the process that matters most. After that the system grows month by month, guided by what your team tells us.
We give you a range rather than a fixed price, based on what the first release needs to do. You budget for the top of the range and we aim for the bottom. A workshop gets you a range you can plan around.
Usually, yes: Microsoft 365, your finance software, your CRM and more, wherever they offer a way in. Information goes in once and gets passed to wherever it's needed. If a tool can't connect, we'll tell you in the workshop.
Your data, user accounts and files sit in the region you choose, the UK included, on platforms independently audited to SOC 2 Type 2 and ISO 27001. Staff sign in with their work accounts, and the rules about who sees what live in the database itself.
No. Your web app is built on open, widely used technology. It can run in our managed space or in your own accounts, the data comes out with standard tools, and another supplier could pick it up.
Support starts the day the first release goes live, from the people who built it, with a monthly allocation of time that you direct.









