Five services · one bench of nine
WordPress Development Services
WordPress, WooCommerce and headless engineering from Pune, for businesses and agencies in the US, UK and Canada. Native block themes built in code and deployed from Git, no page-builder licence to renew, and nothing in the stack you cannot remove.
2 WordPress developers free within four weeks
The five services
Every way we sell WordPress engineering
Same engineers, same review standards, same published rate. What differs is who owns the scope and who carries the launch date.
WordPress 6.8GutenbergACF Pro Best when scope keeps moving WooCommerce development STORES Checkout that converts, subscriptions that reconcile against the gateway, and catalogues past forty thousand products on HPOS. 
WooCommerce 10HPOS
Stripe Best for real commerce WordPress development company FIXED SCOPE One price, one launch date, a late penalty and thirty days of defect warranty. We own scope and QA; you approve a content model. Best for a hard launch date WordPress web design DESIGN + BUILD Design and build together, when the site has to look different as well as work. Blocks and patterns your editors can actually compose with. 
FigmaBlocksPatterns Best for a rebrand WordPress plugin development PLUGINS Custom plugins to WordPress coding standards, and the audits that prove which of your inherited ones will not survive the next core update. Best for custom behaviour Capabilities
What the work actually is
Most of this work arrives on a site somebody else built, with eleven plugins doing the job of two. That is the speciality, not the compromise.
Native block theme builds
A content model first, then a theme built in code and deployed from Git. Editors get a real layout system rather than a blank canvas.
WordPress 6.8GutenbergACF Pro WooCommerce engineering
Checkout, subscriptions, tax and fulfilment on HPOS, reconciled against the gateway rather than assumed correct.
WooCommerce 10HPOSSubscriptions Headless and decoupled builds
Editors keep the admin they know; the front end stops being bound to PHP rendering and starts hitting Core Web Vitals.
Astro
Redis Migrations and replatforms
Shopify, Magento, Drupal or host moves with the redirect map built URL by URL and the cutover rehearsed on a clone.
Plugin and integration work
Custom plugins to WPCS, plus the CRM, ERP and PIM integrations that make a site useful rather than decorative.
Performance and Core Web Vitals
Object caching, an image pipeline that actually works, and the plugin audit that finds what is really costing you the LCP.
Lighthouse CI
Cloudflare Straight answer
Why we will not build you an Elementor site
Page builders are genuinely good at one thing: letting a non-developer produce a page today without waiting for anybody. If that is your constraint, a premium theme and Elementor is the right purchase, and we will tell you so on the first call rather than quote you for a custom build.
What they are bad at is the fifth year. Licences renew whether or not you still use the plugin, the markup is unrecoverable if you ever want to leave, and the performance cost lands on your Core Web Vitals rather than on the vendor. Every rescue job we take on starts by removing something a builder added.
So we build native block themes in code, versioned in your Git repository, with ACF for structured fields and patterns your editors compose with. It costs more up front than a builder and less than a builder by year three, and if you ever replace us, the next team inherits ordinary WordPress rather than someone else’s abstraction.
We have turned away six enquiries this year because a theme and a freelancer were the right answer. Two came back with a real project once the business had grown into one.
In every engagement
Six terms that do not change
- IP assigned on the first commit
- Not on final payment. An assignment clause, not a licence.
- Ten working days risk-free
- Real tickets. Walk away at the end and owe nothing.
- NDA before repository access
- Yours or ours, signed before anyone joins your organisation.
- Published rates, one price for all
- No regional pricing, and no discount for negotiating hardest.
- Thirty days’ notice to stop
- Month to month after the trial. No annual minimum, no exit fee.
- Named engineers, not a pool
- The same people for the engagement, named in the contract.
Proof, not adjectives
What we hold every commit to
Not a portfolio. These are configured in CI, so a pull request that misses them cannot merge, and you can read the configuration in your own repository during the trial.
Where the work comes from
The four situations that bring people to this page
WordPress enquiries are more predictable than PHP ones. These four cover most of a year.
Forty plugins, and nobody can say what a third of them do
The site works, slowly, and every core update is a small act of faith. A two day audit lists every plugin with its last release date, known vulnerabilities and what it actually does. In practice a third turn out to be doing nothing anyone can name, and removing them is usually the cheapest performance work available to you.
The site was built in a page builder and now nobody wants to touch it
Elementor and WPBakery make the first page fast and the fifth year expensive. Licences renew, the markup does not travel, and the performance cost lands on your Core Web Vitals rather than the vendor’s. We will maintain what you own, but rebuilding on native blocks is what we would actually recommend.
WooCommerce was fine at two thousand products and is not at forty thousand
Almost always HPOS not being enabled, cart fragments running on every page, and shipping rate calls happening uncached at checkout. These are known problems with known fixes, and the work is measured in weeks rather than a replatform. Anyone recommending Shopify before looking at your queries has not looked.
Somebody has decided the site is moving, and the deadline is already public
Shopify, Magento, Drupal or a host change. The content is the easy part. The risk is entirely in the URLs, because three thousand addresses that ranked and got linked will not survive a bulk redirect rule. The first week is a crawl and a spreadsheet, and that document is what the project is measured against.
The honest version
What WordPress is genuinely good at, and where it stops
WordPress runs a large share of the web for a reason that has nothing to do with engineering fashion: a person who is not a developer can publish to it, and everybody already knows how. That is a real advantage and it is worth building around. Where teams get into trouble is asking it to be an application framework because it is already installed.
Content, publishing workflows, marketing sites, catalogues and membership are all things WordPress does well with a proper content model behind them. Once the requirement involves complex business rules, multi-step calculations, real-time data or a mobile client, you are fighting the platform. At that point a Laravel application with WordPress kept for the content it is good at is usually cheaper over three years than forcing everything into one install.
The other honest limit is the plugin economy. It is the reason WordPress is fast to start with and the reason it decays: every plugin is a dependency with its own release schedule, its own security record and its own idea of how to hook into your site. Thirty of them interacting is not a system anybody designed. Managing that number down is most of what maintenance actually means.
So we build native block themes in code, version them in your repository, and add plugins deliberately rather than by default. It costs slightly more up front than assembling something from the repository and it costs considerably less by year three, mostly because there is less of it to go wrong.
If a premium theme and a competent freelancer will do the job, that is the advice you will get on the first call. We have turned away six enquiries this year on exactly that basis.
Before you commission anything
Four questions worth asking us
- Who owns the markup if we leave?
- With native blocks, you do, and the next team inherits ordinary WordPress. With a page builder the answer is more complicated than the salesperson will admit.
- What renews every year?
- Ask for the list of licences and their cost before signing. A site with eight premium plugins has an annual bill that nobody mentioned at quote stage.
- Can our editors build a new page?
- If the answer involves a developer, the content model was not designed properly. Your team should compose pages from patterns without opening a ticket.
- What happens on the next core release?
- Everything we write is tested against the current release and the beta. Ask anyone quoting you how they know their work will survive December.
The stack, in detail
What we actually build with, and why
Not a logo wall. These are our defaults and the reasoning behind each, so you can push back before anything is committed.
Themes and editing
Native block themes written in code, with ACF Pro for structured fields and patterns your editors compose from. No page builder, on new work, ever. The trade is honest: slightly more up front, and nothing in the stack you are locked into paying for or cannot remove later. Editors get a layout system rather than a blank canvas.
WordPress 6.8GutenbergACF ProBlock patterns Commerce
WooCommerce 10 with HPOS enabled from the start, because retrofitting it on a live store with order history is a job nobody enjoys. Subscriptions reconciled against the gateway rather than assumed correct, and shipping rate calls cached. Above roughly forty thousand products the index strategy matters more than the hosting tier.
WooCommerce 10HPOSStripeSubscriptions Performance and front end
Object caching, an image pipeline serving modern formats at sensible sizes, and critical CSS decided during design rather than retrofitted after a poor Lighthouse score. For headless builds, Astro against WPGraphQL, which keeps the admin your editors know while the front end stops being bound to PHP rendering.
AstroWPGraphQLCloudflareLighthouse CI Standards and deployment
Everything to WordPress coding standards, checked by PHPCS in CI, with Playwright covering the paths that would embarrass you if they broke. Version controlled and deployed from your main branch. Hosting is set up in your name at Kinsta or WP Engine, and we do not resell it or take a commission on it.
Kinsta FAQ
Questions before the first call
If yours is not here, email it. We publish the answer rather than saving it for a call.
What does a WordPress development company in India charge?
Hourly rates start at $20 and every band is published on the rates page, no gate, no call required. Fixed-scope site builds start at $8,500 after a paid discovery, and a two-day audit is $800.
Which of these five services do I need?
If scope is moving, hire a developer. If the launch date is external, buy fixed scope. If the site needs to look different too, that is design and build. If you need custom behaviour, that is plugin work. We will say which on the first call, including when the answer is none of them.
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.
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, and we run a training session before launch and record it.
Can you take over a site another agency built?
Yes, starting with a paid audit rather than a quote, plugins, theme, hosting and what is actually costing you performance. You own that report regardless of what you do next.
Do you do hosting?
No, and we do not resell it. We will recommend Kinsta or WP Engine, set it up in your name, and configure deploys, but the account and the invoice are yours.
What about SEO?
The technical half: Core Web Vitals, schema, redirects, crawlability and a content model that supports it. Strategy and content are somebody else’s job, and we will recommend someone.
How quickly can someone start?
Two WordPress engineers are free within four weeks, and a shortlist with rates and start dates reaches you inside one business day.
Do you maintain sites you did not build?
Yes, and it starts with a paid audit rather than a retainer quote. We need to know what the plugin list, theme and hosting actually look like before committing to a response time. You keep the report regardless of what you do next.
Can you work with our marketing agency?
Regularly. We take the technical half and they keep strategy, content and campaigns. It works best when one person on their side owns the brief, and worst when requests arrive from four people in three channels.
What is your position on multisite?
Useful for genuinely similar sites that want one codebase and one update cycle, such as country or brand variants. A poor fit when the sites differ substantially, because you inherit shared plugin versions and a single point of failure without gaining much.
Do you do SEO?
The technical half only: Core Web Vitals, schema, redirects, crawlability, internal linking structure and a content model that supports it. Keyword strategy and content production are somebody else’s craft, and we will recommend somebody rather than improvise.
What happens if a core update breaks something?
Everything we write is tested against the current release and the beta before it ships, which is why nothing we have built has broken on a core update to date. If you are on a maintenance retainer, we test your whole site against each release on staging before it reaches production.
How quickly can you start?
Two WordPress engineers come free within four weeks, and audits can usually begin within a week. Fixed-scope builds start after a paid discovery, so allow two weeks before build work begins. If your date is not achievable we will tell you at the enquiry stage.
Do you offer ongoing maintenance?
Yes, as an optional retainer after launch: core and plugin updates tested on staging first, dependency work, backups verified rather than assumed, and uptime monitoring. Critical fixes inside five business days. Priced on the rates page and cancellable with thirty days notice.