A lot of business owners arrive at a conversation with a new developer already guarded, and usually for good reason. Somewhere in the past there was an agency that overpromised, buried every question in jargon, went quiet for weeks at a time, and then made leaving so painful that staying felt easier. Or they have watched it happen to someone they know, which teaches the same lesson.
The uncomfortable truth is that buying software or a website is a trust purchase. You cannot inspect the goods before they exist, you probably cannot read the code afterwards, and the person selling knows far more about the subject than you do. That gap is where bad agencies live. The way to protect yourself is not to become a technical expert, it is to ask questions whose answers you can judge as a businessperson.
Here is the list. Ask every one of these of anyone you consider hiring, including us.
The questions that matter
Who owns the code, the domain, the hosting accounts and the content when we part ways? Ask this first, because everything else depends on it. The answer should be immediate and unambiguous: you do, all of it. Be suspicious of anything hedged, anything involving a licence to use your own website, or anything that requires a payment to release your own assets. The domain deserves particular attention. If an agency registers your domain in their own name, they own your front door, and every future negotiation happens with their hand on the lock.
Can I show you something you built that is still running years later? Portfolios show launch day, when everything gleams. What you want to see is year three. A site or system that is still live, still maintained and still serving the same client tells you the work was built to last and the relationship survived contact with reality. If everything in the portfolio is recent, ask what happened to the older work.
Who exactly does the work? Many agencies sell a polished front and quietly outsource the building, sometimes several layers deep. There is nothing wrong with subcontracting done openly. There is a great deal wrong with discovering it after launch, when the person who actually wrote your system is unreachable and the agency you paid cannot answer detailed questions about it. Ask who writes the code, who you will speak to when something breaks, and whether those are the same person.
What happens after launch, and what does support actually cost? Launch is the beginning of the site’s life, not the end of the project. Get the ongoing arrangement in writing before you sign anything: what hosting costs, what updates cost, what a small content change costs, and how quickly they respond when something is wrong. Vague answers here become invoices later.
Tell me about a time something went wrong. Ask for a real incident, not a platitude about processes. Anyone who has run software in production has a story about a bad day, and how they tell it is revealing. You want to hear what broke, how they found out, what they told the client and when. Someone who claims nothing ever goes wrong is either very new or not being straight with you.
Will you explain decisions in plain English? Test this in the first meeting by asking why they would choose one approach over another. If the answer is a wall of acronyms, that is a preview of every future conversation, and jargon has a way of functioning as a pricing strategy. You should not need a translator to supervise your own project.
The red flags
Some warning signs are reliable enough to act on regardless of how charming the pitch is.
A detailed quote produced with no discovery phase means one of two things. Either the number is guesswork that will be corrected later through change requests, or you are being sold a template with your logo on it. Nobody can price work they have not scoped.
The word “unlimited” attached to anything, revisions, support, changes, is a marketing device, and the limit appears the first time you rely on it.
A refusal to provide references, or references who all turn out to be from the last six months, tells you how earlier relationships ended.
Hosting bundled into the contract so tightly that leaving means rebuilding from scratch is a structural trap, however reasonable the monthly figure looks. So is any contract under which the agency owns or registers your domain.
Any arrangement that is painful to leave was designed that way.
None of these red flags requires technical knowledge to spot. They are visible in the paperwork and the conversation, which is exactly where an owner is qualified to judge.
What price actually tells you
Cheapest and dearest are both signals, and both deserve interrogation rather than instinct.
A quote far below the others usually means corners you cannot see: a template presented as bespoke, work passed to the lowest bidder, or a loss-leading build priced to be recouped through captive hosting and support fees. The build is the hook, and the ongoing relationship is where the money was always going to be made.
A quote far above the others might mean genuine depth, or it might mean you are paying for the agency’s office and pitch team. The number alone cannot tell you which.
The question that cuts through price is what happens when something breaks. Who answers, how quickly, at what cost, and do they already know your system or will they be reading it for the first time on your emergency? A middling quote with a clear, honest answer to that question is worth more than the cheapest build ever delivered, because you live with the answer for years and the build price only once.
What to do about it
Turn this into a routine rather than a mood. Ask every candidate the same six questions, in writing where you can, and keep the answers. Written answers have a wonderful way of making evasion visible, and they give you something to point at later.
Actually ring one reference, and ask them the year-three questions: is it still running, do they still respond, what did the last problem cost?
Before signing, check the practical details yourself. Confirm the domain is registered in your name, not the agency’s. Confirm you will hold the logins to your own hosting and analytics accounts. Get the ownership position stated plainly in the contract, not implied.
Compare quotes only after each firm has done some genuine discovery, so you are comparing considered prices rather than opening bids. And weigh how each candidate explains things at least as heavily as what they promise, because the explaining is what the next five years will feel like.
The partner test
A good partner will welcome this list. The questions cost an honest firm nothing, because the honest answers are already their standard practice, and the same questions cost a bad firm the deal. We publish this knowing prospective clients will use it on us, which is rather the point. A promise of no lock-in only means something if you can verify it before you sign, and every item above is verifiable.
Flux Dynamics is a fractional-CTO-led software consultancy built on the principle that clients own their code, domain and data from day one. Start a conversation and put every question on this list to us first.