DEV Community: S.M.Rejuanul Islam

The Gap Nobody Budgets For

S.M.Rejuanul Islam — Sat, 25 Jul 2026 23:40:17 +0000

I spent four years building websites for other people. The website was almost never the reason they lost the deal.

Businesses spend real money getting people to their site. Ads, SEO, a designer, a developer, months of work. Then someone lands on the site at 11pm, fills in the contact form, and waits.

Nobody replies until morning.

By then that person has messaged two or three competitors. Whoever answered first usually wins, and it has very little to do with who was actually the better choice.

That is the gap. It sits between the form and the reply, and no one budgets for it because it does not look like a problem. The website works. The form works. The lead is right there in the inbox. It just sat still for twelve hours while the person on the other end moved on.

I built BuyerLoop to close that gap.

What it actually is
BuyerLoop is a widget you drop onto your website. One line of embed code.

A visitor can type to it or talk to it out loud, in real time, on the page. Both work. Some people want to read, some people would rather just ask a question and hear an answer, and there is no reason to force everyone down the same path.

But the part I care about most is what happens before any of that.

You build the agent first
Most chat tools give you a generic bot with your logo on it. Everyone can tell. It answers three questions well and then falls apart the moment someone asks something real.

In BuyerLoop, you create your own agent before it ever goes live.

You give it a name. A role. A photo. A tone of voice. And a knowledge base — your listings, your pricing, your process, whatever you would tell a new hire on their first day.

Then it goes live in the widget instantly.

The result is that visitors are talking to someone from your company, not to a chatbot that happens to be on your site. That distinction sounds small. It is not. It is the difference between a lead engaging for four messages and a lead closing the tab.

Then it runs on its own
Once the agent is live, the loop runs without you:

It qualifies in conversation. Not a form with six fields. An actual back-and-forth where it asks about budget, timeline, and how soon they want to move, the way a good salesperson would.

It follows up if they disappear. Someone starts a conversation and goes quiet. The agent emails them. Not once, at 9am on a Monday. When it makes sense.

It hands you the lead ready to work. Everything lands in your dashboard, already sorted, with the qualification answers attached and the requested viewing time ready for you to confirm.

You wake up to qualified leads instead of a form fill and a guess.

Why real estate first
I started with real estate agencies because the gap is most expensive there.

A property enquiry is worth a lot. Buyers browse listings at night, often from a different country entirely if you are selling in a market like Dubai. They are comparing four agencies at once, and the questions are repetitive enough that a well-briefed agent can genuinely answer most of them: is it still available, what is the service charge, can I see it Saturday.

Every one of those questions has a right answer that already exists somewhere in the agency. It just is not available at 11pm.

But the pattern is not specific to property. Interior design studios, clinics, contractors, education consultants, anyone whose business runs on enquiries and appointments has the same gap. The noun changes — viewing, walkthrough, consultation, demo — and nothing else does.

The honest version
BuyerLoop is early. It is live at buyerloop.app, it works end to end, and it is my entry in the XPRIZE x Google vibe coding hackathon.

I built it alone, from Chattogram, Bangladesh, in few weeks.

I am looking for real businesses to use it.

The website was never the problem. The wait was.

I wasn't chasing a perfect Lighthouse score when I started this project.

S.M.Rejuanul Islam — Mon, 27 Oct 2025 17:28:35 +0000

My focus was simple: build something fast, clean,
and accessible for the client.

But here's what I learned:

when you make thoughtful decisions from the start,
the results follow naturally.

Things like structuring content with performance in mind,
optimizing images properly, eliminating layout shifts,
and writing semantic, accessible HTML.

The outcome? 100/100 across all four Lighthouse metrics.

But here's the thing. The score isn't what matters most.

It's that the site loads fast on slow networks.

It works beautifully across devices. Users get what they need, quickly.

The perfect score? That's just a side effect of building with care.

And yes, Google appreciates it too 😊

How I Built Mentorak in Days Using Kiro: A Dev Journey With Specs, Hooks, and AI

S.M.Rejuanul Islam — Mon, 15 Sep 2025 18:15:03 +0000

As a solo developer and hackathon enthusiast, I'm constantly searching for ways to build smarter, not harder. That’s why I turned to Kiro for my latest project Mentorak, an AI-powered quiz generator designed to help students, educators, and lifelong learners generate custom quizzes in seconds.

Users type in any topic from Photosynthesis to World War II and Mentorak instantly returns 10 multiple-choice questions with answer options, scoring feedback, and a saved history for future review.

Instead of writing boilerplate code, I started with structured natural language specs, which Kiro translated into routes, components, and logic. It completely shifted how I approached building products.

📐 How Kiro Changed My Development Process
With traditional development, I’d usually:

Create the folder structure manually
Write repetitive components, APIs, types, and error handling
Then wire everything together

What Surprised Me
A few moments stood out where Kiro exceeded my expectations:

Edge Case Handling: Kiro auto-added error boundaries and loading states I hadn’t thought of
Agent Hooks: Though I didn’t use many in this build, experimenting with them showed me how async logic and state transitions could be modular and powerful
Speed of Iteration: I built, broke, and rebuilt faster than ever before — because I wasn’t afraid to try new things. Specs made rollback and rethinking feel safe.

🏁 Final Thoughts
Mentorak is just getting started — but I already have some exciting future plans:

🎤 Voice input + feedback: Turn the quiz into an interactive conversation
🎮 Multiplayer quiz battles: Challenge friends on shared topics
📊 Analytics and skill tracking: Visualize learning over time

Try it out https://mentorak.com/

But most importantly this project has permanently changed how I code.

I no longer want to write everything from scratch.
With Kiro, I can stay in flow, stay creative, and ship more in less time.