01
A product that does not exist yet
Requirements, architecture options and what the first evidence should be.
T · [CLIENT TO PROVIDE] E · [CLIENT TO PROVIDE]
Direct contact
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.
Fields marked * are required.
Scope
A first conversation is more productive when it is aimed at one of these.
01
Requirements, architecture options and what the first evidence should be.
02
Noise, thermal, timing, yield or reliability problems that need measurement before opinion.
03
Obsolete components, missing design data or an unsupported toolchain.
04
DFM, test coverage, build packs and supplier questions before the first article.
05
Hardware, PCB, embedded or test capability added to an existing programme.
06
A design review against constraints, with findings written down.
Process
No sales sequence — a technical path from your first message to a scoped engagement.
Describe the product, the constraint and the stage you are at.
An engineer responds with questions aimed at the constraint, not at your budget.
A conversation about architecture and evidence, under NDA if you prefer.
A written statement of what would be engineered, what is delivered and what is excluded.
Commercial terms follow the technical scope, not the other way round.