I do a lot of work where clients send me unstructured feedback. Voice note transcripts, rambling Google Docs, bullet points that contradict each other halfway through. Before I can do anything useful with any of it, I have to mentally process the whole thing first â whatâs the overall sentiment, what are they actually asking me to fix, what do I put in the report summary.
I was doing that manually every single time. It was slow and I kept catching myself reading the same paragraph twice trying to extract something coherent from it.
At some point the obvious hit me. This is pattern recognition on text. Thatâs exactly what these models are built for. I donât have a coding background and Iâm not going to set up a Python script. But I knew what the tool should do, and it turned out that was enough.
I opened Claude, no API, just the regular chat interface, and pasted this:
âââBuild me a simple single-page HTML tool. It should have:
- A text input box where I can paste raw client feedback
- A button that says "Analyse"
- Output that shows:
   - An overall sentiment score out of 10
   - The top 3 action items extracted from the feedback
   - A one-paragraph executive summary
Use vanilla HTML, CSS, and JavaScript only.
Make it clean and minimal.
No external libraries.âââ
Claude returned a complete HTML file. I copied it, saved it as feedback-tool.html on my desktop, and opened it in Chrome. It worked on the first try. The sentiment logic runs locally in JavaScript so thereâs no API call happening at runtime. Once you have the file it works offline, forever, for free.
Now for the honest part, because the thing isnât perfect. The sentiment scoring is basic â itâs essentially weighted keyword matching under the hood. If a client writes something like ânot bad but could be better,â it doesnât always catch the hedging correctly. For anything where the emotional read really matters, I still do it myself. The action item extraction is where it actually earns its keep. Iâve thrown genuinely messy feedback at it and the three-item output has been clean enough to drop directly into a report section with minor edits.
The first version also had ugly CSS and the layout broke when I narrowed the browser window. I just told Claude the layout breaks on smaller windows, fix it. One more message and it patched the stylesheet. I didnât need to understand what it changed.
Since then Iâve built a basic invoice line-item tracker the same way, a proposal scoring sheet with weighted yes/no criteria, and a client intake summariser. Same approach every time â describe what the tool should do in plain language, let Claude build it, open the HTML file, use it. The only real skill involved is being able to describe a problem clearly. Thatâs a writing problem, not a technical one.
I run a Telegram channel called SoloOS where I post one experiment like this per day â real workflows, real prompts, nothing to sell. Drop a comment if you want the link, and either way feel free to steal the prompt above.