@miranda0808/maya-codex 0.1.0

package/payload/.agents/skills/revops/evals/evals.json

@@ -0,0 +1,91 @@
+{
+  "skill_name": "revops",
+  "evals": [
+    {
+      "id": 1,
+      "prompt": "Help me set up our lead lifecycle stages. We're a B2B SaaS company selling to mid-market. We use HubSpot as our CRM and have marketing and sales teams that aren't aligned on lead definitions.",
+      "expected_output": "Should use approved TASK-PACKET.md inputs first in Maya task workflows, and read PRODUCT.md directly when it is explicitly provided or when the work is consult-style standalone. Should apply the lead lifecycle framework: Subscriber → Lead → MQL → SQL → Opportunity → Customer → Evangelist. Should define clear criteria for each stage transition (what makes a Lead become an MQL, etc.). Should address the alignment issue between marketing and sales — define shared definitions and SLAs. Should recommend CRM implementation steps for HubSpot. Should include lead scoring setup. Should provide a handoff process between marketing and sales.",
+      "assertions": [
+        "Uses approved TASK-PACKET.md inputs or PRODUCT.md context first",
+        "Applies lead lifecycle framework with all stages",
+        "Defines criteria for each stage transition",
+        "Addresses marketing-sales alignment",
+        "Provides CRM implementation guidance for HubSpot",
+        "Includes lead scoring setup",
+        "Provides handoff process between teams"
+      ],
+      "files": []
+    },
+    {
+      "id": 2,
+      "prompt": "Set up lead scoring for us. We want to prioritize which leads sales should call first. We sell enterprise software ($50k+ ACV).",
+      "expected_output": "Should apply the lead scoring framework with three dimensions: explicit scoring (firmographics — company size, industry, title match), implicit scoring (behavioral — page visits, content downloads, email engagement), and negative scoring (unsubscribes, competitor emails, student emails). Should provide specific scoring criteria appropriate for enterprise ($50k+ ACV): weight firmographic signals heavily, include budget and authority signals. Should define score thresholds for MQL and SQL. Should recommend lead routing based on scores.",
+      "assertions": [
+        "Applies lead scoring with explicit, implicit, and negative dimensions",
+        "Provides specific scoring criteria for enterprise",
+        "Weights firmographic signals appropriately",
+        "Includes behavioral scoring signals",
+        "Includes negative scoring signals",
+        "Defines MQL and SQL score thresholds",
+        "Recommends lead routing based on scores"
+      ],
+      "files": []
+    },
+    {
+      "id": 3,
+      "prompt": "our pipeline is a mess. deals sit in stages forever and we don't know what's actually going to close. how do we fix this?",
+      "expected_output": "Should trigger on casual phrasing. Should apply the pipeline stage management guidance. Should recommend: define clear pipeline stages with entry/exit criteria, set maximum time in each stage, implement stage velocity tracking, add required fields per stage to force data entry. Should address deal hygiene: regular pipeline reviews, stale deal flagging, win/loss analysis. Should recommend CRM automation to enforce stage rules. Should provide a practical cleanup plan for the current mess.",
+      "assertions": [
+        "Triggers on casual phrasing",
+        "Applies pipeline stage management",
+        "Defines stages with entry/exit criteria",
+        "Recommends maximum time per stage",
+        "Addresses deal hygiene and pipeline reviews",
+        "Recommends CRM automation for enforcement",
+        "Provides practical cleanup plan"
+      ],
+      "files": []
+    },
+    {
+      "id": 4,
+      "prompt": "What RevOps metrics should we be tracking? We want to build a dashboard for our leadership team.",
+      "expected_output": "Should apply the RevOps metrics dashboard framework. Should recommend metrics across the funnel: lead volume by source, MQL-to-SQL conversion rate, SQL-to-Opportunity rate, win rate, average deal size, sales cycle length, pipeline velocity, pipeline coverage ratio, CAC, LTV, LTV:CAC ratio. Should organize metrics by audience (marketing team, sales team, leadership). Should recommend dashboard structure and cadence for reviews.",
+      "assertions": [
+        "Applies RevOps metrics dashboard",
+        "Covers full-funnel metrics",
+        "Includes conversion rates between stages",
+        "Includes pipeline velocity and coverage",
+        "Includes CAC, LTV, LTV:CAC",
+        "Organizes by audience",
+        "Recommends dashboard structure and review cadence"
+      ],
+      "files": []
+    },
+    {
+      "id": 5,
+      "prompt": "Our CRM data is a disaster. Duplicate records, missing fields, inconsistent naming. How do we clean it up and keep it clean?",
+      "expected_output": "Should apply the data hygiene guidance. Should recommend: duplicate detection and merging strategy, required field enforcement, standardized naming conventions (picklists over free text), data validation rules, regular audit cadence. Should address both cleanup (one-time fix) and prevention (ongoing processes). Should recommend CRM automation for data hygiene. Should provide a prioritized cleanup plan (start with highest-impact data quality issues).",
+      "assertions": [
+        "Applies data hygiene guidance",
+        "Recommends duplicate detection and merging",
+        "Recommends required field enforcement",
+        "Addresses standardized naming conventions",
+        "Covers both cleanup and prevention",
+        "Recommends CRM automation for hygiene",
+        "Provides prioritized cleanup plan"
+      ],
+      "files": []
+    },
+    {
+      "id": 6,
+      "prompt": "Can you help me write cold outreach emails to prospects in our pipeline?",
+      "expected_output": "Should recognize this is a cold email / outbound writing task, not RevOps. Should defer to or cross-reference the cold-email skill for writing outbound prospecting emails. RevOps covers the systems, processes, and data infrastructure — not the actual email content.",
+      "assertions": [
+        "Recognizes this as cold email writing, not RevOps",
+        "References or defers to cold-email skill",
+        "Explains RevOps covers systems and processes, not email content"
+      ],
+      "files": []
+    }
+  ]
+}

package/payload/.agents/skills/revops/references/automation-playbooks.md

@@ -0,0 +1,290 @@
+# Automation Playbooks
+
+Platform-specific workflow recipes for HubSpot, Salesforce, scheduling tools, and cross-tool automation.
+
+## HubSpot Workflow Recipes
+
+### 1. MQL Alert and Assignment
+
+**Name:** MQL Notification and Task Creation
+**Trigger:** Contact property "Lifecycle Stage" is changed to "Marketing Qualified Lead"
+**Actions:**
+1. Rotate contact owner among sales team (round-robin)
+2. Send internal email notification to contact owner with lead context
+3. Create task: "Follow up with [Contact Name]" — due in 4 hours
+4. Send Slack notification to #sales-alerts channel
+5. Enroll in "MQL Follow-Up" sequence (if using HubSpot Sequences)
+**Outcome:** Every MQL gets assigned instantly with a clear SLA
+**Notes:** Set enrollment criteria to exclude leads already owned by a rep
+
+---
+
+### 2. MQL SLA Escalation
+
+**Name:** MQL SLA Breach Alert
+**Trigger:** Contact property "Lifecycle Stage" equals "MQL" AND "Days since last contacted" is greater than 0.5 (12 hours)
+**Actions:**
+1. Send internal email to contact owner: "SLA warning: [Contact Name] has not been contacted"
+2. If still no activity after 24 hours → send alert to sales manager
+3. If still no activity after 48 hours → reassign contact owner via rotation
+4. Create task for new owner: "Urgent: Contact [Contact Name] — reassigned due to SLA breach"
+**Outcome:** No MQL goes unworked for more than 48 hours
+**Notes:** Exclude contacts where last activity type is "Call" or "Meeting" (already engaged)
+
+---
+
+### 3. Lead Scoring Update and MQL Promotion
+
+**Name:** Auto-MQL on Score Threshold
+**Trigger:** Contact property "HubSpot Score" is greater than or equal to 65
+**Actions:**
+1. Set lifecycle stage to "Marketing Qualified Lead"
+2. Set "MQL Date" to current date
+3. Suppress from marketing nurture workflows
+4. Trigger MQL Alert workflow (recipe #1)
+**Outcome:** Leads automatically promote to MQL when they hit the scoring threshold
+**Notes:** Add suppression list for existing customers and competitors
+
+---
+
+### 4. Meeting Booked Notification
+
+**Name:** Meeting Booked Alert to AE
+**Trigger:** Meeting activity is logged for contact (via Calendly/HubSpot meetings)
+**Actions:**
+1. Send internal email to contact owner with meeting details
+2. Update contact property "Last Meeting Booked" to current date
+3. If lifecycle stage is "Lead" → update to "MQL"
+4. Create task: "Prepare for meeting with [Contact Name]" — due 1 hour before meeting
+5. Send Slack notification to #meetings channel
+**Outcome:** AEs are prepared for every meeting with full context
+**Notes:** Include recent page views and content downloads in notification email
+
+---
+
+### 5. Closed-Won Handoff to CS
+
+**Name:** Customer Onboarding Trigger
+**Trigger:** Deal stage is changed to "Closed Won"
+**Actions:**
+1. Update associated contact lifecycle stage to "Customer"
+2. Set "Customer Since" date to current date
+3. Assign contact owner to CS team member (based on segment/territory)
+4. Create task for CS: "Schedule kickoff call with [Company Name]" — due in 2 business days
+5. Enroll contact in "Customer Onboarding" email sequence
+6. Send internal notification to CS manager
+7. Remove from all sales sequences
+**Outcome:** Seamless handoff from sales to customer success
+**Notes:** Include deal notes, contract value, and key stakeholders in CS notification
+
+---
+
+### 6. Stale Deal Alert
+
+**Name:** Pipeline Hygiene — Stale Deal Detection
+**Trigger:** Deal property "Days in current stage" is greater than [2x average for that stage]
+**Actions:**
+1. Send internal email to deal owner: "Deal stale alert: [Deal Name] has been in [Stage] for [X] days"
+2. Create task: "Update or close [Deal Name]" — due in 3 business days
+3. If no update after 7 days → alert sales manager
+4. Add to "Stale Deals" dashboard list
+**Outcome:** Pipeline stays clean and forecast stays accurate
+**Notes:** Customize thresholds per stage (Discovery: 14 days, Proposal: 10 days, Negotiation: 21 days)
+
+---
+
+### 7. Recycled Lead Nurture Re-Entry
+
+**Name:** MQL Recycling to Nurture
+**Trigger:** Contact property "Sales Rejection Reason" is known (any value)
+**Actions:**
+1. Update lifecycle stage to "Recycled"
+2. Reset engagement score to baseline (keep fit score)
+3. Enroll in "Recycled Lead Nurture" sequence (lower frequency)
+4. Set "Recycle Date" to current date
+5. Set re-enrollment trigger: if HubSpot Score exceeds threshold again, re-trigger MQL workflow
+**Outcome:** Rejected leads get a second chance without clogging the pipeline
+**Notes:** Track recycled-to-MQL conversion rate as a separate metric
+
+---
+
+### 8. Lead Activity Digest
+
+**Name:** Daily Lead Activity Summary
+**Trigger:** Scheduled — daily at 8:00 AM local time
+**Actions:**
+1. Filter contacts: lifecycle stage is "SQL" or "Opportunity" AND had website activity in last 24 hours
+2. Send digest email to each contact owner with their leads' activity
+3. Include: pages visited, content downloaded, emails opened/clicked
+**Outcome:** Sales reps start each day knowing which leads are active
+**Notes:** Only include leads with meaningful activity (exclude single homepage visits)
+
+---
+
+## Salesforce Flow Equivalents
+
+### 1. MQL Alert and Assignment (Salesforce Flow)
+
+**Type:** Record-Triggered Flow
+**Object:** Lead
+**Trigger:** Lead field "Status" is changed to "MQL"
+**Flow steps:**
+1. Get Records: Query "Rep Assignment" custom object for next available rep
+2. Update Records: Set Lead Owner to assigned rep
+3. Create Records: Create Task — "Contact MQL: {Lead.Name}" with due date = NOW + 4 hours
+4. Action: Send email alert to new lead owner
+5. Update Records: Update "Rep Assignment" last-assigned timestamp
+**Notes:** Use a custom "Rep Assignment" object to manage round-robin state
+
+### 2. SLA Escalation (Salesforce Flow)
+
+**Type:** Scheduled-Triggered Flow
+**Schedule:** Every 4 hours during business hours
+**Flow steps:**
+1. Get Records: Leads where Status = "MQL" AND LastActivityDate < TODAY - 1
+2. Decision: Is lead older than 48 hours with no activity?
+   - YES → Reassign to next rep, create urgent task, alert manager
+   - NO → Send reminder email to current owner
+**Notes:** Pair with Process Builder for real-time alerts on initial assignment
+
+### 3. Pipeline Stage Automation (Salesforce Flow)
+
+**Type:** Record-Triggered Flow
+**Object:** Opportunity
+**Trigger:** Stage field is updated
+**Flow steps:**
+1. Decision: Which stage was it changed to?
+2. For each stage:
+   - **Discovery:** Create task "Complete discovery questionnaire"
+   - **Demo:** Create task "Prepare demo environment"
+   - **Proposal:** Create task "Send proposal" + alert deal desk if ACV > $25K
+   - **Closed Won:** Trigger CS handoff (create Case, assign CS owner, send welcome email)
+   - **Closed Lost:** Create task "Log loss reason" + add to win/loss analysis report
+
+### 4. Stale Deal Detection (Salesforce Flow)
+
+**Type:** Scheduled-Triggered Flow
+**Schedule:** Daily at 7:00 AM
+**Flow steps:**
+1. Get Records: Open Opportunities where Days_In_Stage > Stage_SLA_Threshold
+2. Loop through results:
+   - Create Task: "Update stale deal: {Opportunity.Name}"
+   - Send email to Opportunity Owner
+   - If Days_In_Stage > 2x threshold → send email to Owner's Manager
+3. Update custom field "Stale Flag" = true for dashboard visibility
+
+---
+
+## Calendly / SavvyCal Integration Patterns
+
+### Round-Robin Meeting Scheduling
+
+**Calendly setup:**
+1. Create a team event type with all eligible reps
+2. Distribution: "Optimize for equal distribution"
+3. Availability: Each rep manages their own calendar
+4. Buffer: 15 min before and after meetings
+5. Minimum notice: 4 hours (avoid last-minute bookings)
+
+**CRM integration:**
+1. Calendly webhook fires on booking
+2. Match invitee email to CRM contact
+3. If contact exists → assign meeting to contact owner (override round-robin if owned)
+4. If new contact → create lead, assign via routing rules, log meeting
+5. Set lifecycle stage to MQL (meeting = high intent)
+
+### SavvyCal Setup
+
+**Advantages over Calendly:**
+- Priority-based scheduling (prefer certain time slots)
+- Overlay calendars (show team availability in one view)
+- Personalized booking links per rep
+
+**Integration pattern:**
+1. Create team scheduling link with priority rules
+2. Webhook on booking → Zapier/Make → CRM
+3. Match or create contact, assign owner, create task
+4. Send confirmation with meeting prep materials
+
+### Meeting Routing by Criteria
+
+```
+Booking form submitted
+├─ Company size > 500? (form field)
+│  ├─ YES → Route to enterprise AE calendar
+│  └─ NO ↓
+├─ Existing customer? (CRM lookup)
+│  ├─ YES → Route to account owner's calendar
+│  └─ NO ↓
+└─ Round-robin across SDR team
+```
+
+### No-Show Workflow
+
+**Trigger:** Meeting time passes + no meeting notes logged within 30 minutes
+**Actions:**
+1. Wait 30 minutes after scheduled meeting time
+2. Check: Was a call or meeting logged?
+   - YES → No action
+   - NO → Send "Sorry we missed you" email to prospect
+3. Create task: "Reschedule with [Contact Name]" — due next business day
+4. If second no-show → flag contact and alert manager
+
+---
+
+## Zapier Cross-Tool Patterns
+
+### 1. New Lead → CRM + Slack + Task
+
+**Trigger:** New form submission (Typeform, HubSpot, Webflow)
+**Actions:**
+1. Create/update contact in CRM
+2. Enrich with Clearbit (if available)
+3. Post to Slack #new-leads with enriched data
+4. Create task in project management tool (Asana, Linear)
+
+### 2. Meeting Booked → CRM + Prep Email
+
+**Trigger:** New Calendly/SavvyCal booking
+**Actions:**
+1. Find or create CRM contact
+2. Update lifecycle stage to MQL
+3. Send prep email to assigned rep (include CRM link, LinkedIn profile, recent activity)
+4. Create pre-meeting task
+
+### 3. Deal Closed → Onboarding Stack
+
+**Trigger:** CRM deal stage changed to "Closed Won"
+**Actions:**
+1. Create customer record in CS tool (Vitally, Gainsight, ChurnZero)
+2. Add to onboarding project template
+3. Send welcome email via email tool
+4. Create Slack channel: #customer-[company-name]
+5. Notify CS team in Slack
+
+### 4. Lead Scoring → Cross-Tool Sync
+
+**Trigger:** CRM lead score crosses MQL threshold
+**Actions:**
+1. Update marketing automation platform status
+2. Add to retargeting audience (Facebook, Google Ads)
+3. Trigger SDR outreach sequence
+4. Log event in analytics (Mixpanel, Amplitude)
+
+### 5. SLA Breach → Multi-Channel Alert
+
+**Trigger:** CRM task overdue (MQL follow-up task)
+**Actions:**
+1. Send Slack DM to rep
+2. Send email to rep
+3. If 2+ hours overdue → Slack DM to manager
+4. If 4+ hours overdue → reassign in CRM (via webhook back to CRM)
+
+### 6. Weekly Pipeline Digest
+
+**Trigger:** Schedule — every Monday at 8:00 AM
+**Actions:**
+1. Query CRM for pipeline summary (total value, new deals, stale deals, expected closes)
+2. Format as summary
+3. Post to Slack #sales-team
+4. Send email digest to sales leadership

package/payload/.agents/skills/revops/references/lifecycle-definitions.md

@@ -0,0 +1,278 @@
+# Lifecycle Stage Definitions
+
+Complete templates for lead lifecycle stages, MQL criteria by business type, SLAs, and rejection/recycling workflows.
+
+## Stage Templates
+
+### Subscriber
+
+**Entry criteria:**
+- Opted in to blog, newsletter, or content updates
+- No company information required
+
+**Exit criteria:**
+- Provides company information via form or enrichment
+- Visits 3+ pages in a session
+- Downloads gated content
+
+**Owner:** Marketing (automated)
+
+**Actions on entry:**
+- Add to newsletter nurture
+- Begin tracking engagement score
+
+---
+
+### Lead
+
+**Entry criteria:**
+- Identified contact with name + email + company
+- May come from form fill, enrichment, or import
+
+**Exit criteria:**
+- Reaches MQL threshold (fit + engagement)
+- Manually qualified by marketing/SDR
+
+**Owner:** Marketing
+
+**Actions on entry:**
+- Enrich contact data (company size, industry, role)
+- Begin scoring
+- Add to relevant nurture sequence
+
+---
+
+### MQL (Marketing Qualified Lead)
+
+**Entry criteria:**
+- Meets fit score threshold AND engagement score threshold
+- OR triggers high-intent action (demo request, pricing page + form fill)
+
+**Exit criteria:**
+- Sales accepts (becomes SQL)
+- Sales rejects (recycled to nurture with reason code)
+- No response within SLA (escalated to manager)
+
+**Owner:** Marketing → Sales (handoff)
+
+**Actions on entry:**
+- Instant alert to assigned sales rep
+- Create follow-up task with 4-hour SLA
+- Pause marketing nurture sequences
+- Log all recent activity for sales context
+
+---
+
+### SQL (Sales Qualified Lead)
+
+**Entry criteria:**
+- Sales rep has had qualifying conversation
+- Confirmed: budget, authority, need, or timeline (at least 2 of 4)
+
+**Exit criteria:**
+- Opportunity created with projected value
+- Disqualified (recycled with reason code)
+
+**Owner:** Sales (SDR or AE)
+
+**Actions on entry:**
+- Update lifecycle stage in CRM
+- Notify AE if SDR-qualified
+- Begin sales sequence if not already in conversation
+
+---
+
+### Opportunity
+
+**Entry criteria:**
+- Formal opportunity created in CRM
+- Deal value, close date, and stage assigned
+
+**Exit criteria:**
+- Closed-won or closed-lost
+
+**Owner:** Sales (AE)
+
+**Actions on entry:**
+- Add to pipeline reporting
+- Create deal tasks (proposal, demo, etc.)
+- Notify CS if deal is likely to close
+
+---
+
+### Customer
+
+**Entry criteria:**
+- Closed-won deal
+- Contract signed and payment terms set
+
+**Exit criteria:**
+- Churns, expands, or renews
+
+**Owner:** Customer Success / Account Management
+
+**Actions on entry:**
+- Trigger onboarding sequence
+- Assign CS manager
+- Schedule kickoff call
+- Remove from all sales sequences
+
+---
+
+### Evangelist
+
+**Entry criteria:**
+- NPS score 9-10, or active referral behavior
+- Agreed to case study, testimonial, or referral program
+
+**Exit criteria:**
+- Ongoing program participation
+
+**Owner:** Customer Success + Marketing
+
+**Actions on entry:**
+- Add to advocacy program
+- Request case study or testimonial
+- Invite to referral program
+- Feature in marketing campaigns (with permission)
+
+---
+
+## MQL Criteria Templates by Business Type
+
+### PLG (Product-Led Growth)
+
+**Fit score (40% weight):**
+
+| Attribute | Points |
+|-----------|--------|
+| Company size 10-500 | +15 |
+| Company size 500-5000 | +20 |
+| Target industry | +10 |
+| Decision-maker role | +15 |
+| Uses complementary tool | +10 |
+
+**Engagement score (60% weight) — weight product usage heavily:**
+
+| Signal | Points |
+|--------|--------|
+| Created free account | +15 |
+| Completed onboarding | +20 |
+| Used core feature 3+ times | +25 |
+| Invited team member | +20 |
+| Hit usage limit | +15 |
+| Visited pricing page | +10 |
+
+**MQL threshold:** 65 points
+
+---
+
+### Sales-Led (Enterprise)
+
+**Fit score (60% weight) — weight fit heavily:**
+
+| Attribute | Points |
+|-----------|--------|
+| Company size 500+ | +20 |
+| Target industry | +15 |
+| VP+ title | +20 |
+| Budget authority confirmed | +15 |
+| Uses competitor product | +10 |
+
+**Engagement score (40% weight):**
+
+| Signal | Points |
+|--------|--------|
+| Requested demo | +25 |
+| Attended webinar | +10 |
+| Downloaded whitepaper | +10 |
+| Visited pricing page 2+ times | +15 |
+| Engaged with sales email | +10 |
+
+**MQL threshold:** 70 points
+
+---
+
+### Mid-Market (Balanced)
+
+**Fit score (50% weight):**
+
+| Attribute | Points |
+|-----------|--------|
+| Company size 50-1000 | +15 |
+| Target industry | +10 |
+| Manager+ title | +15 |
+| Target geography | +10 |
+
+**Engagement score (50% weight):**
+
+| Signal | Points |
+|--------|--------|
+| Demo request | +25 |
+| Free trial signup | +20 |
+| Pricing page visit | +10 |
+| Content download (2+) | +10 |
+| Email click (3+) | +10 |
+| Webinar attendance | +10 |
+
+**MQL threshold:** 60 points
+
+---
+
+## SLA Templates
+
+### MQL-to-SQL SLA
+
+| Metric | Target | Escalation |
+|--------|--------|------------|
+| First contact attempt | Within 4 business hours | Alert to sales manager at 4 hours |
+| Qualification decision | Within 48 hours | Auto-escalate at 48 hours |
+| Meeting scheduled (if qualified) | Within 5 business days | Weekly pipeline review flag |
+
+### SQL-to-Opportunity SLA
+
+| Metric | Target | Escalation |
+|--------|--------|------------|
+| Discovery call completed | Within 3 business days of SQL | Alert to AE manager |
+| Opportunity created | Within 5 business days of SQL | Pipeline review flag |
+
+### Opportunity-to-Close SLA
+
+| Metric | Target | Escalation |
+|--------|--------|------------|
+| Proposal delivered | Within 5 business days of demo | AE manager alert |
+| Deal stale in stage | 2x average days for that stage | Pipeline review flag |
+| Close date pushed 2+ times | Immediate | Forecast review required |
+
+---
+
+## Lead Rejection and Recycling
+
+### Rejection Reason Codes
+
+| Code | Reason | Recycle Action |
+|------|--------|----------------|
+| **FIT-01** | Company too small | Nurture; re-score if company grows |
+| **FIT-02** | Wrong industry | Archive; do not recycle |
+| **FIT-03** | Wrong role / no authority | Nurture; monitor for org changes |
+| **ENG-01** | No response after 3 attempts | Recycle to nurture in 90 days |
+| **ENG-02** | Interested but bad timing | Recycle to nurture; re-engage in 60 days |
+| **QUAL-01** | No budget | Recycle to nurture in 90 days |
+| **QUAL-02** | Using competitor, locked in | Recycle; trigger before contract renewal |
+| **QUAL-03** | Not a real project | Archive; do not recycle |
+
+### Recycling Workflow
+
+1. Sales rejects MQL with reason code
+2. CRM updates lifecycle stage to "Recycled"
+3. Lead enters recycling nurture sequence (different from original nurture)
+4. Engagement score resets to baseline (keep fit score)
+5. If lead re-engages and crosses MQL threshold, re-route to sales with "Recycled MQL" flag
+6. Track recycled MQL conversion rate separately
+
+### Recycling Nurture Sequence
+
+- **Frequency:** Bi-weekly or monthly (lower frequency than initial nurture)
+- **Content:** Industry insights, case studies, product updates
+- **Duration:** 6 months, then archive if no engagement
+- **Re-MQL trigger:** High-intent action (demo request, pricing page revisit)