Extend
The software your ERP will never cover
Customer-facing products and internal tools, built by senior engineers on a schedule you can plan around. The 20% of your stack that is genuinely specific to your business.
Sound familiar?
Your ERP covers the standard process and the thing that makes you different is still run on spreadsheets.
Your last agency delivered something that worked on demo day and nobody can safely change now.
You need to ship before a funding round or a customer deadline and your own team is already committed.
What we do
Capabilities
- Web applications
- Customer portals, dashboards and internal tools, built on TypeScript and React with the same standards we hold our own work to.
- Mobile
- Cross-platform applications where that is the right call, native where it is not. We will tell you which, and why.
- APIs and integration
- The services that connect your ERP, your product and the third parties you depend on, designed to be debuggable at 2am.
- Legacy rescue
- Taking on a codebase someone else left behind: stabilise, test, document, then change safely. Rarely glamorous, frequently urgent.
- Testing and CI
- Automated tests and pipelines from the first commit, because retrofitting them costs several times more than writing them.
- Handover
- Documentation, architecture decision records and onboarding for your team. Built on the assumption you will take it in-house.
Outcomes
What changes
Before
The gap between what the ERP does and what the business needs is filled with spreadsheets.
After
It is filled with software that is tested, deployed and owned.
Before
Changes reach production when somebody feels confident enough.
After
They reach production when the pipeline is green, which is a different and more reliable thing.
Before
Handover means a repository and a conversation.
After
Handover means tests, documentation, and a team that has already run the deployment themselves.
How it works
The engagement
- 01
Discovery
1–2 weeks
Requirements, architecture and a fixed-price scope. You leave with a plan you could hand to another firm.
- 02
Foundations
1–2 weeks
Repository, pipeline, environments and the design system, so the first feature ships into something production-shaped.
- 03
Build
6–16 weeks
Two-week increments, each deployed to a preview environment you can click through rather than read about.
- 04
Launch and hand over
2–4 weeks
Production launch, monitoring, documentation and a working session with whoever owns it next.
Go deeper
The playbooks set out how these processes run, step by step — what is standard, what gets configured, and what changes.
Stack
- TypeScript
- React
- Next.js
- Node
- Python
- PostgreSQL
- AWS
- Vercel
Questions
The things people actually ask
- Fixed price or time and materials?
- Fixed price for well-scoped work after discovery, monthly for a dedicated pod when the scope will genuinely evolve. We will recommend whichever fits — fixed-pricing a vague scope is how both sides end up unhappy.
- Who actually writes the code?
- Senior engineers. No pyramid staffing, and the person who scoped the work is on the build. You meet them before you sign.
- What happens if we want to take it in-house?
- That is the assumed end state. You own the repository from the first commit, and handover documentation is written as we go rather than assembled at the end.
- Can you work with our existing team?
- Yes, and it is often the best arrangement. We join your standups and your repository rather than running a parallel project and integrating at the end.
- How do you handle changing requirements?
- Two-week increments with a demo at the end of each. Change is expected; what we protect against is change nobody costed. Scope changes get an estimate before they get built.
- Will you rescue a project another agency started?
- Often. We begin with an audit and an honest recommendation on whether to continue or restart. Sometimes restarting is cheaper, and sometimes it only looks that way to the firm who would be paid to do it.
Tell us what’s breaking.
Thirty minutes, no deck. We’ll tell you whether this is the right place to start.

