Free Web Design Retainer Agreement Forms

What Is a Web Design Retainer Agreement?

A web design retainer is a continuing services agreement between a client and an independent web designer or design studio under which the designer reserves a defined hour bank per calendar month for UI, UX, and visual design work across the client's web properties. The instrument controls the scope of work, the monthly fee and overage rate, deliverable formats and source-file rights, revision rounds, responsive breakpoint requirements, accessibility conformance level, third-party asset licensing, and IP assignment under 17 U.S.C. § 101 work-for-hire combined with § 201(d) absolute assignment as a backstop. Because pictorial works generally fall outside the nine work-for-hire categories at § 101, the assignment language is the operative clause; without it the designer retains copyright by default under § 201(a) even after full payment.

The retainer model fits clients with continuous design demand: SaaS platforms iterating on product UI, e-commerce brands launching weekly landing pages, marketing teams running A/B tests on conversion surfaces, publishers maintaining editorial design systems. Project-by-project contracting is more expensive in aggregate because each engagement requires re-onboarding the designer to the brand system, design tokens, accessibility baseline, and approval workflow. A retainer keeps a single designer (or studio team) ramped on the system and available with predictable turnaround. The model only works if the contract defines what the hour bank purchases, how scope creep is controlled through change orders, and what becomes of the Figma files and design tokens when the engagement ends.

Hourly hour bank vs flat monthly retainer

Two pricing structures dominate. Hourly hour-bank retainers prepay a defined block (typically 20, 40, or 80 hours) at a fixed rate ($85 to $250 mid-level, $200 to $400 senior or studio leads), with overage billed at the same rate or a modest premium. Hour banks favor the client when scope varies month to month and protect the designer when scope surges. Flat monthly retainers fix the fee regardless of effort, suitable when scope is genuinely steady-state and the designer can underwrite variance through repeat components and templates. Most retainers carry a 3-month minimum to amortize onboarding (brand audit, design token capture, component inventory, approval workflow setup). Rollover of unused hours should cap at one cycle to prevent open-ended carry that the designer cannot capacity-plan against.

Scope creep and the change-order requirement

Scope creep is the single largest cause of retainer disputes. The contract must distinguish a revision (an in-scope adjustment to an in-progress deliverable) from a change order (new or expanded work). A revision tweaks typography, swaps copy, adjusts spacing, refines color. A change order adds pages beyond the brief, redesigns an approved layout, introduces a new responsive breakpoint, integrates a new third-party tool, or restarts work after client approval. Change orders require a written amendment signed by both parties stating the additional scope, hours, fee, and revised timeline. Verbal or Slack-based authorizations are not enforceable. Enforce the rule from day one; informal scope expansion that the client later refuses to pay for is the most common cause of designer collection actions in small-claims court.

Web Design Retainer Form Preview

Key Components

How to Create a Web Design Retainer Agreement

Deliverables & Formats

IP & Asset Ownership

Design-file ownership is the load-bearing IP clause in every web design retainer. Under 17 U.S.C. § 201(a), copyright vests in the author at the moment of fixation. For pictorial works produced by an independent contractor, there is no automatic transfer to the commissioning party; the work-for-hire doctrine at 17 U.S.C. § 101 reaches only nine enumerated categories, and most web design copy does not fit cleanly within those categories. The retainer must therefore include both a work-for-hire recital (for contributions that may qualify) and a § 201(d) absolute assignment of all rights, title, and interest in approved deliverables. Without that language, paying the invoice does not transfer the copyright; the designer can lawfully relicense the work to a third party including a competitor.

Source code and CMS template handover

When the engagement includes development (HTML, CSS, JavaScript, CMS templates for WordPress, Shopify Liquid, Webflow, or a headless React/Next.js front end), the source code is also a copyrighted work that must be assigned. Specify the deliverable: source repository (typically Git on GitHub or GitLab) transferred to a client-controlled organization, README documenting build commands and dependencies, environment variable manifest, deployment configuration, and a 30-day post-handover support window for transition issues. The designer warrants no third-party code beyond properly licensed open-source components is included; require an SBOM (software bill of materials) listing every dependency with its license (MIT, Apache 2.0, GPL, BSD) so the client can avoid copyleft contamination of proprietary code.

Frequently Asked Questions

Official Resources