The work is the proof.
Two entries, because these are the two I can point at. The best way to make a case about how product teams should build is to build something that way. The rest was made for specific companies, and I show it on request.
Throughline
A working console that answers one question: did what we shipped actually land. It reads a real company from public information only. Password-gated, and I will open it for anyone who asks.
- ◆The whole loop end to end: a read that concludes, the move it recommends, and who has to approve that move
- ◆Every number computed by code, with the test suite that fails the build when one drifts
- ◆It says what is inferred and what is measured, on the surface, not in a footnote
Dacard.ai
This site. My own research sandbox, free to read, with no users and nothing for sale. You are standing in it. The paid work is the fractional practice.
- ◆The case is about how AI-era products get built, and the site was built that way
- ◆Agents wrote most of it. Deciding what to show and what to leave out was my job
- ◆Built in the open, reviewed by someone trying to break it, plain about what it is
Some of the work was made for one company and one conversation: a working console or a kit, built before the meeting. Those are not listed here, on purpose. If we are already talking, you have the link. If we are not, the fastest way to see them is to write to me.