Fixed-Price Software Testing Projects | Agreed Scope & Cost Skip to main content
QAonTOP
Contact Us

One project. One price. Agreed before we start.

A fixed-price project is a testing engagement where the scope, deliverables, end date and price are agreed in writing before work begins. We retest fixes until the agreed criteria are met. If the scope changes, we re-estimate it and you approve it first. When the deliverables are handed over, the engagement ends.

Price
One price, agreed upfront
Scope
Agreed in writing first
Starts
Within a week
Retests
Until criteria are met
Scope changes
Re-estimated, approved first
Commitment
None after delivery

[ Is it right for you? ]

When a fixed-price project is the right choice

Fixed price works best when you can describe the work up front. If your testing needs are ongoing, another model will serve you better.

A good fit if…

  • You have one launch, migration, audit or release with a clear start and end
  • You need a known cost before you start, for example to get budget approved
  • You want a specialist test, such as security, performance or accessibility, without a long contract
  • You need a clear set of deliverables for stakeholders or auditors

[ Who does what ]

Clear responsibilities, written into the scope

Because the price is fixed, both sides need to know exactly what they’re signing up for.

Owned by

You

  • Share requirements, builds and access
  • Fix the bugs we report
  • Approve the scope, acceptance criteria and any change
  • Make the go-live decision
Shared

Together

  • Agree scope, deliverables, end date and acceptance criteria
  • Review findings as they come in
  • Agree any change request before work on it starts
Owned by

QAonTOP

  • Plan and run testing to the agreed scope
  • Report bugs with steps and evidence
  • Retest fixes until the criteria are met
  • Hand over every agreed deliverable

[ What’s fixed ]

Fixed from the start, with no surprises later

Five phases, run against the scope you approved. And if you need to change that scope, you’ll know the cost before anything changes.

  1. Phase 01

    Scope agreed

    Scope, deliverables, end date, acceptance criteria and price, agreed in writing.

  2. Phase 02

    Plan and set-up

    Test plan written and test environments set up.

  3. Phase 03

    Testing

    Testing runs against the plan, with bugs reported as they’re found.

  4. Phase 04

    Findings

    Every finding reported with steps to reproduce and evidence.

  5. Phase 05

    Retest and sign-off

    Fixes retested until criteria are met, then the final sign-off report.

Locked in when you approve the scope
  • The price
  • The scope and platforms
  • The deliverables
  • The end date
  • The acceptance criteria
If the scope changes
  1. 01You ask for a changeSomething new needs testing, or the scope needs to grow.
  2. 02We re-estimateWe tell you the extra time and price for the change.
  3. 03You approve it firstNo work on the change starts until you say yes.

The original price stays fixed for the original scope.

[ How it starts ]

From brief to kick-off in four steps

You know the price before any testing starts.

  1. Step 1 of 4

    Send your brief

    Tell us what needs testing, on which platforms and by when. An engineer replies the same working day.

  2. Step 2 of 4

    Agree the scope

    We clarify the details with you and turn them into a written scope, deliverables, end date and acceptance criteria.

  3. Step 3 of 4

    Get your fixed price

    One price for the agreed scope, confirmed before any work begins.

  4. Step 4 of 4

    Kick off

    Work starts within a week, and runs through the five project phases above.

[ Compare models ]

Fixed-price project, on-demand testing or a dedicated team?

The question to ask: is this a one-off piece of work, occasional testing, or something you need every sprint?

Fixed-price QA project compared with on-demand testing and a dedicated QA team
Compare onThis pageFixed-price projectCompareOn-demand testingCompareDedicated QA team
Best forLaunches, migrations, audits and one-off releasesIrregular releases, peak periods and extra capacity on top of a core teamProducts with continuous releases that need QA every sprint
PricingOne fixed price, agreed upfrontPer test cycle bookedMonthly, quote-based
CommitmentEnds at deliveryNo retainer3 months, then monthly
StartsWithin a weekIn 48–72 hoursEngineers join in 3–5 days
Who managesWe manage delivery against the agreed scopeWe run each cycle you bookQAonTOP, to your priorities

Need the full picture? Compare all six engagement models or find your model in four questions.

[ FAQ ]

Fixed-price project questions, answered

{{ f.a }}

[ Contact us ]

Get a fixed-price quote

✓ Free one-week POC✓ NDA before access✓ A QA lead replies the same day

[ Keep exploring ]

Other engagement models

All engagement models →

Also useful: Fixed-price packages · All testing services · Estimate your QA scope