Skip to content
URBANUPLINK

01

Street level. One detail, lit properly.

Most agency sites open with a stock photograph of somebody at a laptop. This one opens with a single continuous shot, rendered and scrubbed by your own scrolling, because a site that argues for building sites should make the argument with itself.

02

Up the facade. Nothing here came out of a template.

No theme, no page builder, no component kit bought off a marketplace. The design system on this site exists for this site only, and the same is true of every one that leaves here.
What a build includes

03

The price is on the site, with its conditions.

A landing site is EUR 2,000. A corporate site up to eight pages is EUR 2,600. A shop is EUR 4,400. Every one of those numbers is published with what it includes, what it excludes and what moves it.
Every price, in one table

04

Signal array. Static files, no runtime, no lock-in.

What gets handed over is plain HTML, CSS and JavaScript, plus the repository and every credential. It runs on any host, it outlives this studio, and leaving costs nothing.
Start a project

What you can buy, and what it costs

Six things, each with a published number and a timeline.

Not a grid of cards that all say the same thing in a different order. One ladder, so the differences between a landing site and a shop are adjacent and comparable instead of spread across six boxes.

Full price table, with exclusions

Why this studio rather than the next one

The page you are reading, measured.

Claims about quality are easy to write and hard to check. The page in front of you is the opposite, so here are its numbers - and you can check every one of them in your own browser before you believe any of it.

JavaScript on this page
181 kB

Eight compressed files, the whole framework included. None of it is analytics, and none of it comes from another origin.

CSS on this page
7 kB

One compressed stylesheet for the entire site. No unused framework CSS in it, because there is no CSS framework under it.

HTML on this page
14 kB

Prerendered at build time and compressed in transit. The text you are reading arrives in the first response rather than after a round trip to an API.

Fonts
113 kB

Two families, latin subset, served from this domain. Three files are preloaded; the rest arrive only if a weight is actually used.

The film
4.02 MB / 1.67 MB

Desktop and mobile encodes. Not requested until the largest paint has already happened, and not requested at all when your system asks for reduced motion.

Requests to other domains
0

No font CDN, no tag manager, no embedded video host, no chat widget. Check the network panel and filter by domain.

Delivery
Static files

Every route is prerendered at build time and served as plain HTML. There is no Node runtime on the host and nothing runs per request.

Infrastructure
Shared Apache, no CDN

This site is not propped up by an edge network. What you are measuring is the build, not the hosting budget.

Accessibility target
WCAG 2.1 AA

Held as an engineering standard rather than sold as a feature. Colour contrast, focus visibility and keyboard reach are checked on every page before release.

Third-party scripts
None

No analytics, no tag manager, no chat widget, no font CDN. The only value stored in your browser is your own cookie choice.

Open your browser’s developer tools and check any of this against the network panel. That is the point of publishing it.

How the work actually proceeds

Four points where something concrete changes hands.

Timelines slip on missing content and late approvals far more often than on engineering. So each step names what comes from this side and what has to come from yours.

  1. Day one

    Scope and a fixed number

    Your brief comes back as a written scope: the page list, what is built on each, the timeline and a fixed price. Not a range.

    You supply

    The site type, a rough page count, and the date it needs to be live.

  2. Day three

    The design system, before any page

    Palette, type, spacing, motion and the layout families the site will be built from - agreed as a system rather than argued page by page.

    You supply

    One named decision-maker, and the logo files if a mark already exists.

  3. Mid-build

    A running site on a real URL

    Pages land in priority order on a URL you can open on your own phone, so review happens against the real thing and not a flat mockup.

    You supply

    Copy and images for the pages being built, and the first consolidated round of comments.

  4. Handover

    Everything, transferred

    Production build deployed, repository with its history, design system, DNS and every credential. Plus a written note on how to change the things that change.

    You supply

    The second round of comments, and where you want it hosted.

What will be refused

Five kinds of work that get turned down.

Faster for both sides if you can rule this studio out in ten seconds. The reasoning behind each one is on the about page.

  1. Installing a theme on your existing CMS

    That is a different trade, and it is not priced here.

  2. Monthly content-marketing retainers

    Projects with an end date only.

  3. Builds where nobody can supply the copy

    Commission it or write it - a site cannot be finished around missing text.

  4. Rescuing a project in dispute with another agency

    Settle that first.

  5. Discounts without a smaller scope

    A price on the price page comes down only when scope comes out with it.

If the scope is clear, the first reply carries a number rather than a meeting invitation.

Send the brief