Why we design in the browser as early as we can.

In a design file, everything fits. Every headline sits on one line, every photo has the right proportions and the screen is exactly as wide as the designer intended. A real website doesn’t get that luxury. So we bring a design into the browser as early as we can, and we build in code rather than with a template or page builder. Here we explain why, what it gives you and where the limits are.

A picture leaves out what matters most

A traditional web design is a series of still images. One for desktop, sometimes one for mobile, and someone fills in everything in between later. How a menu opens, how fast an animation runs and what happens on a tablet or a narrow laptop screen: none of it is visible. Those decisions get made during the build, often by someone who wasn’t part of your conversations.

In the browser, nobody has to fill anything in. You scroll, click and turn your phone sideways. A movement that looked elegant in a still sometimes turns out to be slow. A layout that feels calm on a large screen can feel like a long corridor on mobile. You want to know that before you sign it off, not after.

Real content, real conditions

Designing with placeholder text is like fitting out a wardrobe without knowing what goes in it. A three-word headline fits anywhere. A twelve-word headline, or a translation that runs a little longer, shows whether the typography holds up. So we work with real copy, real names and real images as early as possible.

For a site that has to explain something, that matters twice as much. STEQ’s website explains in plain language how investing in property works: what you buy, what you get and when. You start from €100 and reach your first investment in five clicks. Whether a route like that feels clear is not something you can judge from a static design. You only find out by clicking through it yourself.

Some qualities don’t show up in a design file at all. How fast a page loads on a slow connection. Whether you can use the site with just a keyboard, and whether a screen reader understands what’s on it. In code, these are properties of the design itself, not a check at the end. A heavy video on the homepage is a choice with a cost, and we see that cost straight away.

We’d rather decide on the website itself than on a picture of it.

Why this is possible now

Building used to be expensive, so it came at the end. Everything was approved as images first, and only then built. AI has changed that order. We can now have a working version of an idea up quickly, so the browser is no longer the last stop but a place to work from the start.

What AI doesn’t do is choose. Positioning, direction and the core of the design are ours. AI gives us more versions to compare and something to react to sooner. Which version is right remains a matter of taste, and that stays with us.

No template, and why that matters

WordPress, Webflow and Framer are good at what they do. You can put together a tidy site quickly and keep it up to date yourself. For a business that needs three pages and expects little to change, a good template is a perfectly sound choice. We mean that.

But the platform then decides what your website can do: the templates, the plug-ins and whatever the editor allows. The companies we work with tend to run into exactly that limit. They need an extensive website, a platform or an interactive tool. Behind STEQ’s website sits an investor platform where you can see your positions, the offering and your documents. Something like that doesn’t fit in a template.

Building in code does ask something of you. You don’t change the structure yourself by dragging and dropping. So we agree clearly up front on management and handover: what your team adjusts itself, and what comes through us.

The brand lives in the same code

A brand is a set of agreements: colours, type, spacing, how a button looks and how things move. We record those in design tokens, named building blocks that the guidelines and the website both use. A colour then has one name and one value wherever it appears. Because brand and website take shape in the same sprint, nobody has to line them up afterwards.

That keeps the site consistent later on, too. A new page is built from the same components as the first. For STEQ we went a step further and built a dedicated tool that stacks bricks into towers, stairs and pyramids. STEQ uses it to make new images and animations themselves, and they always stay within the brand. The guidelines live online in two versions: one for people and a brand.md for AI agents.

What it gives you

For a founder or marketing team, this isn’t a technical question. It changes how you make decisions, and what you can do with your site after launch.

1. Fewer surprises. You’re reviewing something that works from the start, so what goes live is something you’ve already seen and tried.
2. Decisions on the real thing. A conversation about taste becomes concrete when you can scroll and click.
3. A site that can grow. From an extensive website to a platform or interactive tool, without switching systems first.
4. Clear agreements. You know up front what your team can change itself and what you receive at handover.

If you feel your website is falling behind your business, tell us where you are. We reply within one working day.