I solve the problem in front of me — then I leave the tool behind.

I am Richard. I write software the way I wish the world worked: little ceremony, no unnecessary bureaucracy, and a result you can feel before the coffee cools.

I came up through engineering at Hanoi University of Science and Technology (HUST), followed by years of corporate engineering. But the habit never left: when a workflow hurts, I don’t add a bloated dashboard. I look for the one simple feature that makes the hurt disappear.

x.com/itbk95 is where I document the journey and build in public. The products are how the work leaves my machine and enters someone else’s week.

Personal first. Then the team.

Ebookany began because essays I loved kept vanishing behind paywalls. Sheetany began because I was tired of rebuilding websites around a spreadsheet I already trusted. Sheetfetch began because Monday meant copy-pasting CSVs from dashboards. Upwip began because user feedback was scattered across DMs and dying silently. Row.so began because a directory shouldn't take a quarter and four WordPress plugins to earn its first dollar.

I did not set out to build platforms for agencies. I set out to end a specific pain. Agencies and product teams arrived later — because they had the same knots, only larger. That is the pattern I trust: if it saves me an afternoon, it can save a team a quarter.

Simple Feature

The name of the work is not a brand exercise. It is a constraint. Each product should be explainable in one sentence, and that sentence should name the pain it cuts. If I need a paragraph, the feature is not simple yet. If I need a platform, I have lost the plot.