How to Read a Software House Proposal: Twelve Red Flags and What Good Looks Like
November 11, 2026 · 6 min read · Etzal Group Team
Two proposals arrive for the same project. One is forty pages with a glossy cover, a company history, a long list of technologies and one line for the price. The other is twelve pages, begins by restating the client's problem, lists what is excluded, names four people and breaks the price into six parts. The first looks more impressive. The second is from the vendor more likely to deliver. Reading a software house proposal well is mostly knowing which pages matter.
Read in this order
- Their understanding of your problem.
- Scope: included and excluded.
- Assumptions.
- Team.
- Plan and milestones.
- Price breakdown and payment terms.
- Warranty, support and ownership.
Company history, awards and technology logos can wait. They say who the vendor is in general. The seven items say what they will do for you.
Red flags in understanding and scope
1. Your problem is not restated. The proposal goes straight to the solution, or repeats your brief word for word. A vendor who understood would describe your situation in their own words, including something you did not say but recognise as true.
2. No exclusions. Every project has things that are out of scope. A proposal without an exclusions list has not thought about the boundary, and you will discover it later, one invoice at a time.
3. Features listed, outcomes missing. "Dashboard, reports, user management" describes software. "Branch managers see yesterday's stock by 08:00 without calling the warehouse" describes a result. Proposals written only in features cannot be held to a result.
4. No questions. A vendor who asked nothing before proposing has guessed. Good proposals follow a conversation and often list open questions that still need answers.
Red flags in assumptions and team
5. No assumptions section. Every estimate rests on assumptions: that data is clean, that an interface exists, that users are available for testing. Unstated assumptions become disputes. A long, honest list is a good sign.
6. No named people. "Our experienced team" is not a team. Look for names, roles and the share of time each will give. Ask whether those people are employed by the vendor, and whether they can be replaced without your agreement.
7. The people you met will not be on the project. The senior consultant who presented so well appears nowhere in the plan. Ask directly who will attend the weekly meeting.
Red flags in plan and price
8. A timeline that is suspiciously short or perfectly round. "Three months" with no phases is a wish. A credible plan shows phases, dependencies on you, such as reviews and data, and time for testing and fixes.
9. One number for the price. A single total cannot be examined, compared or adjusted. A breakdown by phase or module lets you see where the money goes and what could be removed.
10. Payment far ahead of delivery. Half or more due before anything can be tested moves the risk to you. Payments should follow accepted milestones.
11. Silence on running costs. Hosting, licences, third-party services, maintenance. The build price is only part of what you will pay over three years. A proposal that omits these has given you a partial figure.
Red flags in terms
12. Vague ownership, warranty or exit. Who owns the source code, and when? What is fixed free of charge after go-live, for how long? What do you receive if the relationship ends: code, documentation, credentials? If the proposal does not say, assume the answer is unfavourable until it is written down.
What a good proposal shows
| Area | Good sign |
|---|---|
| Understanding | Your problem in their words, with an insight you had not stated |
| Scope | A clear list of included items and a clear list of exclusions |
| Assumptions | Written, specific, including what they need from you |
| Team | Named people, roles, experience, time commitment |
| Plan | Phases with deliverables, reviews, testing and buffers |
| Price | Breakdown by phase or module, day rates for changes |
| Payment | Linked to accepted milestones, with a retention |
| Running costs | Estimated for the first years |
| Risk | Risks they see, and how they would handle them |
| Terms | Ownership, warranty, support and exit stated plainly |
One more good sign: the vendor tells you something you did not want to hear. That your deadline is unrealistic, that a requested feature is not worth its cost, or that part of the project should wait. A vendor who disagrees with you before the contract is likely to be honest with you after it.
Questions to ask in the presentation
- What did you leave out, and why?
- Which assumption, if wrong, would change the price most?
- Who exactly will work on this, and what else are they working on?
- What is the riskiest part of this project?
- What will you need from us, and when?
- How do you handle a change request? Show us the form.
- What happened on the last project that went badly, and what did you do?
- If we part ways after phase one, what do we take with us?
- May we speak to two clients, including one where there were problems?
Listen to how the answers are given as much as to their content. Specific, unhurried answers suggest experience. General reassurance suggests the question was not expected.
Comparing proposals fairly
Proposals rarely cover the same scope. Before comparing prices:
- List every item in any proposal.
- Mark for each vendor: included, excluded or unclear.
- Ask each vendor to price or confirm the unclear and excluded items.
- Add running costs over the same period.
Only then compare. The cheapest proposal on paper is often the one with the most exclusions.
When something feels wrong
A proposal that is unclear before signing will not become clearer after. If you have asked twice for a breakdown, for names or for exclusions and received general answers, treat that as information about how communication will go during the project.
A note from the other side
We write proposals for a living, and we know which parts are tempting to leave vague. The exclusions list costs us deals to vendors who promise everything. We keep writing it, because the alternative is an argument in month four. If you are comparing proposals now and would like an independent reading, we are glad to give one, whether or not ours is among them. See how we scope work in Enterprise Software, or contact us.
Summary
Read the understanding, scope, assumptions, team, plan, price and terms before anything else. Be wary of missing exclusions, unnamed teams, round timelines, single-figure prices, early payments, absent running costs and vague ownership. Look for specifics and for honest disagreement. Normalise scope before comparing prices, ask the hard questions in person, and take vagueness before signing as a forecast of what follows.
Frequently asked questions
What is the most important part of a software proposal?
The section where the vendor describes your problem and what is and is not included. A vendor who restates your situation accurately and lists clear exclusions has understood the work. Price means little until scope is clear, because two prices for two different scopes cannot be compared.
Is the cheapest proposal always a bad sign?
Not always, but it deserves a specific question: what is different? A lower price can come from a smaller scope, a more junior team, reused components, or an underestimate that will return as change requests. Ask the vendor to explain the difference against the other proposals' scope.
Should a proposal name the people who will work on the project?
Yes, at least the lead roles. Names, roles, relevant experience and the share of their time committed. A proposal that describes only the company's general strengths gives you no assurance about who will actually do the work.
Related service
Free consultation
Not sure where to start? We will map the right system for your business, free.
