Fixed Price vs Hourly Software Projects

Understand what each model covers

• Fixed priceYou agree on a price for a defined piece of work. The description of that work establishes what is included.
• HourlyYou pay for the agreed time spent on the project. Priorities, progress reports and spending limits help you manage the total.

The scope is the written description of what will be delivered. It might cover a quoting tool, a customer portal or one stage of a larger project. A clear scope helps under either model.

A price should also say how planning, testing, meetings and launch work are charged. This makes it easier to compare proposals without guessing what the headline figure leaves out.

Use fixed price for work you can describe clearly

Fixed price can suit a first release when the main tasks, rules and connections are understood. You know the agreed build price before work starts, and can plan payments around dates or completed stages.

For example, a quote tool could have agreed inputs, pricing rules, a document layout and a way to save revisions. Try sample quotes together before treating that description as complete.

Ask what happens if a detail turns out differently from an assumption in the proposal. A useful agreement makes the next conversation clear instead of leaving either side to guess.

Use hourly work with an agreed limit and review point

Hourly work can suit an investigation, ongoing improvements or a project where priorities are likely to change. For example, a developer may need to inspect an old system before knowing what a replacement involves.

An estimate of the likely hours is not necessarily a spending limit. Agree on the amount that can be spent, when you will receive an update and whether work pauses before that amount is exceeded.

Work to start with

Describe the immediate task and what the developer should report back when it is finished.

Rate and reporting

Confirm the rate, which activities are charged and how you will see time used and work completed.

Spending limit

Agree on a limit and an earlier notification point so you have time to decide what happens next.

Further approval

Name the person who can approve more work, and record that approval before the limit is increased.

Distinguish a correction from a new request

• The agreed calculation is wrongA quote applies a different discount from the written pricing rule. Compare the result with the agreement and review the correction under the agreed fix arrangements.
• You want an additional featureThe quote already works, but customers should now be able to approve it through a new online portal. Ask for the extra work and its effect on price and dates to be explained.

Changes are normal as you see the software taking shape. Keep a record of the request, whether it is already covered and what decision was made.

You can approve additional work, keep it for later or discuss replacing another planned feature. The important part is agreeing on the revised work and cost before it proceeds.

Combine models when that suits the work

You can commission a limited planning or investigation stage, then request a fixed price for the build once the unknowns are clearer. The planning stage can itself have a fixed price or a capped hourly budget.

Agree on what that stage produces, such as a description of the first release, sample screens or a checked integration approach. You should be able to use the result to decide whether to continue.

After launch, you may prefer defined prices for larger additions and hourly help for occasional small changes. These are choices to discuss, not commitments you need to make for every future task.

Keep progress visible under either arrangement

Ask to see working software at agreed points, with time to provide feedback. A payment schedule tells you when money is due; demonstrations help you understand what is being delivered.

The guide to development reviews explains how to prepare for demonstrations, try realistic tasks and record useful feedback.

Your next step

Before approving the next stage, make sure you can explain what will be delivered, how it is charged, when payments are due and who must approve a change. If any answer is unclear, ask for it to be written into the project agreement.