v1.3.0

MAKE IT Product R&D · Mission Statement

The commitment behind everything we design, build and industrialise.

Helping innovators develop smart products

Turning challenges and ideas into technology products that are viable, useful and ready for the real world.

Proposed institutional version
September 2026
MAKE IT Product R&D
Full stack product development

01

Mission and purpose

This is what MAKE IT Product R&D stands for: the value we exist to create, and the principles behind every technical, commercial and project decision we make.

Our mission

We help companies conceive, validate, develop and industrialise technology products — integrating engineering, design and software to turn uncertainty into something real: useful, technically sound, manufacturable, and ready for the world.

Our purpose

We exist to close the gap between an opportunity and a real product. Startups and SMEs rarely have the multidisciplinary capability this takes on their own — we bring it to the table, with technical rigour, fast learning and a seat next to the client.

Full Stack Product Development

We treat the product as one complete system, not a handoff between departments. Research, definition and design. Engineering, prototyping and software. Straight through to industrialisation.

The change we want to bring about

We want more organisations turning innovation into reality — with less uncertainty, stronger technical grounding, and sharper decisions on risk, cost, time, manufacturing and maintenance. The result isn't just a prototype: it's validated knowledge and a credible foundation to build on.

02

Our promise

Every project is a journey of risk reduction — from the first sketch of the problem to the industrialisation line.

Design the right thing. Design the thing right.

01

Design the right thing

We investigate and validate the problem, the user and the value at stake — before we ever converge on a solution.

02

Design the thing right

Every engineering discipline works together from day one: performance, usability, cost, manufacturing, testing, compliance, evolution.

03

Evidence before scale

We validate hypotheses through experiments, prototypes and real data. Decisions evolve with evidence, not just convictions.

04

Transparency and co-creation

We share process, priorities, decisions, risks and knowledge, working as an extension of the client's team — not a vendor at arm's length.

05

Capability that stays behind

We document every decision and transfer the knowledge behind it, so the client walks away more capable, not more dependent.

How we work

We combine Design Thinking and Lean Startup to clarify the problem and validate value; Agile practices to organise learning and delivery into short cycles; and manufacturing-oriented engineering to prepare the move from prototype to product. A Minimum Viable Product (MVP) isn't just a version with fewer features: it's the minimum experience needed to test a critical hypothesis with users, clients, data or real-world performance, following the build, measure, learn cycle. The methodology adapts to each project's maturity level, risk and context, and assumes the client's active participation in priorities, decisions and learning.

03

Principles that guide decisions

Six principles. One test for every decision we make.

  1. 01

    Start with the problem.

    Understand users, context, constraints and expected value before converging on a solution.

  2. 02

    Manage uncertainty.

    Identify the most critical hypotheses first and choose experiments that produce relevant learning.

  3. 03

    Integrate from the start.

    Avoid local decisions that would harm the system, its usability, its manufacture or its future evolution.

  4. 04

    Design for production.

    Consider materials, components, suppliers, assembly, testing, compliance and total cost.

  5. 05

    Communicate with clarity.

    Make assumptions, alternatives, decisions, limitations, progress and deviations visible.

  6. 06

    Build to last.

    Favour solutions that are robust, documented, repairable and evolvable, suited to the real-world context.

Coherence test

A decision is aligned with the mission when:

  • it solves a relevant problem and is tied to verifiable value for the user or the business;
  • it reduces a material uncertainty or creates evidence that leads to a better decision;
  • it keeps technology, experience, cost, timeline and industrialisation coherent with one another;
  • it makes risks and trade-offs explicit, without promising what hasn't yet been validated;
  • it leaves the client with more knowledge, capability and autonomy than they had at the start.

Short formulation

We help you discover the right product — then integrate engineering, design and software to build it right, and get it ready to produce.