Everything you need to know to hire the right web developer without getting burned

1. Do you need a web developer?

Before you hire anyone, ask whether you need a developer at all. Plenty of businesses hire developers when a website builder would have done the job fine. Plenty of others use website builders when they needed a developer instead and spend years paying the price in performance, limitations, and eventual migration costs.

For a purely informational site, such as name, services, contact details, perhaps a gallery, Squarespace or Wix is a legitimate choice if you can maintain it yourself. A $17–$23 monthly plan provides a basic online presence (as of mid-2026).

Self-maintenance changes when you need custom booking, portals, calculators, payment logic or CRM integration. Unsupported features require plugins with subscriptions/security/compatibility risks, or a developer adapting a platform never designed for them.

Leaving later means rebuilding: you rent platform access, not portable code. Faster hosting, another host or a new developer requires starting over, mapping redirects for ranked URLs and re-entering copy.

If you're on the fence, the framework at DIY website vs. hiring a developer walks through specific scenarios and gives you a structured way to think through the decision before committing either way.

2. Freelancer vs. agency vs. boutique developer

Once you've decided you need a developer, the market splits into three main categories. They're not interchangeable, and the right fit depends on your scope, budget, and how you prefer to communicate.

Freelancers range from $25/hour CS students to $150+ specialists with 15 years' experience. Match skills: WordPress-only builders may lack server logic; backend specialists can produce 2009-looking frontends. Concurrent clients, illness and weak documentation can stall work or leave a week's archaeology. Experienced freelancers offer direct access and affordable craftsmanship.

Agencies bring account/project managers, designers and frontend/backend developers with organizational backup. Salespeople rarely build; handoffs can distort layouts across browsers, while noncoding staff add overhead. For 5–10 marketing pages, quotes often reach 2–4x independent rates, with small businesses gaining little from extra coordination.

Boutiques pair direct developer access with an LLC, contracts and defined deliverables, usually one person or a small team. Unified design/development aligns layout and performance. For most small-business $2,800–$5,000 sites/apps, lower overhead, clearer communication and personal accountability make this a strong fit.

For a deeper comparison of what agency overhead costs versus what you get, the ArdinGate vs. Agency comparison breaks it down side by side.

The Freelancer vs. Agency page covers the specific tradeoffs for projects at different sizes and complexity levels, with a framework for deciding which model fits your timeline and risk tolerance.

3. Custom code vs. WordPress vs. page builders

"What platform are you building on?" ranks among the most important questions you can ask, and the answer matters far more than most clients realize going in. The platform decision affects load speed, security surface, ongoing maintenance burden, portability, and what the site can do five years from now.

WordPress powers roughly 43% of sites, showing accessibility rather than universal suitability. Its 20-year expansion from blogging creates plugin dependencies, security exposure and performance costs: 12 plugins mean 12 update cycles, conflicts and codebases to align with core releases. WordPress vs. custom explains further.

WordPress carries theme loading, plugin activation, database queries and Gutenberg markup. Good optimization can overcome this structural weight with effort. Custom PHP starts without it, consistently improving mobile speed, Google's speed-related rankings and bounce rates.

Squarespace, Wix and Webflow offer polished templates, accessible drag-and-drop and CSS control respectively. But infrastructure, hosting and proprietary designs stay platform-bound. Price changes, retired features or revised business terms force compliance or rebuilding. Custom vs. builders compares where each wins economically.

Custom code includes auditable PHP routing, HTML, CSS, forms and database queries. Move to standard PHP hosts, hand off to PHP developers or extend freely. Scratch builds cost more than templates, but the gap for 5–15 marketing pages is often modest; no plugin ecosystem substantially reduces ongoing upkeep.

4. How web development pricing works

Web development quotes confuse almost everyone who hasn't hired a developer before. Two quotes for "a 5-page website" might come in at $900 and $9,000. Neither number is necessarily wrong. They're describing fundamentally different products, even though they both technically result in a website that has five pages.

The low end generally means: a developer will install a pre-built theme, drop in your content, and do minimal customization. Fast to do, fast to price, functionally adequate. The site works, looks like the template it's based on, and is maintained via whatever update cycle the theme vendor ships.

Higher quotes often fund custom CSS/layout, built-in technical SEO/business labels, initial speed optimization and clean dependency-free PHP. That's skilled development time, not padding.

Here's what moves the number:

• Custom vs. template: Building from scratch costs more than filling in a template. Both can look good. Only one is unique, fully extensible, and free of third-party theme licensing.
• Page count and feature scope: A 3-page informational site and a 12-page site with a client portal, a quote calculator, and a booking flow are not the same scope. Writing accurate scopes is the single biggest factor in getting comparable quotes.
• Design included or not: If the developer is designing the site as well as building it, that work is additional. If you're supplying final design files in Figma or equivalent, the developer is implementing, not originating.
• Copywriting: Most developers don't write copy and most quotes don't include it. If there's no explicit line item for copywriting, you're expected to supply it. Many clients discover this on launch week when placeholder text is still sitting in final pages.
• Hosting and support structure: A one-time build, a build with managed hosting, and a build with a monthly retainer for ongoing changes are three different products with three different price structures.
• Integrations: Connecting your site to a CRM, a booking calendar, a payment processor, or a custom API is additional scope. It's not hard to miss in the initial conversation and painful to add as a surprise at the end.

Fixed project prices put estimation-overrun risk on developers; hourly puts it on you. Use fixed fees for defined scope. Hourly/retainers suit open-ended content updates, on-call support and evolving features.

The Cost Estimator lets you build out your scope and get a live range before any calls, which is useful for calibrating expectations. The Pricing page covers ArdinGate's specific tiers. Single-page builds start at $1,200. Multi-page business sites run $2,800–$5,000.

5. How to evaluate a developer's portfolio

A portfolio is your strongest signal. Unlike a discovery call, it can't be rehearsed. Here's how to evaluate it properly.

Check live sites, not curated screenshots. On your phone, assess speed, small-screen layout, unzoomed readability and breakage. Slow mobile delivery reveals performance wasn't prioritized, regardless of polished screenshots.

Run a performance check. Go to PageSpeed Insights (pagespeed.web.dev) and plug in a URL from the portfolio. Look at the mobile score specifically—mobile is where most small business traffic arrives and where page-speed performance is hardest to nail. A developer claiming to build fast, SEO-optimized sites whose portfolio scores in the 40s on mobile is showing you something important.

View Page Source by right-clicking. Clear HTML/headings indicate quality; generated classes, pervasive inline styles and five JavaScript libraries indicate builders/block editors, not custom code.

Check portfolio variety. Thirty WordPress sites sharing layout, fonts and sections can mean one theme deployed 30 times. Ask each platform and whether themes were written or purchased.

Ask to talk to a past client. Have a conversation, beyond a developer-selected testimonial. Ask about the process, communication, whether the delivered site matched promises, and scope or billing surprises. Confident developers connect you without hesitation.

6. Red flags to watch for before you sign anything

Most web project failures are predictable. These patterns appear before the contract is signed, but clients often don't know what to watch for.

• No business discovery. Initial questions should cover work, customers, visitor goals and current problems. Color-first questions or proposals before discovery suggest decoration without a business solution.
• Require a contract with IP terms: full source on completion/final payment, unrestricted ownership, hosting and maintenance rights. Hosting promises without code delivery create dependency, not ownership.
• A portfolio that's all one template or all one client type. Repetition at scale is a sign of a template deployer, not a developer. Ask how each portfolio site was built. If the answer for every project involves the same premium WordPress theme or the same Elementor layout, you're getting a template with your logo swapped in.
• Require plain-language technical reasoning. Portable, dependency-free PHP and faster loading for your use case explain a choice. "Best practices" or "always used it" don't.
• Own your registrar account. Domain registration in a developer's account without explicit consent gives them leverage; transfer immediately. Managed hosting is normal if source files remain portable. Domain control and locked source are the risks.
• Unlimited revisions can encourage rushed sign-off or endless, resentful projects. Specify rounds instead: two included design rounds, further revisions hourly.

See what to look for in a web developer contract for a full breakdown of the clauses that protect you and the ones that protect only the developer.

7. What belongs in the contract

A web development contract doesn't need to be 30 pages, but it needs to explicitly address what causes disputes. Most project conflicts come down to one of four issues: scope, IP, payment, or timeline. A solid agreement covers all four before work starts.

• IP and code delivery. All deliverables become your property on final payment. The contract should say this explicitly. The developer retains rights to their own pre-existing code libraries and internal tools, but everything built for this project is yours — hosted wherever you choose, modified by whomever you choose.
• Define scope by pages, features, integrations and completion criteria. "Contact form" versus conditional multi-step intake can cause billing disputes. Specificity clarifies change orders and protects both sides.
• Revision rounds. Define how many included revision cycles, what counts as a revision vs. scope change, and the rate for extras. "Two rounds of design revisions; functionality changes outside the original scope billed at $X/hr" is clear and fair. "Unlimited revisions until you're satisfied" is a setup for conflict.
• Timeline and milestone checkpoints. Specific delivery dates for major phases (design review, staging build, content handoff deadline, launch date) create accountability on both sides and give you a clear signal if work is falling behind before it becomes a crisis.
• Payment terms: usually 30–50% upfront, defined review milestone, remainder at launch. Specify written approval for added scope and cancellation handling for completed work/unused deposit.
• Termination clause. Clear language on what you owe and what you receive if either party terminates mid-project. Work completed to date gets compensated. You receive all files produced to that point. Deposits for unstarted phases are returned or classified as a defined cancellation fee.

8. Hosting and code ownership

Hosting is often the last thing clients think about and one of the first things that causes problems. The conversation to have (before the project starts, not after launch) covers where the site lives, who controls it, and what happens when you want to move.

• Own the domain in a registrar account tied to your email before work starts. Namecheap, Cloudflare or Google Domains transfers take about 10 minutes. Developer control risks leverage if relationships fail.
• Own or managed hosting both work. Use Hetzner, DigitalOcean, Cloudways or WordPress-focused WP Engine, or pay the developer to manage servers, SSL, patches, uptime and backups. That expertise warrants a fee. The requirement is portable source; refusing handover is the red flag.
• You should receive the code. At delivery, you get either a GitHub repository or a complete zip of all source files. Not an admin panel login. Not view access to a hosted copy. Actual source code that any developer can open, read, and extend without proprietary tools or credentials.
• What else to keep control of. Beyond the domain and source files: the Google Search Console property (should be verified under your Google account), the Google Analytics property if applicable, any payment processor accounts, and any third-party API keys the site uses. A developer can be a delegate on all of these, but the account ownership should be yours.

For a complete checklist, see website ownership: what to keep control of. The Web Hosting page describes what ArdinGate's managed hosting tiers include (server maintenance, nightly backups, security patching, SSL, uptime monitoring) and what the exit process looks like.

9. SEO: what the developer handles vs. what's your job

SEO confuses hiring conversations more than any other topic because the word covers two completely different categories of work. One falls to the developer. The other doesn't.

Technical SEO belongs in the build: desktop/mobile speed, HTTP codes, duplicate-page signals, homepage/service/FAQ/breadcrumb business labels, social previews, sitemap, indexing rules and usable mobile design. Confirm labels, Google Search Console submission and mobile speed targets explicitly. These are standard one-time deliverables.

Content SEO means ongoing keyword research, strategy, topic clusters, backlinks and blogging, requiring a specialist. Development's one-time technical SEO is distinct; clarify which "SEO included" promises cover.

The SEO Setup service page describes the technical SEO layer included in a new ArdinGate build and when a standalone SEO audit on an existing site makes sense.

After launch, verify the work: run PageSpeed on mobile, check the Search Console coverage report to confirm all pages are being indexed. A developer who delivered clean technical SEO will have nothing to hide.

10. After launch: maintenance and ongoing support

Most don't think about post-launch maintenance until something breaks. Here's what will eventually need attention and how to plan before the site is down and you're scrambling.

PHP upgrades follow host support schedules. Moving 7.x to 8.x can require deprecated-function, edge-case and library fixes by someone familiar with the code. Managed hosts commonly handle it; unmanaged owners must respond.

Security patches matter for WordPress, frameworks and packages: scanners find unpatched CVEs within days. Managed monitoring helps if you aren't watching. Dependency-free custom sites expose fewer documented vulnerabilities.

Content changes. Your team page changes when you hire. Service descriptions evolve with your offerings. Pricing updates when rates change. Someone handles this. Your options: a CMS for non-technical staff, a developer on retainer, or batching changes and paying project rates. All three work. Pick one before launch, not the first time you need a change and scramble.

Hosting migrations. Servers get deprecated. Data center prices shift. Hosts get acquired. Over a 5–10 year lifespan, you'll likely move to a different host. A developer who documented deployment and delivered clean source code can execute the migration. A proprietary platform has no migration path. You rebuild.

Performance audits. Google's ranking algorithms and page-speed requirements evolve. A site that performs well at launch may drift as requirements change or new formats become standard. An annual check (PageSpeed and Search Console on mobile) catches issues before they affect rankings.

The Website Maintenance plans describe ArdinGate's structured ongoing support: what's included at each tier, when a monthly retainer makes more sense than per-incident billing, and what "managed hosting" covers in practical terms.

11. Key takeaways

• Decide platform first, developer second. Custom hand-coded, WordPress, and page builders are fundamentally different products. Understanding which is right for your situation shapes every other decision.
• Own your domain and source files unconditionally. Your domain registrar account is yours. Your source code is delivered to you at launch. These are non-negotiable terms, and any developer who won't agree to them is not the right developer.
• A contract is not optional. It protects both parties. At minimum it needs scope definition, IP terms, revision rules, payment structure, and a termination clause.
• Low price and good value are not the same thing. The cheapest quote almost never represents the best outcome. Evaluate on portfolio quality, communication speed, technical specificity, and contract terms — then on price.
• Technical SEO is a build deliverable, not an ongoing service. It should be included in the initial build scope. Ongoing content SEO is separate work by a different type of specialist.
• Plan the post-launch maintenance model before launch. Whether it's managed hosting, a retainer, or per-incident billing, having a plan means you're never scrambling when something needs attention.
• The boutique or independent developer is often the best fit for small businesses. You get direct access to the person building the project, lower overhead baked into the price, and a developer with a professional stake in the outcome.