[{"data":1,"prerenderedAt":207},["ShallowReactive",2],{"insight-\u002Finsights\u002Fquestions-to-ask-your-developer-or-agency":3},{"id":4,"title":5,"body":6,"category":194,"date":195,"description":196,"extension":197,"meta":198,"navigation":199,"path":200,"readingTime":201,"seo":202,"seoTitle":203,"stem":204,"updated":205,"__hash__":206},"insights\u002Finsights\u002Fquestions-to-ask-your-developer-or-agency.md","10 questions to ask your developer or agency (no technical degree required)",{"type":7,"value":8,"toc":178},"minimark",[9,18,21,26,36,40,48,52,60,64,72,76,84,88,96,100,108,112,120,124,132,136,144,148,155,159],[10,11,12,13,17],"p",{},"One of the hardest parts of commissioning software when you’re not technical is knowing whether you’re getting good advice. The good news: you don’t need to understand the code to ask good questions. You just need to listen carefully to ",[14,15,16],"strong",{},"how"," people answer.",[10,19,20],{},"Here are ten questions I’d ask, what a good answer sounds like and what should worry you.",[22,23,25],"h2",{"id":24},"_1-whats-the-simplest-version-we-could-launch-first","1. “What’s the simplest version we could launch first?”",[10,27,28,31,32,35],{},[14,29,30],{},"Good:"," A clear, confident answer about a smaller first release, with reasons.\n",[14,33,34],{},"Worrying:"," “Well, we need to build everything properly from the start.” Big-bang builds are expensive and risky.",[22,37,39],{"id":38},"_2-what-are-the-biggest-risks-on-this-project","2. “What are the biggest risks on this project?”",[10,41,42,44,45,47],{},[14,43,30],{}," Specific, honest answers: a tricky integration, an unclear requirement, a dependency on a third party.\n",[14,46,34],{}," “There aren’t really any.” Every project has risks. If they can’t name any, they haven’t thought hard enough.",[22,49,51],{"id":50},"_3-can-you-explain-that-without-the-jargon","3. “Can you explain that without the jargon?”",[10,53,54,56,57,59],{},[14,55,30],{}," They happily rephrase and use analogies.\n",[14,58,34],{}," They get defensive or just repeat it louder. If someone can’t explain it simply, you can’t make an informed decision.",[22,61,63],{"id":62},"_4-who-owns-the-code-the-designs-and-the-hosting-accounts","4. “Who owns the code, the designs and the hosting accounts?”",[10,65,66,68,69,71],{},[14,67,30],{}," “You do. Everything lives in your accounts.”\n",[14,70,34],{}," Vague answers, or code hosted only on their systems. You should never be locked in because someone holds the keys.",[22,73,75],{"id":74},"_5-how-will-we-know-how-its-going","5. “How will we know how it’s going?”",[10,77,78,80,81,83],{},[14,79,30],{}," Regular, visible progress: working software you can try every week or two, not just status reports.\n",[14,82,34],{}," Silence for weeks, followed by “nearly there!”",[22,85,87],{"id":86},"_6-how-do-you-test-it-and-how-do-you-deploy-changes","6. “How do you test it, and how do you deploy changes?”",[10,89,90,92,93,95],{},[14,91,30],{}," Mentions of automated tests, a staging site to try things before they go live and a repeatable way to release.\n",[14,94,34],{}," “We test it manually” or “we just upload the files.” It works until it doesn’t, usually at the worst possible moment.",[22,97,99],{"id":98},"_7-what-happens-when-something-breaks-after-launch","7. “What happens when something breaks after launch?”",[10,101,102,104,105,107],{},[14,103,30],{}," A clear support arrangement: who to contact, how quickly they’ll respond and what it costs.\n",[14,106,34],{}," “We’ll sort something out.” Software needs looking after; you want to know how before you need it.",[22,109,111],{"id":110},"_8-what-will-it-cost-to-run-and-maintain-not-just-to-build","8. “What will it cost to run and maintain, not just to build?”",[10,113,114,116,117,119],{},[14,115,30],{}," A realistic view of hosting, licences and maintenance, including what’s likely to change as you grow.\n",[14,118,34],{}," Only talking about the build price. The running costs are where surprises hide.",[22,121,123],{"id":122},"_9-whats-not-included-in-this-quote","9. “What’s not included in this quote?”",[10,125,126,128,129,131],{},[14,127,30],{}," A clear list of exclusions and assumptions, with how changes will be handled.\n",[14,130,34],{}," “Everything’s included!” (Then the quote’s probably vague, and the scope arguments will come later.)",[22,133,135],{"id":134},"_10-what-would-you-do-if-it-were-your-money","10. “What would you do if it were your money?”",[10,137,138,140,141,143],{},[14,139,30],{}," A thoughtful answer, even if it means building less, spending less or using an existing product.\n",[14,142,34],{}," Every answer happens to involve more work for them.",[22,145,147],{"id":146},"how-to-use-this-list","How to use this list",[10,149,150,151,154],{},"You don’t need to ask all ten, or to grade the answers like an exam. Just pay attention to whether you come away ",[14,152,153],{},"understanding more",", and whether the person seems more interested in solving your problem than in selling you a project.",[22,156,158],{"id":157},"when-you-want-a-second-opinion","When you want a second opinion",[10,160,161,162,167,168,172,173,177],{},"If you’ve got a quote, a proposal or a half-built project and you’re not sure whether it’s sensible, an independent ",[163,164,166],"a",{"href":165},"\u002Fservices\u002Ftechnical-audit","technical audit"," gives you a plain-English view of what’s good, what’s risky and what to do next. And if you’d like someone senior on your side throughout, that’s what a ",[163,169,171],{"href":170},"\u002Fservices\u002Ffractional-cto","fractional CTO"," is for. Or simply ",[163,174,176],{"href":175},"\u002Fcontact?topic=audit","get in touch"," and tell me what’s going on.",{"title":179,"searchDepth":180,"depth":180,"links":181},"",2,[182,183,184,185,186,187,188,189,190,191,192,193],{"id":24,"depth":180,"text":25},{"id":38,"depth":180,"text":39},{"id":50,"depth":180,"text":51},{"id":62,"depth":180,"text":63},{"id":74,"depth":180,"text":75},{"id":86,"depth":180,"text":87},{"id":98,"depth":180,"text":99},{"id":110,"depth":180,"text":111},{"id":122,"depth":180,"text":123},{"id":134,"depth":180,"text":135},{"id":146,"depth":180,"text":147},{"id":157,"depth":180,"text":158},"Working with developers","2026-10-22","Not technical? These ten plain-English questions help you spot good (and worrying) answers from the developers or agencies building your software.","md",{},true,"\u002Finsights\u002Fquestions-to-ask-your-developer-or-agency",7,{"title":5,"description":196},"10 Questions to Ask Your Developer or Agency | Chris Mackie","insights\u002Fquestions-to-ask-your-developer-or-agency",null,"35WUxf983MWdR5ZmAjENk4uqEMXfLkySmJTHsNjrRoc",1793821334889]