Skip to content

Custom software costs the hours of skilled work it takes. Agentic development has cut those hours, so older quotes are a poor guide. Here is what drives cost now.

Custom Software Development14 min read

Custom software costs the hours of skilled work it takes, multiplied by the rates of the people doing it, plus an allowance for what is still unknown when the work starts. That has always been true. What has changed in the last two years is the number of hours. Agentic development, where AI agents draft the design, the code, the tests and the documentation and engineers review and approve every step, has cut the effort a build needs.

So the useful question is no longer what software used to cost, but what it should cost when it is built this way. This guide explains what drives the cost of custom software, where AI agents save effort and where they do not, and how to tell whether a quote reflects the way software is built now. Where it uses figures from outside IT Magnet, it names the source.

What you are paying for

Every estimate for custom software is a number of hours multiplied by the rate for each role, from the developers and testers who build it to the architect and project manager who keep it on track. Rates follow salaries. In Sydney, Robert Half's 2026 salary guide puts the median starting salary for a software developer at $109,000 and for a solutions architect at $190,750, before superannuation, and an employer adds superannuation, payroll tax, leave and equipment on top.

Sydney salaries for the people who build software, 2026Starting base salaries in Sydney from the 25th to the 75th percentile, excluding superannuation and bonuses.
  • Software developer$92,650 to $130,800
  • Senior developer (.NET)$147,150 to $168,950
  • Solutions architect$179,850 to $212,550

Source: Robert Half 2026 Salary Guide, Sydney figures for software developer, senior .NET developer and solutions architect.

Rates have not fallen, and experienced engineers are worth more than ever, because they are the ones who decide what the agents build and check what they produce. What has fallen is the number of hours those people need to spend drafting.

How agentic development changes the cost

IT Magnet builds with its own AI agents for design, coding and review, each working inside a human in the loop process. A design agent turns an agreed specification into wireframes and working prototypes in days rather than weeks. Coding agents draft features, integration code and data scripts against the specification and the existing code. A review agent checks every change against our standards, the tests and known security vulnerabilities, and then a senior engineer reviews and approves it before anything ships.

The speed comes out of the drafting, not out of the checks that follow it. That distinction matters, because the saving is real only where the agents take over work that is well defined, and the review is what keeps the result secure and maintainable.

Where agentic development saves effort
StageWhat the agents doWhat people still doEffort saved
Discovery and specificationSummarise workshops, draft user stories and acceptance criteriaDecide what to build, agree priorities and sign offSmall
Design and prototypesTurn the specification into wireframes and working prototypesTest them with users and choose the directionLarge
DevelopmentDraft features, integration code and data scriptsSet the architecture, solve the hard problems, review every changeLarge
Code review and securityCheck every change against standards, tests and known vulnerabilitiesA senior engineer approves before anything shipsModerate
TestingWrite and run test cases, including the edge cases people forgetAcceptance testing with your teamModerate
DocumentationKeep architecture notes and API references current with every changeCheck they are rightLarge
Integrations and data migrationRead the other system's documentation and draft mappingsWork with that system's owners and resolve data problemsSmall
Project managementDraft status reports and release notesMake decisions, set priorities, talk to stakeholdersSmall

The pattern is clear in our own projects. Work that is well defined and checkable gets much faster. Work that depends on people, decisions and other organisations gets only a little faster, and on many projects that is where most of the time goes.

Why AI tools alone do not cut the cost

Giving developers an AI assistant is not the same as building with agents, and the research shows why. In a controlled experiment by GitHub and Microsoft researchers, developers using Copilot built a small web server 55.8 percent faster than those without it. But in a 2025 trial by the research group METR, experienced developers working on large codebases they already knew took 19 percent longer with AI tools, even though they expected to be 24 percent faster and afterwards believed they had been 20 percent faster.

Time to finish a task with AI tools, compared with working without themTask time with AI tools as a share of the time taken without them, where 100 percent means no change.
  • New, well defined task (Copilot study)44% of the time
  • Experienced developers' forecast (METR)76% of the time
  • Their estimate afterwards (METR)80% of the time
  • Measured on mature code (METR)119% of the time

Sources: Peng and others, 2023; Becker and others, METR, 2025. METR studied tools from early 2025.

Our reading of these results matches what we see. AI saves the most on new, clearly specified work and the least when a person is fitting changes into a large system the tool does not understand. That is why our process puts the effort into the specification first, gives each agent a narrow job, and keeps a senior engineer reviewing every change. The tools have also improved a great deal since early 2025, but the lesson about process still holds.

What moves the cost

Two projects with the same number of screens can still differ greatly in cost. These are the things that make the difference, roughly in order of how much they move an estimate, and most of them are the kind of work agents speed up least.

  • Integrations: every system the software talks to, such as an ERP, payments, a POS or a government API, has to be understood, built against and tested
  • Data migration: moving years of records out of spreadsheets or an old system is often a project of its own
  • Security and compliance: government work to the Information Security Manual, privacy obligations, penetration testing and audit logging all add effort
  • Platforms: a web app, an iPhone app and an Android app are three things to build, test and maintain
  • User types and workflows: each role with its own screens, permissions and approvals multiplies the work
  • Unknowns: the less is settled before the build starts, the wider the estimate has to be
What drives the cost of common types of project
Type of projectWhat it usually involvesWhat drives the cost most
Integration between two systemsMoving data between, say, a CRM and an accounting system, with error handling and monitoringThe quality of the other systems' interfaces and data
Internal workflow toolReplacing a spreadsheet or paper process for one team, with approvals and reportingHow many exceptions the process really has
Mobile app with a backendAn iPhone and Android app with its own API and an admin portalOffline use, payments and app store requirements
Customer or partner portalSecure sign in, self service, documents and integration with internal systemsHow many internal systems it reads from and writes to
Business systemA CRM, job or operations system replacing several toolsData migration and the number of roles and workflows
Platform with many integrationsSeveral user types, devices or IoT, heavy compliance and national scaleIntegrations, compliance and staged delivery

The unknowns are why an honest early estimate is a range. Until someone has looked at your data, your integrations and the way your team actually works, nobody can price the job precisely. A short discovery turns the range into a fixed price.

How to tell if a quote reflects how software is built now

Quotes differ because they are rarely quoting the same thing. One includes discovery, testing, project management and a warranty period, another assumes you will test it yourself. One is fixed price with the risk priced in, another is time and materials with the risk left with you. And now one may be priced on agentic development while another is priced on the hours the same work took a few years ago.

Compare quotes by their hours and assumptions, not their bottom line. Ask:

  • How many hours does the estimate assume for each stage and role?
  • How do you use AI agents in the build, and how is their work reviewed before it ships?
  • What is included: discovery, design, testing, project management, deployment, warranty?
  • What assumptions is the price based on, and what happens if one proves wrong?
  • Is the price fixed, and if so, for which stage of the work?
  • Who owns the source code, and is it held in your organisation's own repository?

Be as wary of a quote that is suspiciously low as of one that has not moved in years. Agentic development cuts drafting, not review. If a quote has no time for senior review, testing and security scanning, the saving has come out of the checks.

Budget for after launch

Software keeps costing once it is live. Hosting and licences, monitoring, security patches, the yearly updates Apple and Google require for store apps, support when something breaks, and the improvements your team will ask for once they use it. Plan for a support arrangement and hosting as a monthly cost, and treat larger improvements as their own projects. Documentation that agents keep current with every change also makes later work, and any future handover, cheaper.

You will often see maintenance quoted as a fixed share of the build cost each year. We could not find a primary source for that rule of thumb, and in our experience the real cost depends far more on how much the system keeps changing than on what it cost to build.

Can the R&D Tax Incentive reduce the cost?

Sometimes, but less often than many businesses hope. The R&D Tax Incentive supports experimental work to resolve genuine technical uncertainty, where the outcome could not be known in advance. Building a portal or business system with established tools usually does not qualify, while developing a new algorithm or a technique nobody has proven may. The government announced changes in the 2026-27 Budget that start on 1 July 2028, and the current rules apply until then. Talk to your accountant or an R&D tax adviser before you count on it.

How to keep the cost under control

Overruns are common. A study of 1,471 IT projects by Bent Flyvbjerg and Alexander Budzier of the University of Oxford found an average cost overrun of 27 percent, and one project in six overran by an average of 200 percent. Faster drafting does not change the habits that keep a project on budget.

  • Pay for discovery first, so the build is priced from a specification rather than a guess
  • Fix the price one stage at a time, so a surprise in stage two does not reprice the whole project
  • Build the smallest version that delivers value, then add to it
  • See working software every two weeks, so problems surface while they are cheap to fix
  • Put every change through one written process with its cost agreed before work starts

What we would do

Start with a short discovery that produces a specification, a working prototype of the parts people will use and an estimate by stage. With agentic development the prototype comes early enough to test the idea before you commit to the build. Then fix the price for the first stage, keep a contingency for what discovery could not settle, and set aside a monthly budget for running the software once it is live. It is how we run every custom software project.

Questions about custom software costs

  • It costs the hours of skilled work the project needs, multiplied by the rates of the people doing it, so it depends on scope, integrations, data migration and compliance. Agentic development has cut the hours a build takes, so prices from a few years ago are a poor guide. A short discovery that ends in a fixed price for the first stage is the reliable way to get a figure.

  • Yes, where it is built into the process. AI agents now draft much of the design, code, tests and documentation, and engineers review and approve the work, which cuts the hours a build needs. Research shows AI tools on their own do not guarantee savings, so the gain depends on clear specifications and disciplined review.

  • It depends on what the app does, whether it runs on both iPhone and Android, and what it connects to. Payments, offline use, integrations with other systems and the yearly updates the app stores require all add to the cost. Agentic development has shortened the build, and a working prototype early on lets you test the idea before committing to the full app.

  • Because it is mostly skilled time, and Australian salaries for developers and architects start at around $90,000 and pass $200,000 a year. Agentic development has reduced the hours, but people still decide what to build, design the architecture, review every change and handle integrations. The cost buys software that fits your process exactly and that you own.

  • Not usually to start with. Off the shelf software is cheaper to begin with, but licence fees grow with every user and you adapt your process to the product. Custom software costs more up front and less per user, and it suits processes that set your business apart or that no product handles well.

  • Less time than it used to. With agentic development a working prototype can be ready in days rather than weeks, and builds move faster because agents draft much of the code, tests and documentation. Integrations, data migration and decisions still set the pace, so a short discovery stage gives a firm timeline for the build.

  • A complete quote shows the hours for each stage and role, what is included (discovery, design, development, testing, project management, deployment and warranty), how AI is used and reviewed, the assumptions behind the price, and what support and hosting will cost after launch. It should also confirm that you own the source code.

  • The hourly rate is lower, but the total cost is closer than the rates suggest once you add time zone delays, more management effort and rework. Agentic development has also narrowed the gap, because it cuts the drafting hours that cheaper rates used to save. Offshore rates do not buy Australian data residency or legal protections.

  • Only the experimental part, where the work resolves genuine technical uncertainty that could not be settled in advance. Building software with established tools and methods usually does not qualify. Get advice from your accountant or an R&D tax adviser before relying on it.

  • A fixed price suits work that is well defined, usually after a discovery stage has produced a specification. Time and materials suits exploratory work where the scope will change. Many projects use both: time and materials for discovery, then a fixed price for each stage of the build.

All insights