// Service · Edinburgh

Custom web
development, Edinburgh.

Edinburgh web development from £2,500. Front end, back end, e-commerce, performance, accessibility and security, all handled by two senior developers.

Recent retainers ↓
// Projects from £2,500
// Live in 4–8 weeks
// Studio 50 mi west, G51
// Support From £99/mo

// Edinburgh in numbers

The capital's market, · with the sources shown.

506520 people in Edinburgh (NRS Population Estimates for Settlements and Localities in Scotland, 2020)
19690 registered businesses (Scottish Government, 2025)
70 monthly UK searches for "web development edinburgh" (DataForSEO Labs)

// Edinburgh

Built for scrutiny,
and for August.

Our impression of Edinburgh briefs is that they get inspected more closely than most. A financial services client may have a compliance reviewer looking at how forms handle data. University and public sector tenders often put accessibility in writing. A technology buyer might send a developer to read your markup before anything is signed. None of that is a problem when the build was done properly, and all of it is expensive to retrofit.

The other thing this city does to a website is August. Businesses whose year has a peak in it need a hosting and caching plan sized for the busiest fortnight rather than the average week. That means static pages served from a CDN where possible, cached responses for anything dynamic, and a load test run in spring rather than a nervous evening during the Fringe.

Both are planning decisions rather than clever code. We settle them at kickoff, write them into the scope and test against them before launch. The wider service sits on our UK web development page, and where the brief starts with structure and look instead of code, web design in Edinburgh is the other half of the same studio.

// Our process

Four stages,
each signed off.

01

Scope and technical plan

One call covers what the site has to do commercially, then we write the technical side down: templates, data model, integrations, hosting, and the performance and accessibility targets we will be held to. That document is the quote's basis, and you keep it whether or not you hire us.

02

Build on a preview link

Templates go up as they are written, on a private URL you can open from your own devices. You review real pages with your own content in them, and anything that turns out wrong gets caught while it is still cheap to change.

03

Integrate and test

Payments, forms, CRM handoffs and any third-party feeds get wired in and tested against the live systems. Performance, keyboard navigation and screen reader behaviour are checked here too, before the site is public rather than after a complaint.

04

Launch and transfer

Redirects mapped, schema validated, analytics and Search Console confirmed, backups running, then the repository, hosting and documentation move to you. We watch the first fortnight closely so a dropped page is spotted in days.

// Selected work

Three builds
we can show the work on.

// 01Regulated professional services

UK Visa Assistance

A practice covering dozens of visa routes needed a structure an anxious applicant and an HR manager could both use. We organised it into three hubs, wrote and shipped 42 flagship route pages plus 30 community pages, and built the custom theme underneath.

42flagship pages written in-house
82pages live in the sitemap
Read the case study
// 02Marketing agency

First Digital Media

Two engineering faults cleared in one pass. CloudFlare and image compression for the load times that were costing them phone visitors, then HSTS, SSL and reCAPTCHA so a prospect typing contact details into a form can see the site protects them.

+50 %conversions
Read the case study
// 03Supply-chain technology

9Particle

The front end was the visible half of this job. Filtering, sliders, lightboxes and scroll behaviour were rebuilt on a component framework so that a supply-chain dashboard stopped feeling like a form, and visitors went on to stay noticeably longer.

40 %longer time on site
Read the case study

// Why Delivix

Five commitments
that go in the scope.

  • Saad and Sheikh are the only two people with commit access to your repository, from the first template through to handover.
  • Targets are written into the scope. Page weight, Core Web Vitals and accessibility behaviour are agreed numbers, checked before launch rather than described in a pitch.
  • The stack is chosen around whoever maintains the site afterwards. If WordPress is the wrong answer for your team we say so, even though it is the platform we build on most often.
  • Everything ships under licences you can read. Repository, hosting and build tooling transfer on launch day, ready for whoever you hire next.
  • Scope changes get priced before they get built, and we say when a requested feature is unlikely to pay for itself.

// Platforms

Choosing the stack
before the design.

The platform decision gets made too late on most projects, usually after the design is signed off and the constraints are already baked in. We take it first, because it changes what the pages can do and what the site costs to run for the next five years.

Three answers settle it: how often somebody publishes after launch, whether anyone has to log in, and whether money changes hands on the site. Frequent publishing points to WordPress with a theme written for you, covered on our custom WordPress page. Occasional changes point to a hand-coded static front end, cheaper to host and harder to break. Accounts, dashboards and unusual pricing logic point to a custom application layer.

You get the running costs of every option on one page: hosting, licences, the realistic time your own team will spend, and what leaving that platform would cost in three years. Then you choose, and the answer goes into the scope document before a single template is designed.

// Distance

Fifty miles along the M8.

Fifty miles of M8 sit between your office and ours, close enough that we can be in a room in Edinburgh by mid-morning when a project calls for it. The studio itself is 119 Whitefield Road in Glasgow, and we hold no address in the capital. A kickoff, a board presentation or a launch morning in the city is a straightforward yes.

In practice a handful of those per project is plenty. Development runs on a repository, a preview link and a shared list of open items, and a screen share with the site open settles more in half an hour than a meeting does in two. We would rather put the travel budget into build time, and we will say when a trip is not worth making.

What does not change with distance is who does the work. Two brothers, no juniors, nothing offshored, and a direct line to whoever wrote the part you are asking about. Once the build is stable, ongoing SEO work for Edinburgh clients picks up where development finishes, and clients further north can read web development in Dundee. To price your own brief, book a call.

What our clients say

Trusted by local businesses.
Built for results.

"Delivix transformed our online presence completely. Their SEO expertise helped us rank on the first page of Google within three months. The team is professional, responsive, and truly understands digital marketing."

A
Akil
Whitefield Office Suites

"Working with Delivix was a game-changer for our business. They redesigned our website and implemented an SEO strategy that doubled our organic traffic. Highly recommended!"

H
Harry J
ResearchProspect

"The team at Delivix delivered exceptional results. Our new website is fast, modern, and converts visitors into customers. Their ongoing support and expertise in SEO have been invaluable."

K
Kevin
ePartic
// FAQ

Questions
we always get.

The other questions are answered on the brief. Fill it in or book a call.

£2,500 is the floor. What lifts an Edinburgh quote above it is almost always transactions or accounts, because anything taking payments or holding logins needs a test pass a brochure site never sees. Content volume is the second driver: six service lines and a publications archive need templates a single-service firm will never use. One short call is enough for us to price it.

No. Room 11, 119 Whitefield Road, Glasgow G51 2SD is the only Delivix address there is. Day to day that changes very little, because the thing you review each week is a preview link you open yourself, and a question goes straight to whoever wrote the code instead of being passed along a chain. Travelling through when a project needs it is covered further up this page.

We load test it before launch. A run at several times your expected peak shows where the first thing bends, and in our experience that is the database well before the pages themselves. Whatever bends gets cached, moved onto the CDN or given more headroom, and the test runs again until the graph holds. If your current hosting cannot reach that number, we tell you what a plan that can costs.

It splits in two. The technical half is ours: HTTPS throughout, spam handling on every form, database users limited to exactly what they need, and backups held off-site. The policy half is not, so we build to whatever your privacy notice commits to and leave the drafting to your solicitor or your DPO. If a compliance reviewer wants to walk through how a form handles data, we will join that call.

Yes. The platform question usually answers itself: Shopify where you would rather someone else carried payments and PCI scope, WooCommerce where the pricing rules or the product data need real code behind them. Most of the build time goes on proving the checkout survives every combination of delivery band, discount and tax rule you actually trade with, on a real phone as well as a desk.

Often, and it can be the cheapest way to run a project. Two arrangements work well: we take the front end while your team keeps the API, or we build a CMS layer around a system your own developer maintains. What we ask for is a named contact and agreed boundaries at kickoff, because shared ownership without either of those is where projects stall.

We treat that as a scoping question at the start rather than a rescue job later. If a members area, a second language or a third brand is anywhere on your roadmap, the data model gets room for it now, which costs very little during the build and a great deal in year two. Where the roadmap is genuinely unknown we say so and keep the structure simple.

Care plans start at £99 a month and cover updates, security patches, backups and small content changes. They are optional, and you own the code, the hosting and the documentation whether or not you take one. If you would rather grow the site's search visibility afterwards, that is separate work on an Edinburgh SEO retainer from £1,200 a month.