Most of what separates a good engagement from a bad one shows up before any code is written — in how an agency answers these.
Who's doing the work
- Who is the named technical lead, and are they an employee or a contractor?
- What else is that person working on during our build?
- Can I see apps you shipped that I can actually download and use — not screenshots?
- Which parts of that portfolio app did you build, versus subcontract?
What happens when something goes wrong
- What's your process for scope changes mid-project?
- If we're not happy with a milestone, what happens? (Ours: fixed free or refunded — see our guarantee.)
- Can I speak to a past client about budget and timeline accuracy, not just the finished product?
- What's your QA process — who tests, and how?
Ownership and the exit
- Who holds the code repository during and after the project?
- Is IP assignment explicit in the contract, or implied?
- What do I walk away with if we end the relationship early?
Whether they actually think about trade-offs
- What technology would you reconsider on a past project, and why?
- How do you handle security — specifically, not "the host handles it"?
- Do you quote a price before or after understanding the full scope?
- What's in writing before any money changes hands?