Before You Hire an Agency

The pitch deck was polished. The timeline was aggressive. The price felt right. Six months later, they owned the code and the founder owned the problem.

I’ve seen this pattern more times than I’d like. A non-technical founder needs software built, so they hire an agency. It makes sense. You don’t have engineers, you don’t know what good looks like yet, and someone is telling you they can have it ready in twelve weeks.

But here’s what most founders miss: you’re not buying software. You’re buying a relationship with someone else’s priorities. The agency’s incentive is to deliver something that looks finished. Your incentive is to own something you can build on. Those aren’t always the same thing.

Watch for the signals. A fixed bid on a vague scope means someone is going to eat the difference, and it won’t be them. A “proprietary framework” means your next team will need to learn their system before they can touch yours. No access to source code until final delivery means you’re negotiating from a position you didn’t agree to.

The question that cuts through all of it: what happens when this engagement ends? Do you walk away with something your next engineer can pick up and extend? Or do you walk away with a dependency on the team that built it?

The best agencies want you to outgrow them. They write clean handoffs into the contract. They use standard tools. They insist on putting you in front of your own users. They’re building something for you, not something that needs them.

Before you sign that check, make sure you’re buying an asset and not a lease.

What’s the most important lesson you’ve learned working with an outside development team?