What questions should I ask a software agency to avoid getting burned?

The questions that separate trustworthy agencies from risky ones

U.S. founders and operators lose millions each year to software projects that go over budget, miss deadlines, or deliver code they can't maintain. Most of those situations were predictable. The right questions — asked before you sign — surface the warning signs early.

Ownership and legal

• Who owns the IP when the project ends? In the U.S., work-for-hire agreements transfer IP to the client, but this must be explicit in the contract. If the agency hedges, walk away.
• Will you sign an NDA before we discuss the project? A professional agency should say yes without negotiating the ask to death.
• Do you use any open-source components that carry copyleft licenses (GPL, LGPL)? These can restrict how you distribute your product commercially.

Team and execution

• Who exactly will build my product — your staff or subcontractors? Many agencies front-sell senior engineers and deliver junior offshore contractors. Ask for LinkedIn profiles and insist on meeting the actual team.
• What is your process when a key developer leaves mid-project? Turnover happens. A mature agency has a documented handoff process; a risky one goes quiet.
• Can I see examples of production code or speak with past clients directly? References you can call — not just curated case studies — matter far more in the U.S. market where accountability is expected.

Scope, pricing, and timelines

• How do you handle scope changes, and what triggers a change order? Vague answers here predict budget blowouts. Get a written change-order policy before you start.
• Is pricing fixed-fee, time-and-materials, or milestone-based? Each model has tradeoffs. Fixed-fee protects your budget but can incentivize corner-cutting; T&M gives flexibility but transfers cost risk to you. Milestone-based pricing — where payments are tied to delivered, testable features — aligns incentives on both sides.

Post-launch and continuity

• What does handoff look like — do we get full source code, documentation, and credentials? Some agencies retain repo access or hosting credentials as implicit lock-in. Demand full handoff in writing.
• What is your warranty or bug-fix policy after go-live? Industry standard in the U.S. is a 30–90 day defect-warranty period at no extra charge. Anything shorter is a red flag.

A practical filter

Treat the sales conversation itself as a test. Agencies that push back on detailed questions, rush you to sign, or can't explain their own process clearly are showing you exactly how they will behave under project pressure.

CodeNicely, for example, operates under an NDA-first, milestone-based model with full IP ownership transferred to clients — worth knowing if you are evaluating options. But any reputable agency should be willing to match these basics; hold all of them to the same standard.