// Service · Edinburgh
Web development in Edinburgh
Web development in Edinburgh from £2,500: front end, back end, e-commerce, performance, accessibility and security, with written targets in every scope.
// Edinburgh in numbers
The capital's market, · with sources shown.
// What we deliver
Six parts of every build.
01
Front end
Semantic HTML, hand-written CSS and JavaScript only where a page needs it. Pages stay small and are easy to change later.
02
03 Back end
PHP and Node work behind the pages: custom post types, APIs, scheduled jobs and admin screens designed for the people who use them every day.
E-commerce
Stores on Shopify or WooCommerce, plus the parts customers never see: pricing and tax rules, delivery bands and accurate stock across every channel you sell through.
04Performance
We set a page weight budget and Core Web Vitals targets at kickoff and hold to them. We plan caching, CDN delivery and image handling early, because adding speed later costs more.
05Accessibility
We build keyboard paths, focus states, contrast and screen reader labels into every template. Public sector and education buyers ask for this in writing, and every visitor benefits.
06Security
We patch dependencies on a schedule, agree an incident plan in advance and test backups by restoring one.
// Edinburgh
Close scrutiny and festival traffic.
Our impression is that Edinburgh briefs get checked more closely than most. A financial services client may have a compliance reviewer check how forms handle data. University and public sector tenders often require accessibility in writing. A technology buyer may ask a developer to read your markup before signing. A well-built site passes these checks, and fixing them later is expensive.
August also affects websites in this city. A business with a seasonal peak needs hosting and caching sized for its busiest fortnight. That means static pages on a CDN where possible, cached responses for dynamic content, and a load test in spring, well before the Fringe.
Both are planning decisions. We settle them at kickoff, write them into the scope and test against them before launch. The wider service is on our UK web development page. Where the brief begins with layout and look, web design in Edinburgh covers that stage.
// Our process
Four stages, each signed off.
01
Scope and technical plan
One call covers what the site must achieve. Then we document the templates, data model, integrations, hosting, and the performance and accessibility targets we commit to. The quote is based on that document, and you keep it whether or not you hire us.
02
Build on a preview link
Templates go up on a private URL as we build them, and you can open it on your own devices. You review real pages with your content in them, and we fix problems while they are cheap to change.
03
Integrate and test
We connect payments, forms, CRM links and third-party feeds and test them against live systems. We also check performance, keyboard navigation and screen reader behaviour before the site goes public.
04
Launch and transfer
We map redirects, validate schema, confirm analytics and Search Console and start backups. Then the repository, hosting and documentation move to you. We monitor the first two weeks closely, so we spot any dropped page within days.
// Selected work
Builds we canshow you.
// 01Regulated professional services
UK Visa Assistance
An immigration practice covering dozens of visa routes needed a site that both anxious applicants and HR managers could use. We organised it into three hubs, wrote 42 flagship route pages and 30 community pages, and built the custom theme.
42flagship pages written in-house
82pages live in the sitemap
// 02Marketing agency
First Digital Media
We fixed two problems in one pass. Cloudflare and image compression cut the load times that were losing phone visitors. HSTS, SSL and reCAPTCHA show prospects that the forms protect their details.
+50 %conversions
// 03Supply-chain technology
9Particle
The front end was the visible part of this rebuild. We rebuilt filtering, sliders, lightboxes and scroll behaviour on a component framework, so the supply-chain platform became easier to use. Time on site went up 40%.
40 %longer time on site
// 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 to handover.
- Page weight, Core Web Vitals and accessibility targets go into the scope as numbers, and we check them before launch.
- We choose the stack for the people who maintain the site. If WordPress does not suit your team, we say so, even though we build on it most often.
- Everything uses licences you can read. The repository, hosting and build tools transfer to you on launch day.
- We price scope changes before we build them, and we tell you when a feature is unlikely to pay for itself.
// Platforms
Choosing the stack before the design.
On most projects the platform is chosen too late, after the design is approved and the limits are fixed. We choose it first, because it affects what the pages can do and what the site costs to run for the next five years.
Three questions decide it: how often someone publishes after launch, whether anyone logs in, and whether the site takes payments. 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, which costs less to host and is harder to break. Accounts, dashboards and complex pricing point to a custom application layer.
You see the running costs of every option on one page: hosting, licences, your team's time and the cost of leaving that platform in three years. You choose, and the decision goes into the scope before we design any template.
// Where we work
Where else this studio builds.
// Distance
Fifty miles along the M8.
Our studio is at 119 Whitefield Road in Glasgow, fifty miles along the M8 from your office. We can reach an Edinburgh meeting by mid-morning when a project needs it, and we have no office in the capital. Kickoffs, board presentations and launch mornings in the city are easy to arrange.
Most projects need only a few of these visits. Development runs on a repository, a preview link and a shared list of open items. A screen share with the site open often settles more in thirty minutes than a two-hour meeting. We prefer to spend the travel budget on build time, and we tell you when a trip is not worth making.
The same people do the work wherever you are, and you contact the person who wrote each part directly. Once the build is stable, SEO work for Edinburgh clients can continue where development ends. Clients further north can read web development in Dundee. To price your brief, book a call.
What our clients say
What our clients say about us.
"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."
"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!"
"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."
// FAQ
Questions we always get.
The other questions are answered on the brief. Fill it in or book a call.
Custom builds start at £2,500. Payments and user accounts raise most Edinburgh quotes, because they need testing that a brochure site does not. Content volume comes second: six service lines and a publications archive need more templates than a single-service firm. One short call is enough for us to price your project.
No. Room 11, 119 Whitefield Road, Glasgow G51 2SD is our only address. Day to day this changes little. You review the work each week on a preview link, and your questions go straight to the person who wrote the code. The section on distance, further up this page, covers when we travel.
We load test it before launch. A test at several times your expected peak shows what fails first, and in our experience that is the database, well before the pages. We cache it, move it to the CDN or add capacity, then test again until it holds. If your current hosting cannot handle that load, we tell you what a suitable plan costs.
There are two parts. We handle the technical part: HTTPS throughout, spam protection on every form, database users with only the access they need, and off-site backups. Your solicitor or DPO handles the policy part, and we build to what your privacy notice says. If a compliance reviewer wants to check how a form handles data, we join that call.
Yes. Choose Shopify if you want someone else to carry payments and PCI scope. Choose WooCommerce if your pricing rules or product data need custom code. Most of the build time goes on testing the checkout against every delivery band, discount and tax rule you use, on a real phone and on a desktop.
Often, and it can be the cheapest way to run a project. Two set-ups work well: we build the front end while your team keeps the API, or we build a CMS layer around a system your developer maintains. We ask for a named contact and agreed boundaries at kickoff, because shared projects stall without them.
We plan for growth at the start. If a members area, a second language or a third brand is on your roadmap, we leave room for it in the data model. That costs little during the build and saves a lot in year two. If the roadmap is unclear, 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 either way. To grow search visibility after launch, see our Edinburgh SEO retainer from £500 a month.