Custom software
Web apps, internal tools, platforms, APIs and MCP servers, built around how your organisation works.
What we build
Custom software is software made for one organisation’s way of working, instead of bending your process to fit an off-the-shelf product. Below is what each kind is, and when it tends to make sense.
Web apps
A web app is software you use in a browser, with logins, data and screens designed for a specific job. Nothing to install.
You might want one when a spreadsheet or a shared inbox has become the system, and several people need to work from the same up-to-date record.
Internal tools
An internal tool is software for your own staff rather than your customers: an admin screen, a review queue, a reporting page, a simple back office.
You might want one when the team repeats the same steps by hand across several systems, and a small, focused tool would remove the copying.
Platforms
A platform is a larger product with several parts that work together, such as accounts, a database, user roles, and an API or integrations on the side. It is meant to grow over time.
You might want one when you are launching a product, or when separate tools need to become one system. We built Casen, an AI platform designed for MARA-registered migration agents in Australia. You can read about it in our work.
APIs
An API is a way for one piece of software to talk to another in a defined, documented way. It lets your systems share data without anyone re-typing it.
You might want one when other software, a partner or a mobile app needs to read from or write to your data, or when two systems you already use need to be connected.
MCP servers
An MCP server lets an AI assistant, such as Claude, use your software and data through a defined set of actions. You decide what the assistant may see and do.
You might want one when your team already works with an AI assistant and you want it to look up or update records in your own systems, instead of copying information in and out.
How the work runs
1
Scope
We start by working out what the software needs to do, and what is out of scope. Nothing is built until we agree on that.
2
Build
We build in small steps and show you working software in a demo each week, so you can correct course early.
3
Handover
You get the code, the documentation and a walkthrough, so your team can run it.
More on how we work.
Tell us what you need built.
Send a short note on the problem and who it affects, and we will reply by email.