Web applications
The thing your business runs on, built for your workflow rather than bent out of a template. Job cards, scheduling, inventory, dispatch, quality checks — fast enough to use all day.
Software built to order.
You describe what it has to do and who has to use it. We build it, ship it, and hand it over — with the source code and every account in your name.
For founders, product owners, CTOs and heads of IT.
What we build
Six things we get asked to build.
Whether it is a product you sell or a screen five people use every day, the work is the same: understand who uses it, build it properly, hand it over.
SaaS products
A product you sell, not just software you use. Multi-tenant from the start, with billing, plans, onboarding and an admin panel — because retrofitting those later costs more than building them now.
Internal tools and admin panels
The unglamorous screens your team lives in. Built to be fast and boring, with the permissions and audit trail you will need the first time someone asks who changed a number.
Client and vendor portals
A place for people outside your company to check status, raise requests, upload documents and pull invoices, instead of emailing someone in your office to ask.
Landing pages and marketing sites
Fast, accessible, properly structured for search, and editable by your team without a developer. Built to be measured, not just to look good in a review meeting.
Mobile apps
iOS and Android for teams who are not at a desk — field staff, drivers, technicians, sales. Works on a bad connection and syncs when it comes back.
How we build
You see it working before it is finished.
Software goes wrong when the first honest look at it happens at the end. You get something usable early and a working build at every milestone, so the direction can still be changed while changing it is cheap.
Requirements
We work out what it has to do, who uses it, what it must connect to, and what is genuinely out of scope.
- A written requirement list, in your words not ours
- An honest note on anything we think you should not build
Scope and estimate
The requirements become a scope you can hold us to, with a fixed price against each milestone.
- A written scope naming what is in and what is explicitly out
- A fixed quote, or a range with the reason it is a range
Design
Screens and data model before code. Disagreements are cheapest to settle here, on a drawing.
- Screens or flows for every part we disagreed about
- The data model and the third-party services it depends on
Build
Something usable in your hands early, then a working build at every milestone, on ordinary current technology another team could pick up.
- A working environment you can open, not a progress report
- Regular releases, each signed off by the people who will use it
QA
We break it before your users do — the paths people actually take, on the devices and connections they actually have.
- Automated checks on the parts that must not silently break
- A tested build on real devices, not just a developer laptop
UAT
Your team uses it against real work and signs it off. Anything found here is fixed before launch, not after.
- A tracked list of what you raised and what we did about it
- Written sign-off from the people who have to live with it
Handover
Source code, documentation and every account created for the project become yours.
- Full source and repository access in your own organisation
- Written documentation, kept with the code, and 90 days of support
Fixed price per milestone, quoted after the scope.
We do not quote a number before we know what the thing has to do — a figure invented in the first call is either padded or wrong. Scope is free for a defined brief, and the quote that follows is fixed. If scope changes, the change is priced before it is built.
Selected work
Things we have built.
What the software does and what it was built with. No client names — where work was commissioned, the client owns it.
An embeddable AI product assistant, shipped as a one-line SDK.
Read the case study →TypeScript · React · Node.js
A 24-module business OS with a double-entry general ledger.
Read the case study →Internal projectNext.js · React · TypeScript
Multi-tenant vertical SaaS running logistics for Indian transporters.
Read the case study →Next.js · React · Node.js
Healthcare platform for patients, doctors, nurses and admin staff.
Read the case study →Flutter · Node.js · Express
Case-management platform for legal teams.
Read the case study →React · Node.js · Express
Full-stack product across web, admin and mobile.
Read the case study →React · React Native · Node.js
Healthcare CRM: leads, counsellors, appointments and claims in one workspace.
Read the case study →Hospital internal systemNext.js · React · TypeScript
Farm ERP with a biochar carbon-credit dMRV platform.
Read the case study →React · TypeScript · Vite
A children's product spanning a device, a parent portal and an admin console.
Read the case study →In Play Store reviewRaspberry Pi · Python · React
CRM for a payments business, on a Firebase backend.
Read the case study →React · TypeScript · Firebase
A structured book-review platform, published on Google Play.
Read the case study →In Play Store reviewFlutter · Dart · Node.js
Consumer mobile application, published on Google Play.
Read the case study →Flutter · Dart
Laboratory application for zebrafish behaviour tracking and analysis.
Read the case study →Desktop applicationPython · Arduino · FLIR SDK
Web-to-print design tool and admin portal, with a companion Android app.
Read the case study →React · Fabric.js · Node.js
Campus application for Al Akhawayn University, on Google Play.
Read the case study →Flutter · Dart
AI business management platform.
Read the case study →React · TypeScript · Node.js
AI-powered body measurement from a phone camera.
Read the case study →In Play Store reviewFlutter · Dart · Python
Work built by the Leapforge team. Where a product is live the case study links to it; where it sits behind a sign-in, it says so.
Ready to discuss?
Tell us what it has to do and who has to use it. You get a written scope, a fixed quote, and an honest note about anything we think you should not build.