Custom Software Development
Systems that fit how your business actually runs, built from the ground up.
Learn more →A free 30-minute assessment to find where AI would save your team time, then fixed-price builds and an ongoing retainer to put it to work.
Answer a few questions about where your team loses time or money. A senior developer reads them before your free 30-minute call.
A call about your bottlenecks, the tools you use and the hours involved, followed by a short written summary of what is worth doing and what is not.
The tasks where AI can work reliably, ranked by time saved against cost to build and run, so the first build is the one that pays back fastest.
The first feature built into your existing software, so it shows up in the workflow rather than as another tab to check.
Question-and-answer and search across your own documents and records, with answers that cite where they came from.
Checks on the output and a way for staff to correct it, with logging so you can see what the system did and why.
Monitoring, tuning and new workflows month by month, with usage cost and model choice managed as better or cheaper options appear.
Each step stands on its own. You can stop after any of them and keep what you paid for.
A 30-minute call about where time goes in your business. You get a short written summary of the opportunities and our view on which one to do first.
For anything bigger than a small feature, a fixed-fee Discovery produces the written scope and a fixed quote. It is credited against the build if you build with us.
One narrow feature, built into your existing systems at a fixed price, with a person kept in the loop on anything that carries risk.
Optional. We keep the feature running, tune it, and add the next workflow when the first has proven its value.
It is a working conversation with a senior developer, not a sales pitch. We would rather tell you AI is the wrong tool than sell you a build that does not pay back.
The task that eats the most hours, how often it happens, which tools it touches, who does it today and what a mistake costs.
A written summary of the best opportunities, a rough cost to build and run the first one, and a plain recommendation on whether to proceed.
Small and mid-sized Australian businesses with a repeatable process that takes staff time: admin, enquiries, quoting, document handling, reporting.
Businesses after an AI strategy deck, a chatbot for its own sake, or a general training session on ChatGPT.
AI pays off on specific tasks with clear inputs and outputs you can check. It is a poor choice when a plain rule would do the job, or when a wrong answer costs more than a slow one.
Sorting incoming email, drafting a first version of a document, pulling data out of PDFs and forms, checking submissions for errors, and answering questions across your own documents.
Decisions where nobody can check the output, tasks a simple rule already solves, and work where being wrong is expensive. In those cases we will say AI is not the answer.
| Rule or script | Smaller model | Large language model | |
|---|---|---|---|
| Best for | Fixed logic with clear conditions | Classifying and extracting from text | Drafting, summarising and answering questions |
| Running cost | Negligible | Low | Highest per use |
| Example | Send invoices over a set amount to approval | Tag incoming emails by topic | Draft a reply from a customer’s history |
| Checking the output | Predictable | Spot checks and thresholds | A person or a rule reviews it first |
Incoming email sorted, summarised and routed to the right person.
A first version of a report, quote or letter for a person to review.
Questions answered from your own records, with a citation to where each answer came from.
Fields pulled out of PDFs, forms and invoices into your system.
Submissions checked before a person spends time on them.
An AI feature inside the tools your team already uses, not another tab.
A retainer makes sense once a first build is running and there is a queue of further workflows worth doing. It is quoted individually after the assessment, because the right size depends on how much is running and how much you want added each month. The scope is agreed in writing before it starts.
The next bottleneck from the assessment, built and added once the previous one has proven its value.
We watch how often staff override the output and fix the prompts, data and rules behind it.
Usage cost tracked against the time saved, with the model swapped when a better or cheaper one fits.
What ran, what it cost, what staff corrected and what we recommend next, in plain English.
Anything that carries risk is reviewed by a person or checked by a rule before it takes effect.
You can see what the system did and why, so mistakes can be traced and fixed.
Business API tiers where your content is not retained for training, or models on infrastructure you control for sensitive material.
Built with the Australian Privacy Act in mind, with on-shore hosting in most cases.
The assessment is free. Builds land roughly between $5k and $100k+, depending on size, complexity and deliverables. A first, narrow feature is a small build, and you get a fixed price before we start. Running cost depends on volume and the model, and we estimate it up front.
| Project size | Typical cost | What it usually covers |
|---|---|---|
| Small | $5k–$10k | One narrow feature in one workflow, such as triage or extraction, with review |
| Medium | $10k–$30k | Several features, or search across your own documents, wired into your systems |
| Large | $30k–$100k+ | AI woven through a platform, with custom retrieval, evaluation and monitoring |
Larger builds start with a fixed-price Discovery, which is separate from the build cost. Retainers are quoted individually after the assessment. We usually add the feature to software you already run, see existing software. More on pricing in the FAQ.
If this sounds like your project, Discovery is the next step.Start with a fixed-price Discovery — you get the scope, the plan and the number before you commit.
See how Discovery works →We start with the work, not the technology. We learn where time goes and pick a task where the input is clear and the output can be checked, and where being slow today carries a real cost.
We try the plainest thing that could work first. Often a small, well-scoped feature beats an ambitious one, and sometimes the answer is not AI at all.
Senior developers build the feature into your existing system in short cycles, with a person kept in the loop on anything that carries risk.
After launch we watch how often staff override the output and what the feature costs to run, then tune the prompts and the data behind them and change the model if a better fit appears.
An honest starting point, not a fixed menu. We pick per project and tell you why.
Systems that fit how your business actually runs, built from the ground up.
Learn more →Your own platform, built to your process — not another off-the-shelf tool you have to bend around.
Learn more →Inherited something half-built or stalled? We take it over, tidy it up, and move it forward.
Learn more →Last updated