How we work

A clear path from question to prototype.

We run hardware projects in short, visible steps — so you can see progress every week, steer every decision and stop at any gate with everything we’ve built.

Ways to work together

Start small. Prove it.
Then build it.

Every engagement is scoped around a clear question — and ends with something you can hold, test or decide on.

  1. 01

    Consulting

    Expert eyes on your idea, design or problem.

    Typical duration
    1–3 weeks
    Best for
    Early ideas, stalled projects and technical due diligence.

    You get

    • Feasibility & risk assessment
    • System architecture & component selection
    • BOM and cost estimates
    • A written, costed roadmap
  2. 02

    Proof of Concept

    Answer the riskiest question with working hardware.

    Typical duration
    3–6 weeks
    Best for
    Validating a core technology before you commit serious budget.

    You get

    • A focused bench or field demonstrator
    • Test data against agreed success criteria
    • Go / no-go recommendation
    • Plan and estimate for the prototype
  3. 03

    Prototyping

    A functional prototype you can demo, test and pitch.

    Typical duration
    6–16 weeks
    Best for
    Investor demos, pilot customers and user trials.

    You get

    • Integrated mechanics, electronics & firmware
    • Demo-ready units
    • Test reports and known-issues log
    • Full design files & documentation

Need ongoing engineering capacity? We also work on retainers — embedded with your team or owning a subsystem end to end.

Process

A process built around decision gates.

Hardware gets expensive when surprises arrive late. We front-load risk, show progress every week and give you a clean decision point at the end of every phase.

  1. Discover

    1–2 weeks

    Workshops, requirements and constraints. We map the technical risks and agree what success looks like.

    OutputTechnical brief, risk map & plan

    Decision gate after phase 1: Feasible?

  2. Prove

    3–6 weeks

    Targeted experiments on the riskiest assumptions — on the bench or in the field — before anything gets expensive.

    OutputWorking proof of concept + test data

    Decision gate after phase 2: Does it work?

  3. Prototype

    6–16 weeks

    Integrated design across mechanics, electronics, firmware and software, built and iterated in short cycles.

    OutputFunctional, demo-ready prototype

    Decision gate after phase 3: Is it right?

  4. Validate

    2–6 weeks

    Testing, refinement and design-for-manufacture review, then a clean handover to your team or manufacturer.

    OutputValidated design & handover pack

Every gate is a clean exit. You keep the code, schematics, CAD and documentation produced so far — no lock-in, no surprises.

Working together

A weekly rhythm you can rely on.

Predictable communication is half of a good engineering partnership. Here’s what a normal week looks like.

  1. Mon

    Plan

    Priorities, risks and the goal for the week — agreed with you.

  2. Tue–Thu

    Build & test

    Design, code, build and measure. Blockers raised the same day.

  3. Fri

    Demo & report

    Live or recorded demo, plus a short written update and decision log.

  • Direct access to engineers

    You talk to the people doing the work — no account-manager relay.

  • Shared, version-controlled work

    Code, schematics and CAD live in repositories you can see from day one.

  • Milestones with acceptance criteria

    Each phase has measurable success criteria, agreed before it starts.

  • Confidential by default

    Mutual NDAs on request and careful handling of your data and IP.

Handover pack

Everything you need to carry it forward.

Whether the next step is production, certification or your own team taking over, you get a complete, organised package — not a zip file of loose ends.

  • 01Source codeGit repository with build, flash and test instructions
  • 02ElectronicsSchematics, PCB layout, Gerbers and assembly files
  • 03MechanicalNative CAD + STEP, drawings and print/CNC files
  • 04Bill of materialsCosted BOM with sourcing notes and alternates
  • 05Test evidenceTest plans, logs and reports against acceptance criteria
  • 06DocumentationArchitecture, setup, user and maintenance guides

FAQ

Commercial questions.

Do you sign NDAs?

Yes. We are happy to sign a mutual NDA before you share anything sensitive — just mention it when you get in touch.

Who owns the intellectual property?

Under our standard terms, the project deliverables we create for you — designs, source code, schematics and CAD — are yours. Any pre-existing tools or libraries we bring are declared upfront.

Can you work alongside our in-house team?

Absolutely. We can own a complete subsystem, add engineering capacity on a retainer, or review and de-risk designs your team has already built.

Do you handle manufacturing?

We design for manufacture from the start, prepare production files and documentation, and support pilot builds with fabrication and assembly partners. We are not a contract manufacturer — but we will get you to one, ready.

How do you price projects?

Discovery and consulting are usually time-based. Proofs of concept and prototypes are scoped as fixed-price milestones wherever the requirements allow, so you know the cost of each phase before it starts.

Start a project

Have a machine in mind?

Tell us what you’re building. We’ll come back with questions, a first view on feasibility and the fastest path to a working prototype.