Okay, I have to share this because it’s been a total game-changer for my consulting side-hustle. I was drowning in leads from my website and newsletter, never knowing who to prioritize. My old "star them in Gmail" method was not cutting it.
I finally built a real-time lead scoring system using a few tools that play nicely together. The goal was simple: automate the scoring so I can instantly see who’s hot and who’s not, right from my dashboard.
Here’s the basic workflow I pieced together:
* **Form Capture:** I use **Tally.so** for my contact forms. It’s fantastic because it can send data to multiple places via webhooks.
* **Central Brain:** All form submissions land in **Airtable**. This is my source of truth. Each lead gets a record with fields for initial data (like company size, need urgency).
* **The Scoring Magic:** This is where **Make.com** (formerly Integromat) comes in. I have a scenario that triggers on new Airtable records. It does a few checks:
* Checks the lead's domain against my past client list (in another Airtable).
* Looks for keywords in their message that indicate budget or timeline.
* Even scores based on how they found me (newsletter subscribers get a small bump).
* Each check adds or subtracts points. Make.com then updates the lead's record in Airtable with a final "Hot Score" (1-100).
* **Real-Time Dashboard:** I have a separate **Notion** dashboard that pulls in the scored leads from Airtable via the official integration. I sort them by score and have different views for "Hot (>80)", "Warm (50-80)", and "Cold (<50)". This is what I look at every morning.
The beauty is it all happens in about 60 seconds after they hit submit. No manual tagging, no guesswork. I can now focus my energy on the leads that are most likely to convert.
Has anyone else built something similar? I’d love to compare notes, especially on the scoring criteria. I'm sure mine could be more sophisticated!
Attached are a couple of screenshots of my Notion dashboard and the Make.com scenario flow. It looks complex but it's really just a series of simple "if this, then add points" routers.
✨ laura
null
Nice setup! I've built something similar with Airtable and Make, though I also feed in Clearbit enrichment data for the domain check. It adds firmographic scoring automatically - employee count, funding, tech stack.
One thing I'd watch: if your newsletter source is a high-intent signal, you might want to give it a bigger score bump than a generic web visit. I made that tweak and it really helped prioritize my warmest leads.
Have you thought about piping the final score back into something like a Slack alert for the real screamers?
spreadsheet ninja
Clearbit's a great addition for that automatic enrichment. The firmographic data saves so much manual look-up time.
I like your point about weighting the newsletter source higher. It's easy to treat all lead sources the same in a scoring matrix, but intent really does vary. We found that leads from our "Pricing" page download got a much higher initial score than blog subscribers, and it cut our response time down.
Piping to Slack is a solid next step. We actually set up a dedicated channel for high-priority alerts, and it creates a nice sense of urgency for the team. The only caveat we learned is to set the threshold high enough, or the channel gets noisy and people start to ignore it.
Keep it civil, keep it real
The Slack noise point is crucial. We learned that the hard way after creating alert fatigue in a sales channel.
What worked better for us was a dual approach: a low-volume Slack channel for the true "screamer" leads (e.g., score > 85), and a daily digest email sent via a scheduled workflow that listed all leads scored above 70. The digest gave the team context without the constant interruptions, and they could batch their outreach.
It also forced us to define our scoring tiers more rigorously, which improved the model itself.
That's a smart way to handle alert fatigue. I've seen teams get overwhelmed quickly with notifications. The daily digest email for leads above 70 is clever.
How did you decide on those specific score thresholds? Was it based on historical conversion data, or more of a starting guess you refined later?