Home

Services

SEO Services Social Media Website Development AI Automation About Reviews Portfolio Blog Contact Free Website Audit
WordPress Development

You Are Not Choosing a CMS. You Are Choosing Who Can Change It Later

Almost every WordPress decision is made on how quickly something can be launched, and almost every WordPress regret is about what it cost to maintain. The plugin that saved a fortnight becomes the plugin nobody dares update. The page builder that let marketing edit a hero becomes the reason a developer quotes four days for a change that should take one. This page is about the second number, because the first one is the one everybody already asks about.

No credit card required · 30-minute call · No obligation to sign up

12+ years in digital marketing Working with WordPress Development businesses
✓ You Own The Code — No Lock-In ✓ Quoted & reported in USD ($) ★★★★★ Trustpilot 5.0 ★★★★★ Google 4.9
Two desktop monitors showing web page layouts and a design file open in an editor
Question we ask firstWho edits?
Initial term, then monthly3-month
The Numbers First

Six build decisions that bill you later

None of these shows up in a launch quote. All six show up in the second year, and by then the cost of reversing them is the reason they do not get reversed.

  • Every plugin is a dependencySomeone else’s code, updated on their schedule
  • Page builders trade edit for lock-inMarketing can change it · nobody can leave it
  • Themes are abandonedA premium theme is a bet on a small company
  • Updates break things quietlyOne page, some browsers, nobody looks for weeks
  • Hosting decides half the speedAnd the cheap tier is cheap for a reason
  • “Custom” means unmaintainable by anyone elseIncluding you, when we are gone

The last row is the one worth being suspicious of when you read any agency’s WordPress page, including this one. “Bespoke build” sounds like craftsmanship and often means a theme only its author understands, with the business now dependent on one supplier for every change. We build so that a competent WordPress developer who has never met us can open the site and work out what is going on, because you should be able to leave. That is a lower-margin way to build and it is the right one.

Straight Talk

Ask who edits the site before choosing anything

The first question in a WordPress build is not design and it is not features. It is who will change the site once it is live, and how often. A business where marketing publishes twice a week needs a completely different build from one where the site is touched three times a year by whoever is available. Every subsequent decision — theme, builder, plugin set, hosting — follows from that answer, and getting it wrong is what produces sites that are technically fine and practically frozen.

Page builders are the clearest example of the trade. They genuinely do let a non-technical person change a layout without breaking anything, and for a marketing team publishing weekly that is worth real money. They also embed their own markup into every page, which means the content is not portable, the site is slower than it needs to be, and moving away later means rebuilding rather than exporting. Neither of those facts is a reason to avoid them. They are a reason to choose deliberately, knowing which cost you are buying.

Plugins deserve the same treatment and rarely get it. Every one is a dependency on somebody else’s code, released on their schedule, and a site with forty of them has forty small chances of something breaking each month. The discipline is not “use fewer plugins” as a slogan — it is asking, for each one, whether the job is worth a permanent dependency, and whether the plugin is maintained by somebody who will still be there in three years.

Then there is the update problem, which is a process failure more than a technical one. WordPress, its theme and its plugins all update independently and none of them tells you what broke. Sites do not usually fail loudly after an update; they fail on one template, in some browsers, and nobody notices for weeks. A staging copy and a short checklist fixes this permanently and costs less than one emergency does.

  • Who edits, and how often — The answer that determines every other decision. Ask it before design, not after launch.
  • Page builders are a trade, not a mistake — Editability now for portability later. Choose it knowingly or inherit it accidentally.
  • Each plugin is a permanent dependency — Not "use fewer" as a slogan — ask whether this job is worth owing somebody else code.
  • Updates fail quietly — One template, some browsers, weeks unnoticed. Staging plus a checklist ends it.
  • You should be able to leave — Built so a developer who has never met us can pick it up. Lower margin for us, and correct.
A developer working at a desktop with a content management screen open

The plugin that saved a fortnight in month one becomes the plugin nobody dares update in year two. Both facts are true and only one of them is in the quote.

.
Ghalib Ashrafi Founder & Digital Strategist · 12+ years across search, social & web

What a WordPress build actually involves

Six things, and the first one decides the other five.

01

The Editing Question

Who changes the site, how often, and how technical they are. Answered before anything is chosen, because theme, builder, plugins and hosting all follow from it and none of them is cheap to reverse.

02

Theme or Custom, Decided Honestly

A well-supported theme is often the right answer and we will say so. Custom is for when the requirement genuinely is not met — not as a default that sounds more impressive on an invoice.

03

A Justified Plugin Set

Each one argued for individually: what it does, what it would cost to remove, and whether whoever maintains it will still be maintaining it in three years.

04

Performance in the Build

Core Web Vitals designed in rather than bolted on with a caching plugin at the end. Hosting is part of this conversation, because it decides roughly half the result.

05

Staging and an Update Routine

A copy to break, and a short checklist for what to look at afterwards. This is the cheapest insurance in WordPress and the most commonly skipped.

06

Documentation and Handover

What was installed, why, and how to change the things you will want to change. Written so somebody who has never met us can take over — because you should be able to.

12+Years building and maintaining sites
4Services run by one team
100%Of the code and content is yours
3-monthInitial term, then month to month

What clients say

Real clients, quoted in their own words — published with their permission.

More of them, in full, on our reviews page.

— Our Proprietary Methodology —

The Visibility Framework™, applied in WordPress Development

The method doesn’t change by market. What it’s pointed at does.

Step 01

Audit & Discovery

What the current site earns, where it leaks, what your competitors do better, and what the new one must achieve. Ends in a written scope and a fixed price — not an estimate that grows.

Step 02

Structure & Design

Sitemap, wireframes and user journeys agreed before decoration, then a design system applied consistently. You approve the shape before we make it beautiful.

Step 03

Build & Test

Front end, back end, CMS and integrations, on a staging site you can see from day one. Tested on real devices, real screen readers and real slow connections.

Step 04

Launch & Improve

Redirects verified, analytics connected, handover recorded — then we look at what real visitors actually do and fix what the design assumed wrongly.

Honest, No-Nonsense Commitment

The price we quote after discovery is the price you pay — if we underestimated the work, that is our problem, not a change request. And on any rebuild, if organic traffic drops because of something we did at migration, we fix it at our cost, however long it takes.

Investment

Website Development pricing for WordPress Development, in USD

Quoted per build rather than per month, because a website is a project with an end. What moves the number is how much is genuinely custom and how much content has to be migrated — content migration is routinely underestimated and it is usually the largest single line.

Starter

A well-built site on a supported theme.

$2,500 – $5,000
  • Theme selection & configuration
  • Justified plugin set, documented
  • Staging environment & handover notes
Get a Quote

Enterprise

Multi-site, multi-language or integrated builds.

$15,000+
  • Dedicated senior developer
  • Integrations & multi-site architecture
  • Ongoing maintenance retainer available
  • Optional: combine all 4 services for full-funnel growth
Get a Quote

Every plan is scoped around your market — get a free audit and we’ll recommend what fits, priced in USD.

What you’re actually committing to

Most agencies keep this in a contract you only see after the sales call. We would rather you knew now, because it is the question everyone asks second — right after the price.

  • A fixed price, agreed before we startQuoted after discovery, not estimated on a call. If the work takes longer than we thought, that is our risk — the price does not move unless you change the scope.
  • 50% to begin, 50% at launchNo large upfront payment held for months, and nothing owed until the site is live and you have seen it working.
  • You own everythingDomain, hosting, code repository, design files and content — all in your name from day one, and still yours if we never work together again.
  • No proprietary lock-inStandard, widely-used technology only. Any competent developer can take the site over, and nothing stops working because you stopped paying us.
  • Two rounds of revisions per stageIncluded at wireframe and design stage, where changes are cheap. Beyond that, or after sign-off, changes are quoted before any work starts.
  • 30 days of support after launchBugs and small tweaks included as standard. A care plan afterwards is optional, never automatic, and cancellable with 30 days’ notice.

These are the terms as they appear in the agreement itself — nothing here is softened for the website. The full wording lives in our terms and conditions, and you get the agreement to read before anything is signed or invoiced.

WordPress Development Website Development questions, answered

Should we use a page builder like Elementor? +
It depends entirely on who edits the site. If marketing publishes weekly and needs to change layouts without a developer, a builder earns its cost. If the site changes three times a year, you are paying in speed and portability for a convenience nobody uses. Both are defensible; what is not defensible is ending up with one by accident and discovering the trade two years later.
The number is the wrong question, and "use fewer plugins" is a slogan rather than a method. Each one is a permanent dependency on somebody else’s code, released on their schedule. The right test is per plugin: is this job worth owing somebody else code, and will whoever maintains it still be maintaining it in three years? Twelve well-chosen plugins beat six badly chosen ones.
Frequently not, and we will say so even though custom bills more. A well-supported theme is maintained by people whose job it is, and it will still work after the next three WordPress releases. Custom is right when the requirement genuinely is not met by anything available — not as a default that sounds more impressive on an invoice.
Almost nothing fails loudly. What happens is that one template renders wrong in some browsers and nobody notices for weeks. That is a process problem rather than a technical one, and it is solved permanently by a staging copy and a short post-update checklist — which costs less than a single emergency.
Usually, and they are quoted separately because they are separate jobs. This page is about the build: what gets installed, who maintains it, what breaks on update. The SEO side — crawling, indexation, schema, the settings inside the SEO plugin — is covered on our WordPress SEO page, and the two are deliberately kept apart so neither one pretends to be the other.
Yes, and we build for it. The code, the content and the documentation are yours, and the site is put together so that a competent WordPress developer who has never met us can open it and understand what is going on. That is a lower-margin way to build — it makes us easier to leave — and it is the right way.
Keep Exploring

Related Website Development pages

Same service, different angle — by market, by discipline and by platform.

Get A Free WordPress Review

Send us the site and we will tell you what it costs to maintain — the plugin debt, the update risk, and what a change actually takes.

Ready to build something you can still change in two years?

Free 30-minute audit · No obligation · Response within 24 hours

Get in touch with Ghalib Ashrafi HQ

Ghalib Ashrafi takes on work for brands in six markets — the UK, USA, UAE, Saudi Arabia, Australia and Pakistan. Every enquiry gets a reply within 24 hours.

Phone / WhatsApp: +92 343 2653224
Email: info@ghalibashrafi.com
Hours: Mon–Sat, 10am–7pm (PKT)
Still deciding? Get a free website audit — no obligation. Get Free Audit