Entry offer
Sample report
See exactly what you would get — before you spend anything.
Free
no email required
· Published — read it now
Most consultancies ask you to book a call to find out what they actually deliver. I would rather just show you — no form, no email address, no follow-up sequence.
This is a complete readiness review — the same structure, severity framing and remediation detail a paid engagement delivers — applied, in public, to code thousands of product teams start from: the Matter bridge-app reference application, pinned to an exact commit. A client report would be redacted; this one you can verify. Read it, hand it to your firmware lead, and let them check the work line by line before you spend anything.
Sample report · no email required
See what an auditor opens.
A complete readiness review, applied in public to the Matter bridge reference application at a pinned commit — every finding checkable against source, line by line. No form, no email, no drip sequence. Read it, or hand it straight to your firmware lead.
What is in it
- Nine findings with severity, regulation mapping and remediation
- The evidence standard: Demonstrated versus Declared, applied throughout
- An SBOM gap sized against 78 pinned components and an OSV screen
- The exec summary a budget-holder reads, and the annexes an engineer checks
What you get
- The complete report — findings, remediation roadmap, evidence annexes
- Real findings with severity and fix priorities
- The exact structure a buyer or auditor sees
- Every claim checkable against public source at a pinned commit
- Published openly — no form, no email, no drip sequence
Worth reading if
- You are weighing outside help for CRA or PSTI and want evidence of depth before a conversation.
- You need something concrete to circulate internally before asking for budget.
- You want to see how findings are framed for an exec readout, not just for engineers.
How it works
-
Open it
The PDF is published on this site. No form, no email address, nothing to wait for — the link is on this page.
-
Check the work
Every finding cites public source at a pinned commit, so your firmware lead can verify the reasoning independently rather than take it on trust.
-
Decide what comes next
If the structure looks like what your buyer or auditor will ask for, the Snapshot or the Readiness Review is the natural next rung.
Asked before reading
-
Do I have to give you my email?
No. The report is published openly — there is no form in front of it and no way for me to know you read it. The field-notes list exists separately if you want it: occasional notes on firmware regulation, every two weeks, one-click unsubscribe in every issue.
-
Is this from a client engagement?
No — client reports are confidential, and I would rather show you checkable work than a redacted excerpt you have to take on trust. The sample applies the full engagement methodology to a public open-source subject — the Matter bridge reference application, pinned to an exact commit — so every finding is independently verifiable. What a paid engagement adds is your firmware, your build and your evidence, under NDA.
When you have read it
If the depth is right, start where it makes sense: an outside-in Snapshot for £950, or the full Readiness Review.
Field notes
Join the list
One field — your work email. One email every two weeks.