Drawn and built together
Interface decisions are made with the constraints already known, so the design does not have to survive a negotiation later.
A design engineering studio is a team that designs an interface and writes the production code that ships it, rather than a design agency that hands files to a separate development shop. One group owns the work from the first sketch to the deployed product, so there is no translation layer between what was drawn and what users get.
A handoff needs explicit decisions about content, states and behaviour, whether the people involved work at one company or several.
A static design can leave loading states, empty results, errors or interactions unspecified. Agree who designs and implements those cases, and check the working screens against the approved result.
Combining design and implementation makes those decisions easier to discuss in one team. It still requires a clear scope, tests and review of the actual product.
Interface decisions are made with the constraints already known, so the design does not have to survive a negotiation later.
Loading, empty, error, offline and the too-long name someone will eventually type. These are design work, not leftovers.
Ongoing support can stay with the people who built the product when agreed. If the project ends at handover, record the access, documentation and maintenance responsibilities.
Search for design engineering and you will mostly find structural and mechanical engineering firms. That is the older, physical meaning: engineers who design bridges, parts and machines.
The meaning on this page is the software one, popularised in the last few years by teams at companies like Vercel and Linear. A design engineer in that sense is a person who is genuinely good at both interface design and front-end engineering, and who does both jobs on the same product. Both meanings are legitimate. They just describe different professions that happen to share a name. Both of them turn up on our blog, which is mostly about the design process itself.
Products and client sites that run today, not portfolio mock-ups.
Giftalytics and JP Studio Search both run in production. When we say we ship SaaS rather than mock it, these are the receipts.
Client work. An audiovisual production company in the Netherlands: light, sound and video for events. Dark and cinematic with a gold accent, and in Dutch, because that is who they are talking to.
Every project is quoted individually, because the honest answer is that it depends.
Guide prices are available on our Packages page. The same brief can mean very different work depending on what already exists and what has to run afterwards. We give you a fixed quote for the agreed scope before any work starts.
Reusable brand assets and content can save work. Data, integrations and migration can offset that saving, so an existing site does not automatically make the project cheaper.
A site that presents is not a product that transacts. Accounts, payments, permissions and an admin area are where cost actually lives.
Every extra language touches copy, checkout, legal text and metadata, not just the visible words on the page.
A hand-over and a continuing engagement are different commitments, and they price differently.
A design engineering studio is a team that designs an interface and writes the production code that ships it. The same group is responsible for how the product looks, how it behaves and whether it runs, so there is no handoff between a design agency and a development shop.
Product design often focuses on research, interaction and interface decisions. Design engineering combines that work with implementation. Responsibilities can overlap; either team structure still needs clear handover and checks of the working product.
Both, on the same project. We do not take design-only work that we then hand to another company to build, because the handoff is the specific problem this studio exists to remove.
Guide prices are published on the Packages page, and every project receives an individual quote. What moves the number most is scope: how much already exists, whether the build needs accounts, payments and an admin area, how many languages it runs in, and whether the studio keeps it running after launch. You get a fixed quote before any work starts.
Amsterdam. We work with clients across the Netherlands and the rest of Europe, and the studio is deliberately small, so we take on few projects at a time.
A short description of the product and the deadline is enough to start. You will get a real answer from the person who would do the work.