Web design project management for freelance designers and developers

Scope a website in units you can count

• Pages or templates, listed by name.
• Revision rounds included per stage (design, build).
• Deliverables: responsive build, basic on-page SEO, CMS setup, handover.
• Who supplies content and images, and by when.
• Estimated hours and the agreed price.

Explicitly noting what is not included — extra languages, e-commerce, integrations, ongoing maintenance — prevents most disagreements before they start.

The three places web projects leak time

Design revisions. Homepage rounds multiply when feedback comes from several people. Record each round and consolidate feedback into one list per round.

Late content. Building with placeholder copy usually means building the layout twice. Track the delay as a scope event, not as your problem.

“Small” additions. A booking form, a newsletter integration, an extra landing page — each is a quotable piece of work.

Development projects follow the same shape

For freelance web development, replace pages with features or milestones and keep the rest identical: estimated hours per feature, rounds of change requests included, and a price for anything beyond the agreed list. See freelance project management for the general version.

Know when the project stops being profitable

Compare hours spent against your estimate throughout the build, not at handover. When your effective hourly rate drops below your target, that is the signal to quote the outstanding requests rather than absorb them — the approach described in managing scope creep.