Fixed Price or Hourly? How Software and Web Projects Are Priced

When a developer sends a quote, the number matters less than the model behind it. A fixed price, an hourly rate and a monthly retainer all have different risks, and each suits a different kind of project. Understanding the difference helps you compare quotes properly and avoid a nasty surprise halfway through the work.

For general budgeting figures, see what a business website costs in South Africa and what a custom business system costs.

The three common pricing models

Model	You pay	Who carries the risk	Best for
Fixed price	An agreed total for an agreed scope	The developer, if the work takes longer	Clear, well-defined projects
Hourly (time and materials)	For each hour worked	You, if the work takes longer	Unclear or changing requirements
Retainer	A fixed monthly amount for a set of hours or services	Shared	Ongoing work and support

Fixed price

You and the developer agree exactly what will be delivered and exactly what it costs. This is how we price our website plans, which start at R6,500 for a Starter Site and R18,000 for a Business Site.

Advantages:

• You know the cost before you start.
• The developer is motivated to work efficiently.
• It is easy to compare quotes.

Risks:

• The price is only as good as the scope. If the scope is vague, expect arguments later.
• Changes cost extra. If you add features mid-project, they are quoted separately. That is fair, but only if it is clear up front.
• A very low fixed price can mean corners cut or hidden extras.

What to check: a written list of pages, features and deliverables, what is excluded, how many rounds of revisions are included, and how change requests are handled. Our guide on how to brief a software developer helps you write a scope that holds up.

Hourly or time and materials

You pay for the hours actually worked, at an agreed rate, often with a monthly report.

Advantages:

• It is flexible. You can change direction without renegotiating.
• It is fair when nobody can know the scope at the start, such as research-heavy or exploratory work.
• You only pay for the work done.

Risks:

• The final cost is unknown, and can exceed expectations.
• There is little incentive to finish quickly.
• It is hard to compare with fixed quotes.

What to check: the hourly rate, whether there is a cap or estimate, how often you receive time reports, and who approves extra hours. Without a cap, an hourly project can run away from you.

Retainer

You pay a fixed monthly fee for an agreed amount of time or a defined service.

Advantages:

• Predictable budget.
• Priority access to your developer.
• Good for maintenance, small improvements and support.

Risks:

• Unused hours may expire, so you pay for time you do not use.
• It can become a way to avoid decisions about priorities.

Our hosting and care plans work like a light retainer. See website hosting and care plan costs in rands.

Which model suits which project?

Fixed price suits a brochure website, a store with a known product count, or a single-purpose workflow tool. The scope is clear and a written quote protects both sides.

Hourly suits investigation, a problem nobody has diagnosed, or a project where you genuinely do not know what you need yet.

Phased fixed price suits larger systems. You split the project into phases, such as discovery, a first working version and extensions, and fix the price of each phase. This is how we handle larger platforms. You get cost certainty for the next step without committing to the whole journey.

Retainer suits what comes after launch: updates, content changes, minor features and support.

How discovery turns a vague idea into a fixed price

The reason many software projects go over budget is not bad estimating. It is skipped planning. A discovery workshop is a short, focused piece of work where the developer learns how your business operates, maps the process and writes down what the system must do.

For our custom system projects, we run a paid discovery workshop first. It produces a written scope and a fixed quote, and the workshop fee is credited to the build if you proceed. If you decide not to, you keep the document and can use it with anyone. Preparing beforehand helps, so read how to document business processes before building software.

Red flags in any quote

• A single line with a single number. Ask for a breakdown.
• No mention of what is excluded. What you do not get matters as much as what you do.
• "Unlimited revisions." It sounds generous and usually means an unclear end point.
• A price far below everyone else's. Ask what is missing.
• No payment milestones. A deposit and staged payments tied to delivery protect you.
• No clarity on ownership. You should own your code, design and content when you have paid. See how to choose a web developer in South Africa.

How to manage scope changes

Changes are normal. What matters is how they are handled:

1. Write the change down.
2. Get a price and a time impact before work starts.
3. Approve it in writing.
4. Update the scope document.

This habit protects both sides. It stops the slow growth of "just one more thing" that quietly doubles a project.

Our approach

We prefer fixed prices wherever the scope allows, because it gives you cost certainty. Our plans on the pricing section show starting prices. When a project is uncertain, we use discovery to remove the uncertainty first, then fix the price. You always see the number before we start the work.

Choosing for yourself

Ask three questions:

1. How clear is the scope? Clear: fixed price. Unclear: discovery first, or hourly with a cap.
2. How much cost certainty do I need? A lot: fixed price. Some flexibility: hourly with estimates.
3. Is the work ongoing? Yes: a retainer for the long term.

If you are not sure, talk to us. We will tell you which model fits, and why.