How to Hire a Web Developer: Hiring a Website Developer, What to Ask, and What It Costs

To hire a web developer, first decide whether you are buying a website or a web application, because those are two different jobs at two different prices. Then write down what the site has to do in one sentence, ask for work they have shipped and still maintain, and buy one small paid piece of work before you commission the full build. Most web projects that go wrong were mispriced at the brief stage, not mismanaged at the build stage.

Last updated August 2026.

How much does it cost to hire a web developer?

Freelance web developers in the US commonly charge 50 to 150 dollars an hour, and project pricing is more common than hourly at the small business end. A marketing site on a CMS typically runs 2,000 to 8,000 dollars. A site with custom functionality, accounts, or payments runs 8,000 to 40,000. A genuine web application with its own data model starts around 25,000 and has no natural ceiling.

The salaried reference points are worth carrying into any negotiation, because they explain the spread better than any rate survey does:

Two gaps in that table do more explanatory work than the individual numbers. The federal data separates Web Developers from Software Developers by 20.84 dollars an hour, and Indeed's back end developer postings average 75,367 dollars a year more than its web developer postings. Same industry, same tools in many cases, roughly double the pay. That is the single best answer to why one developer quotes 4,000 dollars for your project and another quotes 20,000: they are not pricing the same job. One is building pages, the other is building a system.

Note also that Upwork's 15 to 50 dollar band is drawn from contracts worldwide rather than US only, which is why it sits so far below every US figure. Comparing a worldwide platform median to a US salary is the most common mistake buyers make when they decide a quote is unreasonable. Our web developer cost guide breaks the project bands down by site type.

Should I hire a web developer or a web designer?

A web designer decides what the site looks like and how someone moves through it. A web developer builds it and makes it work: templates, forms, integrations, performance, and anything touching a database. On a five page marketing site, hiring one person who does both is usually simpler and cheaper.

The split starts to matter the moment the site does something rather than says something. If you need payments, user accounts, a booking system, or a custom CMS, hire for the development skill and treat design as the smaller half of the budget. If the site basically works but looks dated and converts badly, you want the designer. Getting this backwards is expensive in both directions, and it is the most common category error in this market.

Do I need a front end or a back end developer?

Front end developers build what runs in the browser: layout, interactions, and the screens people touch. Back end developers build what runs on the server: APIs, databases, authentication, integrations, and scheduled jobs. Most small business websites need mostly front end work. Most things people call a "platform" or a "portal" are mostly back end work.

If your project is essentially an interface over data that already exists somewhere, the hard part is the server side, and you want a Node.js or backend developer rather than someone who mainly builds pages. If you need one person to carry both halves, which is usually the right answer for an early product, hire a full stack developer. For interface-heavy products built on a modern JavaScript framework, a React developer is the specific skill to ask for.

One practical shortcut: describe your project without using any technology names. If the description is mostly about screens, you need front end weight. If it is mostly about data, rules, and things that happen automatically, you need back end weight. Buyers who lead with a framework name instead of a problem usually get quoted for the framework rather than for the problem.

How to hire a website developer, step by step

1. Write the one-sentence brief

Finish this sentence before you contact anyone: "This site needs to help [who] do [what], and today that fails because [why]." That sentence makes quotes comparable, because every developer is pricing the same outcome instead of guessing at your intentions. It also exposes within one reply whether someone is listening to you or pitching a package they already had.

2. Ask what they built, and whether they still maintain it

Portfolios show launches. What you want to know is what survived. Ask which of these projects they still maintain, what broke after launch, and what they would build differently now. Developers who have supported their own work for a year answer this immediately and specifically. Developers who hand off and disappear give you a list of URLs.

3. Buy one small paid scope first

Before a 15,000 dollar build, buy a 400 dollar piece of it: one page built to spec, one integration wired up, or one broken thing fixed. You learn more from that than from three interviews. How someone handles a small job, especially how they communicate when something is ambiguous, predicts almost exactly how they handle a large one.

4. Settle ownership and hosting in writing

Agree before work starts on who owns the repository, who holds the domain and hosting accounts, and what happens to both if you part ways. This is the single most common source of genuinely painful disputes in web projects, and it costs nothing to resolve up front. If a developer is reluctant to put your name on the accounts, that answer is the information you needed.

5. Agree what happens after launch

Ask who applies security updates, who is called when the site goes down at 2am, and whether that is included or billed. A site is not a delivery, it is a thing that keeps running. Budget for that or you will pay for it as an emergency later.

Where to hire web developers

There are four realistic channels, and they suit different budgets. Marketplaces let you compare packaged, fixed-price work and buy without a proposal round, which is the fastest route for a defined project. Agencies cost two to four times more and are worth it when you need a team, guaranteed availability, and someone accountable who is not the person writing the code. Referrals from businesses with a site like yours produce the highest hit rate and the slowest timeline. And because strong developers are frequently already employed, some buyers find them by advertising alongside the remote roles that verified companies post, which reaches people who are not actively browsing for freelance work.

Whichever channel you use, the comparison that matters is scope, not hourly rate. A 120 dollar an hour developer who scopes accurately and finishes in 40 hours is cheaper than a 60 dollar an hour developer who takes 120 hours and needs supervision.

What should I ask a web developer before hiring?

Five questions separate people quickly. What will you build this on, and why that rather than the obvious alternative? What is explicitly not included in this quote? How do you handle changes I ask for mid-project? Who owns the code and the accounts? And what does support look like in month three?

The answers matter less than the shape of them. Experienced developers answer the scope and change questions without hesitation, because they have been burned by both. Anyone who says every change is fine and nothing is out of scope is either inexperienced or planning to renegotiate later.

How long does it take to build a website?

A template-based marketing site with your content runs one to three weeks. A custom designed site of ten to twenty pages runs four to ten weeks. A site with accounts, payments, or a booking system runs two to four months. A web application with its own data model runs three to nine months and is the one where estimates go wrong most often.

The variable that moves these timelines is almost never development speed. It is content and decisions. Projects stall because copy is not written, photos are not chosen, or nobody will approve the homepage. If you want a build to finish on schedule, have the content ready before the developer starts.

Should I hire a freelance web developer or an agency?

Hire a freelancer when the project is well defined, you can make decisions quickly, and one skilled person can hold the whole thing in their head. That covers most sites under about 20,000 dollars. Hire an agency when you need multiple specialists working in parallel, when availability has to be contractually guaranteed, or when the site is business-critical enough that a single person getting sick is an unacceptable risk.

The honest middle path most small businesses miss: hire one strong freelancer for the build and pay a second, separate developer a few hundred dollars to review the code before final payment. That buys you most of the accountability of an agency at a fraction of the cost, and a reviewer who did not write the code will tell you things the author will not.

The short version

Decide whether you are buying a website or a system, because that decision sets the price more than any other. Write the one-sentence brief. Buy a small paid scope before the big one. Put ownership and post-launch support in writing before work starts. And compare quotes on what is included rather than on hourly rate, since the federal wage data alone spans a 21 dollar an hour gap between the two jobs people both call web development.

When you are ready to compare specific people, our web developer gig pages show scope, delivery time, and price up front, with no bidding and no proposals to read.