How to choose a software development agency (without going broke)

Choosing a development agency is one of the most expensive decisions a small business or startup makes, and it is usually made with little information. Every agency shows a nice portfolio, every agency says it works with agile methodology and every agency promises to deliver on time. The difference is in what they ask before selling and what they put in writing afterwards.
This guide is not about finding the cheapest agency, but about avoiding the most expensive one: the one that leaves you with a product you cannot maintain and code you do not own.
Ten questions that separate an agency from a salesperson
- Who will be the technical lead on the project and how many projects do they run at once?
- What part of the work is done in-house and what part is subcontracted?
- How do you estimate, and what exactly does the estimate include?
- Can I see a working product demo, not just screenshots?
- Who owns the code and intellectual property when the project ends?
- What happens if I want to change provider? Do you hand over the repository, documentation and access?
- How do you handle scope changes and what do they cost?
- What warranty is there after delivery and what does it cover?
- How do you test, and what test automation exists?
- Can you give me two clients I can talk to, not two logos?
Red flags
- A price well below market without reducing scope: someone pays for it later.
- No questions about the business: they start talking about technologies on the first call.
- No contract, or a contract that does not clarify ownership, deadlines and exit.
- A portfolio that only shows screens, never results or live products.
- Promising full availability and unlimited changes for a fixed fee.
- Not making clear who executes: the salesperson who sells never appears again.
- Pressure to sign "this week" because the rate changes.
- They cannot explain what happens if the project is delayed or a requirement turns out to be unfeasible.
Look at the process, not the portfolio
A portfolio proves they delivered something, not how they do it. Ask about the process: how they go from an idea to a scope, how they estimate, how they show progress, how they test and how they document. A serious agency shows you a real board, a repository with history and a demo that works. A sales-driven agency shows you a presentation.
The contract: what cannot be missing
Want to optimize your technology?
We design and build bespoke AI automation pipelines and cloud architectures.
- Intellectual property and code ownership from the first payment, not only at the end.
- Scope by milestones and written acceptance criteria.
- Payment tied to deliverables, not everything upfront.
- A scope-change procedure with price and timeline.
- A warranty for bugs after delivery and a fix window.
- Confidentiality and data processing (GDPR if personal data is involved).
- Exit terms: repository, documentation, access and handover.
- What happens if the agency closes or the key person leaves.
How to validate the technical side without being technical
- Ask for an independent architecture review before signing a large project.
- Hire a fractional CTO to sit on your side of the table and ask the questions you cannot ask.
- Start with a small pilot and measure how they work before committing the annual budget.
- Ask for access to a real repository and check that there are tests, documentation and a coherent commit history.
- Call two references and ask what went wrong, not only what went well.
Price is not the same as cost
The cheapest proposal is often the most expensive after two years: code without tests, dependency on one person, no documentation and a migration that costs more than the original project. Compare total cost: development, maintenance, changes, handover and risk. A €5,000 difference in the proposal can be a €30,000 difference in the future invoice.
Conclusion
A good agency does not sell you technology: it helps you decide what to build and tells you when something is not worth it. If they ask about your business, show live products, sign a clear contract and accept an independent technical review, you are on the right track. If everything is urgency and promises, keep looking.
Fractional CTO: technical leadership without a full-time CTO salary
I take on the technical leadership of your product by the hour or by the day: architecture, stack decisions, team hiring and roadmap. You focus on the business; I make sure technology is not what slows you down.
See the serviceRelated Articles
Full-time CTO vs fractional CTO: when to hire each
An honest comparison between a full-time CTO and a fractional CTO: what each does, what they cost, when you need each and how to move from one to the other.
How much does a fractional CTO cost in 2026? Real prices and what is included
Fractional CTO price ranges in Spain for 2026: hourly or retainer, what each model includes and how to compare proposals without overpaying.

Tomás Ledesma
Tomás Ledesma is a software architect and technical consultant specializing in intelligent process automation, scalable cloud architectures, and cross-platform app engineering.