Product (re)engineering / Define · Build · Produce · Operate

From idea to product in the field

Whether you build a new product or give an existing one a future, we take it from requirements to production.

Technical drawing of a design desk, a pick-and-place machine placing components on a panel of six boards, and a test fixture
Product (re)engineering / Where you start

Two ways in

Technical drawing of loose components and a sheet of firmware, each hovering above its place on a circuit board that is still a dashed outline
New product

You have an idea, a set of requirements or a partial design, but no embedded team of your own. We fill in the rest: architecture, electronics, firmware and prototypes, tested on real hardware and designed for production from the start.

Technical drawing of a closed product seen through its lid, with the microcontroller marked end of life
Existing product

Components go end-of-life, costs rise, the knowledge has left or new requirements arrive, such as the CRA or a new radio standard. We take over the existing design, firmware and documentation and choose the way forward.

Product (re)engineering / Our approach

Four phases to the field

Phase 01Define

We fix requirements and concept, or take over the existing design, firmware and documentation.

Phase 02Build

Electronics, firmware and prototypes. When renewing, we test against the old behaviour.

Phase 03Produce

Ready for manufacturing, with a test jig and a production file. Production by us if you want it.

Phase 04Operate

Firmware updates, component management and maintenance, for as long as the product lives.

A decision point after each phase, so you stay in control of what comes next.

Product (re)engineering / How it fits together

One hardware choice touches everything

It changes the firmware, the testability, the assembly and the BOM. That is why we decide on all of it together, from the start.

Example · A different MCU → a different firmware architecture → a different test jig → a different BOM.

Product (re)engineering / Faster through Kilby

Kilby speeds up, an engineer signs off

Kilby is our AI embedded engineer. He takes over work where that is faster. Experienced engineers decide and sign off on the result.

Meet Kilby ↗

KilbyWhere Kilby helps
  • Firmware analysis
  • Firmware migration
  • Regression tests on hardware
  • Documentation
What stays with engineers and with you
  • Architecture choices
  • Which option goes ahead
  • Validation and release
  • Revalidation where needed (CE, RED)
Product (re)engineering / Where to start
Kickstarter · Existing product

Modernisation Assessment

Give your product a future.

We analyse your existing product: components, firmware, documentation and production.

You getA roadmap with the technical options, their risks and an indicative investment per option.
How it worksFixed scope, fixed price. You decide which option goes ahead.
First phase · New product

Product Definition Phase

Turn your idea into a plan.

Together we set the requirements, work out a concept and map the risks.

You getRequirements, a concept and the main risks, with a proposal for the build phase.
How it worksA clear scope for Define. After it, you decide whether the next phase goes ahead.
Contact

Bring us the hard problem.

A conversation about your problem is the first step.

Proven on real hardware