Engineering
Custom Software Engineering
We design and ship real products — web applications, internal tools, and integrations — with the same operational bias we bring to a floor deployment. Typed end to end, instrumented, deployed on infrastructure we can debug at 2 a.m. See the products we run ourselves for the standard we hold.
- Scopes it runs at
- 3
- Steps in a job
- 3
- Deliverables
- 5
- Estimate
- $0
Scope
From a single tool to build-and-run
Most custom software is bought from people who will never operate it. That shows up later as an application nobody can deploy, a database nobody can migrate, and a handover that is a repository and a wish of luck. Software written by people who also get paged when infrastructure breaks tends to be software that can be run.
- 01
An internal tool
The spreadsheet that has outgrown itself, or a process that lives in somebody's head. Usually the highest return available.
- 02
A product build
A customer-facing application from discovery through launch, with a fixed first milestone before either side is committed.
- 03
Build and run
The same team keeping it monitored, patched and changed after launch, which is the option most studios leave off the menu.
How it runs
In the order the work happens
The sequence matters more than the list. Most of what goes wrong on these jobs traces back to a step skipped early rather than to the work itself.
- 01
Free discovery, and a fixed first milestone
The first conversation costs nothing, and the first piece of work is priced fixed. If it goes badly you have lost a known amount rather than an open-ended one.
- 02
Ship in units rather than against a timesheet
Work is quoted as defined pieces — accounts and permissions, a payments integration, an admin dashboard — at a published price. Whether one takes a day or a fortnight is our problem rather than a line on your invoice.
- 03
Hand over something that can be operated
Repository, accounts and domains in your name from the start, a documented deploy, and a runbook. Taking the keys and walking away is a supported outcome rather than an awkward one.
What you get
What is actually delivered
- Discovery, scoping, and a fixed first milestone
- Full-stack build in TypeScript, React, and Postgres
- Authentication, billing, and third-party integrations
- CI, observability, and deployment pipeline
- Handover documentation, or ongoing retainer
Not this
What we do not do here
Stating this is what makes the rest of the page worth believing, and it saves you a call that was never going to end in work.
- Staff augmentation — we take defined work rather than placing bodies into your team's backlog.
- Rescuing an actively burning codebase without an assessment first.
- Design-only engagements with no build attached.
Questions
Before you call
- Who owns the code?
- You do, from the first commit. The repository, the accounts and the domains are in your name rather than ours, which is what makes leaving a decision rather than a negotiation.
- What does it cost?
- Work is priced in fixed units at a published rate, and the estimator on the software page will give you an indicative range without an email gate. A real number follows a conversation.
Related
Usually bought alongside
- Field Services
Endpoint & Access Hardening
Close the gaps that an audit — or an incident — will find first.
- Infrastructure
Network & Telecom Infrastructure
Switching, structured cabling, and closets that a stranger can read at a glance.
Next step
Need Custom Software Engineering?
Free discovery and a fixed first milestone. Tell us what it has to do and we will tell you what it takes.
- Free diagnostics
- Same-day across most of the metro
- Named technicians
- No fix, no labour charge