Fixed price or hourly: buying software without surprises
Fixed price or hourly for custom software? When each one fits, how to handle change requests, and why a short first stage protects first-time buyers.
Fixed price suits work that can be described clearly before it starts, and hourly suits work that can't. For a first custom build, the safest route is usually a short first stage that ends in something you can judge, followed by a fixed price for the build once the scope is clear. Most budget surprises come from a vague scope and no agreed way to handle changes, whichever pricing model you pick.
What a fixed price actually fixes
A fixed-price project has a written scope, a price and a delivery date. If the work takes the builder longer than they estimated, that's their cost to carry, as long as you haven't changed what you asked for. That's the appeal. You know the number before you start.
The builder takes on the risk of a bad estimate, so the price includes a buffer for it. That's fair, and it means part of what you're paying for is certainty. A fixed price works best when the software can be described in detail up front, down to the screens, what each type of user can do, which systems it connects to and what counts as finished.
It works badly when the scope is vague. A one-page brief turned into a fixed quote after a single meeting leaves room for two honest people to disagree about what was included. Every gap then becomes an argument, and the builder has every reason to deliver the narrowest reading of the brief.
A good fixed-price contract protects both sides. It lists what will be delivered, says how each piece will be checked before it's accepted, and ties payments to working software you can try rather than to dates on a calendar. It also says plainly what isn't included, such as entering your content, moving data from your old system or app store fees, so those don't turn up later as surprises.
If two fixed quotes for the same scope are far apart, ask each builder what they assumed. The gap usually comes from different readings of the brief, and that conversation shows you exactly where the brief is unclear.
How hourly pricing works
With hourly pricing, often called time and materials, you pay for the hours the team actually works, at agreed rates. You get an estimate at the start, then regular reports of hours spent and work done. Rates often differ by role, so ask who will do the work and at what rate, and watch for hours from people you've never heard of.
The risk sits with you. If the work takes longer, you pay more. In return, there's no risk buffer built into the price, and you can change direction without renegotiating a contract each time.
Hourly work does need more attention from you. You, or someone you trust, should review progress every week or two and decide what comes next. Ask for the estimate as a range, with a low and a high figure, since a range tells you how sure the team is in a way a single number hides.
Good hourly arrangements have controls built in. Set a monthly cap that can't be exceeded without your written approval, and ask for weekly reports that show hours against specific pieces of work. Expect regular demos of working software. Keep the right to pause or stop at the end of any period.
When hourly is the better choice
Hourly is often the better choice, and there's no reason to avoid it by default. It suits work whose shape genuinely isn't known yet, such as connecting to an old system nobody has documented, or testing whether an idea will work at all. It suits ongoing improvement after launch, where the list of changes is decided month by month. And it suits small jobs, where writing a detailed fixed scope would take longer than doing the work.
It also suits buyers who have someone on their side able to manage a technical team's time, whether that's an in-house lead or an adviser they trust. Without that person, a first-time buyer usually gets more protection from a fixed scope.
Many projects end up using both. A fixed price covers a clearly defined first release, and hourly work or a monthly arrangement covers improvements once the software is in use. That way, each kind of work is priced in the way that suits it.
Remember the costs after launch, whichever model you choose. Hosting, updates, security fixes and small changes continue for as long as the software runs. Ask each builder what support costs each month and what it covers before you choose between them.
Changes are where budgets go wrong
Every software project changes along the way. You see the first version and realize your staff need an approval step. A customer asks for something you hadn't thought of, or your accountant wants a different export. That's normal, and it happens on almost every project once real people start using real software.
What matters is agreeing in advance how changes will be handled. Put it in the contract: how you request a change, how it's priced, who approves it on your side and what it does to the delivery date. Keep a simple change log that both sides can see, listing every change with its cost and its status.
Agree as well on the difference between a defect and a change. If something in the agreed scope doesn't work, fixing it is the builder's cost. If you want something different from what was agreed, that's a change, and it's yours to pay for. Clear acceptance criteria for each piece of work make that line much easier to draw when the moment comes.
Small changes are the ones to watch. Each one seems too minor to write down, and ten of them can add weeks. Log them all, even the ones you agree to absorb.
Two quotes for the same project
Say you need a booking and invoicing system for a field service company with twenty technicians, and two builders quote for the same written scope. The first offers a fixed price. The second works by the hour, estimates 480 hours, which comes to the same total, and agrees to a cap 10 percent above it.
Halfway through, you decide customers should get text reminders, and your accountant asks for a monthly export. On the fixed-price project, those are change requests, each quoted before work starts, and together they add about 7 percent. You approve both, and the project ends a little above the original price, with each addition agreed before anyone started on it.
On the hourly project, the same two changes take about 32 hours. But the original work also runs ten percent over the estimate, another 48 hours, so you reach the cap with one piece unfinished. Now you're negotiating.
Change the assumptions and the result flips. If the hourly team had come in under its estimate, it would have been the cheaper option. These numbers are made up, and neither outcome would be unusual. The real difference is who carries which risk, and how early you hear about it.
Start with a short stage you can judge
Whichever model you choose, begin with a short first stage of a couple of weeks that ends in something concrete. That might be a written scope with screens and a firm quote for the build, or a small working version of the most important part.
You learn how the team works, and they learn your business, before either side commits to the full project. If you don't like what you see, you stop, and you still have something you can take elsewhere.
Give the first stage its own short agreement, with its own price and date. Whatever it produces, whether a plan or a working version, should be yours to keep and use with any builder.
At eORB, every project starts with two weeks that end in a clear plan or a working first version, and you don't pay for a stage that isn't delivered by the written date.
Where to start
- Write a one-page description of what the software must do, who will use it and what it replaces. If you can't fill the page, you need a first stage before anyone can give you a fair fixed quote.
- Ask every builder you're considering how they price and approve changes, and get the answer in writing before you compare quotes.
- Ask for the first stage to be priced and dated separately, with a named result you can judge at the end of it.
Related
Opening a second location: what to set up before the doors open
Opening a second clinic, studio or shop? What to set up first: the Google listing, booking and phones across sites, shared systems and first customers.
Hire a marketing manager, or work with a team first?
When a growing business should hire a marketing manager and when to work with a team first, what a hire really costs, and how to make it work later.
How long should a custom build take before you see something real?
Buying a website, app or system? You should be using something real within weeks. What counts as real, a sensible timeline and the warning signs.
Tell us what should change first
Share your website. We review your business and contact you within one working day to arrange a short call.
Book a 30-minute callor write to hello@eorbsolutions.com