Software3 min readBy Published

How do you choose a software agency, and what are the red flags?

We're an agency, so read this with that in mind. But we've also picked up enough half-finished projects from other agencies to have firm opinions about what separates a good partner from an expensive lesson.

Short answer

Choose an agency that asks about your business before it quotes, starts with a small paid first phase, shows work you can verify, names the people who'll build your project, and gives you ownership of the code and accounts from day one. Walk away from a firm price after a single call, a vague scope, no testing, or code you can't see until the final invoice.

Green flags and red flags

Most bad agency experiences were visible in the first two meetings. The signs are rarely subtle once you know what to look for.

What to look for in the first conversations

Green flags

  • They ask about your customers and goals before talking price
  • They suggest a short paid discovery or pilot first
  • You own the code, the repositories and the app store accounts
  • You see working software every week or two, not just status reports
  • They write automated tests and plan for life after launch
  • They tell you who will actually do the work

Red flags

  • A firm price after one call, with no discovery
  • A scope full of words like "modern" and "scalable" but no detail
  • No access to the code until the final payment
  • No past work you can check and no clients you can call
  • Everything is easy and nothing is a risk
  • A large upfront payment for the whole project

Questions to ask before you sign

Ask these out loud and listen to how the answers sound. Confident and specific is good. Vague and cheerful is not.

Five questions, and what a good answer sounds like

  1. Who owns the code?

    You do, from the first commit, in a repository you control.

  2. What if we stop halfway?

    You keep everything built so far, with notes someone else can pick up.

  3. How do you test?

    Automated tests on the important parts, and a staging version you can try.

  4. Who does the work?

    Named people, and you can talk to them directly.

  5. What happens after launch?

    A support plan with a clear monthly price, or a clean handover to your own team.

Agency, freelancer or in-house team?

An agency isn't always the right answer. A good freelancer is perfect for a small, well-defined job. A permanent team makes sense once software sits at the center of your business and changes every week.

Who should build it?

Freelancer

Time to start
Days
Skills on hand
One person's
Cost of a first version
Lowest
Where the knowledge lives
With the freelancer
Best for
Small, clear tasks

Agency

Time to start
Days to weeks
Skills on hand
Design, build and testing
Cost of a first version
Medium
Where the knowledge lives
Shared and documented
Best for
A first product or a large build

In-house team

Time to start
Months of hiring
Skills on hand
Whoever you hire
Cost of a first version
Highest, with salaries
Where the knowledge lives
In your company
Best for
Core software that changes weekly

Is outsourcing good or bad?

Neither. It goes well when ownership, communication and testing are clear, and badly when they aren't. The time zone matters less than whether things get written down.

Plenty of companies start with an agency and hire their own developers later. If that might be you, ask for documentation and a handover plan in the contract. A good agency will agree without blinking.

Questions people also ask

How much does custom software cost?

It depends on scope more than anything else, which is why a fixed price before any discovery is a warning sign. We scope a first useful version after a short discovery and give a fixed price for that phase.

Who should own the code?

You. The code, the repositories, the cloud accounts and the app store listings should be in your company's name from the start, even if the agency does all the work.

How do we compare quotes from different agencies?

Line them up feature by feature and check what each one leaves out. Testing, design, deployment and support are the usual gaps. A cheaper quote that skips testing usually costs more by the end.

Related service

Custom SoftwareCustom software development for growing companies: web platforms, client portals, internal tools, admin panels and APIs, built around your processes and connected to your systems.See the service

Have a project in mind? We'll tell you honestly if we're the right fit.

Talk to us

More articles

What we learn building AI, sent to your inbox

Our newsletter

Practical AI notes for growing businesses. One email a month.