WORKING TOGETHER

Start with a conversation.
Build with a clear scope.

A practical process for a new product, an existing design or a specific engineering problem.

01

Share your starting point

Tell us what you are building, what you already have and where you need help.

Useful inputs include a short product description, sketches, current design files or a repeatable problem. Confidentiality arrangements can be discussed before sharing sensitive material.

02

Agree the next milestone

Define the scope, deliverables, schedule and commercial terms before work starts.

We agree the work boundaries, required inputs, deliverables, review points and acceptance checks. The proposal sets out the schedule, price and payment terms for that scope.

03

Build, test & review

Review progress against the agreed checks and make decisions with the results in hand.

Work proceeds against the agreed milestone. Findings and open decisions are reviewed together. Changes to requirements are assessed for their effect on scope and timing.

04

Receive the handover

Get the agreed files, findings and practical next steps for the following build.

The handover includes the files and records listed in the scope. We identify remaining issues and agree any further prototype revision, validation or production support.

Before we start

Do I need a finished specification?

No. A product description, sketch or explanation of the problem is enough for an initial discussion. We identify the missing information together.

Can you help with just one stage?

Yes. Design reviews, firmware tasks, prototype investigations and production preparation can each be scoped as a separate piece of work.

How are cost and timing agreed?

After reviewing the requirements, we define the scope, dependencies, deliverables and schedule in a project proposal. There is no fixed price or delivery promise before this review.

Can you also arrange manufacturing?

PCB fabrication, component sourcing and assembly can be coordinated with production partners. Manufacturing quantities, lead times and test coverage are confirmed for the specific build.

Who receives the design files?

The proposal identifies the files, source code and documentation included in the handover, alongside any third-party dependencies or licensing terms.

LET’S START WITH YOUR PROJECT

Tell us where you are.
We’ll help with what’s next.

A short description, an existing design or a prototype issue is enough to start the conversation.

Prepare your project brief