Northbank Studio
A recording studio that needed the room, the rates and the availability to be legible on a phone before anyone would enquire.
Brand site + headless CMS · 2026Service · Direct
Web design that survives contact with development
Most website designs are approved as pictures and then quietly changed during the build. We design and build in the same place, so what is signed off is what goes live.
01Scope
What we design
Design work here always ends in a working website. We do not sell design as a standalone deliverable that someone else has to interpret.
Marketing and brochure sites
The site that has to explain what you do and get people to make contact. Structure first — what goes on which page, and in what order — then the pages themselves.
Design systems and component libraries
If you publish often, you need a set of pieces rather than a set of pages: type scale, spacing, buttons, cards, forms, states. Designed once, built once, reused by whoever edits the site next.
Redesigns of a site you already have
Redesigning a site that ranks is a different job from designing a new one. Structure and URLs are treated as assets to be carried across, not as things to be tidied up. See also CMS migration.
Landing pages and campaign sites
Single-purpose pages built to the same standard as the rest of the site, with the tracking in place before the campaign starts rather than after the first week of data is lost.
02Method
How we design
Content first, not lorem ipsum
A layout that only works with placeholder text is not finished. We design against your real headings, your real product names and your longest paragraph, so nothing breaks the week you start editing it. If the content does not exist yet, we design against a written outline of it and say so.
Designed to a performance budget
A page speed target is agreed before the design starts, and the design is held to it. That decides how many typefaces the site can carry, how large the hero image can be, and whether a particular animation is worth what it costs. It is much cheaper to make that decision in design than to strip it out after launch.
Accessibility is part of the design, not a fix
Colour contrast, focus states, hit areas, heading order and keyboard paths are decided in the design file. Retrofitting accessibility after a build is expensive and it usually shows.
03Engagement
How a design project runs
- 01
Scope. We agree what the site has to do, who it is for, and how many page types it actually needs. Most sites need fewer than the sitemap suggests.
- 02
Structure. Sitemap and page outlines, in writing, before anything is drawn. This is the stage that saves the most money and the one most often skipped.
- 03
Design. Key pages first, at the breakpoints that matter, with the components named. You review against the outline, not against taste alone.
- 04
Build. The same team develops it. Questions that would have gone back and forth for a week between two suppliers get answered the same day.
- 05
Launch and hand over. Documented, with a short guide for whoever edits the site.
04Deliverables
What you get
- The design files, in full, with the components named and organised.
- A written page-type inventory — what exists, what each one is for.
- The built site, in a repository you own.
- A short guide for whoever edits the content.
- A list of anything deliberately left out of scope, so it does not surface later as a surprise.
After launch you can keep running the site yourself or put it on a support agreement. Both are normal. Neither is a condition of the other.
05Proof
Selected work
Placeholder — invented projects, pending real client work
Fold & Co.
A packaging studio with a large back catalogue and one designer editing it. Built as a set of components rather than a set of pages.
Brochure site + design system · 2024Halcyon Sound
Campaign pages built to the same standard as the rest of the site, with the tracking in place before the campaign opened.
Landing pages · 202506FAQ
Questions we get asked
Do you design in Figma?
Yes. You get the file, and it stays readable after we hand it over — named components, not a hundred loose frames.
Can you work with our existing brand?
Yes, and it is the more common case. We work to the brand guidelines you have. Where they run out — and for most brands they run out at about the second web breakpoint — we extend them and document what we added.
Can we take the design elsewhere to be built?
You can, and the files are yours. We will say plainly that it is not what this service is set up for: the performance and accessibility decisions above are only worth anything if the person building it knows they were made.
Do you use templates?
No. We build from the design. If a project genuinely suits an off-the-shelf theme we will tell you that, because paying us to rebuild something you could buy is not a good outcome for either of us.
How long does a site take?
It depends almost entirely on content readiness rather than on design or build time. We give a date at the end of the scope stage, once we know how many page types there are and who is writing them.
07Next step
Start a project
Tell us what the site has to do and when it needs to be live. If we are not the right people for it, you will hear that first.
Or email us at hello@felixwebsolutions.com.
Agency looking for a build partner? We work white-label →