About This Build

A snapshot of what is live in the Meshy lead pipeline today, what is planned next, how it was built, and the guardrails that keep it compliant and safe to send from.

Lead scoring
Live
  • Fit, Signal and Seniority scored independently: 0 to 100 total
  • Reasoning step runs before email drafting: AI determines fit before writing anything
  • Management filter: Senior, Manager, Director, C-Level, Head, Founder, VP
  • Director-level contacts weighted higher in seniority scoring
Planned
  • Auto-reject leads scoring under 70: score still visible in dashboard
  • Previous engagement as a scoring input
  • ICP engaging with competitor posts as a signal
  • Per-lead signal verification: no recycled signals across same-company leads
Development roadmap
Live
  • Human-in-the-loop review: no message sends without approval
  • Inline message editing before approval
  • Two tone versions per lead: Peer and Informed Outsider
  • Disqualified leads visible with score and reject reason
Future
  • SMTP relay connection to inbox
  • DISC personality profile matching: tailor tone to Dominant, Influential, Steadiness, or Conscientiousness type per lead
  • API connection with Meshy to generate creative assets for outreach
  • Team command cheat sheet (Tier A / Top 5 / by title)
  • Email tracking module
  • UI enhancements
How it was built
01 · Logic design
AI-assisted session to define ICP rules, signal hierarchy, scoring dimensions, and the decision to run scoring and qualification as independent Claude calls so neither contaminates the other.
02 · Pipeline architecture
Make.com built as orchestrator. Scoring, qualification, and email drafting run as three isolated Claude calls: each with its own system prompt, input schema, and JSON output contract. Neither call sees the other's output, preventing scoring from influencing qualification and vice versa.
03 · Frontend
Lovable.dev built from a single master prompt containing the full Supabase schema, webhook endpoint, Meshy design system tokens, and component layout specs.
Compliance and safety
Data and privacy
GDPR compliantNo LinkedIn Cookie Session Risk
  • Coresignal used for all LinkedIn data: no cookies, no session tokens, no scraping
  • Data stored in an isolated Supabase instance
Responsible sending
  • Randomised delays and rate-limiting logic in Make.com
  • Human review required before any message sends
  • Disqualified leads never receive outreach: rejection logged and visible