Fixed-scope delivery · US · UK · Canada
WordPress Development Company
A WordPress development company in India that quotes fixed scope, names the launch date, and puts a penalty against missing it. Discovery, build, QA and handover: one price agreed before we start, native block themes rather than a page-builder licence, and your IP assigned from the first commit.
A written spec, architecture, risk list and one fixed build price, not a range. Yours to take elsewhere.
Below that figure a smaller engagement is the better buy, and we will say so.
Two build slots open for October starts
How we contract
Six terms we put in writing
The things every buyer of offshore WordPress work has been burned on. Each of these 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
A build, a developer, or a theme? The honest split
Start with the cheapest honest answer: if you need a marketing site of ten or fifteen pages and your requirements are ordinary, a well-chosen theme configured by a good freelancer will cost a fraction of this page and serve you perfectly. We will tell you that on the first call rather than quote you for a custom build.
Fixed-scope delivery earns its keep when WordPress is doing real work and the deadline is real: a store with unusual pricing rules, a membership tied to content access, an ERP that must own stock, a publishing workflow with approvals. Those need a spec, a content model and QA, and someone accountable for a launch date rather than an hourly meter.
The uncomfortable truth about fixed price is that both sides price the risk. Our number carries a buffer for the unknowns, third-party plugins, an undocumented theme, content that turns out to be messier than the spreadsheet suggested. You pay that buffer whether or not they materialise. If you can carry variance, hire a developer by the month instead; if you need one number for a board, fixed price is what certainty costs.
One thing we will not do is quote a fixed price without discovery. Any agency that gives you a firm number for a substantial WordPress build from a two-page brief is either padding it heavily or planning to make the difference back on change requests. Two weeks of discovery is how the number becomes real, and you own the content model and spec afterwards whether or not you hire us to build it.
We have turned away six enquiries this year because a theme and a freelancer were the right answer. Two of them came back with a real project once the business had grown into one.
The three routes
Fixed scope, dedicated developer, or a theme
The theme column assumes a premium theme licence and a competent freelancer configuring it. The dedicated-developer column is our own published monthly rate.
Capabilities
What we build
Eight kinds of WordPress project we quote most often. If yours is not on this list, describe it in a paragraph and we will tell you honestly whether it is us.
Custom site builds on a native block theme
Content model first, then a block theme built in code and deployed from Git. Your editors get a real layout system; you get a site with no page-builder licence to renew and nothing you cannot remove.
WordPress 6.8GutenbergACF ProWP-CLI WooCommerce store builds
Checkout, subscriptions, tax and fulfilment on HPOS, reconciled against the gateway.
WooCommerce 10HPOS Membership and course platforms
Content gating tied to billing, with the renewal and dunning logic actually tested.
Stripe Headless WordPress builds
Editors keep the admin they know; the front end stops being bound to PHP rendering.
Astro Migrations and replatforms
Shopify, Magento, Drupal or host moves with the redirect map built URL by URL, historical content and orders imported, and the cutover rehearsed on a clone before DNS moves.
Multisite and multi-region
One codebase, many country sites, one update cycle, with editors keeping local control.
Plugin and integration builds
Custom plugins to WPCS, and the CRM, ERP or PIM integrations that make the site useful.
Discovery and specification
Content model, wireframes, plugin decisions, risk list and a fixed build price. Yours to keep.
Is a custom build overkill?
Sometimes, and we will say so. If a premium theme and a freelancer will do the job, that is the advice you will get, for free, on the first call.
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 fixed-scope build includes
On fixed scope we own the outcome, so these are contractual rather than aspirational. Each one is in the agreement before any code is written.
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.
Miss it through our own fault and the final invoice drops 10% per week late, capped at 30%.
If a week produces nothing demonstrable you find out that Friday, rather than at the end of the month.
Anything we built that does not do what the spec says is fixed free. A defect warranty, not support hours.
No separate project-management fee, no QA line item, and no charge for the handover.
Signature, midpoint demo, sign-off. No hourly overages on a fixed-scope build.
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.
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 development company in India charge?
Discovery is a fixed fee over two weeks, and it ends with one fixed build price rather than a range. Our discovery fee is $2,400 and builds start at $8,500, both published on the rates page; what your own site costs comes out of discovery, because that is the only honest way to name it.
Why do you insist on paid discovery?
Because a fixed price without it is a guess, and wrong guesses come back as change requests on your invoice. Two weeks produces a content model, wireframes, plugin decisions and a risk list, and you keep all four whether or not we build it.
Do you build with Gutenberg or a page builder?
Native blocks with ACF, in code, deployed from Git. We will maintain an Elementor or WPBakery site you already own, but we will not start one: the licence, the lock-in and the performance cost all land on you rather than us.
What happens if you launch late?
The final invoice drops 10% for every week we are late through our own fault, capped at 30%. It is a clause in the contract, not a goodwill gesture, and it has been invoked once in four years.
How do you handle change requests?
You get a written price and schedule impact before anyone writes code, and you approve or decline. We do not absorb scope quietly and then argue about it at launch, which is how most fixed-price relationships fail.
Who owns the code and the IP?
You do, assigned from the first commit rather than on final payment. Work happens in your repository and your hosting account, so there is no handover event to negotiate.
Is a custom build overkill for us?
Often, and we will say so. If you need fifteen marketing pages with ordinary requirements, a premium theme and a good freelancer will beat us on price and on time. We are worth paying when WordPress is running something the business depends on.
What is included in the price?
Project management, QA, code review, documentation, deployment, editor training and thirty days of defect warranty after launch. No separate PM fee, no QA line item, no charge for handover.
Will our editors be able to use it?
That is what the content model is for. Editors get blocks and patterns that compose into real layouts rather than a blank canvas, and we run a training session before launch and record it.
Can you take over a build another agency started?
Yes, and it starts with a paid audit rather than a quote. We need to know what is actually there before putting a date against finishing it, and you own that report regardless.
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.