How to tell if your dev agency is ripping you off — 9 warning signs

Most founders who hire a development agency aren’t technical. That’s the whole reason they hired one. But it also means that when something feels off, they can’t quite tell whether they’re being difficult or being fleeced.

I get called in after the fact — to rescue codebases that agencies delivered — so I’ve seen the patterns. Here are nine warning signs, roughly in order of how worried you should be, and what to do about each.

1. You can’t get a straight answer to “why is this taking so long?”

A good partner explains delays in terms you understand: “the payment integration has edge cases we’re testing,” or “we found the previous data model won’t scale, so we’re fixing it now.” A bad one gives you vague reassurance, moving goalposts, and a vocabulary designed to end the conversation. If every timeline question produces fog, that’s the sign.

2. The demo always works, but you never get to touch it

Agencies in trouble become experts at the controlled demo. They screen-share, they drive, everything’s smooth. But when you ask for a link to click around yourself, it’s “not quite ready for that.” Real progress survives you poking at it. Insist on hands-on access to a staging environment, early and often.

3. No tests, or they can’t show you any

You don’t need to read code to ask: “Can you show me your automated tests running?” Every serious build has them — they’re how you know a change didn’t break something else. If the answer is a pause, a redirect, or “we test manually,” you’re paying for a house with no smoke detectors.

4. Nobody will explain the architecture in plain English

Ask: “Draw me how the pieces fit together.” A team that understands what it built can sketch it in five minutes — the app, the database, the payment provider, where your data lives. A team that can’t is either hiding something or doesn’t actually understand the thing they sold you.

5. Everything is a change request

Scope creep protection is fair. But when every small fix or obvious omission becomes a billable “that wasn’t in scope,” you’re in an incentive trap: the worse the original build, the more they earn fixing it. A partner absorbs small things; a vendor milks them.

6. You don’t own your own code (or you’re not sure)

Ask flatly: “Do I have admin access to the code repository and the servers?” You should own the GitHub/GitLab account, the domain, the hosting, and the accounts for every third-party service. If access runs through the agency and they’re cagey about handing it over, that’s leverage they’re keeping over you — and a genuine emergency waiting to happen.

7. One person is a black box

Sometimes the whole project lives in one developer’s head, and the agency guards access to them. If you can never talk to the people actually building your product, you can’t assess anything — and you’re dangerously exposed the day that person leaves.

8. The bill is detailed but the value isn’t

Timesheets showing 160 hours tell you that time was spent, not that it was spent well. The real question is output: what can your product do this month that it couldn’t last month? If hours keep climbing while the visible product barely moves, ask for a demo of the actual new capability behind those hours.

9. Your gut has been uneasy for a while

This one isn’t technical, and it’s the most reliable. Founders almost always sense trouble months before they act on it — they just talk themselves out of it because they “can’t judge the technical stuff.” You can judge the signals above without being technical. Trust the pattern, not the reassurance.

What to do if a few of these ring true

Don’t blow up the relationship on a hunch, and don’t keep pouring money in on faith either. Get an independent second opinion: a senior engineer, working for you and not the agency, who reviews the code, the security, and the delivery process and tells you in plain English what you actually have and what it’s worth.

It’s a few days of someone’s time against a build you might otherwise sink months of runway into. Whatever it finds — reassurance or a red flag — it’s the cheapest clarity you’ll buy all year.