Direct contact

Reach the engineering team

Technical enquiries are answered by engineers. If your question needs a measurement or a datasheet to answer properly, say so and we will treat it that way.

  • Address[CLIENT TO PROVIDE]
  • Telephone[CLIENT TO PROVIDE]
  • Email[CLIENT TO PROVIDE]

Tell us about the project

Fields marked * are required.

Scope

What we can usefully talk about

A first conversation is more productive when it is aimed at one of these.

01

A product that does not exist yet

Requirements, architecture options and what the first evidence should be.

02

A design that misbehaves

Noise, thermal, timing, yield or reliability problems that need measurement before opinion.

03

A product that cannot be built

Obsolete components, missing design data or an unsupported toolchain.

04

A design going to production

DFM, test coverage, build packs and supplier questions before the first article.

05

A team that needs a discipline

Hardware, PCB, embedded or test capability added to an existing programme.

06

A second opinion

A design review against constraints, with findings written down.

Process

What happens next

No sales sequence — a technical path from your first message to a scoped engagement.

  1. You write

    Describe the product, the constraint and the stage you are at.

  2. We reply

    An engineer responds with questions aimed at the constraint, not at your budget.

  3. Technical call

    A conversation about architecture and evidence, under NDA if you prefer.

  4. Scope

    A written statement of what would be engineered, what is delivered and what is excluded.

  5. Proposal

    Commercial terms follow the technical scope, not the other way round.