How to check a software quote before you sign: 12 checks, no tech knowledge needed

Short answer: you don’t need to read code to check a software quote. You’re checking what the quote promises in writing. Do you own the code and the accounts? Does it say what’s in and what’s out? Are payments tied to milestones you can test? Can another developer take over if this one disappears? And one check no developer can tick for you: have at least three buyers paid for what this quote builds? If not, sell it before you build it.

Why most quotes go wrong before a line of code is written

I spent two years on the other side of this, selling offshore development to businesses in Australia and Japan. Most problems I saw weren’t about the code. They came from what the quote didn’t say.

Developers quote what you describe. A vague brief gets a vague, expensive quote, and a fix you can’t check.

There are three ways it goes wrong.

Problem 1: you don’t own what you paid for

If a developer or agency holds the keys, you don’t own your product. The code sits in their account. The domain is in their name. The app store login is theirs. It’s fine while the relationship is good, and a mess when it isn’t.

The fix: get ownership in writing before you sign. Ask in writing, now, while the relationship is good.

Problem 2: nobody agreed what “done” means

“MVP” and “version 1” aren’t a scope. If the quote doesn’t list every feature and screen, and what’s not included, you’ll find out at the end. Admin tools, emails, payments, analytics and app store submission are the usual surprises.

The fix: a scope that lists what’s in, what’s out, and how changes get priced.

Problem 3: the quote is perfect and the build is still a waste

This is the one nobody talks about. A quote can pass every check and still pay for something nobody buys. No developer can cover that risk. Only buyers can.

The fix: sell it before you build it. If fewer than three buyers have paid, pre-paid or signed a letter of intent, any build now is a guess with a price tag.

The 12 checks

Tick one box per line, going by what’s written in the quote, not what was said on a call. “Not sure” counts as No.

A. Ownership: who holds the keys

1. You own the code, designs and IP once each invoice is paid. (critical)
2. The code, domain, hosting and app store accounts are set up in your company’s name, not the developer’s. (critical)

B. Scope: what “done” means

3. It lists every feature or screen included, not just “MVP” or “version 1”.
4. It says what’s NOT included.

C. Price and payments: who carries the risk

5. It’s a fixed price or a capped budget, not open-ended hourly billing.
6. Payments are tied to milestones you can test yourself, with only a small deposit upfront. (critical)
7. Each milestone has a target date.

D. Changes: what happens when plans move

8. It says how changes are priced, and nothing extra is billed without your written OK.
9. Bug fixing after launch is included for a set period, ideally 30 to 60 days.

E. Handover: if they disappear tomorrow

10. It includes documentation, logins and a walkthrough so another developer could take over. (critical)
11. Monthly running costs are listed: hosting, licences, AI usage and maintenance.

F. Buyer proof: the risk no quote covers

12. At least 3 buyers have paid, pre-paid or signed a letter of intent for what this quote builds.

Your verdict

Count your No and Not sure answers.

• Any No on a critical line, or 4 or more: don’t sign yet. Ownership, payments and handover are what lock people in. Get them fixed in writing first.
• 1 to 3, none critical: ask before you sign. Nothing fatal, but there are gaps. Send the questions below and get the answers in writing.
• 0: looks solid. The quote covers the basics. Still get a second opinion on the scope and the price before you commit.

Questions to send your developer

For every No or Not sure, send the matching question by email. A good developer never minds you checking.

1. Can you confirm in writing that I own all code, designs and IP once each invoice is paid?
2. Will you set up the code repository, domain, hosting and app store accounts in my company’s name, with me as owner?
3. Can you list every feature and screen included, so we both know what “done” means?
4. What isn’t included that I might assume is, like admin tools, emails, payments or analytics?
5. Can we agree a fixed price, or a capped budget, for this scope?
6. Can we tie payments to milestones I can test, with only a small deposit upfront?
7. Can you add target dates for each milestone, and what happens if one is missed?
8. How are changes priced and approved? Can nothing extra be billed without my written OK?
9. How long after launch will you fix bugs at no cost?
10. Will you hand over documentation, logins and a walkthrough so another developer could take over?
11. What will this cost each month to run once it’s live?

Number 12 has no question for the developer. If you ticked No, it’s a question for you: who has paid?

What to cut before you sign

Most quotes are too big, not too expensive. Your customer doesn’t need 100% of your app. They need the part that solves their problem. Everything else can wait, or be done by hand.

Before you sign, go through the feature list and ask of each line: has someone paid for this, or asked for it twice? If not, park it. Every manual step you repeat later is a feature someone has already paid for. Build that step, nothing else.

FAQ

Do I need to understand the tech to check a quote? No. You’re checking what the quote promises in writing: ownership, scope, payments, changes and handover. None of that needs code.

Is hourly billing always bad? Not always, but it moves the risk to you. If you go hourly, ask for a cap and a weekly report of hours against the scope.

How much deposit is normal? There’s no fixed rule. The safer pattern is a small deposit and the rest paid against milestones you can test yourself.

What if the developer won’t put ownership in writing? Treat that as a no. If a developer or agency holds the keys, you don’t own your product.

Should I get a second quote? Yes, but compare scopes, not just prices. Two quotes for different scopes tell you nothing.

Not legal advice. For contracts, talk to a lawyer where you are.