Software agency red flags
The warning signs that show up before the contract, the ones that appear mid-build, and the signals people mistake for problems.
The short answer
The clearest software agency red flags are a price quoted before any questions, uncapped hourly billing, accounts opened in the agency's name, no written change pricing, reporting only they can produce, a deadline with no weekly milestones, pressure to sign quickly, and a claim that no project has ever gone wrong.
Red Flags Before the Contract
Most bad engagements were visible in the first two conversations. The signals are commercial rather than technical, and they are easy to spot once you know what you are listening for.
| Red flag | What it usually means |
|---|---|
| A price before any questions | You are being sold a template, not a build. |
| Hourly billing with no cap | Delay is profitable for them and expensive for you. |
| Accounts opened in their name | Leaving later means rebuilding. |
| No written change pricing | Every request after signature becomes a negotiation. |
| Reporting only they can produce | You cannot check whether the work is paying off. |
| A deadline with no weekly milestones | Nobody finds out it slipped until it has. |
| Pressure to sign this week | Their pipeline problem is becoming your decision. |
| Nothing has ever gone wrong | Either inexperience, or you are not being told. |
Red Flags During the Build
Once work starts, watch for updates that describe activity instead of progress, demos that are always a week away, and scope quietly moving into a later phase. Any of those on its own is normal. All three in the same month means the schedule has already gone and the conversation has not caught up yet.
The most expensive red flag is the one you can see and forgive.
Missing change pricing feels like a small gap at signature and costs the most by launch.
Signals That Are Not Red Flags
Some things worry buyers unnecessarily. A small team is not a problem; a small team with named people is often faster than a large one you never meet. Being told your idea needs cutting back is a good sign, not a sales failure. So is a builder who asks for weekly decisions from you, because the alternative is guessing at your business.
What to Do When You Spot One
Put it in writing and ask for the answer in the same form. Ownership, change pricing and the delivery window belong in the document, not the conversation. A builder who is comfortable with the terms will write them down within a day. Hesitation at that point has told you everything, at a stage where walking away costs you nothing but a call.
Nobody regrets asking for terms in writing. Plenty of people regret not asking.
From the people who build these
Missing change pricing is the flag buyers forgive most often and pay for most heavily, because every request after signature turns into a separate negotiation.
There's a better way.
Almost every flag on the list disappears when the numbers, the accounts and the reporting sit somewhere you control rather than somewhere you request.
Dashboards and reporting
Progress and results in a screen you own, so nothing depends on a monthly summary.
SEO and AI search performance
Search visibility you can verify yourself instead of taking on trust.
Role-based access
Accounts and permissions held by you, with access granted rather than surrendered.
Prefer terms in writing first?
Or calculate your savings firstKeep reading
Questions to ask a software agency
Twelve questions and what a weak answer to each one means.
How to hire a software agency
Eight checks that separate a partner from an invoice.
How to get a quote for custom software
What to prepare and what a real quote must contain.
Stop paying dev agencies
Why hourly billing rewards the slowest possible build.