CRM and Lifecycle skill 05 of 13
Lead Scoring and Routing SKILL.md
The Lead Scoring and Routing skill makes Claude, Codex or another AI agent build B2B scoring and routing from closed-won data. It writes lifecycle stage definitions sales and marketing both sign, separates fit from intent with decay, builds a fit-by-intent action matrix, adds product-qualified signals, designs routing and speed-to-lead service levels, and sets up a feedback loop with sales.
lead-scoring-routing/SKILL.md, version 1.0.0, 1,750 words.
By Afeez Adebayo, Marketing, SEO & Growth Expert with 10+ years of experience.
Created 10 October 2026. Updated 10 October 2026. Free to use under CC BY 4.0.
In B2B, lifecycle marketing meets sales at one point: deciding which leads are ready for a conversation, who should have it, and what happens to everyone else. Poor scoring sends sales people who downloaded one ebook and ignores the account that visited pricing five times. Poor routing leaves hot leads waiting days, or sends them to the wrong rep. Both waste the budget that created the leads.
This skill builds a scoring model from closed-won data, defines lifecycle stages sales and marketing both accept, and designs routing and service levels so the right lead reaches the right person quickly, while everyone else gets nurtured.
Operating principles
- Score from outcomes. Weights come from what closed-won customers did and looked like, not from what feels important.
- Separate fit from intent. Fit (who they are) and intent (what they did) answer different questions; combine them deliberately.
- Decay old behaviour. A pricing visit last week matters; one last year doesn't.
- Agree definitions in writing. MQL, SQL and SAL mean nothing unless sales and marketing sign the same definitions.
- Speed matters. Response time to high-intent leads is one of the biggest controllable factors in conversion. [Consensus from sales research]
Fit and intent
| Dimension | Signals | Example weights (illustrative) |
|---|---|---|
| Fit: firmographic | Industry, company size, region, tech stack | Target industry +15; under 10 employees -20 |
| Fit: person | Role, seniority, department | Decision-maker role +20; student -30 |
| Intent: high | Pricing page visits, demo request, trial sign-up, product usage in trial | Demo request: route immediately |
| Intent: medium | Case study views, webinar attendance, comparison pages | +10 each, decaying |
| Intent: low | Blog visits, newsletter clicks | +2 each, decaying |
| Negative | Competitor domain, job seeker, unsubscribed, personal email (sometimes) | Exclude or subtract |
Weights must be calibrated on your own data; the numbers above only illustrate structure.
When to use, and when not to
Use it for B2B and high-consideration B2C (finance, property, education) when sales complain about lead quality, when leads wait too long, when MQL volume rises but pipeline doesn't, or when moving CRM.
Don't use it for self-serve products where no salesperson is involved (use onboarding-activation and product-qualified signals instead) or to clean the data first (crm-data-hygiene).
Inputs to ask for, in one message
- CRM (HubSpot, Salesforce) and marketing automation setup.
- Closed-won and closed-lost deals for 12 to 24 months with contact and account properties and activity history.
- Current lifecycle stage definitions and scoring rules.
- Sales team structure: territories, segments, round-robin rules, capacity.
- Current speed-to-lead and conversion rates by stage.
- Product usage data if there's a free trial or freemium plan.
Raw SKILL.md file
This is the exact file agents read, including the credit header and licence notice. Save it as lead-scoring-routing/SKILL.md.
--- name: lead-scoring-routing description: "Build B2B lead scoring and routing from closed-won data: signed-off lifecycle stage definitions (MQL, SAL, SQL), separate fit and intent scores with decay, a fit by intent action matrix, product-qualified lead signals, routing by territory, segment, ownership and capacity, speed-to-lead service levels, sales feedback loops and nurture for everyone below threshold in HubSpot or Salesforce. Use whenever someone asks about lead scoring, MQL definitions, lead routing, sales and marketing alignment, lead quality complaints, speed to lead, product-qualified leads or why marketing leads don't turn into pipeline." license: CC-BY-4.0 metadata: author: Afeez Adebayo author_url: https://afeezadebayo.com author_linkedin: https://www.linkedin.com/in/afeez-adebayo/ author_x: https://x.com/za_icon source: https://afeezadebayo.com/skills-md/marketing/crm-lifecycle/lead-scoring-routing/ category: marketing subcategory: crm-lifecycle version: "1.0.0" created: "2026-10-10" updated: "2026-10-10" --- # Lead Scoring and Routing In B2B, lifecycle marketing meets sales at one point: deciding which leads are ready for a conversation, who should have it, and what happens to everyone else. Poor scoring sends sales people who downloaded one ebook and ignores the account that visited pricing five times. Poor routing leaves hot leads waiting days, or sends them to the wrong rep. Both waste the budget that created the leads. This skill builds a scoring model from closed-won data, defines lifecycle stages sales and marketing both accept, and designs routing and service levels so the right lead reaches the right person quickly, while everyone else gets nurtured. ## Operating principles 1. **Score from outcomes.** Weights come from what closed-won customers did and looked like, not from what feels important. 2. **Separate fit from intent.** Fit (who they are) and intent (what they did) answer different questions; combine them deliberately. 3. **Decay old behaviour.** A pricing visit last week matters; one last year doesn't. 4. **Agree definitions in writing.** MQL, SQL and SAL mean nothing unless sales and marketing sign the same definitions. 5. **Speed matters.** Response time to high-intent leads is one of the biggest controllable factors in conversion. [Consensus from sales research] ## Fit and intent | Dimension | Signals | Example weights (illustrative) | |---|---|---| | Fit: firmographic | Industry, company size, region, tech stack | Target industry +15; under 10 employees -20 | | Fit: person | Role, seniority, department | Decision-maker role +20; student -30 | | Intent: high | Pricing page visits, demo request, trial sign-up, product usage in trial | Demo request: route immediately | | Intent: medium | Case study views, webinar attendance, comparison pages | +10 each, decaying | | Intent: low | Blog visits, newsletter clicks | +2 each, decaying | | Negative | Competitor domain, job seeker, unsubscribed, personal email (sometimes) | Exclude or subtract | Weights must be calibrated on your own data; the numbers above only illustrate structure. ## When to use, and when not to Use it for B2B and high-consideration B2C (finance, property, education) when sales complain about lead quality, when leads wait too long, when MQL volume rises but pipeline doesn't, or when moving CRM. Don't use it for self-serve products where no salesperson is involved (use `onboarding-activation` and product-qualified signals instead) or to clean the data first (`crm-data-hygiene`). ## Inputs to ask for, in one message 1. CRM (HubSpot, Salesforce) and marketing automation setup. 2. Closed-won and closed-lost deals for 12 to 24 months with contact and account properties and activity history. 3. Current lifecycle stage definitions and scoring rules. 4. Sales team structure: territories, segments, round-robin rules, capacity. 5. Current speed-to-lead and conversion rates by stage. 6. Product usage data if there's a free trial or freemium plan. ## Workflow ### Step 1. Agree stage definitions Write definitions for lead, MQL (marketing qualified), SAL (sales accepted), SQL (sales qualified), opportunity and customer, with entry criteria and owner for each. Get both teams to sign off. ### Step 2. Analyse closed-won patterns Compare won, lost and never-converted leads: firmographics, roles, sources, pages visited, content consumed, product usage. Identify the signals that separate them. ### Step 3. Build the model Separate fit and intent scores. Use a matrix (fit A to D, intent 1 to 4) rather than one blended number, so a perfect-fit account with no intent gets nurture, and a high-intent poor-fit lead gets a lighter touch. | | Intent high | Intent medium | Intent low | |---|---|---|---| | Fit A | Route to AE now | SDR outreach | Account-based nurture | | Fit B | SDR outreach | Nurture plus SDR | Nurture | | Fit C | Self-serve or partner | Nurture | Nurture | | Fit D | Disqualify politely | Exclude | Exclude | ### Step 4. Add decay and thresholds Reduce intent points over time (for example halve after 30 days). Set the MQL threshold where historical conversion to opportunity justifies sales time. ### Step 5. Design routing Rules by territory, segment, account ownership (existing accounts go to their owner), language and capacity. Use round-robin within teams, with fallbacks for absence. ### Step 6. Set service levels Response times by lead type (for example demo requests within business hours the same day), follow-up attempts, and when a lead returns to nurture. ### Step 7. Build feedback loops Sales reject reasons recorded in a picklist; weekly review of rejected MQLs; quarterly recalibration of weights against new closed-won data. ### Step 8. Nurture the rest Leads below threshold enter nurture tracks by fit and interest, with clear re-entry rules when intent rises. ## Product-qualified leads For products with trials or free plans, usage signals (seats added, key feature used, usage limit reached) often predict buying better than marketing activity. Define product-qualified lead criteria with product and sales teams, and route accounts that hit them. ## Sales reject reasons picklist | Reason | What it tells marketing | |---|---| | Not the decision-maker | Adjust role weights or add account-based routing | | Company too small | Raise the fit threshold for size | | No current need | Intent signals may be weak or decayed too slowly | | Already a customer | Routing should check account ownership first | | Student or job seeker | Add negative signals or form questions | | Unreachable | Data quality or phone capture problem | | Competitor | Exclude competitor domains | Review rejected MQLs weekly for the first two months after launch, then monthly. ## Speed-to-lead playbook - High-intent forms (demo, contact sales) create a task and an alert to the assigned rep immediately. - Use scheduling links on the thank-you page so prospects can book straight away. - Out-of-hours leads get an automatic, human-sounding reply with booking options. - Measure median and 90th-percentile response time by rep and by lead source. - Escalate to a team lead if a high-intent lead is untouched past the service level. ## Calibration check (quarterly) 1. Pull leads created in the last two quarters with their scores at MQL. 2. Compare conversion to opportunity and to closed-won by score band. 3. If a lower band converts nearly as well as a higher one, the threshold or weights need adjusting. 4. Check each signal's contribution: remove ones that no longer separate won from lost. 5. Document changes and tell sales what changed and why. ## Account-based routing basics - Match leads to existing accounts by domain before any round-robin. - If the account has an owner, route to them, even if the lead's score is low. - For target accounts without an owner, assign by territory and notify the account team. - Group multiple contacts from one account into one opportunity view. ## Edge cases and judgement calls | Situation | What to do | |---|---| | Many contacts from one account | Score and route at account level; avoid several reps contacting the same company | | Personal email addresses | Don't auto-disqualify in markets or segments where they're common; use other fit signals | | Very low lead volume | Simple rules and manual review beat complex models | | Inbound demo from a poor-fit company | Route to a lighter process (self-serve, partner) rather than ignoring | | Sales ignores MQLs | Check speed-to-lead and reject reasons before changing the model | | AI or vendor predictive scores | Validate against your outcomes and keep the explanation visible to reps | ## Handoffs to related skills - Clean data and enrichment: `crm-data-hygiene` - Journey stages: `customer-journey-mapping` - Nurture content: `lifecycle-email-copy-design` - Trial users: `onboarding-activation` - Funnel reporting: `lifecycle-reporting-attribution` ## Worked example A B2B analytics company sent 600 MQLs a month to sales, who accepted fewer than a third. Analysis of 18 months of deals showed webinar attendance and ebook downloads barely predicted wins, while pricing visits, integration page views and company size between 50 and 1,000 employees did. A fit and intent matrix with 30-day decay replaced the single score. Demo requests went straight to account executives with a same-day service level, and existing accounts routed to their owners. MQL volume fell to 220 a month, sales acceptance rose to most of them and pipeline from inbound grew. ## Output format ``` # Lead scoring and routing plan: <business>, <date> ## Stage definitions (signed off) ## Closed-won analysis (signals that predict wins) ## Scoring model: fit and intent criteria, weights, decay, thresholds ## Fit x intent action matrix ## Routing rules and service levels ## Feedback loop and recalibration schedule ## Nurture tracks for below-threshold leads ``` ## Common mistakes - Weights based on opinion rather than closed-won data. - One blended score that hides poor fit or missing intent. - No decay, so old activity keeps leads hot forever. - No agreed definitions, so teams argue about lead quality. - Slow follow-up on high-intent leads. ## Questions to ask before you build - What does a closed-won customer look like, by data? - How fast does sales respond today, by lead type? - Who owns stage definitions and recalibration? ## Self-check before you answer - Are fit and intent separate and based on outcomes? - Is there decay and a threshold tied to conversion? - Are routing rules and service levels explicit? - Is there a feedback loop with sales? ## Official documentation - HubSpot lead scoring: https://knowledge.hubspot.com/ - Salesforce lead assignment rules: https://help.salesforce.com/ --- Created by Afeez Adebayo, Marketing, SEO & Growth Expert Website: https://afeezadebayo.com LinkedIn: https://www.linkedin.com/in/afeez-adebayo/ X: https://x.com/za_icon Source: https://afeezadebayo.com/skills-md/marketing/crm-lifecycle/lead-scoring-routing/ Licence: CC BY 4.0 (https://creativecommons.org/licenses/by/4.0/). You may copy, share and adapt this skill, including for commercial use, as long as you credit Afeez Adebayo and link to the source URL above. Keep this notice in any copy or adapted version.
Workflow
Step 1. Agree stage definitions
Write definitions for lead, MQL (marketing qualified), SAL (sales accepted), SQL (sales qualified), opportunity and customer, with entry criteria and owner for each. Get both teams to sign off.
Step 2. Analyse closed-won patterns
Compare won, lost and never-converted leads: firmographics, roles, sources, pages visited, content consumed, product usage. Identify the signals that separate them.
Step 3. Build the model
Separate fit and intent scores. Use a matrix (fit A to D, intent 1 to 4) rather than one blended number, so a perfect-fit account with no intent gets nurture, and a high-intent poor-fit lead gets a lighter touch.
| Intent high | Intent medium | Intent low | |
|---|---|---|---|
| Fit A | Route to AE now | SDR outreach | Account-based nurture |
| Fit B | SDR outreach | Nurture plus SDR | Nurture |
| Fit C | Self-serve or partner | Nurture | Nurture |
| Fit D | Disqualify politely | Exclude | Exclude |
Step 4. Add decay and thresholds
Reduce intent points over time (for example halve after 30 days). Set the MQL threshold where historical conversion to opportunity justifies sales time.
Step 5. Design routing
Rules by territory, segment, account ownership (existing accounts go to their owner), language and capacity. Use round-robin within teams, with fallbacks for absence.
Step 6. Set service levels
Response times by lead type (for example demo requests within business hours the same day), follow-up attempts, and when a lead returns to nurture.
Step 7. Build feedback loops
Sales reject reasons recorded in a picklist; weekly review of rejected MQLs; quarterly recalibration of weights against new closed-won data.
Step 8. Nurture the rest
Leads below threshold enter nurture tracks by fit and interest, with clear re-entry rules when intent rises.
Product-qualified leads
For products with trials or free plans, usage signals (seats added, key feature used, usage limit reached) often predict buying better than marketing activity. Define product-qualified lead criteria with product and sales teams, and route accounts that hit them.
Sales reject reasons picklist
| Reason | What it tells marketing |
|---|---|
| Not the decision-maker | Adjust role weights or add account-based routing |
| Company too small | Raise the fit threshold for size |
| No current need | Intent signals may be weak or decayed too slowly |
| Already a customer | Routing should check account ownership first |
| Student or job seeker | Add negative signals or form questions |
| Unreachable | Data quality or phone capture problem |
| Competitor | Exclude competitor domains |
Review rejected MQLs weekly for the first two months after launch, then monthly.
Speed-to-lead playbook
- High-intent forms (demo, contact sales) create a task and an alert to the assigned rep immediately.
- Use scheduling links on the thank-you page so prospects can book straight away.
- Out-of-hours leads get an automatic, human-sounding reply with booking options.
- Measure median and 90th-percentile response time by rep and by lead source.
- Escalate to a team lead if a high-intent lead is untouched past the service level.
Calibration check (quarterly)
- Pull leads created in the last two quarters with their scores at MQL.
- Compare conversion to opportunity and to closed-won by score band.
- If a lower band converts nearly as well as a higher one, the threshold or weights need adjusting.
- Check each signal's contribution: remove ones that no longer separate won from lost.
- Document changes and tell sales what changed and why.
Account-based routing basics
- Match leads to existing accounts by domain before any round-robin.
- If the account has an owner, route to them, even if the lead's score is low.
- For target accounts without an owner, assign by territory and notify the account team.
- Group multiple contacts from one account into one opportunity view.
Edge cases and judgement calls
| Situation | What to do |
|---|---|
| Many contacts from one account | Score and route at account level; avoid several reps contacting the same company |
| Personal email addresses | Don't auto-disqualify in markets or segments where they're common; use other fit signals |
| Very low lead volume | Simple rules and manual review beat complex models |
| Inbound demo from a poor-fit company | Route to a lighter process (self-serve, partner) rather than ignoring |
| Sales ignores MQLs | Check speed-to-lead and reject reasons before changing the model |
| AI or vendor predictive scores | Validate against your outcomes and keep the explanation visible to reps |
Handoffs to related skills
- Clean data and enrichment:
crm-data-hygiene - Journey stages:
customer-journey-mapping - Nurture content:
lifecycle-email-copy-design - Trial users:
onboarding-activation - Funnel reporting:
lifecycle-reporting-attribution
Worked example
A B2B analytics company sent 600 MQLs a month to sales, who accepted fewer than a third. Analysis of 18 months of deals showed webinar attendance and ebook downloads barely predicted wins, while pricing visits, integration page views and company size between 50 and 1,000 employees did. A fit and intent matrix with 30-day decay replaced the single score. Demo requests went straight to account executives with a same-day service level, and existing accounts routed to their owners. MQL volume fell to 220 a month, sales acceptance rose to most of them and pipeline from inbound grew.
Output format
# Lead scoring and routing plan: <business>, <date>
## Stage definitions (signed off)
## Closed-won analysis (signals that predict wins)
## Scoring model: fit and intent criteria, weights, decay, thresholds
## Fit x intent action matrix
## Routing rules and service levels
## Feedback loop and recalibration schedule
## Nurture tracks for below-threshold leadsCommon mistakes
- Weights based on opinion rather than closed-won data.
- One blended score that hides poor fit or missing intent.
- No decay, so old activity keeps leads hot forever.
- No agreed definitions, so teams argue about lead quality.
- Slow follow-up on high-intent leads.
Questions to ask before you build
- What does a closed-won customer look like, by data?
- How fast does sales respond today, by lead type?
- Who owns stage definitions and recalibration?
Self-check before you answer
- Are fit and intent separate and based on outcomes?
- Is there decay and a threshold tied to conversion?
- Are routing rules and service levels explicit?
- Is there a feedback loop with sales?
Official documentation
- HubSpot lead scoring: https://knowledge.hubspot.com/
- Salesforce lead assignment rules: https://help.salesforce.com/
On this page
- When to use this skill, and when not to
- Example prompts
- Example output
- What the agent needs from you
- How this skill hands off to related skills
- How to run Lead Scoring and Routing step by step
- Situations this skill handles
- What makes this skill different
- Practical tips from real projects
- Frequently asked questions
- Changelog
When to use this skill, and when not to
Use it for B2B and high-consideration B2C (finance, property, education) when sales complain about lead quality, when leads wait too long, when MQL volume rises but pipeline doesn’t, or when moving CRM.
Scoring decides which leads deserve a salesperson’s time; routing decides who gets them and how fast. Weights based on opinion send sales ebook downloaders and ignore the account that visited pricing five times, so the skill calibrates everything on what closed-won customers actually did.
Don’t use it for self-serve products without sales (use Onboarding and Activation) or to clean data first (use CRM Data Hygiene).
Example prompts
- “Rebuild our MQL definition from 18 months of closed-won deals in HubSpot.”
- “Sales accepts fewer than a third of MQLs. Diagnose why.”
- “Design routing rules by territory, segment and account ownership.”
- “Define product-qualified leads for our free plan.”
- “Set speed-to-lead service levels and escalation for demo requests.”
Example output
The skill returns a fixed structure. A shortened example for an imaginary site:
# Lead scoring and routing plan: example analytics SaaS, 10 October 2026 ## Closed-won signals Strong: pricing visits, integration pages, 50-1,000 employees. Weak: webinars, ebooks. ## Fit x intent matrix | | High intent | Medium | Low | | Fit A | AE now | SDR | ABM nurture | | Fit B | SDR | Nurture + SDR | Nurture | | Fit C | Self-serve | Nurture | Nurture | ## Rules Intent decays by half after 30 days. Demo requests: same business day. Existing accounts route to owner.
Weights are calibrated on your own closed-won data and recalibrated quarterly, because buying patterns change.
What the agent needs from you
The skill asks for your CRM and marketing automation setup, 12 to 24 months of closed-won and closed-lost deals with properties and activity, current stage definitions and scoring rules, sales team structure and capacity, current speed-to-lead and conversion rates, and product usage data if you have a trial or free plan.
How this skill hands off to related skills
Scoring connects marketing and sales work. Clean data and enrichment come from CRM Data Hygiene, stages from Customer Journey Mapping, nurture content from Lifecycle Email Copy and Design, trial users from Onboarding and Activation and funnel reporting from Lifecycle Reporting.
How to run Lead Scoring and Routing step by step
- Install the skill as
lead-scoring-routing/SKILL.md. - Export 12 to 24 months of deals with contact, account and activity data.
- Share current stage definitions and scoring rules.
- Describe the sales team: territories, segments, capacity and round-robin rules.
- Review the model, matrix, routing and service levels with sales.
- Launch, review rejected MQLs weekly and recalibrate quarterly.
Situations this skill handles
Lead quality complaints have different causes. The skill handles these situations:
| Situation | What the skill does |
|---|---|
| Too many MQLs, low acceptance | Rebuilds weights from closed-won data and raises the threshold |
| Hot leads wait days | Sets service levels, alerts and escalation |
| Several reps contact one company | Routes by account ownership first |
| Free plan with no sales signal | Defines product-qualified leads from usage |
| Personal email domains common | Uses other fit signals instead of auto-disqualifying |
| Vendor predictive scores | Validates them against your outcomes before use |
What makes this skill different
Most lead scoring is a points table someone wrote years ago. This skill rebuilds it from what closed-won customers actually did and looked like, separates fit from intent, decays old activity and turns scores into actions through a matrix, so poor fit and missing intent are never hidden in one number.
It also covers the half that scoring guides skip: routing, service levels and a feedback loop with sales, because a perfect score is worthless if the lead waits three days or reaches the wrong rep.
Practical tips from real projects
- Get stage definitions signed by sales and marketing before building anything.
- Decay intent; last year’s ebook download isn’t buying intent.
- Route existing accounts to their owner before any round-robin.
- Record reject reasons in a picklist so marketing can learn from them.
A worked example: a B2B analytics company sent 600 MQLs a month and sales accepted fewer than a third. Eighteen months of deals showed webinar attendance and ebook downloads barely predicted wins, while pricing visits, integration page views and company size between 50 and 1,000 employees did. A fit-by-intent matrix with 30-day decay replaced the single score, demo requests went straight to account executives with a same-day service level and existing accounts routed to their owners. MQLs fell to 220 a month, sales accepted most of them and inbound pipeline grew.
The skill includes a reject-reason picklist, a speed-to-lead playbook (alerts, booking links on thank-you pages, out-of-hours replies, escalation) and a quarterly calibration check comparing conversion by score band, so the model improves instead of drifting.
For companies with free plans or trials, product signals often beat marketing activity. Seats added, a key feature used or a usage limit reached can indicate readiness to buy more reliably than any number of content downloads, and the skill defines product-qualified lead criteria with product and sales teams together.
Account-based routing finishes the system: leads matched to accounts by domain, owners notified, multiple contacts grouped and target accounts assigned by territory. The result is one coordinated conversation per company instead of several reps calling the same buyer.
Stage definitions are the foundation. Lead, MQL, SAL, SQL, opportunity and customer each need written entry criteria and an owner, agreed by both teams. Without them, every lead-quality discussion becomes an argument about words rather than a review of evidence, and no scoring model can satisfy everyone.
Leads below threshold enter nurture by fit and interest, with clear rules for re-entry when intent rises.
Frequently asked questions
What is lead scoring?
A way to rank leads by how well they fit your ideal customer and how strongly they show buying intent, so sales focuses on the ones most likely to buy.
Why separate fit and intent?
They answer different questions. A perfect-fit company with no intent needs nurture; a high-intent poor-fit lead needs a lighter process. One blended score hides both.
What is score decay?
Reducing intent points over time, so a pricing visit last week counts more than one last year.
What is a product-qualified lead?
An account whose product usage, such as adding seats or hitting a usage limit, signals readiness to buy. Often a better signal than marketing activity.
How fast should sales respond?
For high-intent requests such as demos, as quickly as possible, ideally the same business day. Response speed is one of the biggest controllable factors in conversion.
How often should scoring change?
Review rejected MQLs weekly at first, then recalibrate weights against new closed-won data every quarter.
Changelog
- 1.0.0, 10 October 2026: first release.
Use, adapt and share this skill under CC BY 4.0: credit Afeez Adebayo and link to this page.
All CRM and Lifecycle Marketing skills
- Lifecycle Marketing Audit
- Customer Journey Mapping for Lifecycle
- Lifecycle Segmentation and Engagement Tiers
- CRM Data Hygiene and Enrichment
- Onboarding and Activation Sequences
- Retention and Churn Prevention
- Win-Back and Reactivation Campaigns
- Email Deliverability and Inbox Placement
- Lifecycle Email Copy and Design
- SMS and WhatsApp Lifecycle Messaging
- Lifecycle Experimentation and Holdout Testing
- Lifecycle Reporting and Attribution
