Three years ago you asked for a quote on a custom system for your business and got a number with too many zeros and a timeline measured in quarters. You bought a subscription instead, and you have been bending your process around it ever since.
The cost of custom software in 2026 is a different conversation, and most owners have not had it yet. Agentic coding (AI tools that plan and write software under a developer’s direction) has cut the labor in the standard parts of a build to a fraction of what it was. Some vendors have passed that on. Some have not. A few are using the word “AI” to charge more.
This article is about what actually got cheaper, what did not, why, and how to buy custom software now so that you pay for the parts that still cost money and not for the parts that no longer do.
What this actually is
Custom software has always been priced on labor. A developer’s week costs what it costs, and a project was estimated in weeks of developer time. A modest internal tool for a business (a dispatch board, a quoting tool, a customer portal) commonly ran to several months of one or two people, which is how “six figures” became the normal answer.
Agentic coding changed the labor per feature. A developer describes a screen, a rule, or an integration in plain language, and an AI agent writes the code, runs the tests, and fixes its own errors, with the developer reading and correcting rather than typing. We explain the mechanics in Agentic Coding Explained for Business Owners in 2026. The result is that the typing-heavy majority of a project now takes a small fraction of the time it did.
The analogy is a print shop after digital presses. Setting type by hand was the cost. Once it was not, the price of a print run fell hard, but the price of good design, proofreading, and knowing what the customer actually wanted printed did not move at all. Those became the whole job. The same is true here.
What got cheaper, what did not, and how to buy accordingly
1. Standard screens, forms, and reports got very cheap
Every business system is mostly the same fifty things: log in, list records, filter and sort, open one, edit it, save it, export it, email a notification, print a PDF. An agent produces these quickly and, when given a clear description, correctly. This was the bulk of the old estimate, and it is where most of the savings are.
The buying consequence: a quote that still prices these at the 2022 rate is either from a shop that has not adopted the tools or one that hopes you have not noticed. It is fair to ask a vendor how they build and to expect the standard parts of a scope to be priced in days, not weeks.
2. Understanding your business did not get cheaper
The agent does not know that your dispatchers reschedule by dragging, that “net 30” means something different for your top five accounts, or that the sales team’s “closed” and the accounting team’s “closed” are different events. Somebody has to find that out by asking, watching, and writing it down. This is discovery, it is done by a person, and it takes about as long as it ever did for a given size of problem.
It is also where projects fail. Fast software built on a wrong understanding is expensive in a new way: it arrives quickly, is wrong quickly, and gets rebuilt quickly, and every rebuild costs you attention. Pay for discovery, insist on a written scope that comes out of it, and treat that document as the most valuable thing produced in the first two weeks.
3. Integration is still the expensive middle
Connecting to QuickBooks, your phone system, your industry’s scheduling software, or a supplier’s ordering portal is where time still goes. The code is fast to write. What is slow is everything around it: getting credentials, reading another vendor’s documentation (or discovering there is none), finding that their “customer ID” is your “account number,” handling the day their system is down, and testing against the real account without breaking anything. None of that is typing.
Budget for integration by the number and awkwardness of the systems involved, not by the number of screens. Three integrations with well-documented services like Stripe, Twilio, and a modern accounting platform are a known quantity. One integration with a fifteen-year-old industry system with no documentation can cost more than the rest of the project.
4. Review, testing, and security are where the senior engineer’s time goes now
Agents make confident mistakes: a permission check missing on one screen, a total that rounds the wrong way, a payment that can be submitted twice. The safeguard is a senior engineer reading every change, and automated tests that run on every change so that a fix in one place cannot silently break another. That review time is real, it is skilled, and it is not something to cut.
A vendor whose price is low because review is thin has moved the cost onto you, to be paid later in a failure. In our practice, review is a named line in every scope and nothing reaches a customer’s system without a senior engineer having read it.
5. Ownership is worth paying for and should not cost extra
Because building got cheap, a new pricing model appeared: the vendor keeps the code on their platform and charges you monthly to use your own software. It looks inexpensive up front and is a lease on something you should own.
The right structure has not changed. The code lives in a repository in your account. The hosting is in your account. The notes and tests come with it. Any competent developer can pick it up. A vendor who resists this is pricing in a future they intend to keep you in. The checklist for this conversation is in How to Hire an AI Consultant Without Getting Burned.
6. Small scopes and early demonstrations are now the sensible way to buy
When a build took a season, you had to specify everything up front and hope. Now a first working piece can exist in days. That changes the shape of a good engagement: a short discovery, a written scope, a fixed price for a first useful piece, and a real demonstration before you commit further.
This is also your protection against the vendors who have not changed. Ask for the smallest useful piece first, at a fixed price. What arrives, and how long it took, tells you everything about how they work.
7. Maintenance got cheaper, but it did not go away
Software needs attention after delivery: a connected service changes its behavior, a library needs a security update, your business changes a rule. Agents make these changes faster to implement, and a well-documented codebase with tests makes them safe to implement. What does not change is that someone has to notice and decide.
Plan for a small, regular amount of a competent person’s time rather than a large support contract. The practices that keep a system from breaking quietly are in Automation Error Handling for Businesses Tired of Silent Failures.
8. Some things you should still buy off the shelf
Cheaper custom software does not make every subscription a mistake. Accounting, payroll, email, and document storage are solved problems with compliance obligations attached; do not have them rebuilt. The case for custom has strengthened where a subscription forces your process into someone else’s shape, where you are paying per seat for something simple, or where two systems need to be joined in a way no vendor offers. The decision rules are in Build vs Buy AI Tools for Your Business, the Decision Rules.
Picture a business like this one
The business below is a composite of the kind of company that writes to us, not a client. The numbers describe the shape of the problem, not a case study.
Picture a business like this one: a commercial cleaning company with 80 staff and about 200 client sites. Scheduling lives in a subscription product that charges per user, which means only three office staff have logins and supervisors phone in changes. Inspections are done on paper and photographed. Invoicing is re-keyed into QuickBooks from a spreadsheet at month end. The owner priced a custom system in 2022 and was quoted well into six figures.
A company like this, buying in 2026, would go through something like:
- A one-week discovery with the scheduler, two supervisors, and the bookkeeper, ending in a written scope of a few pages: sites, shifts, the rules for cover when someone calls in sick, what an inspection must capture, and what QuickBooks needs to receive.
- A first fixed-price piece: the schedule itself, with a phone view for every supervisor, built mostly by agents and reviewed by a senior engineer. Live and in use within a few weeks.
- A second piece: inspections on the phone with photos, feeding a per-site report.
- A third: month-end invoicing generated from the completed shifts and pushed to QuickBooks, tested against a copy of the real books before it touches them.
- All of it in the company’s own repository and hosting accounts, with tests and notes.
The standard screens are the cheap part. The scheduling rules and the QuickBooks work are where the engineer’s time goes. The total is a fraction of the 2022 quote, the per-user subscription is cancelled, and every supervisor has the system in their pocket.
What it costs to run
The building cost is the part that moved. The running cost is much as it has always been for a small business system, and it is modest.
Hosting a small web application typically costs somewhere between $10 and $50 a month for a server or hosting plan, with a managed database in a similar range if you want one. Services the software talks to bill on their own terms: text messages through Twilio are priced per message, transactional email through Postmark or Resend is often free or a few dollars a month at low volume, and card payments through Stripe are a percentage of each transaction. Check the current pricing pages; these move.
If the software has AI features inside it (summaries, drafts, classification), there is a usage cost for the model, which for most small business tools is tens of dollars a month rather than hundreds; we break it down in AI Cost for Small Business, What It Really Costs to Run in 2026. Add a few hours a month of a competent person’s attention, and that is the whole running bill.
The mistakes we see most
Paying 2022 prices for 2026 work. If the standard screens are priced by the week, ask how the vendor builds and get a second quote.
Being charged more because it says “AI.” Agentic coding should make the labor line smaller. A vendor who prices it as a premium has it backwards.
Skipping discovery because building is fast. Speed makes a wrong scope cheaper to build and more expensive to live with. Pay for the week of asking questions.
Underestimating the awkward integration. One undocumented legacy system can outweigh the rest of the scope. Have the vendor investigate it before quoting.
Renting your own software. Monthly fees to use code you paid to build, on a platform you cannot leave, is the new lock-in. Own the repository.
Buying the whole thing at once. A fixed-price first piece, delivered and demonstrated, is the cheapest due diligence available.
When to bring in help
Some owners now build small tools themselves with Claude Code, Cursor, or an app builder like Lovable, and for a personal utility or a prototype that is a fine use of an afternoon. If the tool touches nothing important and you can afford for it to be wrong, go ahead.
The judgment parts, understanding the business, catching the agent’s mistakes, connecting to real systems safely, and structuring ownership, are why a senior engineer is still the difference between software you rely on and software you apologize for. Those are the parts you are paying for now, and they are worth it.
Levelbrook builds custom web apps, automations, and AI systems for businesses using agentic coding with senior-engineer review, at a fixed price from a written scope, with everything delivered into accounts you own. If you were quoted six figures in 2022 and never went ahead, the form below is how a new conversation starts.