By the time you are choosing who builds your website, store or app, you have usually done the hard thinking: you know what you need and roughly what it is worth to you. The last step is picking a partner you can trust with it. This guide gives you the questions that separate a good fit from an expensive lesson, the warning signs to watch for, and a checklist to make sure you own what you pay for.

Questions worth asking

Any developer or agency worth hiring will be glad you asked these. Listen for specific, plain answers.

  • Can I see something similar you have built, and talk to that client? A live site you can test beats a screenshot.
  • How will you plan the project before building it? Look for a written scope, a structure for the data and integrations, and milestones.
  • What will I see along the way? Working features to review every week or two are far better than one big reveal at the end.
  • What happens if I want to change something mid-project? A good answer: you get a price for the change before any work on it starts.
  • How will you measure speed and quality? Ask which tools they use, and whether you can run them yourself.
  • Who owns the code, the domain and the accounts? The only right answer is you.
  • What happens after launch? Ask who fixes problems, how quickly, and what ongoing care costs.

Warning signs

  • A firm price before anyone has asked about your business, your data or your integrations.
  • No written scope, or a scope so vague that every request becomes an argument.
  • The domain, hosting or code registered in their name rather than yours.
  • Months of silence between kickoff and launch, with nothing to review in between.
  • Speed and search claims with no way for you to check them.
  • A platform or plugin stack chosen because it is what they always use, not because it fits you.

What a good proposal includes

  • The problem, in your words. Proof they listened before they quoted.
  • Scope: what will be built, and just as important, what will not.
  • Milestones with prices: each stage, what you receive at the end of it, and what it costs.
  • Technology choices explained: why this platform, and what that means for running costs and future changes.
  • How changes are handled: priced and approved before work starts.
  • Launch and after: redirects, monitoring, training, and what support looks like.

Ownership checklist

Before you sign, make sure the agreement and the setup give you all of these:

  • The domain name registered to you, in an account you control.
  • Hosting, payment, email and analytics accounts in your business's name.
  • Access to the code repository, and the right to take the code elsewhere.
  • Admin logins for every system, with your own credentials.
  • Documentation good enough for another developer to pick up the work.

After you choose

Start with something small if you are unsure: a technical audit or the first milestone of a larger project shows you how a partner communicates and delivers before you commit to everything. Agree how you will communicate, who approves what, and when you will review progress, and put those in writing alongside the scope.