Red flags when hiring a development agency
Most agencies that disappoint were not dishonest at the sales stage. They were vague, and vagueness in a proposal reliably becomes vagueness in delivery. These are the signals that show up before you sign, when they are still cheap to act on.
A firm price before anyone understands the scope
This is the most common and the most costly. A number produced on the first call is not an estimate — it is a bid to win the deal, and it has to be protected later. It gets protected in one of two ways: change requests for everything not explicitly named, or quiet reductions in the care taken where you cannot see. Neither is announced.
What good looks like: a paid or unpaid discovery step that ends with a written scope and a number you can approve, and a willingness to say “we cannot price this responsibly yet.”
The people who impress you are not the people who build
Ask who will write the code, by name, and how many other projects they are on. If the team is assigned after signature, you are buying capacity, not the expertise you were shown. This is not automatically disqualifying — but you should know which you are purchasing.
Warmth about ownership, silence in the contract
“Of course the code is yours” is easy to say. The questions that separate a real answer from a reassuring one: whose name are the cloud accounts in, at what point does the repository transfer, and is any of this code reused for other clients? Vagueness on the third question in particular is worth pressing on.
Nothing has ever gone wrong
Everyone who has shipped software at any scale has a story about an outage, a bad migration or an estimate that was badly wrong. A studio that cannot produce one is either inexperienced or managing you. What you want is a specific story with a specific change that followed it — that is what a feedback loop sounds like.
Process described only in adjectives
“Agile”, “collaborative” and “transparent” are claims, not mechanisms. Ask what you receive at the end of each stage, how often you see working software, and what happens when a deadline is at risk. Named artefacts and named cadences are the answer; more adjectives are a warning.
No answer about the day after launch
If maintenance, monitoring and incident response are not discussed in the proposal, they have not been costed, and they will either be absent or billed as a surprise. Ask what happens when something breaks at 2am in month four, and listen for whether anyone is actually responsible.
A portfolio you cannot visit
Screenshots and case-study PDFs are cheap. Ask to see something still running today. Real client work under NDA is a legitimate reason not to publish — but a studio in that position should offer a reference call or walk you through the architecture verbally. What should concern you is a long list of launches with nothing you can open.
| Red flag | The question that tests it |
|---|---|
| Instant firm price | “What would change this number after discovery?” |
| Unnamed team | “Who writes this, and what else are they on?” |
| Vague ownership | “Whose name are the cloud accounts in?” |
| No failure story | “What broke last year and what changed after?” |
| Adjective process | “What do I receive at the end of each stage?” |
| No support model | “Who is responsible at 2am in month four?” |
The sales conversation is the most cooperative a studio will ever be. Whatever is vague now will be more vague under delivery pressure.
- A price before scoping is a bid, and it will be protected at your expense.
- Meet the people who will build it, and ask what else they are working on.
- Ownership belongs in the contract, including whose name the accounts are in.
- No failure story means either no experience or no candour.
- If post-launch support is not in the proposal, it has not been costed.
The takeaway
None of these require technical knowledge to check, which is the point — they are all answerable in a conversation before money changes hands. A studio that answers them plainly is not necessarily the cheapest, but you will know what you are buying.
The matching list of questions to ask is here. If you would like ours answered directly, ask us.