How to Choose a Software Development Agency

Most software shops fall into one of three structures. The differences matter more than the websites suggest.

You manage the project; they supply the engineers. Cheaper hourly rate, but you own scope, process, and outcomes. Good if you have engineering leadership in-house and just need hands. Bad if you’re a non-technical founder.

A small senior team that owns projects end to end. Higher hourly cost, but they bring product judgment, design, and engineering together. Good if you need a partner, not just builders. This is Heartwood’s category. We work with mission-driven nonprofits, faith-rooted organizations, and scaleups who need senior engineering judgment without enterprise overhead.

Hundreds or thousands of staff, multiple delivery centers, layered project management. Good for large, complex, multi-quarter programs. Bad if you’re under $500K — you’ll pay for overhead you don’t need.

Most agencies will happily build whatever you describe. The good ones make sure you’ve described the right thing. Walk into evaluation knowing the business outcome you’re buying — revenue, retention, efficiency, compliance — not the feature set. The agency’s first question should be about that outcome.

Pull two or three case studies. Ask what was hard, what they got wrong, what they’d do differently. An agency that can’t tell you about a project that went sideways doesn’t have enough scar tissue to be useful. The interesting case studies aren’t the wins; they’re the recoveries.

Free pitches incentivize fast, generic proposals. A paid discovery — even a $2,500 one-week sprint — produces a real plan you can compare across vendors and use as a hiring artifact even if you walk away. This is the single highest-leverage move in the entire process. The agencies that resist it are usually the ones you don’t want.

Ask: “What should we not build?” Ask: “Where is our scope unrealistic?” Ask: “What would you do with this budget if you were us?” An agency that gives you back a smaller, sharper plan than the one you walked in with is showing you their judgment in real time. An agency that just nods is selling you the project they want, not the project you need.

Who owns the code? (You.) Who owns the IP? (You.) What does documentation look like at the end? (Real, written, in your repo.) If the answers are vague, the lock-in is the business model.

Ask which engineers, designers, and PMs will work on your project. Get names. Ask whether any of the work will be subcontracted, and to whom. The bait-and-switch (senior engineer in the pitch, junior engineer in the build) is the #1 staffing complaint across software-buyer surveys.

“Were you happy?” gets you nothing. Ask: What surprised you? What did they push back on? Did they ever tell you no? Did they stay after launch? Would you hire them again knowing what you know now? The most useful reference is the one that ended.

Run a paid pilot — a Clarity Sprint, a discovery week, a small first milestone. You will learn more in a paid two-week pilot than in three rounds of sales calls. This is also when you find out whether they communicate well at the speed your business needs.

Eight signals that predict trouble:

• Fixed-price quote on day one — for a system that doesn’t yet exist on paper. They’re either underestimating (and you’ll pay in change orders) or padding (and you’ll overpay).
• No discovery process or a discovery that’s actually a sales pitch in disguise.
• No questions about your business — only questions about your features.
• Subcontracting they don’t disclose.
• A team you’ll never meet until kickoff.
• Lack of senior engineering leadership in the room. If a salesperson is the most technical person you’ve talked to, walk.
• No conversation about what happens after launch.
• Pressure tactics, urgency framing, or “expiring” pricing on a six-figure decision.

The 2024 Deloitte Global Outsourcing Survey found cost has fallen from the #1 outsourcing driver (70% in 2020) to just 34% in 2024 — replaced by access to specialized talent (42%) and meeting customer demand (35%)[6]. The smartest buyers in 2026 select for fit and durability, not price.

1. What kinds of projects do you say no to, and why?
2. Walk me through a project that went badly. What did you learn?
3. Who specifically will work on this project, and at what staffing level?
4. What’s the smallest version of this we could ship, and why might that be the right answer?
5. What does discovery cost, and what do I walk away with?
6. Who owns the code, IP, and documentation at the end?
7. What happens after launch — what does ongoing support look like?
8. How do you handle scope changes mid-project?
9. Can I talk to a client whose project ended without a renewal?
10. What would you do with our budget if you were us?

The answers will tell you more than any pitch deck.

Hiring the wrong agency creates technical debt that follows you for years. Companies estimate technical debt at 20–40% of their entire technology estate, and 86% of IT executives report tech debt impacted their company in the past year[7]. Per Stripe’s Developer Coefficient, 42% of professional developer time goes to managing technical debt[7]. Bad code today is bad code your future team is paying for.

This is why partnership posture beats project posture. The 2024 Deloitte survey found 40% of firms are expanding outsourcing contracts and shifting to outcome-based models — buyers are voting with renewals, not RFPs[6]. The agencies worth working with are usually the ones still answering your texts a year after launch.

We’re a boutique studio. We’re partial to long relationships, paid discoveries, and small first builds that prove the path forward. We say no to a lot — not because we don’t want to work hard, but because we want the right work. We’d rather tell you the hard truth than sell you something you don’t need.

We have a name for this: Irrational Care. We care more than makes sense on paper. That’s not a tagline. It’s a daily practice. It looks like sending a handwritten note after a kickoff call. Flying in for a meeting when a video call would’ve been fine. Losing sleep over your architecture because we know how much is riding on it. We believe the best work happens when someone is emotionally invested in the outcome, not just contractually obligated to deliver it.

If you want to test that, our Clarity Sprint is a one-week paid discovery, starting at $2,500, that produces a prioritized feature roadmap, a technical architecture recommendation, a risk and feasibility assessment, a go/no-go recommendation with rationale, and a written brief you can hand to any dev team. Whether or not we end up building it together. We’d rather earn the next phase than assume it.

If software can help you set your corner of the world right, we’d love to hear about it. See how we partner, or read the founder’s letter.