Work

Case studies, not a highlight reel.

What the problem actually was, what got built, and what happened after.

Case study

SmartLeadGen — from a stalling Streamlit prototype to a real product

The problem

Manually searching for businesses with a weak online presence — the easiest kind of client to pitch web/SEO work to — took hours of scrolling Google Maps by hand, with no way to track who'd already been contacted.

The approach

Built on Google's own Places API (New) — not scraping — so every result is a real, current listing. Each business's own website gets checked for a contact email and social links, then scored by how weak its online presence actually is.

What it does today

Live-updating results table, CSV export, direct push to Google Sheets, and a bring-your-own-key model so each user's search costs stay on their own account, not a shared bill.

Stack

Cloudflare Workers + D1 for the product backend, a companion Streamlit build for a lighter-weight version, GitHub Actions for CI/CD on every push.

Case study

SmartGen — 120+ tools, one person, no funding

The problem

Most free "web tool" sites are ad-choked, slow, or quietly discontinued. There was room for a fast, GitHub-hosted set of utilities maintained by one person who actually uses SEO discipline on every page.

The approach

Static hosting on GitHub Pages (zero server cost), a custom Node.js static-site generator, and strict editorial standards on every tool page — title length, meta description length, no duplicate headings.

What it does today

120+ live utilities plus a full digital-marketing curriculum published on the blog — social platforms, WordPress, on-page/off-page/technical/local SEO, content marketing, and Bangladesh-specific freelancing content.

Stack

GitHub Pages for static hosting, Cloudflare Workers as a backend for any tool that needs server-side logic GitHub Pages can't provide on its own.

Want a case study like this for your own project?

Start a project