Research
Prior art and landscape
What exists, who owns it, what lapsed and where the space is. Delivered as a document with a number and a date behind every claim we make.
What we do
Three activities, in that order, and the order is the whole method. Reading is cheap, building is expensive, and documenting afterwards means building twice.
Research
What exists, who owns it, what lapsed and where the space is. Delivered as a document with a number and a date behind every claim we make.
Research
A field you are considering entering, mapped: the players, the filings by year, the standards in force and the ones about to change under you.
Engineering
From sketch to a board that boots and an enclosure that closes. Measured on a bench, with the numbers written down whether or not they flatter us.
Engineering
Models that run on the device, in the vehicle or on your own hardware. Evaluated against a set you hold, so the score is yours to reproduce.
Conformity
Risk assessment, standards applied, test plan and the declaration of conformity. Built alongside the product rather than reconstructed from memory at the end.
Review
A team, a design or a roadmap read by someone who is not invited to the next meeting. Two weeks, one document, no diplomacy.
How an engagement runs
Every engagement starts with a written scope: what gets built, what it must measure, what it explicitly does not include, and what it costs. Both parties sign it before anyone starts. A change is a new scope with a new price, agreed before the work, not an adjustment discovered on an invoice.
Once a week you get the thing itself, running, plus a short note on what moved and what did not. Not a status deck. If a week produced nothing, the note says the week produced nothing and why.
At handover you receive the source, the design files, the measurements and the technical file, in a repository you control. Access for us ends the same day unless you ask for it to continue.
Most work fits one of these. If yours does not, say so on the call and we will write a fifth.
| Shape | Typical length | What you end up holding |
|---|---|---|
| Search | Two to four weeks | A landscape document and a recommendation, which may be to stop |
| Second opinion | Two weeks | One written review of a design, a team or a roadmap |
| Prototype | Two to five months | A working object, its measurements and its design files |
| Product to file | Four to nine months | The above plus the technical file and the declaration |
Lengths are the range we plan against, not a promise made before we have seen the problem. The number in your scope is the one that counts.
If you are not sure, that is the first call. It is free and it is short.