Cost and process

    What early-stage hardware founders actually need from a design studio

    It is rarely a beautiful rendering. From the founders we have worked with, the needs that matter most and the ones that look important but are not.

    Robrecht LambrechtsCo-founder, Business Director··3 min read
    Back of a small silver wearable device with an olive fabric strap

    Founders with a hardware idea arrive with a prototype, a pitch deck and a deadline set by investors. They often think they need a design. From the ones we have worked with, that is seldom the first thing they need.

    What they need

    A number they can defend. Not a design fee. A unit cost at a realistic volume, a tooling estimate and a timeline to a pilot batch. Investors ask for these; founders guess. A discovery sprint replaces the guess with a number that has a basis, and that number is usually worth more to the company than any render.

    The list of things that could kill the product. Every hardware product has a few: a mechanism, a certification, a component with one supplier, a finish nobody can apply at the planned volume. A founder needs those named and ranked, with the cost to test each one. Then they can spend their next money on the right risk.

    A product architecture before a product look. Where the electronics live, how the parts split, how it is assembled and serviced. This is what makes the engineering quote real and the manufacturing conversation possible. Styling comes after, and is faster for it.

    A manufacturer in the loop early. A factory's opinion on a design costs nothing and changes everything. Founders rarely have the relationship. We do, in Europe and in Shanghai, and bringing a factory into month one saves a redesign in month six.

    Phases they can stop. Early-stage money comes in rounds. A project priced in phases, each with a defined output, lets a founder finish the phase the money covers and raise on the result. A single large contract does the opposite.

    Honesty about what they do not need yet. A brand identity, a packaging system, a product family, a patent for the styling. These may come. In the first year most of them are weight.

    What looks important but is not

    A hero render for the deck. Useful for a week. If it shows a product that cannot be made at the target cost, harmful for a year. We would rather give a founder a crude prototype that works and a render that is honest about the volume it is designed for.

    A full feature set. The first product should do the one thing well that makes someone buy it. Every feature after that adds parts, testing and risk. The second product can have the second feature.

    An investor-demo prototype. A prototype built to look finished for a pitch is a different object from one built to become a product, and the money spent on it rarely carries over. We do not build them. A working prototype that answers a technical question, and an honest render of what the product will be, serve the pitch better.

    A studio that says yes to everything. A founder needs to hear "that will not pass the standard", "that tooling will cost more than your round" and "that supplier will not make five hundred units". A studio that never says these things is not reducing risk. It is deferring it.

    How we work with founders

    A two-week discovery sprint at a fixed 10,000 euros, ending with a requirements list, a risk map, an architecture and a phased proposal. Then a scoped budget per phase, with a gate after each. Factories involved from the sprint. Our Shanghai team for the manufacturing conversation when the volume points that way.

    The founders who get the most from this are the ones who arrive with a problem they understand deeply, funding that matches the ambition, and a product they are willing to change. Our design projects start at 30,000 euros; a founder whose whole budget is below that is better served by a discovery sprint and an honest conversation about timing. The design is the easy part.

    Not sure where to start? A two-week discovery sprint answers the first questions.

    Start with a discovery sprint