How to Build a Lead Scoring System Without a $50K CRM

How to Build a Lead Scoring System Without a $50K CRM

Lead scoring has a reputation as an enterprise feature requiring Salesforce, Marketo, and a dedicated RevOps team to configure correctly. That reputation is wrong. A functional lead scoring system that separates active buyers from passive subscribers and routes the right leads to the right follow-up can be built with Mautic, EspoCRM, and n8n for under $50 per month in infrastructure costs.

The complexity is not in the tools. It is in the scoring logic. Getting the scoring logic right is a week of work, not a quarter.

The Scoring Framework

Lead scoring assigns numeric values to contact behaviors. Engagement depth (email opens, article reads, newsletter replies) signals ongoing interest but not imminent purchase intent. Points: low, 1 to 5 per action. Intent signals (pricing page visit, contact form view, case study download) signal active evaluation. Points: high, 10 to 20 per action. Qualification signals (form submission with company and role data, demo request, webinar attendance) signal both intent and qualification. Points: very high, 20 to 30 per action.

Decay: scores should decay over time for inactive contacts. A contact who scored 60 six months ago and has not engaged since is not a hot lead. Implement score decay at 10 percent per month for contacts with no activity in 30 days.

Mautic Configuration

Mautic's Points module handles scoring natively. Configuration path: Points, then Triggers, then Actions. Define each behavior type as a point action with the appropriate value. Page visits require the Mautic tracking pixel installed on your site.

Set threshold triggers at three levels: 25 points (warm lead, tag and increase email frequency), 50 points (hot lead, route to CRM), 100 points (champion, flag for personal outreach). These thresholds are starting points; calibrate them against your actual conversion data after 60 to 90 days.

EspoCRM Routing

When a contact hits the hot-lead threshold in Mautic, an n8n workflow fires: it reads the contact data from Mautic's API, creates a Lead record in EspoCRM with the contact's email, name, score, and niche, and assigns it to the appropriate follow-up queue.

EspoCRM's Lead records should capture: score at time of routing, niche (which newsletter they subscribed to), last engagement action, and company and role if captured. These fields inform the follow-up message. A finance newsletter subscriber at a mid-market company who visited the pricing page after a CFO-focused article gets a different outreach than a tech subscriber who clicked a general-interest link.

Practical Thresholds

The common mistake in lead scoring is setting thresholds too low, resulting in a flood of hot leads that are actually just moderately engaged subscribers. A hot-lead threshold should represent a contact that a reasonable salesperson would prioritize reaching out to within 24 hours. If more than 5 percent of your list hits the hot-lead threshold in a given month, your threshold is probably too low.

For an early-stage newsletter business with a list under 5,000 subscribers, aim for 1 to 3 percent of the list hitting the hot-lead threshold per month. Quality of follow-up on a small number of genuinely high-intent leads beats volume of mediocre follow-up on a large number of loosely scored contacts every time.

Marketing OS runs on the same growth stack Crescevo builds for B2B marketing teams and agencies. If you’re building owned audience instead of renting it — see how →
No guarantee of traffic, rankings, leads, conversions, or revenue from any strategy discussed. Full disclaimer →