Checklist

What a software development quote should include

Most quotes describe what will be built. Fewer describe what happens around it: testing, handover, running costs, and who owns the result. Use this list to check any quote before you sign.

By Usman, co-founder · Content needed: publish date
Suggested: a software quote with checkmarks and two red flags
  1. Scope and features

    What good looks like: Every feature from your requirements is listed, with what is included and what is not.

    Red flag: Phrases like "standard admin panel" or "basic reporting" with no detail.

  2. Design

    What good looks like: Number of screens or flows, rounds of revision, and who approves designs.

    Red flag: Design described only as "UI/UX included".

  3. Testing

    What good looks like: How and when testing happens, who does it, and how bugs found before launch are handled.

    Red flag: No mention of testing, or testing left entirely to you.

  4. Launch and app stores

    What good looks like: Who sets up hosting, domains and app store accounts, and in whose name.

    Red flag: Accounts registered in the vendor's name.

  5. Hosting and running costs

    What good looks like: Expected monthly costs after launch for servers, services and licenses.

    Red flag: Only the build price, with nothing about what it costs to run.

  6. Handover and documentation

    What good looks like: You receive source code, credentials and enough documentation for another team to continue.

    Red flag: Handover not mentioned, or code delivered only at the very end.

  7. Ownership of code and designs

    What good looks like: You own what you paid for once invoices are settled. Ask your lawyer to confirm the wording.

    Red flag: Ownership unclear, or the vendor keeps rights to reuse core parts without saying so.

  8. Maintenance and support

    What good looks like: What happens after launch: response times, monthly cost, what counts as a fix versus new work.

    Red flag: "Support available" with no terms.

  9. Change requests

    What good looks like: How new requests are estimated, approved and billed.

    Red flag: Hourly billing for changes with no approval step.

  10. Payment milestones

    What good looks like: Payments tied to delivered, testable milestones.

    Red flag: Large upfront payments before anything is delivered.

  11. Team and communication

    What good looks like: Who works on your project, how often you see progress, and who your main contact is.

    Red flag: A sales contact only, with the delivery team unnamed.

Take this checklist into your next vendor call

Content needed: downloadable PDF version and optional email gate

This guide is general information, not legal advice. Have a lawyer review any contract before you sign.

Holding a quote right now?

We review proposals as part of vendor selection, including a single-quote review.

Book an intro call