Find software that
earns its place
in your business.
Practical AI and software for founders and small teams. The task, the tradeoffs, and what to check before you pay.
The details are the story.
A subscribe button needs somewhere to start.
First, the email field was missing. Then, the button was hard to see. My feedback on this site became a useful lesson in making the next step obvious.
Read the storyBased on this site build. No conversion results claimed.
Where do I type?
A button cannot complete a form on its own.
Make the next step clear.
Email addressA visible field. A button you can find.
A simplified reconstruction of the issues reported while building this site. These are explanatory visuals, not screenshots or measured conversion results.
A QUESTION I KEEP COMING BACK TOWhat happens
after the demo?
A clean output is a useful start. I also want to know what needs fixing, who checks it, and whether it fits the way the business works.
That is the perspective behind these field notes.
How I evaluate products ↗Count the cleanup.
When comparing a new tool with your current method, record three things separately.
- SetupPreparing the tool and inputs.
- ExecutionRunning the actual task.
- CorrectionGetting the output ready to use.
Example totals include setup, execution, and correction. No product benchmark implied.
Try your own numbers ↗On the research desk.
Can the reader explain your offer after five slides?
Product storytelling ↗02 / RETELL AIThe customer corrected the day. Did the booking change?
Customer experience ↗03 / N8NCan every claim in the research brief find its source?
Business workflows ↗What’s taking
longer than it should?
The spreadsheet you keep fixing. The follow-up you keep forgetting. Tell me about a task you would like investigated.
Suggest a taskI’ll ask before quoting you. Submissions do not guarantee a test.