Fixed-scope delivery · US · UK · Canada
WordPress Web Design
WordPress web design and build from one team, for businesses in the US, UK and Canada. Design in Figma, built as native blocks your editors can compose with: one price agreed before we start, a launch date with a penalty behind it, and no page-builder licence to renew.
- Content model, not a page list 2 wks
- What the site is made of, post types, fields, patterns, before anyone opens Figma.
- Design, in Figma 3-4 wks
- Key templates and a component set, reviewed against real copy rather than lorem ipsum.
- Build as native blocks 5-8 wks
- Every design decision becomes a block or a pattern. Versioned in your Git repository.
- Editor training, recorded 1 wk
- Your team composes three real pages with us watching, before launch rather than after.
2 design slots open this quarter
How we contract
Six terms we put in writing
The things every buyer of a website redesign has been burned on, most of them about what happens after launch. Each is a clause in our MSA, not a promise on a website.
Fixed price, agreed before we start
After discovery you get one number, not a range. It does not move unless you change the scope in writing, and then you see the revised number before anyone writes code.
A launch date with a penalty behind it
We name the launch date in the contract. Miss it through our fault and the final invoice drops 10% per week late, capped at 30%. It has been invoked once in four years.
Weekly demo, not a monthly update
Every Friday there is something running you can click. If a week produces nothing demonstrable, you find out that Friday rather than at the end.
Thirty days of warranty after launch
Anything we built that does not do what the spec says is fixed free for thirty days after launch. Not "support hours": a defect warranty, because sites break in the first month or not at all.
Your repository, from the first commit
Work happens in your GitHub organisation and your cloud accounts. There is no handover event because you already have everything.
One invoice schedule, no surprises
40% on signature, 40% at the midpoint demo, 20% on sign-off. Net 15, USD or GBP. No hourly overages on a fixed-scope build.
The team you get
Who is actually on your project
A pod of four, named in the contract, on your build for its duration. Not a resource pool that changes between sprints, and not an account manager who disappears after signature.
You meet the delivery lead and the senior engineer during discovery, before you commit to the build. If either is not right, we change them then.
Straight answer
When a redesign is the wrong purchase
Most people asking for a redesign do not have a design problem. They have a content problem, a performance problem, or a site nobody can update without a developer, and a new visual layer fixes none of the three. We will ask which it is before quoting, because the answers cost very different amounts.
A redesign earns its keep when the site is genuinely holding the business back: the brand has moved on, the content model cannot express what you now sell, or every page change needs an agency ticket. Those are structural, and they are worth eleven to fifteen weeks. A site that simply looks dated to the person who commissioned it usually is not.
The uncomfortable truth about design work is that the expensive part is not the design. It is the content: someone on your side has to decide what every page now says, and that is the thing that delays almost every redesign we have delivered. We build the content model first for exactly this reason, so the writing can start in week three rather than week ten.
One thing we will not do is design in a page builder. Elementor and WPBakery make the first page fast and the fifth year expensive, licences that renew, markup you cannot take with you, and a performance cost that lands on your Core Web Vitals rather than the vendor’s. Native blocks cost a little more to build and nothing at all to keep.
Three clients this year wanted a redesign and needed a content strategist. We said so, recommended one, and built for two of them a year later.
The three routes
Design and build, build-only, or a theme
The theme column assumes a premium theme licence and a competent freelancer configuring it. Build-only assumes you supply the Figma file and a component set.
Capabilities
What the design work covers
Design and front-end work we quote most often. If you already have a designer or a brand system, we will build to it and price accordingly.
Content modelling
Post types, taxonomies and fields decided before any visual work. It is the difference between a site your editors use and one they fight.
Design systems in Figma
A component set and type scale, not a stack of page comps, so page fifty looks like page one without another design round.
FigmaTokens Block and pattern libraries
Every design decision becomes a native block or pattern. Editors compose real layouts; nobody edits CSS to add a section.
Responsive and accessible build
WCAG 2.2 AA as the build standard: contrast, focus order, keyboard paths and real screen-reader passes.
Core Web Vitals from the start
Image pipeline, font strategy and critical CSS decided in design, not retrofitted after a bad Lighthouse score.
Lighthouse CIAVIF Editor training and documentation
A recorded session and a written guide, so the site survives the person who commissioned it leaving.
LoomRunbook Migration of existing content
Your current pages mapped into the new model, with every URL redirected one by one rather than in bulk.
Design-only or build-only
If you have a designer, we build. If you have developers, we design and hand over a component set with specs.
Already have a designer?
Then you are buying the build, and it costs less. Send the Figma file and we will tell you what is straightforward, what is expensive, and what will not survive an editor.
Tech stack
Current versions, not a wish list
What is in production for our clients this quarter. We will work in older versions too, most rescue jobs start there.
WordPress & PHP
PHP 8.3 / 8.4 
WordPress 6.8 Gutenberg ACF Pro 
WooCommerce 10 WP-CLI Data & infrastructure
MySQL 8 
Cloudflare 
Redis 
Docker 
Kinsta · WP Engine 
GitHub Actions Quality & front end
Lighthouse CI 
Astro 
Tailwind 4 
Alpine The engineers
The engineers who would build it
Salaried staff, named in your contract for the duration of the build. You meet the delivery lead and the senior during discovery, before you commit to anything.
Large catalogues and the checkout path. HPOS, index strategy and the plugin cull that usually matters more than either.
WordPress 6.8 WooCommerce HPOS Runs our headless builds and keeps the editor experience simple while the front end changes.
Astro Redis Plugin work that survives core updates, and the audits that prove which ones will not.
Builds native block themes and the Playwright suites that stop them regressing.
Tailwind Two build slots open for October starts. The full pod is named in your contract before you sign it. Meet the whole team →
How we work
What every design and build includes by default
Design work gets judged years later, by whoever is editing the site. These defaults are for them as much as for you.
Post types, taxonomies and fields decided first. It is the difference between a site your editors use and one they fight.
Editors compose pages from pre-built sections rather than raw columns and spacers. The patterns are the guardrail.
Colours, spacing and typography defined once, with the arbitrary inputs turned off, so the site cannot drift off-brand.
Block locking stops somebody deleting the header while trying to edit the text above it.
Field data over real networks, not a lab score on office wifi. Images generated on upload, fonts self-hosted.
Recorded, so the person who joins next year gets the same handover you did.
You do not have to take any of this on trust. The first ten working days are risk-free, every rate is published in full, and the work happens in your repository from the first commit.
How it works
From first email to a signed-off build
Discovery is two weeks and produces a spec you own. Nothing is committed until you have both the spec and the price.
- Day 0
Send us the brief
A document, a Figma file or three paragraphs. An engineer replies inside one business day, never a form response.
- Week 1-2
Discovery, fixed fee
Requirements, architecture, risk list and a written spec. You own it whether or not we build it.
- Week 2
One price, one date
A fixed number and a delivery date, both in the contract, with the late penalty attached.
- Build
Weekly demos
Something clickable every Friday, sprint reports, and staged releases into your environment.
- Launch
Launch + 30 days
Documentation, runbook and a defect warranty. Your repo already has everything.
Why India
Why choose a WordPress development company in India
A four-person pod here costs roughly what one senior contractor costs in the US, which is what makes fixed-price delivery viable at all: the risk buffer that protects a fixed quote would price a domestic team out of the deal entirely. WordPress also runs an enormous share of Indian agency work, so the depth is in the unglamorous parts that decide whether a launch goes well: content migration, redirects, plugin decisions and multisite.
YOUR WORKING DAY, AND OURS
- IP assignment on day one
- Everything written for you is yours on commit, not on final payment. Assignment clause, not a licence.
- NDA before repository access
- Yours or ours, signed before anyone is added to your repository or hosting account.
- Your jurisdiction, your paper
- We sign MSAs governed by Delaware, England and Wales, or Ontario law without argument.
- Milestone billing, not monthly hours
- 40% on signature, 40% at the midpoint demo, 20% on sign-off. Net 15, USD or GBP, and no hourly overages on an agreed scope.
- Scope changes priced before they happen
- Any change gets a written price and schedule impact for you to approve or decline. Nothing is absorbed silently and argued about at handover.
Before week one
What we need from you before design starts
Design projects slip on inputs, not on effort. These four things arriving late is the single most common reason a launch date moves.
One person who can approve
Not a committee. Design by consensus produces a site that offends nobody and moves nothing, and it doubles the number of review rounds. We need one name who can say yes.
Real copy, or a writer with a deadline
We design against your actual words wherever possible, because a headline that runs to three lines changes the layout. Placeholder text hides problems until build, which is the expensive place to find them.
Whatever brand material exists
Logo files, fonts you are licensed for, colours, and any prior guidelines even if you dislike them. If there is nothing, say so, and we will recommend somebody rather than improvise a brand.
Access, and someone to grant it
Hosting, DNS, the current admin, analytics and Search Console. Chasing credentials during cutover week is avoidable and always costs a day.
FAQ
Questions buyers ask before the first call
If yours is not here, email it. We publish the answer rather than saving it for a sales call.
How much does a WordPress website redesign cost?
Design-and-build projects start at $8,500 after a paid discovery, and most sit between there and $30,000 depending on how many templates and how much content migration. Build-only, where you supply the design, costs materially less: the rates page has every band.
How long does a redesign take?
Eleven to fifteen weeks from kickoff: two on the content model, three or four on design, five to eight on build, one on training and launch. The thing that delays it is almost always content, not us.
Can we use our own designer?
Yes, and it is cheaper. Send the Figma file and we will tell you what is straightforward, what is expensive, and what will not survive an editor before you commit.
Do you design in Elementor or Divi?
No. We will maintain a builder site you already own, but we will not start one: the licence renews forever, the markup does not travel, and the performance cost is yours rather than the vendor’s.
Will our editors be able to build new pages?
That is the point of the block and pattern library. Your team composes three real pages with us watching before launch, and we record the session so the next hire can watch it.
What happens to our existing content and URLs?
Mapped into the new content model, with a redirect built URL by URL rather than a bulk rule. Zero lost URLs across every migration we have delivered to date.
Is accessibility included?
WCAG 2.2 AA is the build standard, not an upsell: contrast, focus order, keyboard paths and real screen-reader passes. A VPAT or formal audit is separate and we will say so up front.
Do you do branding and logos?
No. We design and build websites; brand identity and naming are somebody else’s craft and we will recommend someone rather than pretend otherwise.
What about copywriting?
Not included, and it is the most common reason a redesign slips. We build the content model first so your writer can start in week three, and we will recommend one if you need it.
What happens after launch?
Thirty days of defect warranty, then a maintenance retainer if you want one, patches, dependency updates, backups and monitoring, priced on the rates page.
Talk to an engineer
Tell us what needs building
You get a reply within one business day from an engineer, not a form autoresponder, with an indicative range, the discovery scope and the next available build slot.
A fixed price and a launch date, before any build work
NDA signed before we see your site or content
Or book a 30-minute scoping call at a time you pick
We never share your details, and we do not run a mailing list.