How to choose a software agency without getting fooled

Choosing a software agency without getting fooled comes down to judging transparency before price: demand a written scope, clarity on who owns the code and the data, a verifiable portfolio, and a maintenance plan, and be wary of anyone who promises everything cheap and fast. Hiring the people who will build your business’s system is an act of trust, and the bad news is that not everyone earns it. The good news is that the signs for telling them apart are in plain sight once you know what to look for.

For a non-technical business owner, the problem is real: you can’t evaluate the quality of code the way you’d judge a physical product. That’s why many end up overpaying for something that doesn’t work, or worse, locked into a vendor who became the only person who understands their own system. This article gives you the criteria to choose with a clear head, even if you don’t know how to program.

What are the red flags of a bad agency?

The worst signs show up before you sign, in how they sell to you. Learn to read them and you’ll avoid most bad deals.

• A price with no clear scope. If they give you a firm number without deeply understanding what you need, they’re guessing (or they’ll charge you “extras” later). A serious price comes from a defined scope.
• They promise everything cheap and fast. Software that’s good, cheap, and fast doesn’t exist: you can pick two. Anyone promising all three either doesn’t know what they’re doing or plans to cut corners where you can’t see.
• They dazzle instead of explaining. If they answer your questions with jargon that leaves you just as lost, that’s a bad sign. A good vendor translates; one hiding something hides behind words.
• They don’t show real work. “We’ve done many projects” with no verifiable portfolio, no clients you can talk to, is smoke.
• They don’t mention maintenance. Software isn’t delivered and forgotten: it needs updates, fixes, and support. If no one mentions what happens after launch, they’ll leave you on your own.
• They want full payment upfront. A reasonable deposit is normal; 100% before you see results leaves you with no leverage if something goes wrong.

What should I demand before signing?

Demand that everything important be in writing, in language you understand. These are the points a serious proposal shouldn’t be missing.

• Scope, deliverables, and milestones. Exactly what will be built, in what parts it’s delivered, and how you’ll know each stage is done. Payments should be tied to completed milestones, not the calendar.
• Ownership of the code and data. This is critical: when it’s done, is the code yours or do you just “rent” it? Do you have access to the repository? Can you export your data whenever you want? Your business shouldn’t be held hostage by your vendor.
• Warranties and bug fixes. What happens if something breaks after delivery. A reasonable warranty period reflects an agency that stands behind its work.
• Communication and points of contact. Who you’ll talk to, how often, and how they report progress. Weeks of silence is one of the most common complaints.
• A maintenance plan. How much it costs and what ongoing support includes. Better to know from the start than to discover it once you already depend on the system.

What key questions should I ask in the first meeting?

The right questions reveal more than any sales pitch. Come with these and watch not only what they answer, but how comfortable they look answering.

• “When it’s done, are the code and data mine?” The answer should be a plain yes.
• “Can I talk to a client you’ve done something similar for?” Those who do good work have happy clients willing to confirm it.
• “What if I need to change something halfway through?” You want a clear process for changes, not a “we’ll figure it out later.”
• “How and how often will you report progress?” Transparency shows in the routine, not in the promise.
• “What does ongoing maintenance include, and what does it cost?” If they stumble here, they didn’t think about the long term (or don’t want you to).
• “What do you NOT recommend doing, and why?” An honest advisor sometimes tells you that you don’t need what you think you do. Anyone who sells you everything you ask for, with no nuance, just wants your money.

The best agency isn’t the one that says yes to everything, but the one that sometimes says no and explains why. That honesty, uncomfortable as it may be, is what protects your investment.

Cheap upfront, or cheap in the long run?

The lowest price is almost never the cheapest in the end. Badly built software gets paid for twice: first to the original vendor and then to whoever you have to hire to fix it or rebuild it. This is called technical debt, and in software it’s as real as financial debt.

Look at the total cost: recurring licenses, maintenance, how easy it is for another developer to pick up the project if needed, and the risk of being locked into a single vendor. A transparent agency helps you see that full picture instead of dazzling you with a small number that quietly grows.

In summary

Choosing the right people to build your software doesn’t require you to learn programming; it requires you to demand clarity. A written scope, ownership of your code and data, a verifiable portfolio, real communication, and an honest maintenance plan. If a vendor delivers on that and also tells you no now and then, you’re on the right track. If they dodge your questions or promise the impossible for almost nothing, they’re already showing you what working with them will be like.

At Normandia Web we work exactly that way: proposals with a clear scope, your code and your data always yours, and an honest conversation about what your business really needs, even when that means recommending less than you came in for. If you’re about to hire a development team and want a no-strings second opinion, we’re glad to review it with you.