Hiring a Freelance Web Developer: Owning What You Paid For
The website gets built, it looks right, you pay, and six months later you want to change the pricing page and discover you cannot. The hosting is on an account in someone else's name, the theme licence is theirs, and the developer has moved on. This happens constantly and almost none of it is about technical skill. It is about what you agreed to before the work started.
The short version
Fiverr's website development category runs from WordPress and Shopify builds through to custom applications, at prices well below agency rates. The work is generally good. What separates a smooth project from a painful one is settling ownership, hosting, platform choice and the definition of finished before you order. Get those four right and the rest is straightforward.
Everything must be in accounts you own
This is the rule that prevents most horror stories. Register the domain yourself. Open the hosting account yourself. Buy the theme and plugin licences on your own account. Then give the developer access to those accounts rather than letting them provide the infrastructure.
It costs the same and it changes your position entirely. When everything sits in a developer's reseller account, you are dependent on them for renewals, migrations and even routine changes, and if the relationship ends badly you can lose access to your own site. When you own the accounts, a developer becomes replaceable, which is the healthy arrangement for both sides.
The same applies to code. State in the brief that you receive full source and that ownership transfers on final payment. For custom work, ask for it in a repository you control rather than as a zip file emailed at the end.
Pick the platform for the second year, not the first
Platform choice is usually made on how quickly the site can launch, which is the wrong criterion. The right one is what you will need to do routinely once it is live.
If the site is mostly content and you will publish often, WordPress remains the sensible default, with an enormous pool of developers who know it and no shortage of people to take over. If you are selling products, a hosted commerce platform handles payments, tax and inventory in ways a custom build will not match for the money. If the site is a brochure that changes twice a year, a static build is faster, cheaper to host and far more secure than a content system nobody logs into.
The expensive mistake is a fully custom build for a site with ordinary requirements. It costs more upfront, it costs more to change, and the pool of people who can maintain it is exactly one person until you pay someone else to learn it.
Define finished in writing
Most disputes come from a shared assumption that turned out to be two different assumptions. Write down what the delivery includes and be tediously specific.
Name the pages. State whether content is provided by you or written by them, because that is the single most common surprise. Say whether images are sourced and licensed, and by whom. Specify responsive behaviour on mobile and tablet as a requirement rather than a hope. Include a contact form that actually sends and is tested. Say who sets up analytics. State the number of revision rounds and what counts as a revision as opposed to a new request.
Then agree on browser and device testing, and on a launch checklist: SSL working, redirects from old URLs in place if the site is a rebuild, sitemap submitted, no staging site left publicly indexable. That last one causes real damage and gets forgotten regularly.
Milestones beat a single payment
Break the project into stages and pay as each is accepted. A common shape is design approval, then build of the main pages, then completion and launch. It protects both sides, since the developer is not carrying the whole project on trust and you are not holding a large payment against work you have not seen.
It also gives you an exit. If the design stage produces something wrong and the conversations are not improving it, you can stop having paid for a third rather than everything. That option is worth more than the small extra admin of splitting payments.
Settle before ordering
- Domain, hosting and licences in your accounts
- Source code ownership transfers on payment
- Who writes the content and sources images
- Exact page list and revision rounds
- Mobile and tablet behaviour as a requirement
- Launch checklist including redirects and SSL
Warning signs
- Developer insists on providing the hosting
- Quote given with no questions about your content
- Portfolio links that are dead or now redesigned
- Unusually low price for a large page count
Common questions
What does a small business site cost?
A well-built five to ten page site on an established platform commonly lands between 300 and 1,500 dollars depending on how much is custom. Ecommerce with real catalogue setup runs higher. Anything quoted at 50 dollars for a full site is a template with your logo pasted in.
Should I supply the content first?
Yes, and it speeds everything up dramatically. Design built around real text is better than design built around placeholder text, and the most common cause of stalled projects is a client who has not written their pages yet.
Who handles updates after launch?
Decide it before launch. Content platforms need security updates, and an unmaintained install becomes a liability within a year. Either buy a maintenance arrangement, use managed hosting that handles it, or make sure you know how.
Can they redesign without changing my URLs?
They can, and they should try. If URLs must change, redirects from every old address are mandatory, not optional. A rebuild without redirects discards whatever search visibility the old site had.
Bottom line
Freelance web development is good value when the boring decisions are made first. Own the accounts, own the code, choose the platform for maintenance rather than launch speed, and write down what finished means. Do that and you get a site you can change yourself next year, which is the actual deliverable.