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, a result you can feel before the coffee cools.

I came up through IT — Hanoi University of Science and Technology, then years of making computers do the boring parts. The habit never left. When a workflow hurts, I do not add a dashboard. I look for the one simple feature that makes the hurt unnecessary.

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

Personal first. Then the team.

Sheetany began because I was tired of rebuilding websites around a spreadsheet I already trusted. Ebookany began because pages I loved kept vanishing. Sheetfetch began because Monday meant exporting CSVs. Upwip began because user voice was living in five places and dying in all of them. Row.so began because a directory should not take a quarter and four plugins to earn its first dollar.

I did not set out to build 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.