Custom Is a Maintenance Decision Wearing a Build Decision’s Clothes
Anything can be built. That is not the question, and treating it as the question is how projects end up somewhere expensive. Every custom thing is a thing only you maintain. No update arrives for it. No plugin replaces it. Nobody else has already hit its bugs and written the fix. The honest version of the question is who looks after it in year three — and whether the thing it does is worth that.
No credit card required · 30-minute call · No obligation to sign up
Six things you give up the moment you go custom
None of these is a reason to refuse. They are the price, and the point of listing them is that they are usually discovered rather than agreed.
- Nobody else finds the bugsOn a platform, thousands do it for you
- No update ever arrivesImprovements are things you commission
- Hiring is harderYour stack, not a common one
- Documentation is yours to writeAnd it is the first thing to slip
- There is no marketplaceEvery integration is a build
- The knowledge sits in a few headsUntil they leave
The last row is the one that actually ends projects. A custom system is fine while the people who built it are still answering questions, and it becomes a liability the month after they stop. That is a staffing risk dressed as a technical choice, and it deserves an answer before the build starts rather than a discovery afterwards.
The test is whether the thing you need is actually unusual
Custom earns its cost when what you do genuinely does not exist as a product. A pricing rule nobody else has. A workflow that is the business rather than a support for it. An integration with something internal that no platform will ever have heard of. In those cases a platform does not save you money — it hides the cost inside a stack of plugins that fight each other, and you pay it anyway with worse visibility.
It does not earn its cost when the requirement is a normal website with an unusual mood. Marketing pages, a blog, a contact form and a handful of services are extremely well served by things that already exist, are patched by other people, and can be maintained by anyone you hire. Building that from scratch buys control nobody will exercise and takes on maintenance nobody budgeted for.
The middle case is the interesting one, and the answer is usually a boundary rather than a side. Use a platform for the ordinary parts and build only the genuinely unusual piece — then be strict about the border between them, because that border is what stops the custom part quietly absorbing everything next to it. This is also, in practice, what most people mean when they say headless: the content and the pages run on something conventional, and the unusual part is a separate application talking to it. It is the same decision as this whole page, asked about one layer instead of the whole site.
Whichever way it goes, the deliverable that matters is not the code. It is whether somebody who has never met us can pick it up. Conventional structure over clever structure, dependencies that are still maintained, a README that describes how to run it, and no piece of infrastructure that only exists in one person’s account. We would rather build something slightly less elegant that you can hand to anyone.
- ✓Custom fits genuinely unusual work — A pricing rule, a workflow that is the business, an internal integration.
- ✓It does not fit a normal site — Marketing pages and a blog are extremely well served by what exists.
- ✓The middle case wants a boundary — Platform for the ordinary parts, custom only for the unusual piece.
- ✓Headless is this question, one layer down — Conventional content layer, separate application. Same trade-off.
- ✓Handover beats elegance — Conventional structure, maintained dependencies, nothing in one person’s account.
A custom system is fine while the people who built it still answer questions. It becomes a liability the month after they stop.
How we build when custom is the right answer
Six commitments, and most of them are about the day we are not here.
Find the Unusual Part
Before anything is built, work out which piece genuinely does not exist as a product. Frequently it is much smaller than the brief assumed, and that is the cheapest finding available.
Draw the Boundary
Platform for the ordinary parts, custom for the unusual one, and a strict border between them. Without the border, the custom part absorbs its neighbours a feature at a time.
Conventional Over Clever
Ordinary structure, mainstream dependencies that are still maintained, no framework chosen because it is interesting. The test is whether a stranger can read it.
Handover Written First
How to run it, deploy it and change it — written while it is being built, not promised for the end. Documentation deferred to the end is documentation that does not exist.
Nothing in One Person’s Account
Domains, hosting, repositories and keys in accounts you own from day one. The commonest way a custom build becomes unmaintainable has nothing to do with the code.
A Maintenance Answer, Agreed
Who looks after it, at what cost, from the month after launch. Quoted with the build rather than raised afterwards, because it is part of the price of custom.
What clients say
Real clients, quoted in their own words — published with their permission.
“It was a pleasure working with Ghalib and his team.”
“Ghalib’s clear guidance has helped improve our website’s SEO performance.”
“We’re very thankful to Ghalib and his team for building a fully-functioning website for our business.”
More of them, in full, on our reviews page.
— Our Proprietary Methodology —
The Visibility Framework™, applied in Custom Web Development
The method doesn’t change by market. What it’s pointed at does.
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.
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.
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.
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.
Website Development pricing for Custom Web Development, in USD
Quoted after the scoping stage, never before — a fixed price given before anyone knows which part is genuinely unusual is a guess with a signature on it. Maintenance is quoted at the same time rather than raised later, because it is part of what custom costs and pretending otherwise is how the number ends up wrong.
Scoping
Find out how much of this is actually custom.
- Which piece genuinely does not exist as a product
- Where the platform boundary should sit
- A written recommendation, including "do not build this"
Custom Build
The unusual part, built properly.
- Conventional structure, maintained dependencies
- Handover documentation written as we go
- Every account in your name from day one
- Optional: bundle in SEO or Social Media
Platform & Application
Headless or hybrid, with a strict border.
- Conventional content layer, custom application
- Documented contract between the two
- Maintenance and support agreed with the build
- Optional: combine all 4 services for full-funnel growth
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.
Custom Web Development Website Development questions, answered
Related Website Development pages
Same service, different angle — by market, by discipline and by platform.
Find out how much of it is actually custom?
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.