All posts
Hiring

5 Red Flags When Hiring a Software Agency

March 15, 20265 min read

Most bad agency hires don't feel bad at the start. They feel great. Confident pitch, beautiful deck, reasonable price. The red flags are there — they're just easy to miss if you don't know what you're looking for.

Here are the five that matter most.

1. Their portfolio is all screenshots, no links

A portfolio of beautiful mockups tells you an agency can design. It doesn't tell you they can ship.

When you look at a portfolio, click every link. If half of them go nowhere, or if the agency can only show you screenshots instead of live products, ask why. Good agencies build things that run. If their past work exists only in a PDF, that's worth questioning.

The best sign is a portfolio where every link works, every product is live, and the agency can tell you what happened after launch.

2. They agree with everything you say

Early in a conversation, pay attention to how much an agency pushes back.

If you describe what you want to build and they immediately say "yes, we can do that, here's the price" — without asking clarifying questions, flagging potential issues, or offering a different perspective — that's a red flag.

Good agencies bring expertise. Part of that expertise is telling you when an approach won't work, when your timeline is unrealistic, or when there's a better way to solve your problem. An agency that just agrees with you isn't a partner. They're an order-taker.

3. Vague on who's actually doing the work

"Our team" is not an answer.

When you ask who will be working on your project, you should get names, roles, and ideally the chance to speak with them. If the agency is evasive — talking in generalities about "our engineering team" or "our senior developers" — it's often because the actual work will be done by someone you haven't met and wouldn't have approved.

This doesn't mean offshore development or contractors are automatically bad. It means you deserve to know what you're getting.

4. The proposal is all price, no process

A proposal that leads with cost is often hiding a lack of process.

What you want to see is a clear explanation of how the project will work: discovery, design, development, review cycles, QA, launch, support. If you receive a proposal that's just line items and a total, ask what's behind the number.

A detailed process proposal takes more effort to write, which is exactly why good agencies write them. It forces everyone to agree on what's actually being built before money changes hands.

5. They can't give you references — or the references are suspiciously smooth

References are standard. Every agency should be able to provide them. If they can't or won't, that's a clear signal.

But even when references are provided, a too-smooth reference should make you think. "They were great, everything was perfect, I'd hire them again" — that's not actually useful information. Real client relationships have friction. Real projects have surprises.

Ask your references specific questions: What was the biggest challenge? What would you do differently? Were there any timeline or budget issues, and how were they handled?

An agency with real relationships has clients who can speak to the hard parts, not just the highlights.


None of these flags guarantees a bad experience. But each one is worth taking seriously. The cost of a bad agency hire — in time, money, and frustration — is high enough that a little skepticism upfront is worth it.

When in doubt, slow down. The right agency will still be there after you've done your homework.

Have a project in mind?

Let's talk about what you're building.

hello@handasa.io