The stack

The stack, layer by layer

Eight layers between a requirement and a product that can be built repeatedly. We work across all of them, which is what keeps the joins from leaking.

Hardware
Electronic architecture, circuit design and component strategy that define what the product can physically do.
PCB & PCBA
The board that turns a circuit into a manufacturable, testable and repeatable physical assembly.
Embedded
System-level engineering where processing, memory, peripherals and timing are decided together.
Firmware
The control layer that makes hardware behave predictably, safely and measurably.
Connectivity
Wired and wireless communication that lets devices exchange data with systems and each other.
Intelligence
Local processing and sensor-driven logic that let devices act on data at the edge.
Product
The complete engineered product: enclosure-aware, serviceable and ready for users.
Production
Documentation, tooling and validation that make the design buildable again and again.

The journey

Eight stages, in this order

Stages can overlap and can be entered part-way, but they are never skipped without a recorded decision about what evidence is being given up.

01

Discover

Requirements, constraints and technical risk are mapped before a single component is chosen.

02

Architect

Hardware, embedded and connectivity decisions are made together as one system architecture.

03

Design

Schematics, board design and software structure are developed against the agreed architecture.

04

Prototype

Physical boards are built and measured so assumptions are replaced with evidence.

05

Engineer

Firmware, drivers and hardware are refined until the product behaves as specified.

06

Validate

Functional, integration and reliability testing verify the design against its requirements.

07

Production

Documentation, test tooling and manufacturing data prepare the design for repeatable builds.

08

Evolve

Products are maintained, modernised and extended across their service life.

Method

Six habits that shape the work

Not a process diagram — the decisions that get made differently because of how this team works.

01

Constraints before solutions

The limits that actually bind a design are identified and written down before any architecture is drawn.

02

Measure, then claim

Behaviour is confirmed with instruments on real hardware. Simulation informs; measurement decides.

03

Design the test with the product

Test points, coverage and fixtures are part of the design, not retrofitted when production asks for them.

04

Second sources at selection

Component availability and alternates are reviewed when the part is chosen, while changing it is still free.

05

Write the intent down

Why a decision was made is recorded alongside what was decided, so future engineers inherit reasoning, not guesswork.

06

Fix in the cheapest layer

When hardware and firmware disagree, the fix goes wherever it costs least across the product's whole life.

Deliverables

What actually leaves our hands

A capability list is easy to write. What matters is the material you hold at the end: schematics you can modify, fabrication data a factory accepts, source you can build, tests you can repeat and documentation that explains why the design is the way it is.

All of it transfers to you. We do not retain design data as commercial leverage, and we do not hand over a product that only its original engineer can maintain.

Technical plate elevation representing design documentation
Design data, source and evidence transfer to the client

Tooling

Tools chosen for the project, not for preference

Specific vendors and toolchains are selected per project, and per-programme tooling is confirmed at scoping: [CLIENT TO PROVIDE].

Hardware & PCB

Schematic captureMultilayer layoutSignal integrity analysisPower integrityThermal reviewLibrary management

Embedded & firmware

C / C++RTOSEmbedded LinuxDevice driversBootloadersVersion controlAutomated buildUnit test

Validation

Functional testEnvironmental testEMC pre-compliancePower profilingProtocol analysisProduction test fixtures

The deliverable is not a working prototype. It is a product someone else can build correctly, on a day when none of us are in the room.

Production readiness

Next step

See how this applies to your programme

Send us the requirement and the constraint. We will map it onto the stack and tell you which layers your project actually needs.