Software Development Quotation: Phases, Change Control and a Free Generator
Quote development work in phases with a deliverable and a payment trigger on each, and define a change request before the first one arrives.
- No signup or login
- Instant PDF download
- Processed in your browser
- Free, with no invoice limit
Development quotations fail in a way that is specific to this trade: the thing being priced does not exist yet, and the client's picture of it is more complete than the specification they have given you.
Phased quoting is the standard answer, and it works — but only if each phase ends in something the client can look at and sign off. A phase with no deliverable is just an invoice with a date on it.
Line items
What goes on a development quotation
Each phase priced, with what the client gets at the end of it.
Discovery
Requirements, user flows, technical approach, and a written specification. Fixed-price this, because it is the one phase whose scope you actually know. Its output is what makes the rest quotable.
Design
Number of screens or page templates, and the rounds of revision included. Templates, not pages — a forty-page site may be six templates, and pricing by page is how designers underquote.
Build
Estimated until discovery is done, then fixed. Broken into modules with a deliverable each, so progress is visible rather than asserted.
Testing and launch
Device and browser matrix, accessibility target, data migration, deployment. The launch itself is work and is routinely left out of the price.
Change requests
The definition of a change, the rate, and the rule that changes are quoted before work starts. This paragraph is worth more than the rest of the quotation combined.
Support and hosting
A separate monthly figure with response times and inclusive hours. Bundled into the build it is undefined; quoted separately it is a second revenue line.
Free, in your browser
Software Development Quotation
Fill in the quotation below and download the PDF. Totals, tax and the deposit calculate as you type, and nothing you enter is sent to us.
Online Quotation Generator
Fill in the quotation below — your details, the customer, the items and the price — then download the PDF or print it. This online quote maker calculates the totals, tax and any deposit for you, and nothing you type is sent to us.
Download or print
Quotation settings
Quote on site, invoice when done?
Quotations, invoices, receipts and waybills on your phone, with your details saved.
Get the Android app| $0.00 |
Avoid these
Where development quotes go wrong
- One number for the whole project. From a one-page brief it is a guess presented as a price, and the difference gets discovered in month three.
- Revisions unbounded. Name the rounds per phase and the rate beyond them.
- Content assumed. State who writes and supplies copy, images and data. Waiting for client content is the most common cause of an overrun nobody is paying for.
- Browser and device support unstated. “It doesn't work on my phone” is unanswerable without a support matrix on the quotation.
- IP left unmentioned. Say who owns what on final payment, and what you retain.
- Third-party costs absorbed. App store fees, SMS and email services, API usage, hosting. List them as excluded or at cost — they recur and they are not yours to carry.
Quote the enquiry while it is warm
Invoice & Quotation Generator keeps your phase structure and day rates on your phone, so a development enquiry gets a real quotation the same day rather than a promise to send one.
- Phase lines with deposits
- Client details saved for reuse
- Quotations that become staged invoices
- Works offline
- Free, unlimited quotations
Questions
Questions
How do you quote for software or app development?
Quote by phase with a deliverable at the end of each: discovery, design, build, test, launch. Put a price and a payment trigger on every phase. A single figure for “an app” is unquotable honestly, because neither side yet knows what is being built.
Should I give a fixed price or an estimate for app development?
Fixed price the discovery phase, because its scope is genuinely knowable. Estimate the build until discovery has produced a specification, then quote it fixed. Quoting the whole project fixed from a one-page brief is how development agencies lose money and clients lose trust.
What should a web design quotation include?
Number of page templates (not pages), rounds of design revision, the CMS or platform, content responsibility, browser and device support, accessibility target, hosting and domain, and what happens after launch. Content is the one that derails timelines: say plainly whether the client supplies it.
How do I handle change requests in a development quotation?
Define a change as anything outside the agreed specification, state that changes are quoted separately before work starts, and give an hourly or daily rate for them. Without that paragraph every “small tweak” is free work, and there is no natural end to them.
Should the quotation cover maintenance and support?
Quote it separately, as a monthly figure with a stated response time and an inclusive hours allowance. Bundling support into a build price makes the build look expensive and leaves the support undefined, which is the worst of both.
Who owns the code and the design?
Say so on the quotation. Common terms are that the client owns the delivered work on final payment, while you keep pre-existing components and libraries. Silence here becomes an argument at exactly the moment you want a reference.