Every week we speak to business owners who have already been burned once. A developer disappeared mid-project. An agency delivered a site that does not work on mobile. A freelancer quoted £300 and then asked for another £800 to “finish” the project. None of this is unusual — and almost all of it is avoidable if you know what to look for before you pay anyone a penny.

This guide is not about pushing you toward any particular type of developer. It is about giving you the questions, red flags and realistic expectations that separate a good hiring decision from an expensive mistake.

Freelancer vs Agency vs Remote Team — What’s Actually Different

Before getting into questions and red flags, it helps to understand the three main types of developer you can hire, because the right questions differ slightly depending on who you are talking to.

Solo freelancers

One person handling everything — design, development, sometimes content. Typically the most affordable option, with hourly rates between £25 and £75 depending on experience and location. The upside is direct communication with the person actually doing the work. The downside is a single point of failure: if they get sick, get busy with another client, or simply disappear, your project stalls with no backup plan.

Traditional agencies

A full team — account manager, designer, developer, project manager — operating under one company. Rates are typically £75 to £150 per hour, with minimum project budgets often starting at £2,000 to £5,000. You get formal accountability and a structured process, but you often end up talking to an account manager rather than the people actually building your site, and junior developers sometimes do the bulk of the work despite senior-level pricing.

Specialist remote teams

A middle ground that has become increasingly common — a coordinated team of specialists (often distributed across different countries) operating with the structure of an agency but the pricing closer to a freelancer. This model gives you genuine specialist expertise across design, development and SEO without the overhead costs of a traditional agency office. The trade-off is that you need to verify the team is genuinely coordinated and accountable, not just a loose collection of outsourced contractors.

The 7 Questions You Must Ask Before Hiring Anyone

These questions work regardless of whether you are talking to a freelancer, agency or remote team. How someone answers them tells you almost everything you need to know.

1. “What exactly is included in this price?”

“A website” is not a deliverable. You need a specific breakdown — number of pages, what functionality is included, whether SEO setup is part of the package, how many rounds of revisions you get. Vague answers here predict vague (and expensive) surprises later.

2. “What is NOT included?”

This is the question most people forget to ask, and it is often more revealing than the first one. Hosting? Domain registration? Stock photography? Content writing? Ongoing maintenance? A good developer will volunteer this information without being asked. A developer who gets evasive here is setting you up for additional invoices later.

3. “Who will actually be building my website?”

Some agencies sell you on senior expertise during the sales call, then quietly hand the actual work to a junior team member or an outsourced subcontractor you never meet. There is nothing inherently wrong with a coordinated team approach, but you deserve to know who is doing the work and what their experience level is.

4. “What is the timeline, with milestones?”

“A few weeks” is not a timeline. You want specific milestones: design approval by date X, development complete by date Y, testing and revisions by date Z, launch by date W. Specific timelines with milestones indicate a developer who has actually planned the project, not someone guessing.

5. “What happens after my website launches?”

This question separates developers who think long-term from those chasing a quick sale. What support is included? What does it cost to fix a bug six months from now? Is there an ongoing maintenance option? A developer who has clearly thought through the post-launch relationship is signalling they intend to be around.

6. “Will I own my domain, hosting and admin access?”

This should always be yes, without hesitation. Some developers register domains or hosting accounts under their own credentials — meaning they effectively control your website and you are permanently dependent on them. Always insist on owning your own digital assets from day one.

7. “Can I see live examples of similar work?”

Not screenshots — live, working URLs. Click around. Check if it works on your phone. Check if it loads quickly. A portfolio of beautiful screenshots means very little if the actual live sites are slow, broken or no longer exist.

8 Red Flags That Should Make You Walk Away Immediately

• Refusing to give a fixed price before starting. Vague “we’ll see how it goes” pricing on a defined project (not an open-ended retainer) is a sign of either inexperience or deliberate ambiguity.
• Demanding full payment upfront. A reasonable structure is 30–50% deposit, with the remainder due on milestones or completion. Anyone asking for 100% before starting any work is asking you to take on all the risk.
• No live examples of past work — only screenshots. If every portfolio piece is a static image with no working URL, ask why. Sometimes there are legitimate reasons (client confidentiality), but it should be the exception, not the rule.
• Registering your domain or hosting under their account. This is one of the clearest signs of a developer who wants to keep you dependent on them rather than genuinely serve your business.
• No written contract or agreement. Even a simple one-page agreement covering scope, price, timeline and ownership protects both parties. Verbal-only agreements protect no one.
• Pressure to decide immediately. “This price is only available today” tactics have no place in a considered business decision like hiring a web developer.
• Unwillingness to explain technical decisions in plain English. A good developer can explain why they recommend WordPress over Wix, or React over a simple HTML site, in language you understand. Hiding behind jargon to avoid explaining is a warning sign.
• Reviews that feel generic or cannot be verified. Check reviews on independent platforms like Google or Clutch, not just testimonials curated on the developer’s own website.

What Fair Pricing Actually Looks Like in 2026

Pricing varies by region, but here are realistic global ranges based on projects we deliver for clients across the UK, USA and beyond.

How to Actually Evaluate a Portfolio (Not Just Look At It)

Most people glance at a portfolio and judge it purely on visual appeal. That tells you almost nothing about whether the developer can actually deliver a functioning, fast, secure website. Here is how to evaluate properly.

• Click through to live sites, not just images. Open them on your phone. Check if menus work, forms submit properly and images load quickly.
• Check loading speed. Use a free tool like Google PageSpeed Insights on 2–3 of their portfolio sites. A pattern of slow sites across their portfolio tells you something important.
• Look for variety relevant to your project. If you need an ecommerce store, a portfolio full of static portfolio sites with no ecommerce examples is a gap worth asking about directly.
• Check if the sites are still live and maintained. A portfolio full of dead links or outdated, abandoned-looking sites suggests clients did not stick around for ongoing work — worth asking why.

What Needs to Be in Writing Before Work Begins

You do not need a 20-page legal document for a £400 website. But a few essential points should always be confirmed in writing — even a simple email exchange counts, as long as both parties have agreed to it clearly.

• The total price, and exactly what it includes and excludes
• The payment schedule — deposit amount, milestone payments, final payment
• The timeline, ideally with specific milestone dates
• Confirmation that you will own the domain, hosting account and all admin credentials
• What happens if the project runs over time or scope changes are requested
• What post-launch support is included and for how long