How to Review a Software Development Proposal Before You Sign
A proposal is the first real look at how a development team thinks. Two quotes for the same idea can differ a lot, and the reason is almost always in what each one includes, assumes or leaves out. Here is how I would read one, section by section, before you sign anything.
In this guide 13 sections
- 1. Does it show they understood the problem?
- 2. Is the scope written down, including what is out?
- 3. Read the assumptions as carefully as the price
- 4. Are milestones tied to working software?
- 5. Understand the price model and payment terms
- 6. Who owns the code, accounts and data?
- 7. Who is actually doing the work?
- 8. How will quality and security be checked?
- 9. What happens after launch?
- Red flags in a proposal
- A quick checklist to compare proposals
- How we write proposals at Creuto
- Frequently asked questions
Founders often send me two or three proposals and ask which one is right. Most of the time the totals are not the interesting part. The interesting part is what each team understood about the product, what they quietly left out and what they will charge extra for later.
This guide walks through a proposal in the order you will usually read it, with the questions to ask at each step. If you have not asked for quotes yet, start with how to write a software RFP so every team quotes the same product.
The one rule
Compare scope and assumptions first, milestones second and price last. A price only means something once you know exactly what it buys.
1. Does it show they understood the problem?
A good proposal opens by restating your goal in its own words: who the users are, what job the software does for them and what success looks like. If this section is generic or copied from a template, the rest of the plan was probably built on guesses.
- Does it name your users and the main workflow, not just "a mobile app"?
- Does it mention the business result you care about, such as fewer manual steps or more bookings?
- Did they ask questions before writing it? Teams that ask nothing tend to find the surprises after you have paid.
2. Is the scope written down, including what is out?
Scope is the heart of the proposal. Look for a feature list for the first release that is specific enough to test. "User management" is vague. "Sign up with phone number and OTP, edit profile, admin can deactivate a user" is testable.
Just as important is an out of scope list. It protects both sides. If nothing is listed as excluded, assume disagreements later about what was "obviously included". Our guide on scope creep explains how unclear scope turns into extra cost.
Check that the scope covers the parts founders often forget:
- The admin panel or back office your team will use every day.
- Design: is it wireframes only, or full screen designs you approve?
- Testing on real devices and browsers.
- Speed, security and scale targets, the non-functional requirements.
- App store submission, hosting setup and launch.
3. Read the assumptions as carefully as the price
Every estimate rests on assumptions. Good proposals list them openly. Typical ones: you provide content and logos, a third-party service has a working API, there is one user role, there is no data to migrate. Each assumption is a place where cost can change.
Go through the list and mark anything you know is not true. If they assumed no migration but you have five years of records in spreadsheets, the price will move. Better to find that now. The guide on how software estimates work covers why this matters.
4. Are milestones tied to working software?
Look at how the work is split. Milestones should end in something you can open and use, not in "40% of development complete". Working software you can click through is the only progress report that cannot be misread.
| Weaker milestone | Stronger milestone |
|---|---|
| Design phase complete | Approved screens for sign-up, booking and payment |
| Backend 50% done | Customers can book and pay on a test build you can install |
| Testing | Release candidate passes the agreed test list on named devices |
| Launch | App live on both stores, admin trained, monitoring switched on |
Ask how often you will see a demo and who you will talk to each week. Short cycles with regular demos are the idea behind most modern delivery practice; the GOV.UK Service Manual on agile delivery is a clear public example of the approach.
Holding a proposal right now?
Bring it to a free 30-minute call. I will go through it with you and point out what is missing, even if you choose another team.
Book a free 30-minute call →5. Understand the price model and payment terms
A proposal is usually either fixed price for a defined scope or time and materials, where you pay for the hours used. Neither is wrong, but you should know which one you are signing and what happens when scope changes. Our comparison of fixed price vs time and materials goes deeper.
- Line items: can you see design, development, testing and launch separately?
- Payments: are they tied to the milestones above, not to calendar dates?
- Change requests: how is new work priced and approved, and who signs off?
- Running costs: hosting, app store accounts, SMS, maps, payment gateway and AI usage are separate from the build. Are they listed so you can budget for them?
To sanity-check a number, compare it with the real breakdowns on our project costs page or get a quick range from the app cost calculator.
6. Who owns the code, accounts and data?
This is the section people skim and later regret. The proposal, and then the contract, should say that you own the source code, designs and data once paid for, and that the code repository, cloud account and app store accounts sit in your name. WIPO's copyright overview is a useful primer on why written ownership terms matter for software.
At Creuto, clients' code lives in their own accounts from day one, so there is nothing to hand over at the end. If a proposal says the code will be "transferred on completion", ask what happens if the project stops halfway.
7. Who is actually doing the work?
- Who leads the project, and will you speak to them directly?
- Which roles are included: design, development, testing, project management?
- Is any part subcontracted to another company or freelancers?
- What happens if a key person leaves mid-project?
Ask to see relevant past work, ideally something close to your product. Our guide to choosing a software development company lists more questions for this stage.
8. How will quality and security be checked?
A proposal should say how the work will be tested and what "done" means. For anything that handles logins, payments or personal data, ask which security checks are included. The OWASP Application Security Verification Standard is a widely used reference you can point to when asking.
9. What happens after launch?
Software needs fixes, updates and small improvements once real users arrive. Look for a warranty period during which bugs in the agreed scope are fixed at no extra cost, and a clear offer for ongoing support after that. Every Creuto launch comes with a 60-day post-launch warranty. Our guide to software maintenance explains what to plan for beyond that.
Red flags in a proposal
- A single total with no breakdown and no assumptions.
- No out of scope list.
- Payments weighted heavily up front, before you see any working software.
- Code and accounts held by the agency until the final payment.
- No mention of testing, the admin side or launch.
- Promises that sound too certain about an unclear idea, such as a fixed date before anyone has asked about integrations.
A quick checklist to compare proposals
| Check | Proposal A | Proposal B |
|---|---|---|
| Restates your goal and users | ||
| Testable scope and out of scope list | ||
| Assumptions listed | ||
| Milestones end in working software | ||
| Line items and running costs shown | ||
| Code and accounts in your name | ||
| Named lead and team roles | ||
| Testing and security described | ||
| Warranty and support after launch |
Once you have picked a proposal, carry its scope into the contract. The software development contract checklist covers what to add.
How we write proposals at Creuto
At Creuto every proposal follows a free 30-minute strategy call and arrives within 24 hours. It sets out the first release, what is out of scope, the assumptions, milestones that end in working software and the running costs you should expect. The first working version typically lands in about 4 weeks, and the code sits in your accounts from the start. If you would rather talk it through, book a call and bring any proposals you already have.
Frequently asked questions
What should a software development proposal include?
At minimum: the problem and goal, a written scope of the first release, what is out of scope, the assumptions behind the price, milestones with deliverables, the team, the price and payment terms, who owns the code and accounts, and what support looks like after launch.
Why are two quotes for the same app so different?
Usually because they are not quoting the same thing. One may include design, testing, an admin panel and launch support while another leaves them out or assumes the client provides them. Compare scope and assumptions before you compare totals.
Is a proposal the same as a contract?
No. A proposal describes what will be built and how. The contract makes it binding and covers payment, ownership, confidentiality and what happens if things change or go wrong. The scope in the proposal should be attached to or referenced in the contract.
Should I choose the cheapest proposal?
Only if it covers the same scope, quality and support as the others. A lower number that leaves out testing, the admin side or post-launch fixes often costs more once those gaps show up.
How long should it take to get a proposal?
For a clear idea, a few days is reasonable. At Creuto we send a written proposal within 24 hours of the free strategy call. Larger or unclear projects may need a short paid discovery first.
Free quote within 24 hours
Want a proposal you can check line by line?
After a short call you get a clear written proposal within 24 hours, with scope, assumptions, milestones and running costs written down.