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.
Most of what goes wrong in a website project goes wrong in the gap between two companies.
A design studio makes a beautiful static file. A development shop reads that file, guesses at everything it does not specify, and builds something adjacent to it. Nobody is at fault and the result is still worse than the drawing: the loading state nobody drew, the empty state nobody drew, the error message written by whoever was closest to the keyboard, the animation that got dropped because it was expensive to build and cheap to draw.
Design engineering removes the gap by removing the second company. The person choosing the type size knows what it costs to render. The person drawing the empty state is the person who has to build it, so it gets drawn.
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.
The people who built it keep it running, so the second month does not start with somebody reading an unfamiliar codebase.
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.
Two of these run as real businesses today, not as portfolio pieces.
JP Trading Capital. A trading education and software platform in English, Dutch, Portuguese, Spanish, German and French. Stripe checkout, signed digital agreements and licence-gated software delivery in a single flow. Designed and built by JP Studio since 2024, and still ongoing.
MyVeridex. A broker comparison product where the data set is the product. Built to stay fast and readable at that size rather than collapsing into an unusable table.
MyVeridex, Giftalytics and JP Studio Search all run in production. When we say we ship SaaS rather than mock it, these are the receipts.
Every project is quoted individually, because the honest answer is that it depends.
We do not publish a price list, because the same brief means very different work depending on what already exists and what has to run afterwards. What we do instead is give you a fixed quote before any work starts, so the number you agree is the number you pay.
A brand, a content set and a clear scope make a project cheaper. Starting from a blank page is design work before it is build work.
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.
A product designer decides what the interface should be and hands that decision to engineers. A design engineer makes the same decision and then implements it. In practice that means the design accounts for real constraints from the start, and nothing gets quietly dropped in translation.
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.
Every project is quoted individually, so JP Studio does not publish a price list. 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.