Handbook / Freelancing
Freelance web developer: niche, pricing, contracts, hosting and support
Web development is one of the most in-demand freelance skills, and also one where projects easily go wrong: vague requirements, endless changes, and clients who disappear before the final payment. Freelancers who do well are clear about what they build, how they price, and who controls what at the end.
Choose a niche and stack
"I build websites" competes with everyone. Narrow by:
- client type: restaurants, clinics, nonprofits, local trades, online stores
- platform: a particular content management system or e-commerce platform
- service: speed and accessibility improvements, migrations, custom integrations
Pick a stack you can deliver, maintain and support. Clients rarely care about your framework; they care that the site works, loads quickly and is easy to update.
Portfolio
Show three to five projects with short case studies: the problem, what you built, and the result. If you are new, build realistic sample sites for imaginary clients in your niche, or improve sites for local organizations with permission. Include links where the client agrees, plus screenshots in case sites change later. The guide to building a freelance portfolio covers presentation.
Pricing
Most website projects suit fixed prices with defined scope:
- list pages, templates, features and integrations
- set the number of revision rounds
- state what the client provides, such as text and images, and when
- split payment into milestones, such as a deposit, design approval and launch
Use hourly or day rates for open-ended work, such as investigating problems in an existing codebase. See project pricing and how to quote a job.
Scope and change requests
Write scope into a statement of work. When the client asks for something new, estimate it as a change and get approval before doing it. The guide to scope creep has wording.
Contracts
Your contract should cover:
- deliverables and acceptance: how you both agree the work is finished
- timeline and dependencies on client inputs
- payment milestones and late payment terms
- hosting, domains and third-party accounts
- ownership of code, design and content
- warranties and support after launch
- confidentiality
- ending the project early
Ownership and licenses
Copyright protects original works of authorship, including computer programs, as soon as they are fixed in a tangible form. Who owns the code you write for a client depends on your agreement. The US Copyright Office explains that a commissioned work by an independent contractor is a "work made for hire" only if it falls into specific categories and the parties sign a written agreement saying so; software for a client site usually does not fit those categories. Many developers instead assign copyright in the final deliverables on full payment, while keeping rights to reusable tools and code they developed before. See intellectual property for freelancers.
Note any open-source components and their licenses, and any paid themes or plugins, and whose name they are licensed in.
Hosting, domains and access
Set up domains, hosting and key accounts in the client's name wherever possible, with access delegated to you. This protects both sides: the client keeps control if you part ways, and you are not responsible for their renewals. Use a password manager for shared credentials, enable multifactor authentication, and remove your access when the work ends.
Security basics
- keep platforms, themes and plugins updated
- use strong, unique credentials and multifactor authentication
- back up sites regularly and test restores; CISA stresses that untested backups often fail when needed
- follow the client's rules on handling customer data
Launch checklist
- test on common browsers and devices
- check forms, links and page speed
- check basic accessibility, such as headings, alt text and contrast
- set up analytics if agreed
- hand over documentation and logins
Support and maintenance
Offer a monthly support plan covering updates, backups, monitoring and a set amount of small changes. It gives clients peace of mind and gives you recurring revenue; see recurring revenue.
Finding clients
- past employers and colleagues who now run or work in small businesses
- agencies that need overflow help
- other freelancers, such as designers and copywriters, who need a developer
- local business groups in your niche
- referrals from happy clients, asked for at launch
A short case study for each launch gives you something specific to share.
Specialise, show real case studies, price by milestone with clear scope, keep client accounts in the client's name, put ownership in writing, and sell an ongoing support plan.
Questions people ask
Should I specialise?
Usually yes. A niche, such as sites for restaurants or a specific platform, makes marketing easier and lets you reuse knowledge.
Hourly or fixed price?
Fixed price with defined scope suits most website projects. Use hourly for open-ended work, such as debugging an unfamiliar codebase.
Who should own the domain and hosting?
Generally the client. Set up accounts in their name and get delegated access, so they keep control if you part ways.
Who owns the code?
It depends on your contract. Copyright law has specific rules for commissioned work, so state ownership and any license terms in writing.
Do this week
- Choose a niche and the stack you will offer.
- Build three portfolio pieces with short case studies.
- Create a proposal and contract template with payment milestones.
- Decide your approach to hosting, domains and client access.
- Design a monthly support plan.
Sources read for this page
- US Copyright Office: Circular 30, works made for hire
- US Copyright Office: what is copyright?
- CISA: cyber guidance for small businesses
Published November 8, 2026. Sources checked November 8, 2026. Rules, limits and forms change; the linked page is the authority.