How to Set Up Lead Scoring + Lead Routing Software in 7 Steps (From MQL to Meeting Booked)

Lead scoring and lead routing are the two levers that determine whether your best-fit buyers get a fast, relevant sales experience—or fall into a queue to be “followed up later.” The goal isn’t to build a complicated scoring spreadsheet. It’s to create a system that reliably moves a lead from **MQL → SQL → meeting booked**.

Below is a 7-step setup you can implement in most CRMs and routing tools (HubSpot, Salesforce + Pardot/Account Engagement, Marketo, etc.). It’s written for teams that already understand demand gen and sales ops basics and want a clean, scalable approach.

---

Step 1) Define what “MQL” and “SQL” mean in your business

Most scoring projects fail because “MQL” is vague (“seems interested”) and “SQL” is subjective (“sales thinks it’s real”). Before you touch software, set working definitions:

- **MQL (Marketing Qualified Lead):** meets minimum fit + shows enough intent to justify sales attention.

- **SQL (Sales Qualified Lead):** sales has validated need, authority, timing, or at least a clear next step.

Keep it operational. A useful definition includes:

- **Entry criteria** (what must be true)

- **Exit criteria** (what must happen to advance)

- **Owner** (who acts next)

- **SLA** (how fast they must act)

**Example:**

- MQL = ICP match (company size + region + industry) AND intent score ≥ 20 in the last 14 days

- SQL = sales confirmed problem + target buying committee identified OR meeting set

This definition becomes the foundation for everything downstream: scoring thresholds, routing rules, and reporting.

---

Step 2) Map your data model: fields you must capture for scoring and routing

Lead scoring + lead routing software can only work with the inputs you provide. At minimum, ensure your CRM has clean, consistently populated fields for:

Fit (who they are)

- Industry

- Employee count / revenue band

- Geography / territory

- Job role / seniority

- Account type (SMB / Mid-Market / Enterprise)

Intent (what they’re doing)

- Website visits (pricing, integrations, security, case studies)

- Form fills / demo requests

- Email engagement

- Product signals (if applicable)

- LinkedIn engagement signals (profile views, post engagement, connection accepted)

Routing essentials

- Account owner / account status (net-new vs existing)

- Lead source (paid, organic, outbound, partner)

- Territory rules

- Duplicate detection keys (email, domain, company)

If you’re using LinkedIn-led outbound, you’ll also want reliable **company domain matching** so a “new lead” can be routed to the correct account owner instead of becoming a duplicate.

Teams that operationalize LinkedIn outreach often feed prospect and engagement signals into their CRM workflow; tools like [PRODUCT_LINK]{Reachy.ai’s LinkedIn outreach agent}[/PRODUCT_LINK] are typically used to standardize sourcing + messaging signals across reps and accounts.

---

Step 3) Build a simple scoring model: start with Fit + Intent (and keep it explainable)

The best lead scoring models are:

- **Simple enough** to maintain

- **Transparent** to sales

- **Accurate enough** to prioritize action

A practical approach is a **two-dimensional score**:

A) Fit score (0–100)

Measures how closely the lead matches your ICP.

**Example Fit points:**

- Industry matches ICP: +25

- Employee count in target band: +25

- Region in supported territory: +15

- Title is decision-maker: +20

- Uses compatible tech stack: +15

B) Intent score (0–100)

Measures buying signals and recency.

**Example Intent points:**

- Visited pricing page (last 7 days): +20

- Viewed 2+ case studies (last 14 days): +15

- Requested demo: +50

- Opened 3+ emails in 10 days: +10

- Clicked integration docs: +15

Add decay + negative scoring

- **Decay:** subtract points if activity is old (e.g., -20 after 14 days of no activity)

- **Negatives:** students, job seekers, irrelevant geos, competitors (e.g., -50)

Why this matters: When sales asks “Why is this lead hot?”, you can answer in one sentence.

---

Step 4) Set thresholds and stages: MQL → SQL → Meeting

Now translate scores into stage transitions.

A clean baseline:

- **MQL:** Fit ≥ 60 AND Intent ≥ 25

- **SQL (auto-create task for SDR):** Fit ≥ 70 AND Intent ≥ 40 OR Demo request

- **High Priority (fast lane):** Fit ≥ 80 AND Intent ≥ 60

Then define what happens at each stage:

For MQL

- Add to SDR queue

- Enroll in short “assist” sequence

- Assign SLA: first touch in 15–60 minutes (depending on your volume)

For SQL

- Require a disposition (Connected / No answer / Nurture / Disqualified)

- Create an opportunity only when a meeting is agreed (avoid pipeline inflation)

For Meeting Booked

- Stamp **meeting source** and **time-to-meeting** for reporting

If LinkedIn is part of your motion, you can speed up the MQL-to-meeting gap by using tools that trigger personalized messages based on real-time signals; for example, [PRODUCT_LINK]{Reachy.ai for hyper-personalized LinkedIn follow-ups}[/PRODUCT_LINK] can help teams operationalize “act fast with context” without relying on rep memory.

---

Step 5) Design lead routing rules that are fair, fast, and conflict-free

Scoring prioritizes; routing decides ownership. Great routing prevents three common issues:

1) **Slow response** (no one knows who owns it)

2) **Territory conflicts** (two reps reach out)

3) **Orphan leads** (no owner assigned)

Routing rules to implement

**1) Existing account wins**

- If domain matches an open opportunity or customer account → route to the account owner / CSM

**2) Territory + segment routing**

- Route by geography, then by segment (SMB/MM/ENT)

**3) Round-robin within a team**

- If multiple SDRs cover the same patch, use round-robin with guardrails:

- capacity caps

- out-of-office checks

- time zone alignment

**4) Source-based routing**

- Demo requests → fastest path (named owner + SLA)

- Content download → nurture-first unless score is high

- Outbound-sourced leads → stay with the originating SDR (prevents “lead theft”)

**5) Fallback routing**

- If no rule matches, route to a default queue with alerts

If your team manages multiple LinkedIn seats, standardizing ownership and activity logging is critical; systems like [PRODUCT_LINK]{Reachy.ai’s multi-account LinkedIn management}[/PRODUCT_LINK] are often used to ensure outbound activity aligns with the same routing and ownership logic in the CRM.

---

Step 6) Connect scoring + routing to actions: tasks, sequences, alerts, and SLAs

This is the step that actually changes outcomes.

Automations to configure

**When a lead becomes MQL:**

- Assign owner (routing)

- Create a task (with due time)

- Send an internal alert (Slack/Teams/email)

- Enroll in the correct sequence (email + LinkedIn + call)

**When a lead becomes high-priority:**

- Escalate SLA (e.g., 15 minutes)

- Notify the AE + SDR manager

- Temporarily pause marketing nurture to avoid mixed messages

**When a lead is not contacted within SLA:**

- Reassign or escalate

- Log SLA breach for coaching + ops fixes

This is where many teams see immediate lift: not because the score is perfect, but because **the handoff becomes reliable**.

If your outreach sequence includes LinkedIn touches, tools like [PRODUCT_LINK]{Reachy.ai integrated with your CRM workflows}[/PRODUCT_LINK] can help ensure the right prospect gets the right message at the right time—while keeping activity visible to the team.

---

Step 7) Measure what matters and iterate weekly (not quarterly)

Lead scoring and routing aren’t “set and forget.” Start with a baseline model, then refine using real outcomes.

Core metrics (MQL → Meeting Booked)

Track these by segment, source, and owner:

- **Speed to lead:** time from MQL to first touch

- **Contact rate:** % of MQLs with a completed first touch

- **SQL rate:** MQL → SQL conversion

- **Meeting rate:** MQL → meeting booked

- **Time to meeting:** median days from MQL to meeting

- **Routing accuracy:** % routed to correct owner on first assignment

- **SLA compliance:** % of MQLs touched within SLA

Practical iteration loop

- Weekly: review top 20 converted leads and top 20 “false positive” MQLs

- Adjust: scoring weights, negative rules, and thresholds

- Fix data: missing fields cause more damage than imperfect weights

A useful rule: **change one thing at a time**, then measure for at least a week (or a full volume cycle) before changing again.

---

Conclusion: A good system is one your team trusts

Lead scoring and lead routing software should create clarity: who to contact, why they matter, and who owns the next step. Start with a simple Fit + Intent model, route by account + territory, and connect the whole thing to real actions (tasks, sequences, alerts, SLAs). Then iterate based on MQL-to-meeting outcomes—not opinions.

When done well, you don’t just “prioritize leads.” You build a consistent, measurable path from **MQL to meeting booked** that scales with your pipeline.