A bounded technical question, answered before you commit to it. For companies facing a decision that rests on an answer nobody inside has the time to establish — and who need that answer in writing, from someone with nothing to sell them afterwards.
Forty-five minutes on the question in front of you, followed by a written one-page summary you keep whether or not anything else follows.
Technical depth in sensing, signal processing, radio and modelling, applied to industries where a wrong technical assumption is expensive to discover late.
Indicative starting prices, excluding VAT. Each study is quoted on scope after the scoping session, so the figure you receive reflects your question rather than an average one. One round of revisions is included, and turnaround is in working days starting when the inputs are complete.
A technical study is usually commissioned because a decision is contested — between engineering and commercial, between a company and its customer, or between a company and a regulator. What matters then is not the conclusion but whether it survives examination.
Every study states its assumptions, its uncertainty, and what would change the conclusion. It is written so that someone who disagrees with it can see exactly where to disagree. That is harder to produce than a recommendation, and it is the only kind of report worth putting in front of a board.
Independence is the point. There is no product, no licence and no follow-on implementation contract behind the recommendation — which is why the answer is allowed to be no.
A scoping session. Forty-five minutes on the question and the decision behind it, and a written one-page summary afterwards. No cost. If it is not a fit, you hear that here.
A fixed quote and a list of what is needed. Price, date and scope in writing, with exactly what is required from you. The clock starts when that is complete.
The work, then one round of revisions. If the question changes, the change is quoted rather than quietly absorbed.
A written answer. Including what is uncertain, what was assumed, and what would change the conclusion.
One paragraph on the technical question and the decision it feeds is enough to book a scoping session — or to get an honest answer that it is not a fit.
hcordova@qumindai.nl Based in the Netherlands. Work is carried out inside the EU and data does not leave it.