01
New projects
A paragraph about the problem is enough to start. We reply within two working days, usually with questions rather than a quote.
Web2 · Service Custom web application development
Custom web applications in React, TypeScript and Node.js: internal tools, customer portals and dashboards, with tests, access control and a clean handover.
In short
A custom web application is software built around how your business actually works, instead of bending the business around a product that almost fits. We build internal tools, customer portals, dashboards and booking or ordering systems in React and TypeScript, with the API, database and hosting behind them, in a repository and cloud account you own.
- How to engage
- Product build, Dedicated engineering pod
- Practice
- Web2
Signs this is the right service
- A spreadsheet or a chain of emails is running a process the business now depends on.
- Off-the-shelf software covers most of the job, and the remaining part is where your work actually differs.
- Customers or partners need a portal for something they currently phone or email you about.
- An older application works but nobody wants to change it, and every new feature takes longer than the last.
What you get
Product design
User flows and clickable designs agreed before the build, so the first argument about a screen happens in a design file.
Front end
A React and TypeScript interface that is fast on a mid-range laptop, usable on a phone, and built to accessibility guidelines.
API and data model
Typed APIs on Node.js or Go over a Postgres schema designed for the reports you will want next year.
Access control
Sign-in, roles and permissions, single sign-on where your organisation uses it, and an audit trail for sensitive actions.
Tests and delivery
Automated tests, a preview environment for every change, and deployment that is a button rather than an event.
The process
- 01
Discovery
Two weeks to understand the process, the users and the systems it touches, ending in a written scope and a fixed quote.
- 02
Design the flows
The main journeys drawn and tested with the people who will use them, before the build starts.
- 03
Build in two-week cycles
A working demo against a live environment every two weeks, with each change reviewed by a second engineer.
- 04
Launch and hand over
Data migration, training, runbooks, and either a handover to your team or a team that stays on.
ReactTypeScriptNode.jsGoPostgreSQLAWSPlaywright
Custom web application development: common questions
Should we build custom software or buy a product?
- Buy when a product fits the process and the process is not what makes you different. Build when the software is the process, when licences cost more than a build over a few years, or when integration is the hard part. We will say so if buying is the better answer.
Can you take over an application another team built?
- Yes. We start with a short audit of the code, tests and infrastructure, so you know what you have before we change it.
How do you keep the scope under control?
- Discovery produces a written scope and a fixed quote. Any change after that is shown to you with its effect on time and cost before it is made.
Who hosts the application?
- It runs in your own cloud account, defined as code, so you are never dependent on us to keep it running.
06 / Let’s build
Bring us the difficult problem.
02
Careers
Engineers, designers and researchers who like systems that are hard to get right. Send something you built and what you would change about it now.
03
Studio
Based in India and working remotely, with overlap hours agreed up front so your team always has a time to reach us.
04
Read
Guides on AI agents, RAG, MCP, tokenization and chain abstraction, written by the engineers who build them.