Most bad website projects are lost at the hiring stage
The common failure is not a vendor who cannot build. It is a mismatch that was visible before anyone signed: unclear scope, an hourly rate against an undefined project, no agreement about who owns what, and no way to see the result before the money is gone.
These are the questions that surface those problems early.
1. Is the price fixed, and what changes it?
Hourly billing means the vendor is paid more when the project runs long. That is not dishonesty, it is just a misaligned incentive. A fixed price moves schedule risk to the vendor, which is why fixed-price vendors ask harder scoping questions up front.
If the quote is fixed, ask exactly what triggers a change order and get it in writing. "Extra pages beyond eight" is a clear trigger. "Significant additional work" is not.
2. When exactly do I pay, and what do I see first?
Standard practice is a deposit up front and the balance on launch. The question worth asking is what you actually get to see before the balance is due. A design mockup is not a website. Ask whether you will see the real, working site on a real device before you pay it off.
Any vendor confident in their work should be comfortable showing it to you before asking for the rest.
3. Do I own everything?
Get explicit answers on three things: the domain must be registered in your name, the content must be yours, and you must be able to take the site elsewhere. Some vendors register the domain themselves and some build on proprietary platforms you cannot leave. Both turn a website into a subscription you cannot cancel.
4. What happens to my search rankings?
If you already have a site that gets found, replacing it without redirecting every old URL to its new equivalent will cost you rankings you spent years earning. Ask specifically: will you set up 301 redirects for every existing page? If the answer is vague, that is a real risk and it is expensive to undo.
5. Will this meet WCAG 2.2 AA, and will I get the report?
Most vendors will not raise accessibility with you. There were 3,117 federal web accessibility filings in 2025, 64% of accessibility suits target companies under $25M, and roughly 94.8% of sites currently fail. Asking this question tells you a great deal about how thorough a vendor is, whatever answer you get.
6. Who actually answers when something breaks?
Ask who you email, and what a realistic response time looks like. A named person beats a ticket queue. Ask what happens after launch if the contact form stops delivering: is that a support request, a billable change, or covered?
7. Can I see three sites you built that are still live?
Live, not screenshots. Then check them yourself: load one on your phone, submit a contact form, run a page speed test. A portfolio image proves a design existed. A live site proves it works.
Also look at reviews, and look at the pattern rather than the average. Surveys of small business owners consistently find that buyers trust a vendor with twenty reviews and a 4.7 more than one with three reviews and a perfect score. A vendor with no reviews at all is the actual warning sign.
On hiring a team outside your country
Plenty of US small businesses work with teams abroad, and the real concerns are practical rather than cultural: can you reach them during your working day, and what recourse do you have if it goes wrong.
Ask for specific working hours in your own timezone rather than a promise to be responsive. Ask whether the contract can be governed by your state's law. And weight the preview question even more heavily, because seeing the finished work before paying the balance removes most of the risk that distance creates.
The shortest version
If you only ask two things, ask whether the price is fixed in writing, and whether you can see the finished site before you pay for it. A vendor who says yes to both has already told you how they work.