Software testing quotation template
Software testing quotation template: test cases per feature area, manual runs on agreed devices, an automated regression set and bug reports per cycle.
Templates by industry
- Test plan and test cases, per feature area
- Manual test run on the agreed devices
- Automated regression tests, initial set
- Bug report with reproduction steps, per test cycle
Preparation guide
Example workflow
Confirm scope and quantities
Example: start with "Test plan and test cases, per feature area", confirm the required quantity and client inputs, then agree completion criteria for each item.
Review and approve the quotation
Confirm acceptance evidence for "Bug report with reproduction steps, per test cycle", all line quantities, exclusions and quote validity with the customer, and retain the approved version.
Deliver and prepare billing
Link subject identifiers to results and deliver observations and agreed follow-up actions. When the agreed milestone is complete, prepare an invoice using actual quantities and approved changes.
Teams without their own testers often hire an outside QA service before a release. What they need to know is how much will be tested, on what, and how often. This template breaks the work into feature areas such as login, checkout or reporting, prices the test cases per area, runs manual tests on a list of devices, builds a first set of automated regression tests, and bills each test cycle's bug report, so the client can add a cycle when the release slips.
Fields to prepare
- Deliverables and line items
- Test plan and test cases, per feature area, Manual test run on the agreed devices, Automated regression tests, initial set, Bug report with reproduction steps, per test cycle: specify the planned quantity and delivery scope for each item.
- Test plan and test cases, per feature area
- Name each feature area and roughly how many test cases it will hold, so a new area can be priced the same way.
- Manual test run on the agreed devices
- List the devices, operating systems and browsers; each addition multiplies the run time.
- Automated regression tests, initial set
- Say which tool the automated tests use, where they will run and who maintains them after handover.
- Bug report with reproduction steps, per test cycle
- Define a cycle as one full run on one build with its report, so retests after fixes are counted the same way.
- Subjects and quantities
- Record sample, asset or site counts, identifiers, test items and accessible areas.
- Method and report
- Specify agreed methods, report format, delivery deadline and whether retesting is included.
- Scope to agree
- Quote by feature area and test cycle, list the devices and browsers covered, and say that testing reports defects but does not fix them.
Before sending
- Does “Test plan and test cases, per feature area” say what is included and what quantity the price assumes?
- Would the customer read “Manual test run on the agreed devices” the way you do, including what it leaves out?
- Can you still honour the price of “Automated regression tests, initial set” on the last day the quotation is valid?
Show 4 more
- Does “Bug report with reproduction steps, per test cycle” say what is included and what quantity the price assumes?
- Separate visit, collection and transport costs from analysis and reporting.
- Document inaccessible areas and excluded tests before work starts.
- Check quote validity, the customer approval method and payment milestones.
Worked example with sample figures
The figures below are invented to show how the template adds up: 4 lines in USD, with an example tax rate of 8%.
| Item | Quantity × unit price | Amount |
|---|---|---|
| Test plan and test cases, per feature area | 5 × $600.00 | $3,000.00 |
| Manual test run on the agreed devices | 3 × $900.00 | $2,700.00 |
| Automated regression tests, initial set | 1 × $3,500.00 | $3,500.00 |
| Bug report with reproduction steps, per test cycle | 3 × $250.00 | $750.00 |
| Subtotal | $9,950.00 | |
| Sales tax (8%) | $796.00 | |
| Total | $10,746.00 | |
Quoted net amount $9,950.00, sales tax $796.00, quoted total $10,746.00.
What the document must show
The details a quotation has to show, and why each one matters, are set out in the guide below.
The sales tax depends on where the work is supplied, so set the rate that applies to your customer before sending.
Official rate reference: US government: state and local taxes
Full requirements: How to write a quotation: format, example and checklist
Frequently asked questions
Does a clean test report mean the software has no bugs?
No. It means the agreed test cases passed on the agreed devices for that build. Say this in the notes so nobody reads the report as a guarantee.
The developers fixed bugs and want another round. Is that included?
Only if your quotation counted it. Pricing per cycle makes the answer easy: each further run on a new build is one more cycle at the same price.
How is the sales tax worked out on this quotation?
The worked example above uses an example rate of 8%: $796.00 on a net amount of $9,950.00, for a total of $10,746.00. The editor recalculates all three when you change a quantity, a price or the country.
How is the document numbered?
QuoteBill gives each new document a unique number of its own. A member can switch to numbers in sequence in settings, such as QUO-2026-0001: one sequence for each kind of document, starting again every calendar year. A number you type yourself is kept as it is.
Can I email it to the customer?
Yes, from your own mail app. With a free account, the editor’s download menu offers Email this document, which opens your mail app with a message about the document already written. QuoteBill sends nothing itself, so save the PDF and attach it before you send.
Read next
Reading for the Software testing quotation template: How to write a quotation: format, example and checklist and Estimate vs quote: what binds you, with a remodeling example. The VAT and GST calculator adds tax to your quoted prices.