Fixed-Price vs Hourly Software Development: What Costs Less?

You have two quotes for the same AI or software project. One says $9,000 fixed. The other says $140 an hour, "probably 40 to 60 hours". They look similar until you notice that only one of them tells you what you will actually pay, and only one of them says what you get at the end.

Short answer: Fixed-price software development usually costs a small business less overall when the job can be described in writing, such as an AI chatbot, a booking system or a quoting tool, because the builder carries the risk of overruns. Hourly suits work that is genuinely uncertain. The best pattern for most projects is a short discovery to pin down scope, then a fixed price to build it.

What is the real difference between fixed price and hourly?

The difference is who carries the risk of the job taking longer than expected. On a fixed price, the builder does: if it takes four weeks instead of two, that is their problem. On an hourly rate (often called time and materials), you do: every surprise is billed.

That one fact explains most of what you will see in quotes:

• Fixed-price quotes look higher than the low end of an hourly estimate, because the builder has priced in some contingency for the unknowns. You are paying for certainty.
• Hourly estimates look lower because the range is anchored on things going well. They rarely include the integration that turns out to be harder than expected, the API that needs a workaround, or the rework after the first round of testing.
• Fixed price forces clarity up front. To quote a fixed price, the builder has to write down what they are building. That document is worth having even if you never sign.

Which pricing model suits which kind of project?

There are more than two options, and the right one depends on how well you can describe the job.

Model	How you pay	Who carries overrun risk	Suits
Fixed price	One agreed amount, usually in milestones	The builder	A defined outcome: chatbot, booking system, quoting tool, integration
Hourly (time and materials)	Hours worked, billed weekly or monthly	You	Exploratory work, unclear requirements, ongoing small changes
Capped hourly	Hours worked, up to an agreed ceiling	Shared	Mostly known work with one or two open questions
Paid discovery, then fixed	A small fixed fee to scope, then a fixed build price	The builder, once scoped	Anything you can describe the outcome of but not the detail
Retainer	A monthly amount for a block of time	You	Continuous improvement after launch

Most small business AI and custom software projects are better described than owners think. "When someone enquires on our website after hours, an AI should answer from our price list, book them into ServiceM8 and text us the details" is a scope. It can be fixed-priced.

When is hourly the better deal?

Hourly is the better deal when nobody can honestly describe the outcome yet. Three cases:

1. You are exploring. "AI could probably help us, but where?" is a discovery question, not a build. A few paid hours to map the opportunities is sensible. A workflow audit does this job too.
2. The work is small and continuous. Tweaks to an existing system, a new report each month, a field added here and there. Fixed-pricing each one wastes everyone's time.
3. The technical risk is genuinely unknown. Connecting to an old system with no documentation, or testing whether an AI can read a particular kind of document reliably. A short, capped hourly spike answers the question; then fix-price the build.

The trap is using hourly for a well-defined job because the rate looked cheap. A "small chatbot project" at $150 an hour that runs to 60 hours is $9,000, the same as many fixed quotes, except you found out at the end.

What should a fixed-price software quote include?

A good fixed-price quote reads like a short specification, not a sales page. If any of the items below are missing, ask for them before you sign.

Caption: The exclusions list matters as much as the scope; it is where most disputes start.

• Scope in plain English. What the software does, step by step, from the user's side.
• Integrations by name. "Connects to Xero, Cliniko and Google Calendar", not "integrates with your systems".
• Acceptance criteria. How you will both know it is finished, for example "answers the 30 most common enquiries correctly in testing".
• Exclusions. What is not included. A quote with no exclusions is a quote that will be argued about.
• A variation process. How changes are priced if you want something new halfway through.
• Milestones. Payments tied to delivered work, not all money up front.
• Running costs. Hosting, AI usage and any third-party subscriptions, estimated per month.
• Ownership. Code, AI instructions, domains and hosting accounts in your business's name.
• A fix period. Bugs found in the first weeks after launch are fixed without a new invoice.

What does a fixed-price AI or software project actually cost?

Most small business AI integrations and custom software projects we scope land between $3,000 and $15,000 as a fixed price, depending on how many systems they connect and how much logic they carry. A single-channel AI enquiry agent sits at the lower end; a custom booking or quoting system connected to accounting and job software sits higher. These are estimates; your scope sets the number.

Running costs are separate and usually small: hosting under $50 a month, and AI usage roughly $20 to $200 a month depending on volume. Ask every builder to state these in the quote so you compare the full cost, not just the build.

How does a fixed-price project run from quote to launch?

A well-run fixed-price project has no surprises, because the surprises were dealt with before the price was set.

Caption: Weekly demos mean you see the thing working long before the final invoice.

1. Audit. We look at the workflow and what is costing you time or leads.
2. Scope and price. A written scope with integrations, exclusions and acceptance criteria, and one number.
3. Build. Most builds ship in two to four weeks, with a demo of working software each week.
4. Test and accept. The system is tested against your real data, such as past enquiries or last month's jobs, and you sign off against the acceptance criteria.
5. Launch, with a person in the loop. Anything outside the rules goes to a named staff member, and a fix period covers anything that turns up after launch.

The Kaladi Kitchens booking system is a good example of a scope that fixes well: members book kitchen time across several locations from one calendar, and complete photo-backed checklists at the start and end of every session. Each piece can be written down, tested and signed off.

How do I compare two quotes fairly?

Put them on the same basis before you compare the numbers:

1. Convert the hourly quote to a total using the top of its range, not the bottom, and add the cost of a round of changes.
2. Check both quotes cover the same integrations and the same exclusions.
3. Add 12 months of running costs to each.
4. Ask each builder who owns the code and the accounts at the end.
5. Ask what happens if it is not finished on time.

The answer to the last question tells you most of what you need to know about the builder.

If you are still deciding what to build, read chatbot platform vs custom AI agent and no-code or custom development first; the cheapest quote is the one for a project you did not need.

Frequently asked questions

Why is a fixed-price quote higher than an hourly estimate?

Because it includes the risk the hourly estimate leaves out. A builder quoting fixed has to price the integration that misbehaves and the extra round of testing; an hourly estimate assumes those will not happen and bills you if they do. Compare final totals, not headline numbers.

What happens if I want changes halfway through a fixed-price build?

You agree a variation: the builder prices the change, you approve it or drop it, and the rest of the scope stays fixed. Small changes are often absorbed; anything that adds a new screen, integration or rule is usually priced separately. A good quote explains this process before work starts.

Should I pay for a discovery phase?

Pay for it when the project is large or the requirements are fuzzy, and make sure you keep the output: a written scope you could take to any builder. For a small, well-defined automation, a free audit and a clear quote is usually enough.

Do fixed-price builders cut corners to stay in budget?

Some do, which is why acceptance criteria matter. If the quote says how the software will be tested and what "done" means, cutting corners shows up before you pay the final milestone. Weekly demos of working software are the other safeguard.

Want a fixed number for your project?

We price every build as a fixed-price project, and if your idea is too loose to fix-price yet, we will say so and suggest the smallest step that pins it down. Book a free AI workflow audit and leave with a clear scope and a number. If you go ahead, the audit fee comes off your first project.