Something we make keeps failing and nobody can say why

Units failing in the field, a project that stalled, or a big decision you want an independent read on: one week inside the problem and a written report you can act on with or without me. AUD 6,000, report within 10 business days.

PriceAUD 6,000

TurnaroundWritten report within 10 business days of your material arriving

PaymentPaid in full up front; credited against follow-on work over AUD 20,000 that starts within 90 days

Next stepIntake form — I reply within one business day

Where you are

Units come back from the field and nobody can say why. It passed on the bench. The customer is losing patience.
The engineer who built it has left — the project’s stalled, or it’s in production and the factory’s questions are landing on your desk — and you need to know what you actually have before you spend more.
You’re about to spend real money — a respin, a certification run, a migration — and want an independent read first.
You’ve been quoted a big number and want a second opinion on the scope before you sign.

What you get

I’ve spent eleven years finding these faults inside companies that ship products like yours — controllers, meters and sensor networks installed by the thousand — and I’m a Registered Professional Engineer in Victoria (about). This week is that, on your product.

A written report, usually 8–15 pages, that says:

What’s actually wrong (or what’s actually there), with the evidence: measurements, logs, code references, photos.
The root cause where a week can establish it — or the short list and the test that decides between them.
Your options, each with a cost and time range, and which one I’d pick.
A fixed price for the fix if you want me to do it. This is the only way I quote fixed prices on open-ended work. Fixes over AUD 15,000 are quoted as a fixed-price project; smaller fixes are done on a monthly support retainer (from AUD 1,250 a month, six-month minimum), which also covers the factory’s questions afterwards.

Plus a 45-minute call to walk through it. To see the shape of what you’re buying before you commit, there’s a sample report: one finding worked all the way through with its evidence, the root cause, the options table and the fixed price for the fix.

What I need from you

The hardware: a failing unit and a known-good one if you have it, posted to me — or remote access to a bench if it can’t leave the building. Both come back by tracked post with the report, return postage within Australia included; say if the good one has to stay untouched. In transit they’re at the sender’s risk each way; on my bench [covered by my insurance — confirm once arranged].
Whatever exists: schematics, layout, firmware source, build instructions, previous test reports.
One person who can answer questions by email during the week. They don’t need to be an engineer; the person who knows the product’s history is more useful than one who knows the code.
The story: what changed, when it started, what’s been tried.

Your material stays confidential and isn’t reused or published (terms). If your company needs an NDA first, attach it to the intake form; I’ll return it signed before the invoice.

What’s not included

The fix itself — that’s quoted in the report.
Lab EMC testing, certification, or anything that needs a third party.
More than one product or one problem. Two problems is two weeks.

How it works

Swipe the diagram sideways to see all of it.

The ten business days start when your material lands on my bench, not when you send the form. Four of them are bench days: I do this alongside a full-time engineering role, which is why the turnaround is ten business days rather than five, and why I take a small number of jobs at a time.

If either of us wants to talk before you commit, that first reply includes a link to book a 30-minute call. Nothing is invoiced until the scope is agreed in writing.