I ship B2B lead lists where every row carries its evidence — source link, verification method and check date. Dead row = replacement or cash back in 24h.
The collection pipeline is open source (stdlib Python, no API keys): it reads public job boards — Greenhouse / Lever / Ashby — to find companies hiring outbound-sales roles right now, which is an approved-budget signal plus a 60-90 day pipeline gap. Last full run: 2,662 matching roles across 214 companies.
What if your finance dashboard caught the money you paid twice? 👀
This is Plug, a product I designed and built.
It scans every vendor payment, flags duplicates and overpayments, and shows exactly why: same invoice, same amount, paid 2 days apart. One click starts the recovery, with approvals and an audit trail.
The design rule I followed: never let AI act without showing its evidence first.
Stop relying on memory to follow up with every property lead.
A simple plan to start from:
📌 Day 0: acknowledge the enquiry promptly
📌 Day 1: check whether they need more information
📌 Day 3: offer a useful next step
📌 Day 7: follow up if it’s appropriate, then only continue when it’s relevant
Automation can manage these tasks, with stop conditions so nobody keeps getting messages after they reply or book.
This is an example, not a rule. Personalize it to the lead, and only message people who have agreed to hear from you.
Save this as a starting point for your follow-up process. 🔖