Eight Mile · Software · London
Software development in London.
A London software development company for enterprises and small businesses. We build SaaS products, customer portals, internal tools, mobile apps and the AI systems inside them, and stay responsible for them after launch. The engineer who scopes the work is the engineer who ships it.
Scope
From the first conversation to production.
Most of what we build falls into one of these six, and the interesting projects cross two of them: a portal with an AI assistant in it, a mobile app on top of an internal tool, an old system rebuilt around the integrations it always needed.
SaaS products and portals
Multi-tenant platforms, customer portals and the billing, roles and audit trails under them. Built on Next.js and NestJS against PostgreSQL, hosted in UK and EU regions, owned by you from the first commit.
Internal tools
The system that replaces the spreadsheet: quoting, scheduling, stock, reporting. Small enough to ship in weeks, structured so it survives the growth that made the spreadsheet fail.
Mobile apps
Flutter apps for iOS and Android that keep working when the connection does not: a reader that decides on the device and reconciles with the server when it can, rather than one that hangs on a spinner.
Integrations and APIs
Stripe and Open Banking, accounting packages, the supplier portal nobody documented, and the public API your partners have been asking for. Webhooks that retry, imports that can be run twice safely, and a log of what crossed the wire.
Rescue and modernisation
The product an agency built and moved on from, or the one that grew faster than anyone could tidy. We read it, write down what is fragile and what it costs to run, stabilise it, and then make it cheap to change again.
How an engagement runs
01
Survey
02
Deliver
03
Support
Who it's for
Built for the size of business you are.
The engineering is the same whoever the customer is. What changes is how the work fits around you: your process and your team, or a system you have never had before.
Enterprise teams
Extra hands that read your code first.
You have developers, a review process and a backlog they will never reach. We take a defined slice of it, work in your repositories and your pipelines, answer your security questionnaire, and leave documentation and knowledge behind.
Small and medium businesses
The system the spreadsheet was pretending to be.
Quoting, scheduling, stock, invoicing and a customer portal, built around how you already work. A focused first release in weeks, priced as one number, with the code and the accounts in your name from day one.
Founders and product owners
A product, not a prototype.
You can describe the idea in a paragraph but have no engineering team. We design it, build it and launch it on your own cloud accounts, release by release, so you can stop at any point and still own something that works.
Practice
How the work is done.
A short list of tools we know well, used the same way on every project, so the next engineer to open the repository can find their way around it.
Languages
TypeScript
Next.js and NestJS
Python and FastAPI
Flutter for iOS and Android
Data and AI
PostgreSQL
LangGraph agents
Guardrails in and out
Caching for repeat questions
Delivery
Terraform for the infrastructure
Automated tests and pipelines
A working link from week two
Fixed price per release
Ownership
Your repository
Your cloud accounts
UK and EU regions
A handover walkthrough
What you get
A scope, a working release, and someone to call.
Every software engagement ends with the same three things in your hands, however large the project.
01
A written scope and price
What we will build, what we will not, and one number for the release. Larger platforms are quoted release by release, so the commitment never runs ahead of what you have seen working.
02
A working release on your accounts
Software running in production on the cloud accounts, domain and database you own, with a staging copy beside it and the pipeline that put it there.
03
Handover and twelve months of cover
Documentation, a walkthrough for whoever looks after it next, and twelve months of cover on everything we delivered. After that, most customers keep us on a monthly support arrangement.
Proof
Work that shows how we do it.
Each of these is told in full on the case studies page: the challenge, the approach, the outcome, and the figures the project's own repository states.
Straight answers
The questions people ask first.
Next step
Tell us what you need built.
Three or four sentences about the problem and who has it is enough to start. You will get a straight answer about what we would build and roughly what it would cost.