One salesperson should be able to work 100,000 leads, and lead scoring is how I get there.
In a March 2026 live stream I spent less time coding than talking about the part most vibe coders skip, which is selling what they built. My goal for LeadScore AI is one salesperson managing 100,000 leads without feeling overwhelmed. I said on the stream that if the app can't do that, it's a royal failure. This is the model behind it, and how I rebuilt the product's website live from screenshots of the app.
The business case
Most builders can ship an app now. Getting it in front of buyers is where things stall. The traditional sales playbook is get a list, segment it, cold call and network. It's standard, and it's dated. One person can't work 100,000 leads that way.
I build around one problem: keeping each conversation personal to the lead while the system does the work for 100,000 people. That takes automation. LeadScore AI is about a year old, with roughly six months of dedicated work in it.
If you've never sold anything, start with three ideas: what a lead is, how leads differ, and how you score them.
What a lead is
A viewer asked what a lead is. A lead is anyone interested in what you sell. At a car dealership, that's someone who walks in, answers a flyer or an email, or calls to book a test drive. Online, it's someone who finds you through a Google ad or an organic result, lands on your page and leaves a name and email in your database.
Leads sit at different stages, and I use star ratings. A one-star lead might buy a car in a year, a two-star lead in six months and a three-star lead in about a month. A five-star lead wants to buy now. When you sell at scale you sort, and you call the fives first. The path from one star to five is the buyer's journey: brochures, calls, deals and events.
Scoring the lead
Scoring turns those stars into a number. Each action that brings a lead closer to buying earns points. In my example, a real business website, a phone number and a newsletter signup are each worth 10 points. The scale is arbitrary. The working assumption is that a lead who reaches 100 buys. That's why the product is called LeadScore AI.
In the demo account, imported leads carry notes and live scores, and they move through pipeline tabs from initial outreach to proposal. The system can also plug into Leadfeeder, which turns a website visitor's IP address into a company name. I said it isn't 100% accurate, but it's fairly accurate.
Scores that move
The score keeps changing. A traditional salesperson chases: you call back next month and the buyer hasn't had time to think about it. In LeadScore AI the system sends the check-in email. If the reply is "not now, check back in a few months", AI schedules the next email and keeps doing that in the background while it re-scores the lead.
When you open the tool, you ask for the people most interested and pick up the phone. The goal is to bring the decision back to a person without the heavy lifting.
Jump to
- 0:00 Setup, and the goal: one rep, 100,000 leads
- 12:26 What a lead is, the buyer's journey and lead scoring
- 24:46 Inside LeadScore AI, and a live bug fix by prompt
- 41:55 Q&A: AI Gateway, OpenClaw vs Claude, Remotion
- 58:23 Monorepos on Cloudflare, launch checklist, Claude in VS Code
- 1:19:27 Keeping up with AI, and web app to mobile shell
- 1:35:43 Rebuilding the LeadScore AI site from app screenshots
- 2:07:18 Shipping to Cloudflare, credits and observability
The full stream, including the live bug fix and the rest of the Q&A, is on my channel: my March 2026 live stream on YouTube.
Questions from the stream
A viewer building a SaaS back end asked about autoscaling. My answer was that on Cloudflare Workers a brand-new app could reach about 10,000 users for around $5 a month, unless you're building something like your own LLM. That was my estimate in March 2026, and I said I'd put my money on it.
Another viewer worried about agents running up model costs. I pointed them to Cloudflare AI Gateway, which monitors calls across models so you can put hard caps on token use per account.
On OpenClaw versus Claude, OpenClaw gives you more extension points, so you can have it open a browser, send a Slack message or control a thermostat. That openness brings more security risk, and setup is finicky. Claude is more restricted because it's built for corporate use, where security comes first. For anyone new, I recommend Claude.
The site, built backwards
Then I rebuilt the LeadScore AI marketing site live, the reverse of how most people do it. Build the app first. Screenshot it. Give the screenshots to the model and let it work out what the copy should say.
I started in Lovable with a prompt describing the customer: business owners and sales professionals at roughly $5 to $10 million in revenue, and the goal of one salesperson managing 100,000 leads. I added full-page screenshots of the old site, taken with GoFullPage, to keep the design style, plus the pricing page and FAQ. Next I screenshotted the demo account's leads and pipeline screens, dropped them into ChatGPT for homepage and feature copy, and fed that back to Lovable.
For proper design work I'd use Google Stitch. For speed, Lovable gets to good enough in one shot. The business is getting to sales, and design time doesn't make sales.
Shipping to Cloudflare
I connected the Lovable project to GitHub and deployed it to Cloudflare Workers. The first build failed. I pasted the troubleshooting section from my Cloudflare course in the Vibe Code to Profit community, plus the build log, into VS Code, and that gave the model enough context to fix it. I walk through the wider setup in building a business on Cloudflare.
Selling is the work
The app exists so a buyer can say yes. With scores, one salesperson knows which buyer to call today. With a site built from the real product, everyone else can see what it does.
If you've built something and the next step is your first paying customers, that's what we work on when you start as a solo founder.