Amazon Discovery Intelligence
Reads a week of customer complaints and says what to work on Monday. It names the first move, who owns it, and what it will cost. It reads reviews people posted publicly about an app I do not work on.
ProblemA PM cannot read every review, so they skim. Skimming feels fine, because you never find out what you missed.
DecisionA ranked list hands the queue back to the PM. So the score is small print, and each problem leads with a finding, a first move and a price.
Evidence299 complaints in the latest week, sorted into 33 problems across 7 parts of the app. Every claim links to the review behind it.
OutcomeOne problem out of 33 had enough behind it to act on, and the page says so plainly instead of ranking all 33.
From a Visual Workflow to Hosted Code
The first buildAn n8n workflow. Twenty-nine nodes on a visual canvas, doing the right thing. Take reviews, clean them, find themes, score them, email a digest.
What brokePutting it behind a website means it has to be running somewhere. Either I leave my machine on, or I pay for hosting. I did not want either for a portfolio project.
The moveEvery node became a TypeScript module. The canvas became an orchestrator.
Who did the portI used Claude for it. Twenty-nine nodes of settled logic, translated rather than reinvented.
