Before this, I was doing digital marketing. Every tool I paid for did the same thing: hand me a spreadsheet of "leads" — a name, a website, a phone number — and call it done.
The problem was never finding businesses. It's a solved problem, there are a hundred tools that spit out lists. The problem was the next step: staring at 200 rows and having no idea which ones were actually worth my time. No signal on which businesses had a weak online presence, which ones were actively losing customers because of it, or which ones would even understand why they needed help.
So I'd burn hours doing manual "presence audits" by hand — checking a business's website, socials, reviews, page speed, whatever — just to figure out if a cold call was worth making at all. That manual audit was doing more work than the lead list itself.
That's the moment LeadFlow started. Not "another list tool," but something that answers the actual question: why is this lead worth calling, specifically?
LeadFlow started as just the presence audit — score a business's online presence, flag exactly what's missing, and turn that gap into a ready-made sales angle before you ever pick up the phone. That part alone fixed the problem I kept running into.
But once the audit existed, the rest of the pipeline sort of had to follow it:
Lead Discovery – AI search for local businesses by type and location, paired directly with a Presence Audit
Presence Audit – scores a business's online presence and flags exactly what's missing
Lead Scoring – rule-based scoring with hot-lead alerts and thresholds you set yourself
Visual Pipeline – drag-and-drop Kanban board with stage automations and win-probability projections
Lead Capture Widgets – six embeddable widgets: exit-intent, slide-in, promo bar, lead magnet, A/B testing, live chat
Email Sequences – timed, automated follow-ups with enrollment tracking
MCP for AI Agents – 19 tools exposed over MCP so an AI agent can actually work the pipeline, not just read from it
I started building it in May 2026, solo, bootstrapped, full-time. No funding, no team — just trying to fix the exact thing that used to eat my own time, then kept adding whatever the next bottleneck turned out to be.
The build is done. Right now the only user is me.
Zero outside users so far — I just shifted from building mode into marketing mode, and this post is basically step one of that.
Next milestone is the Google Play Store launch, then I need to actually figure out how to get this in front of the people who'd use it.
I'd rather post this now, at zero users, than wait until it "looks impressive." Honestly, that's the whole reason I'm posting — I'm good at building, I have no idea what I'm doing on the marketing side, and I'd rather figure that out in public than alone.
The big one: LeadFlow is going on the Google Play Store very soon, so this whole pipeline — Discovery, Presence Audits, Scoring, the pipeline board — moves from "browser tab you have to remember to open" to something you can actually run from your phone.
If you've ever bought a "list of leads" and immediately had no idea where to start — I'd love to hear how you dealt with that. And if anyone's gone through the "I built it, now I have to actually market it" phase — genuinely open to hearing what worked and what didn't. I'm around all day to answer questions in the comments.
The founder-market fit comes through clearly here. You’re not describing a problem you researched; you built around a workflow you were personally doing by hand.