New: remix a demo site in your browser – no sign-up, nothing to install. Try it

← Blog

Custom Design in WordPress: Briefs, Deliverables, Quotes

· 9 min read

Key takeaways

  • A custom design in WordPress brief must specify seven things: goals, page list, content state, motion, performance budget, hosting, and handover.
  • Insist on five written deliverables: a staging site, transferred licence keys, exportable templates, a handover document, and a passing Core Web Vitals check.
  • Score every quote against scope clarity, performance budget, ownership, and post-launch terms before signing.
  • Name the build stack and the motion tool in the brief itself, or you inherit the designer's choice on every future edit.
  • Structure quotes as build plus a fixed number of revision rounds, since per-page pricing hides the real cost driver.

A good custom design in WordPress buys you a site that fits the brief instead of fighting the template, but only if you specify what you want and demand the right deliverables in writing. This guide gives you the buyer-side brief template, the deliverables checklist, and a scoring method for judging whether a quote is worth the money.

What does a custom design in WordPress actually buy you?

A custom design in WordPress means the layout, typography and motion are built for your brand instead of selected from a theme demo. What you pay for is decisions: a designer removes the defaults you would otherwise fight, so the site matches the brief rather than the template author's assumptions.

There are three levels, and the price gap between them is mostly how much is decided before the build starts.

LevelWhat you getBest fit
Tweaked themeColours, fonts and logo changed on Astra, Kadence or GeneratePressTight budgets, standard layouts
Child themeTemplate files and CSS modified on top of a parent theme, as described in the WordPress developer handbookSites needing structural changes that stay upgrade-safe
Fully custom designLayout, templates and interactions designed from scratch, then built in the chosen stackBrands where the design is the product

The third level is where scroll-driven pages, pinned scenes and 3D become possible rather than approximated. Tools like Midground and Greenshift exist to build those interactions without writing JavaScript by hand, and more comparisons live in the scroll animation guide collection.

What should a custom design brief specify?

A brief needs seven sections: goals, page list, content state, motion, performance budget, hosting, and handover. Miss one and the quote you get back will quietly exclude it.

The one-page brief template

Goals come first, stated as outcomes: "quote requests up" beats "modern look". List every page and its template type, because a homepage and a 404 are priced differently. State the content state honestly: who writes copy, who supplies images, and by when. Name the performance budget in numbers, for example under 100KB of CSS and JS on the homepage, so the designer can price for it instead of discovering it at handover. Hosting and handover close the loop: where the site lives, who holds admin, and what documentation you receive.

That last paragraph is the one worth copying into your own brief. A designer who knows the budget, the content state, and the hosting up front can quote accurately; one who doesn't will pad the number or deliver surprises later.

Specifying motion and scroll behaviour up front

Motion is where custom designs drift. "Apple-style scroll" means nothing without examples. Name the effect per section: pinned scenes, parallax, or real 3D, and reference something concrete like the patterns in parallax effect in WordPress. Ask how the effect will be built and what it costs in page weight, so scroll behaviour is a line item rather than a late-stage argument.

Naming the build stack in the brief

Name the stack explicitly: a theme like GeneratePress, a block tool like GenerateBlocks, a builder like Bricks Builder or Elementor, or a scroll-focused theme like Midground. The stack determines who can edit the site after handover and how the performance budget gets met. If you leave it blank, the designer picks for you, and you inherit that choice on every future edit.

What deliverables should a custom wordpress design service hand over?

A custom design in wordpress is only worth the quote if "done" is defined in writing. Insist on these five deliverables before anyone starts: a staging site on a URL you control, the full theme and plugin licence keys transferred to you, an export of the design as reusable templates, a short written handover document, and a passing performance check. "Passing" should mean Core Web Vitals thresholds from Google's PageSpeed Insights documentation, measured on the staging site with real content loaded, not an empty homepage.

The deliverables checklist

  • Staging site with all pages built, populated with your real copy and images
  • Licence keys for every paid theme or plugin, registered in your name
  • Exportable templates or patterns, so you can build new pages without the designer
  • A handover doc: how to edit each template, where global styles live, how to duplicate a page
  • A Lighthouse run on mobile showing LCP, CLS and INP within Google's thresholds

What should never be a deliverable

A proprietary page layout you can only edit inside the designer's own setup. If a rebuild in Greenshift, Bricks Builder or GenerateBlocks would leave you stuck following the template's rules, ask for the design as native blocks instead. A scroll-driven page built with a tool like Midground should hand over as an editable template too, not a locked file.

How do you judge whether a quote is worth it?

Score every quote against four criteria: scope clarity, performance budget, ownership, and post-launch terms. A quote that nails all four is worth paying for. One that misses two is a gamble with your client relationship.

Five questions to ask before signing

  1. What exactly is being designed, and what is explicitly out of scope?
  2. What performance budget will the finished site meet, and how is it measured?
  3. Who owns the design files, the theme, and the content after payment?
  4. What happens when I need a change three months after launch, and what does it cost?
  5. Can I see finished work at the same scope, not just a homepage? A demo library of finished WordPress sites shows what a finished build actually feels like.

Red flags in a quote

A price with no deliverables list. A "responsive design" line item with no performance numbers attached. Ownership that stays with the designer until "final approval" with no defined date. And post-launch edits billed only as hourly work with no retainer or fixed-rate option. Any one of these means you are buying goodwill, not a service.

Which build stack should the brief name: theme, blocks or builder?

Running every option through the same criteria

Your brief should name the stack explicitly, because "custom design in wordpress" means something different on each one. A theme like GeneratePress or Kadence gives you a fast base but leaves layout decisions to you. Block tools such as GenerateBlocks and Greenshift work inside the native editor; Elementor alone lists millions of active installs in the WordPress.org plugin directory, so it is the option your client is most likely to have already used. Bricks Builder sits closer to the code, trading the plugin ecosystem for tighter markup. Judge each against the same four criteria: page weight, how easily a future developer can edit the site, whether the design survives without the tool, and how much of the build is point-and-click versus hand-written.

Where scroll motion fits in a custom design

Most stacks above treat scroll effects as an add-on, so briefs either skip them or hand the work to a developer writing GSAP by hand. If the brief calls for pinned scenes or parallax, name the tool for it too. Midground handles scroll motion as its core job, so it pairs with whichever stack you pick rather than replacing it; the sticky scroll animation guide shows what that looks like in practice.

How much should a custom wordpress website design cost?

Honest answer: it depends on scope, and anyone who quotes per page is guessing. Two five-page sites can differ by 10x in effort because page count says nothing about the work.

What moves a quote up or down

Cost rises with pinned scroll scenes, real 3D, animation timing that needs iteration, and any layout the builder has to invent rather than assemble from patterns. It falls when the brief names a stack, supplies real content, and accepts a theme like GeneratePress or Bricks Builder as the foundation instead of demanding a bespoke build from nothing.

Per-page quotes mislead because they hide the second variable: revision rounds. Ask for a quote structured as build plus a fixed number of revisions, and you'll see which part of the price is design and which is the designer pricing in your uncertainty.

How do you evaluate the design before launch, not after?

Write acceptance criteria into the contract, then test against them before final payment. If the brief named speed targets, a mobile pass, and editor usability, launch is a checklist, not a debate.

The acceptance checklist

Run four gates. First, speed: test on PageSpeed Insights with real throttling, not a fast office connection, and compare against the numbers in the brief. Second, mobile: check every template on an actual phone, including menus and forms. Third, editor usability: have the client log in and change a headline, swap an image, and add a page without calling you. Fourth, content: confirm all templates are populated with real copy, not lorem ipsum.

Testing motion on real devices

Scroll animation that looks fine in a desktop preview often stutters on a mid-range phone. Test pinned scenes and parallax on at least one older Android device. If the build uses Midground, note that the Pro tier covers five websites at $89/yr, so the test licence is trivially cheap.

What happens after launch: handover, edits and growth?

Agree the post-launch terms in writing before you pay the final invoice. Most disputes start when a client wants a change six months later and nobody defined who does what.

Handover terms worth writing down

  • Admin access. The client owns the domain, hosting and WordPress admin account from day one. You hold a working copy, not the keys.
  • Edit scope. Specify who updates plugins, themes and WordPress core, and on what schedule. Agree a monthly retainer rate now, or the client assumes updates are free forever.
  • New pages. State whether the client can build new pages themselves and which templates or patterns they may reuse. If your design depends on you for every edit, say so plainly and price it that way.
  • Documentation. A short written guide covering how to edit text, swap images and add a page beats a training video nobody watches twice.
  • Growth path. Name the point at which the site should move from a starter theme to something more capable, so the client knows the current setup has limits.

A clean handover is also how you get referrals: clients who feel ownership stay clients.

FAQ

Is a custom WordPress design worth it for a small site, or is a premium theme enough?

If a tweaked theme like GeneratePress or Kadence matches your layout needs, take it and spend the savings on copy and images. Custom design pays off when the design itself is the product: pinned scroll scenes, real 3D, or layouts a template demo cannot approximate. Score the quote against scope clarity, performance budget, ownership, and post-launch terms before deciding.

How long does a custom design in WordPress take from brief to launch?

It depends on scope, so no honest answer fits every project. Timeline stretches with pinned scenes, animation timing that needs iteration, and layouts the builder has to invent rather than assemble from patterns. It shrinks when the brief names the stack, supplies real content up front, and accepts a theme as the foundation instead of demanding a bespoke build from nothing.

Do I need a custom design WordPress plugin for animations, or should that be in the theme?

Name the motion tool in the brief itself. Most themes treat scroll effects as an add-on, so pinned scenes and parallax usually need a dedicated tool like Midground or Greenshift rather than theme settings. Ask how each effect will be built and what it costs in page weight, so motion becomes a priced line item instead of a late-stage argument.

Who owns the design files and licence when I hire a custom WordPress design service?

You should, from the day you pay. Insist on licence keys for every paid theme and plugin registered in your name, an export of the design as reusable templates, and a staging site on a URL you control. Ownership that stays with the designer until final approval with no defined date is a red flag in any quote.

Can I get a custom WordPress design without learning to code?

Yes, if the brief names the stack and the deliverables. Tools like Elementor, Bricks Builder, Greenshift, and Midground handle layout and scroll motion through point-and-click interfaces, so the designer writes little or no code by hand. Your job is specifying goals, page list, content state, motion, performance budget, hosting, and handover in writing before anyone starts.