Software Development Red Flags: What to Watch for When Reviewing Quotes

Red flags in software development proposals aren’t always obvious — they’re often omissions rather than errors. The most dangerous proposals aren’t the ones that say the wrong thing; they’re the ones that don’t say enough.

Most bad software engagements don’t start with deception. They start with optimism, vagueness, and an insufficient scoping process. The red flags are usually visible in hindsight. The goal of this guide is to make them visible in advance.

At PostMVP, we’ve taken over projects that went wrong elsewhere. The warning signs were almost always there in the original proposal — the client just didn’t know what to look for.

Red Flag 1: Quote Given After a Single Call

If an agency gives you a meaningful price after a 30-minute call, they have not scoped your project. They’ve made assumptions based on pattern recognition from similar projects, applied a rough multiplier, and given you a number. That’s a guess, not an estimate.

A proper scoping process for an MVP or defined feature set takes 2–4 weeks. For a complex platform, it may take longer. An agency that skips this is telling you that either:

• They’re under pressure to give you a number quickly (sales-driven culture)
• They don’t know how to scope properly (process gap)
• They intend to recover the difference through change requests (intentional underquoting)

The right response is to ask: “How long did your estimation process take, and what assumptions did you make?”

Red Flag 2: No Assumptions Section in the Proposal

Every software project rests on assumptions — things the agency is treating as true when producing the price. A proposal with no assumptions section hasn’t identified them; it’s hidden them.

If those assumptions turn out to be false, you’ll discover it mid-project as a change request. The agency will be technically correct — they never said they were including that. The fact that you assumed it was included is your problem.

Ask any agency without an assumptions section: “What are you treating as true that, if wrong, would affect the price?” Their answer — or inability to answer — is informative.

Red Flag 3: No Exclusions List

Exclusions are the other side of scope — and they’re just as important as inclusions. A proposal that describes what’s included without specifying what’s excluded is incomplete.

Common items that should be explicitly excluded if not in scope:

• Mobile applications
• Admin panels and internal tooling
• Analytics and reporting
• Third-party API costs
• Content creation or population
• Data migration from legacy systems
• Post-launch support and maintenance
• SEO or marketing infrastructure

“We’ll cover all features” is not a scope. Ask for the exclusions in writing.

Red Flag 4: Hourly Rate with No Time Cap

An hourly rate quote without a time cap is not a fixed-price engagement — it’s T&M with fixed-price language. This structure protects the agency entirely. You get an estimate, not a commitment.

Watch for phrasing like:

• “We estimate approximately X weeks at £Y/day”
• “Based on our experience, this should take…”
• “Our project rate is £X/hour, and we anticipate…”

These are estimates, not commitments. The difference matters enormously.

Red Flag 5: No Discovery Phase Offered

An agency that skips discovery is telling you they’re guessing. Discovery (or scoping) is where requirements are defined, assumptions are documented, and the price is earned. Without it, the price is pattern-matching from previous projects.

Some agencies avoid discovery because it takes time and clients resist paying for it. This is short-term thinking. Paid discovery costs £2,000–£8,000 typically. The change requests it prevents routinely save 3–5x that.

If an agency says “we can start next week,” ask where their estimate came from.

Red Flag 6: Vague Milestone Structure

Milestones should describe what software is deliverable at each point — not arbitrary calendar dates. “Phase 1: four weeks” tells you nothing about what you’re getting or how you’ll know it’s done.

Proper milestones look like:

• “User registration, authentication, and profile management complete — demo on [date]”
• “Payment integration tested in staging environment, covering subscription and one-time purchase flows”

Vague milestones protect the agency. Clear milestones protect you.

Red Flag 7: Reluctance to Put Change Process in Writing

Every project has changes. The question is whether there’s a process for handling them. An agency that won’t define the change process upfront is one that wants flexibility to handle changes on their own terms — which usually means charging more with limited notice.

A written change process should specify: how changes are submitted, how the impact is assessed, how the change order is approved, and how the original price is preserved.

Red Flag 8: Requesting 100% Payment Upfront

Milestone-based payment protects the client. Upfront payment protects the agency. A reputable agency with confidence in their delivery doesn’t need full payment before starting — they’ll happily defer 10–20% to final delivery.

An agency asking for 100% upfront either has cash flow problems or doesn’t trust their own delivery enough to have skin in the game.

Standard payment structure: 25–30% kick-off, 25–30% first milestone, 25–30% second milestone, 10–20% final delivery.

Red Flag 9: References They Won’t Provide

Every agency should be able to provide two or three client references on request. Not case studies from their website — actual clients you can call.

If references aren’t offered proactively and aren’t forthcoming when asked, the agency either hasn’t done enough client work to have references, or the references they have wouldn’t speak positively.

The Quick Reference Table

In Summary

The red flags in a software proposal are almost always omissions: missing assumptions, missing exclusions, missing change processes, missing milestone detail. PostMVP includes all of these in every proposal — not because clients demand it, but because a proposal without them isn’t worth the paper it’s on.