@rubytech/create-maxy-code 0.1.26 → 0.1.27

package/payload/platform/plugins/estate-teaching/skills/content-directory/SKILL.md

@@ -0,0 +1,39 @@
+---
+name: content-directory
+description: "Browse, search, and deliver structured education modules from the Real Agency curriculum."
+---
+
+# Content Directory
+
+Handles curriculum navigation, module delivery, and progress tracking. This is the core learning experience.
+
+## When to Activate
+
+A member asks about available content, wants to learn something, requests a specific module, or asks for a recommendation. Also activates when a member returns and wants to continue where they left off.
+
+## Reference Table
+
+| Task | When | Reference |
+|------|------|-----------|
+| Module delivery | Member requests a specific topic or module | `references/module-delivery.md` |
+| Progress tracking | Member asks about progress, or after completing a module | `references/progress-tracking.md` |
+
+## Key Rules
+
+- Deliver content conversationally — don't paste entire modules. Teach through dialogue.
+- Always attribute content to the contributor it came from.
+- Track completion in `memory/users/{phone}/progress.md` after every module.
+- When listing available content, organise by pillar. Keep descriptions concise.
+- If a member asks for content that doesn't exist, say so honestly and note the gap (admin will see it).
+- Modules with `access: member` are gated to paid membership. Check `membership_type` in the member's profile before delivering.
+
+## Curriculum Pillars
+
+| Pillar | Focus | Typical Member Need |
+|--------|-------|-------------------|
+| Agency Blueprint | Setting up and structuring an agency | New agents, career changers |
+| Real Marketing | Social media, content creation, personal brand | Brand builders, content creators |
+| Real Business | Systems, structure, profit, scaling | Growth-stage agents |
+| Real Coaching | Mindset, performance (Backley & Black) | Anyone wanting mental edge |
+| Podcast | Conversations with working agents | Inspiration, peer learning |
+| Resources | Templates, scripts, SOPs, tools | Practical application |

package/payload/platform/plugins/estate-teaching/skills/content-directory/references/module-delivery.md

@@ -0,0 +1,65 @@
+# Module Delivery
+
+## Purpose
+
+Deliver curriculum modules as interactive coaching conversations, not static content dumps.
+
+## Context to Gather
+
+Before delivering a module:
+1. **What the member asked for** — specific topic, or browsing?
+2. **Their profile context** — career stage, goals, current challenges (from `memory/users/{phone}/profile.md`)
+3. **Their progress** — what they've already completed (from `memory/users/{phone}/progress.md`)
+
+## Where to Search
+
+Search `memory/public/courses/{pillar}/` for module files. Each module is a markdown file with frontmatter:
+
+```yaml
+---
+title: Module Title
+contributor: Contributor Name
+pillar: pillar-name
+estimated_time: X minutes
+access: free
+video: https://pinata-url (optional)
+---
+```
+
+If the member asks for a topic without specifying a module, search across all pillars for the best match.
+
+## How to Deliver
+
+**Never paste the full module.** Teach through conversation:
+
+1. **Introduce** — What the module covers, who it's from, why it matters for this member specifically. Reference their profile context.
+
+2. **Teach the core concept** — Present the key insight or framework. Use the contributor's voice and perspective. "Adam's approach to this is..." or "Steve Backley's framework here is..."
+
+3. **Check understanding** — Ask the member to reflect. "How does this compare to how you currently handle...?" or "What would that look like for your patch?"
+
+4. **Go deeper** — Based on their response, expand on the areas they find most relevant. Skip parts that don't apply to their situation.
+
+5. **Offer the video** — If the module has a video link, offer it at the right moment: "Adam walks through a real example of this — want to watch it?" Don't force it.
+
+6. **Reflection questions** — After the core teaching, offer 2-3 reflection questions that help them apply the concept to their own business.
+
+7. **Bridge to next** — Recommend a logical next module or ask if they want to continue in this pillar.
+
+## Pacing
+
+Don't rush. One concept at a time. Wait for the member to respond before moving to the next section. If they engage deeply with one part, stay there — depth beats breadth.
+
+If a module is long, break it across multiple exchanges. The member controls the pace — "Want to continue?" or "Take your time, I'll be here."
+
+## When Content Doesn't Exist
+
+If a member asks for something not in the curriculum:
+1. Acknowledge the gap honestly: "We don't have a specific module on that yet."
+2. Search memory for anything adjacent that might help.
+3. If nothing exists, note it: "I'll flag this as something the team should consider adding."
+4. Write a brief note to `memory/admin/` so the admin agent can surface it.
+
+## Tone
+
+Expert tutor, not lecturer. You're walking alongside the member through the material, not reading it to them. React to their responses. Build on their experience. Make it personal.

package/payload/platform/plugins/estate-teaching/skills/content-directory/references/progress-tracking.md

@@ -0,0 +1,47 @@
+# Progress Tracking
+
+## Purpose
+
+Maintain an accurate record of each member's learning journey and use it to drive personalised recommendations.
+
+## When to Update Progress
+
+Update `memory/users/{phone}/progress.md` after:
+- A member completes a module (all key concepts covered, reflection done)
+- A coaching session ends
+- A member explicitly asks to bookmark or skip a module
+- You learn something new about their goals or focus area
+
+## What to Record
+
+### Module Completion
+Add to the "Modules Completed" section:
+```
+- [YYYY-MM-DD] {pillar} / {module title}
+```
+
+### Current Focus
+Update the "Current Focus" field when the member shifts topics or starts a new learning path.
+
+### Notes
+Record anything that helps personalise future interactions:
+- Topics they found most valuable
+- Areas they struggled with
+- Specific business context they shared (their patch, their agency focus, their brand positioning)
+
+## How to Use Progress Data
+
+**For recommendations:** Check which pillars they've explored and which they haven't. Suggest unexplored pillars that match their goals. Don't repeat modules they've completed.
+
+**For returning members:** When a member comes back after a gap, check their progress and reference it: "Last time we covered {topic}. Want to continue from there, or is there something new on your mind?"
+
+**For coaching:** Progress data tells you what frameworks the member already knows. In coaching mode, you can reference: "Remember Adam's three questions from the listing presentation module? Apply that here."
+
+## When Members Ask About Progress
+
+Summarise their journey conversationally:
+- How many modules completed, across which pillars
+- Their current focus area
+- Suggested next steps based on goals and gaps
+
+Don't present progress as a report — frame it as a conversation about their journey.

package/payload/platform/plugins/leads/.claude-plugin/plugin.json

@@ -0,0 +1,8 @@
+{
+  "name": "real-agency-leads",
+  "description": "Daily morning round and lead-pipeline skills for UK residential sales agents. Composes diary, awaiting-reply, overnight-enquiry triage, and stalled-deal surfacing into one snapshot, plus the chain-progression-tracker shared with chase-progression.",
+  "version": "0.1.0",
+  "author": {
+    "name": "Rubytech LLC"
+  }
+}

package/payload/platform/plugins/leads/PLUGIN.md

@@ -0,0 +1,62 @@
+---
+name: real-agency-leads
+description: "Daily morning round and lead-pipeline skills for UK residential sales agents. Composes diary, awaiting-reply, overnight-enquiry triage, and stalled-deal surfacing into one snapshot, plus the chain-progression-tracker shared with chase-progression."
+tools: []
+skills:
+  - skills/morning-round/SKILL.md
+  - skills/diary-builder/SKILL.md
+  - skills/enquiry-triage/SKILL.md
+  - skills/chain-progression-tracker/SKILL.md
+  - skills/lead-nurturing/SKILL.md
+  - skills/prospecting/SKILL.md
+profileKeys:
+  - realagent.awaiting_reply_lookback_days
+  - realagent.cause_phrases
+  - realagent.diary.postcode_ordering
+  - realagent.diary.show_internal_events
+  - realagent.enquiry_triage.source_weights
+  - realagent.enquiry_triage.spam_phrases
+  - realagent.morning_round.delivery_channel
+  - realagent.morning_round.delivery_time
+  - realagent.morning_round.hidden_sections
+  - realagent.morning_round.section_order
+  - realagent.stalled_threshold_days.broker
+  - realagent.stalled_threshold_days.buyer
+  - realagent.stalled_threshold_days.solicitor
+  - realagent.stalled_threshold_days.surveyor
+  - realagent.stalled_threshold_days.vendor
+always: false
+metadata: {"platform":{"optional":true,"embed":["admin"]}}
+---
+
+# Real Agency, Lead Generation and Morning Round
+
+Six skills: four covering the daily morning round (master plus building blocks) and two covering longer-horizon lead nurturing and prospecting.
+
+## When to Activate
+
+The user is asking for the morning round, the daily brief, the day's diary, overnight enquiries, or anything stalled. Also activates when the user is working on lead nurturing, follow-up cadences, database reactivation campaigns, prospecting activities, or outreach strategies.
+
+## Skills
+
+| Skill | Owner specialist | Purpose |
+|-------|------------------|---------|
+| `morning-round` | negotiator | The daily one-page snapshot: diary, awaiting replies, overnight enquiries, stalled deals, top three |
+| `diary-builder` | negotiator | Today's diary block for the morning round |
+| `enquiry-triage` | negotiator | Triages overnight portal and email enquiries |
+| `chain-progression-tracker` | negotiator | State-of-the-chain view; used by morning round and chase-progression |
+| `lead-nurturing` | negotiator | Systematic follow-up and pipeline warming |
+| `prospecting` | negotiator | Database reactivation, lead generation, campaign chaining |
+
+## Tools Used
+
+No MCP server. Skills operate via existing platform tools:
+
+- `memory-search` to retrieve domain knowledge from the knowledge base
+- `render-component` to present structured choices during interactions
+- `profile-read` and `profile-update` for the customisation profile
+- `task-create` to file an open task when a chase needs deferring
+
+## References
+
+Domain knowledge files loaded on demand by each skill. See individual skill files for their specific reference listings.

package/payload/platform/plugins/leads/skills/chain-progression-tracker/SKILL.md

@@ -0,0 +1,51 @@
+---
+name: chain-progression-tracker
+description: "Build the state-of-the-chain view for a sale-agreed deal. Identifies stalled deals across the pipeline for the morning round, and produces a single-deal deep dive when the chase-progression workflow expands one. Read-only; never sends anything."
+---
+
+# Chain progression tracker
+
+A building-block skill used by two workflows. The morning round calls it for the across-pipeline stalled view. The chase-progression workflow calls it for the single-deal deep dive.
+
+## Two modes
+
+### Across-pipeline mode
+
+Used by `morning-round`. Returns every sale-agreed deal where nothing has moved past the stalled threshold for the relevant stakeholder type. For each, returns:
+
+- Property address
+- Days since the last positive movement
+- The most likely cause from chain state, expressed as one short sentence
+
+The stalled threshold is read from the profile, per stakeholder type. Default 7 days for everyone; learns per type.
+
+### Single-deal deep-dive mode
+
+Used by `chase-progression`. Given a property the operator named, returns:
+
+- Every party in the chain with their role
+- Last known status for each party
+- Every outstanding action with the responsible party
+- Every risk flag (offer expiry approaching, searches outstanding, survey booked but not done, vendor or buyer disengagement signals, chain complexity, onward-purchase status)
+- A timeline view of the last 30 days of contact
+
+## What "most likely cause" means
+
+The skill compares the deal state against the typical stalled patterns: solicitor not responding, mortgage offer expiring, survey scheduled but not completed, search results outstanding, vendor unresponsive, buyer unresponsive, chain party upstream unresponsive. The cause sentence is the pattern that best fits the observable signals, written by `variance-narrator`.
+
+The skill never invents a cause it cannot trace to data. If no pattern fits, the cause line says "no clear cause from connectors, manual check recommended".
+
+## What it does not do
+
+- It does not compute the fall-through risk score. That is `risk-scorer`, called separately by `chase-progression`.
+- It does not draft messages. Draft messages come from `tone-matched-drafter`.
+- It does not write to the CRM.
+
+## Connectors
+
+Read: CRM, email, WhatsApp, calendar, mortgage offer expiry data if held in CRM. No writes.
+
+## Profile keys
+
+- `realagent.stalled_threshold_days.*` (per stakeholder type)
+- `realagent.cause_phrases` (preferred cause phrasings, learned from edits)

package/payload/platform/plugins/leads/skills/diary-builder/SKILL.md

@@ -0,0 +1,38 @@
+---
+name: diary-builder
+description: "Produce the today's diary block for the morning round. Reads the calendar and the CRM to surface every viewing, valuation, market appraisal, vendor meeting, and completion call for today, with times, addresses, contact, and postcode."
+---
+
+# Diary builder
+
+A building-block skill the operator never names. Called by `morning-round` to build the diary block of the daily snapshot.
+
+## What it does
+
+Reads today's calendar entries from the connected calendar (M365 or Google). For each entry it correlates the CRM record so that the line shows the right contact and the property context, not just a calendar title. Items not tied to a CRM record still appear, marked as "calendar entry, no CRM match".
+
+## Output shape
+
+A list, one line per entry, sorted by start time. Each line shows:
+
+- Start time and duration
+- Activity type: viewing, valuation, market appraisal, vendor meeting, completion call, other
+- Address with postcode
+- Contact name and role (vendor, buyer, applicant)
+
+If the order of addresses by postcode is not geographically sensible, a one-line note flags it so the operator can resequence before they leave the office.
+
+## What it does not do
+
+- It does not produce the prep pack for any valuation in the diary. That is `valuation-prep`, which the operator invokes after reading the diary.
+- It does not chase anyone. The diary is read-only output.
+- It does not modify the calendar.
+
+## Connectors
+
+Read: calendar, CRM. No writes.
+
+## Profile keys
+
+- `realagent.diary.postcode_ordering` (boolean, default true)
+- `realagent.diary.show_internal_events` (boolean, default false)

package/payload/platform/plugins/leads/skills/enquiry-triage/SKILL.md

@@ -0,0 +1,36 @@
+---
+name: enquiry-triage
+description: "Classify overnight portal and email enquiries into hot, lukewarm, cold, duplicate, or spam. Built for use inside the morning round; the operator does not invoke it directly."
+---
+
+# Enquiry triage
+
+A building-block skill called by `morning-round`. Takes the new portal and email enquiries since the last round and assigns each one a triage tag.
+
+## What hot, lukewarm, cold, duplicate, and spam mean
+
+- **Hot.** The enquirer named a price range and a timeline, or asked to book a viewing, or referenced a specific property and confirmed they are a proceedable buyer. Hot enquiries appear verbatim in the round so the operator can act on them without re-reading the source.
+- **Lukewarm.** The enquirer asked about a property without naming budget, timeline, or position. The round shows a one-line summary.
+- **Cold.** Generic enquiry with no specifics. One-line summary in the round.
+- **Duplicate.** Matches a previous enquiry by phone, email, or named buyer in the last 30 days. One-line summary referencing the prior contact.
+- **Spam.** Off-topic, lead-broker, or otherwise non-buyer traffic. One-line summary so the operator can confirm the call.
+
+## Triage signals
+
+For each enquiry, the skill considers: source (Rightmove, Zoopla, OnTheMarket, agency website, direct email, WhatsApp), the literal text of the enquiry, the contact details supplied, the CRM history of the same contact, and the property the enquiry refers to.
+
+The decision is the LLM's, not a regex. Classification quality improves as the profile learns from skip patterns (see learning hooks in `morning-round`).
+
+## What it does not do
+
+- It does not reply to enquiries. Reply drafting is `tone-matched-drafter`, invoked from a chase or new-instruction workflow.
+- It does not write to the CRM. The enquiry record itself lives in the portal or the email connector; this skill only reads.
+
+## Connectors
+
+Read: portal feeds (Rightmove, Zoopla, OnTheMarket), email, WhatsApp, CRM. No writes.
+
+## Profile keys
+
+- `realagent.enquiry_triage.source_weights` (map of source to weight, learned)
+- `realagent.enquiry_triage.spam_phrases` (list of phrases the operator has flagged as spam, learned)

package/payload/platform/plugins/leads/skills/lead-nurturing/SKILL.md

@@ -0,0 +1,137 @@
+---
+name: lead-nurturing-v2
+description: "Systematic follow-up and pipeline warming. Adds Serhant Three F's, HOT/WARM/COLD cadence, and value-led touches."
+---
+
+# Lead Nurturing (v2)
+
+Most deals don't close on first contact. Your job is to keep trust and momentum alive until the prospect is ready.
+
+## Three rules
+
+1. **Speed wins first contact.** Respond immediately.
+2. **Never "just checking in".** Lead with value every time.
+3. **Follow up until yes/no.** Silence isn't rejection.
+
+## What nurturing is not
+
+- daily spam
+- guilt-tripping
+- chasing after an explicit "no"
+
+## Operating system (UK estate agency)
+
+When the user asks for help nurturing leads (buyers, sellers, past appraisals, former clients, neighbours, landlords):
+
+1. **Clarify category** (buyer / seller / landlord / past client / SOI / cold database)
+2. **Clarify temperature** (HOT/WARM/COLD) and time sensitivity
+3. **Choose a cadence** (Serhant HOT/WARM/COLD + Keller 33 Touch overlay)
+4. **Choose a channel mix** (call, SMS, email, letter, social touch)
+5. **Every message must contain value** (insight, update, proof, next step)
+6. **Always propose a next action** (call, viewing, valuation, mortgage chat, solicitor intro)
+
+## Core frameworks to use
+
+### 1) Serhant HOT/WARM/COLD cadence (base layer)
+- **HOT:** daily
+- **WARM:** weekly
+- **COLD:** monthly
+
+Use this as the default rhythm unless the user specifies a different standard.
+
+### 2) Keller "33 Touch" system (relationship layer)
+Use 33 meaningful touches per year to stay top-of-mind with your Sphere of Influence (SOI), past clients and nurtured prospects.
+
+Typical mix (adapt to UK channels and compliance):
+- **12 personal calls** (quick check-in + value)
+- **12 pieces of value content** (email newsletter, market update, "what your home could be worth", "buyer demand snapshot")
+- **9 events/gifts/experiences** (client nights, local coffee voucher, handwritten card, charity/community touch)
+
+Principle: people choose the agent they remember.
+
+### 3) Sharran "10x10x10" daily method (daily discipline)
+Use a simple daily prospecting/nurture routine:
+- **10 outbound conversations** (calls or voice notes)
+- **10 follow-ups** (SMS/email to existing leads)
+- **10 relationship touches** (comment/DM/reply to stories; handwritten note; referral thank you)
+
+If the user has their own exact definition of 10x10x10, ask for it and then follow their version.
+
+### 4) Firewave nurture (content + funnels)
+Use a *subscriber briber* (lead magnet) + **email nurture sequence** to move contacts through:
+**KNOW → LIKE → TRUST → TRY (valuation) → BUY (instruction)**
+
+## Channel playbooks and templates
+
+### Tom Panos: SMS templates (buyers/sellers/prospecting)
+Use short, calm, confident texts. Never needy. Avoid "just checking in".
+
+Use templates in `references/tom-panos-sms-templates.md`.
+
+### Tom Panos / Real Estate Gym: OFI follow-up (Saturday afternoon)
+Call and qualify right after open homes (or same day). Use the OFI follow-up dialogue in `references/ofi-follow-up-dialogue.md`.
+
+### Neighbour notification letters (sold / sale agreed / new to market)
+Use letters to turn activity into authority and referrals. Templates in:
+- `references/neighbour-notification-letter.md`
+
+### Buyer search ("home wanted") letters
+Use targeted letters when a buyer has missed out or you have demand exceeding supply. Template in:
+- `references/buyer-search-letter.md`
+
+### Database reactivation
+For old leads/past appraisals/ghosted contacts, run a respectful reactivation campaign:
+- quick reintroduce + market update + clear opt-out
+- ask a simple question to prompt reply ("Still thinking of moving in 2026?")
+Template + cadence in `references/database-reactivation.md`.
+
+## Firewave email nurture sequences (ready-to-use)
+
+Use sequences in `references/firewave-email-nurture-sequences.md`.
+
+Rules:
+- lead with advice, not "book a valuation"
+- one CTA per email
+- always include a soft reply CTA ("Reply with your postcode and I'll send a price snapshot")
+
+## Sphere of Influence methodology (SOI)
+
+Use SOI as an intentional system:
+- segment sphere (inner circle / community / network / audience / strangers)
+- increase engagement frequency with the highest-value relationships
+- bring value first, ask second
+
+Use the Serhant SOI audit prompts in `references/sphere-of-influence-notes.md`.
+
+## What to do when the user asks "what should I say?"
+
+Ask 3 questions, then write the message:
+1. Who is this person and what's the relationship?
+2. What do we want them to do next?
+3. What's the *value* we can lead with today?
+
+Then provide:
+- 1 SMS version
+- 1 email version
+- 1 call opener + 3 questions
+
+## After each interaction
+
+Encourage the user to capture:
+- outcome (yes/no/next step)
+- temperature update
+- next follow-up date
+- notes (kids, job, motivation, timelines)
+
+## References (load as needed)
+
+- **Serhant Three F's** → `references/serhant-three-fs-plus.md`
+- **Keller 33 Touch** → `references/keller-33-touch.md`
+- **Sharran 10x10x10** → `references/sharran-10x10x10.md`
+- **Tom Panos SMS templates** → `references/tom-panos-sms-templates.md`
+- **OFI follow-up dialogue** → `references/ofi-follow-up-dialogue.md`
+- **Firewave email nurture sequences** → `references/firewave-email-nurture-sequences.md`
+- **Sphere of Influence notes (Serhant)** → `references/sphere-of-influence-notes.md`
+- **Neighbour notification letter** → `references/neighbour-notification-letter.md`
+- **Buyer search letter** → `references/buyer-search-letter.md`
+- **Database reactivation** → `references/database-reactivation.md`

package/payload/platform/plugins/leads/skills/lead-nurturing/references/buyer-search-letter.md

@@ -0,0 +1,28 @@
+# Buyer search (“home wanted”) letter (template)
+
+Dear Homeowner,
+
+I hope this letter finds you well. My name is <name> and I’m reaching out because I’m currently working with a genuine buyer who has missed out on available properties in your area.
+
+We’ve exhausted the current listings and made a commitment to our client: to go above and beyond in helping them find the right home — even if that means contacting homeowners directly.
+
+Our buyer is looking specifically for:
+- Location: <estate/road/postcode>
+- Property type: <detached/semi/period/etc>
+- Key needs: <e.g. parking/garden/school catchment>
+
+They are flexible on timing and realistic on price depending on condition and position.
+
+If you have considered selling (or even renting), we’d love the chance to have a confidential conversation.
+
+Please feel free to text me directly on <mobile>.
+
+Warm regards,
+
+<name>
+<agency>
+<mobile>
+
+## Notes
+- Make it specific (estate/road) to avoid “blanket letter” feel.
+- Keep it respectful and confidential.

package/payload/platform/plugins/leads/skills/lead-nurturing/references/buyer-search-letters.md

@@ -0,0 +1,37 @@
+# Buyer Search Letters
+
+Direct outreach letters sent to homeowners on behalf of a specific buyer. Highly effective because they feel personal and genuine.
+
+## Template 1 — Family Relocation
+> Dear Homeowner,
+>
+> We are currently working with a long-term private client planning their next move to [area]. We have exhausted all available listings on the market so we promised our clients that we would contact every homeowner in [area] to find the perfect home.
+>
+> They are a wonderful family with [details], looking to move here from [location]. They have identified [area] specifically due to their interest in [features].
+>
+> They are flexible with timing and open to pricing, depending on the location and condition of the home.
+>
+> We promised our clients we would contact every homeowner, so if you would consider selling or renting your home please contact us immediately.
+>
+> [Agent name and number]
+
+## Template 2 — Specific Buyer With History
+> Dear Homeowner,
+>
+> My name is [name] and I'm reaching out on behalf of a wonderful couple I'm currently working with. We've thoroughly exhausted all available listings on the market and made a commitment to our clients: to go above and beyond in helping them find the right home — even if it means contacting every homeowner in [estate/area].
+>
+> [Buyer details and backstory — e.g. they were the underbidder on a recent sale]
+>
+> This is not a blanket search — it's about finding the right fit for people who have fallen in love with this location.
+>
+> Whether you've considered selling or even just renting your home, we'd love the chance to have a confidential conversation.
+>
+> [Agent name and number]
+
+## Key Principles
+- Always reference a real buyer (never fabricate)
+- Include enough detail to feel genuine
+- Mention flexibility on timing and price
+- Keep the tone warm and respectful
+- Include direct contact details (mobile, not office)
+- Follow up with a phone call 5-7 days after posting

package/payload/platform/plugins/leads/skills/lead-nurturing/references/database-reactivation.md

@@ -0,0 +1,30 @@
+# Database reactivation (old leads / past appraisals / ghosted contacts)
+
+## Goal
+Create replies and restart conversations without awkwardness.
+
+## Rules
+- be respectful
+- offer value
+- make it easy to say “not now”
+- always include opt-out
+
+## 3-message SMS sequence (7 days)
+**Day 1:**
+“Hi <name> — it’s <name> from <agency>. Quick one: I’ve got fresh sold evidence for <area>. Want me to send a quick price snapshot for your road?”
+
+**Day 3:**
+“No rush — if you’re not moving, totally fine. If you are thinking 2026, what’s the one thing that would need to happen for you to make a move?”
+
+**Day 7:**
+“Last one from me — should I keep you on my updates list for <area>, or would you prefer I remove you?”
+
+## Email reactivation (2 emails)
+- Email 1: market update + offer of a bespoke valuation range
+- Email 2: “Are you still considering a move?” + book call
+
+## What to log
+- response
+- updated timeline
+- motivation
+- next follow-up date

package/payload/platform/plugins/leads/skills/lead-nurturing/references/email-nurture-sequences.md

@@ -0,0 +1,45 @@
+# Firewave Email Nurture Sequences
+
+Automated email sequences that move prospects through the customer journey.
+
+## The Customer Journey
+**KNOW → LIKE → TRUST → TRY → BUY**
+
+| Stage | Description |
+|---|---|
+| KNOW | Stranger encounters your content, social media, or letter |
+| LIKE | They take action — download a guide, like a post |
+| TRUST | You have a conversation by email or phone |
+| TRY | They book a valuation |
+| BUY | They instruct you |
+
+## 8-Step Funnel Structure
+1. Set up a landing page offering a digital gift (checklist, guide)
+2. Integrate with email provider (AWeber, Mailchimp, etc.)
+3. Guide is automatically sent to the subscriber
+4. Landing page redirects to a thank you page
+5. Thank you page offers a valuation
+6. Place retargeting pixel for Facebook Ads
+7. Set up email nurture sequence (series of relevant emails)
+8. Add a call to action (CTA) to each email
+
+## Subscriber Briber Ideas
+Specific titles so you learn something about each subscriber:
+- "Moving with a Busy Family"
+- "Selling Your Bungalow"
+- "How to Sell Your Home for the Asking Price in Just 30 Days"
+- "Your Home Moving Checklist"
+- "Planning to Sell? Your Complete Guide to Doing it Right"
+- "What Your Home Is Really Worth in [Area]"
+- "First-Time Buyer's Guide to [Area]"
+
+## Sequence Structure (Example: Seller Lead)
+- **Email 1** (Day 0): Deliver the guide + introduce yourself
+- **Email 2** (Day 3): Share a relevant success story / case study
+- **Email 3** (Day 7): Provide market insight for their area
+- **Email 4** (Day 14): Address common seller concerns
+- **Email 5** (Day 21): Offer a no-obligation valuation
+- **Email 6** (Day 30): Share testimonial + soft CTA
+
+## Key Principle
+If your content doesn't move them from cold to warm, or warm to hot, it's not valuable, relevant, or timely enough.

package/payload/platform/plugins/leads/skills/lead-nurturing/references/facebook-referrals.md

@@ -0,0 +1,30 @@
+# Facebook Referrals — "Referrals on Steroids"
+
+From Tom Panos / Real Estate Gym.
+
+## When to Use
+- At the time of offer acceptance
+- After successful completion
+- When a vendor expresses delight with your service
+
+## Script
+> "Mr & Mrs [Vendor], were you happy with everything?"
+>
+> [If Yes]
+>
+> "The way we get business is by having other vendors talk about us in a positive light. We're big on social media — is it OK if you gave me a one-sentence short testimonial on what you thought of me and my service?"
+>
+> [If Yes]
+>
+> "Can I ask you to also tag me when you post?"
+
+## Why This Is So Effective
+- When the vendor publicly raves about your services, this is often more effective than personal advertising
+- The vendor's friends and your friends/associates will all see the recommendation
+- It's not what you say to the market — it's what the market says to the market about you
+
+## UK Adaptation
+- Works on Facebook, Instagram, Google Reviews
+- Video testimonials are even more powerful
+- Ask: "Would you mind recording a quick 30-second video about your experience?"
+- Share on all platforms with vendor permission