02 · Custom applications
Custom web applications, built for how you actually work
Every growing business reaches the point where the spreadsheet becomes a liability — the one file everybody edits, nobody backs up, and one person quietly understands. That is the point where a real application costs less than the workaround.
Who this is for
- Companies running operations out of a shared spreadsheet that has outgrown itself
- Teams paying for software that does 60% of what they need and blocks the other 40%
- Organisations on Microsoft 365 that want tools built where their data already lives
What is included
- Internal tools, client portals, dashboards and quoting or scheduling systems
- React and Node on the front, Azure, SQL or Dataverse behind it
- Authentication, roles and an audit trail built in from the start, not bolted on
- Microsoft Power Platform work — Power Apps, Dataverse, Power Automate — where that is the faster route
- Documentation and handover, so you are not dependent on one developer forever
How it works
- 01
Map the work
We watch how the job is done today, including the parts that only live in someone’s head.
- 02
Scope and price
A written scope with what is in, what is out, and a fixed price per phase.
- 03
Build in phases
Working software in front of you every two weeks. You change direction while it is still cheap.
- 04
Hand over
Deployed, documented, and yours — with support if you want it, not because you are stuck.
Questions
Scoped in phases, typically from $8,000. Fixed price per phase.
Is this cheaper than buying software?
Usually not upfront, and often cheaper over three years — especially at per-seat pricing across a growing team. The real argument for custom is fit: software you buy makes you work its way. If your process is your advantage, that matters.
What does it cost?
A focused internal tool typically starts around $8,000. Platforms with multiple user types and integrations run higher. We scope in phases so you can stop after phase one if it is enough.
Who maintains it afterwards?
You can, we can, or your next developer can. The code is documented and handed over. Retainers exist but are never a condition of getting your own software.
Can it connect to QuickBooks, Jobber, or what we already use?
If it has an API, generally yes. Integration is often the highest-value part of the build — it removes the double entry nobody enjoys.