Northcode · Software & digital products · Manchester

Digital products, engineered properly.

We design, build and grow websites, platforms and software for businesses that depend on them, then keep making them faster, easier to find and better at their job.

  1. 01Design
  2. 02Build
  3. 03Grow
hello@northcode.ukManchester, United Kingdom

Design · Digital experiences

The interface is where the engineering shows.

People judge a product by how it feels: how fast it answers, whether they can find things, whether it works on the phone in their hand. Design and engineering are one job here, done by the same people.

ConceptOne set of components reflowed across three screen sizes.
Structure before style
Journeys and information architecture first, so the interface has something solid to express.
One system, every screen
Components designed once and reflowed for phone, tablet and desktop, not three separate designs.
Accessible by default
Keyboard, screen reader, contrast and zoom are part of the component, not a later audit.
Fast as a feature
Static where possible, interactive where it helps, and nothing loaded that the page doesn't use.
Web development

Build · Under the surface

Most of a good product is the part nobody sees.

Behind every page is a request that has to be answered quickly, correctly and safely, by an architecture someone can still understand in five years. Follow one through the system.

  1. The request reaches the nearest edge location. Static pages and assets are answered from cache in milliseconds.

  2. The page or app renders on the server where content matters for search, in the browser where interaction does.

  3. One well-defined, versioned API. Authentication, validation and rate limits live here, once.

  4. Business logic in one place. Anything slow or external goes to a queue, so the visitor never waits on it.

  5. Payments, CRMs and third-party APIs, called with retries, idempotency and reconciliation, so failures surface instead of hiding.

  6. A schema that matches the business, migrations that are reversible, backups that are restored, not just taken.

ConceptA request's path through a typical product architecture.
Software development

Grow · Built to be found

Search starts in the codebase.

Before anyone can find a page, a crawler has to reach it, a renderer has to see it, and an index has to understand it. Each step can fail for engineering reasons, which is why we treat search as part of the build.

  1. 01

    Crawl

    Real links, a clean sitemap and no crawl wasted on pages that shouldn't exist.

  2. 02

    Render

    Content in the HTML, not waiting on JavaScript. Fast enough that rendering finishes.

  3. 03

    Index

    One canonical URL per page, structured data that describes what's actually there.

  4. 04

    Rank

    An architecture that groups topics and links them the way people search for them.

ConceptThe pipeline every page passes through before it can appear in a search result.

Strategy and implementation, in the same team.

When we find a search problem, we don't write it up for someone else to fix. We change the information architecture, the templates, the rendering and the structured data ourselves, then measure what happened.

Technical SEO

Grow · Built to improve

Launch is where the useful work starts.

A digital product has to be measured, tested and improved. Most of its value is decided in the months after it goes live, by how well that loop runs, and by whether the people running it can change the product themselves.

  1. 01

    Instrument. Analytics that match the journey, so the numbers mean something.

  2. 02

    Find the leak. Where people drop out, on which devices, and why.

  3. 03

    Test. Experiments where the answer genuinely isn't known; obvious fixes just get fixed.

  4. 04

    Ship. Winning changes built properly into the product, then measured again.

Conversion & analytics
ConceptAn experiment splits traffic, measures one metric, and ships the result.

Built properly

This website is the first example.

We'd rather show than claim. These numbers are measured from the build you're looking at, and a test fails if they ever stop being true.

Pages, every one pre-rendered to static HTML
12
This page’s HTML, CSS and JavaScript, compressed
24.1KB
JavaScript before the optional 3D scene
2.3KB
Third-party requests, trackers or cookies
0
How this site runs: static pages at the edge, one small function for enquiries, nothing else.
export function detectSceneMode(): SceneMode {
  const nav = navigator as NavigatorHints;

  if (window.matchMedia("(prefers-reduced-motion: reduce)").matches) return "poster";
  if (nav.connection?.saveData) return "poster";
  if (nav.deviceMemory !== undefined && nav.deviceMemory <= 2) return "poster";
  if (!hasWebGL()) return "poster";

  const touchFirst = window.matchMedia("(pointer: coarse)").matches;
  const smallViewport = window.matchMedia("(max-width: 60rem)").matches;
  const fewCores = (navigator.hardwareConcurrency ?? 8) <= 4;

  return touchFirst || smallViewport || fewCores ? "lite" : "full";
}
From the hero: the 3D scene is decided before any 3D code downloads. src/components/three/capability.ts

How Northcode works

No disappearing for six months.

You should always know what we’re doing, why we’re doing it, and what comes next.

  1. 01

    Understand

    The business, the goal, the customer and what already exists.

  2. 02

    Design

    Journeys, structure and interface, tested at real sizes before they're built.

  3. 03

    Build

    Small, working increments you can see and use from the first weeks.

  4. 04

    Launch

    Released carefully, with monitoring, redirects checked and a way to roll back.

  5. 05

    Measure

    Real performance, search and behaviour data against an agreed baseline.

  6. 06

    Improve

    Stay involved: refine, extend and keep it healthy over time.

Technical partnership

Start with one thing. Keep going if it works.

  1. 01

    Project

    Build something specific: a site, a platform, an integration, a fix.

  2. 02

    Grow

    Keep improving what was built: search, speed, conversion, new features.

  3. 03

    Partnership

    Take ongoing responsibility for the platform and the decisions around it.

Technical partnership

Our promise

  • If we don’t think we’re the right people we’ll tell you.
  • If something shouldn’t be built we’ll tell you.
  • If there’s a simpler solution we’ll recommend it.
  • If we build it we’ll stand behind it.

Contact

Tell us where your software is today.

Whether it’s already live, half-built, fragile, or still an idea, we’ll give you an honest view of what it needs and what can wait.