# Estate Seller Lead Generation Research

> Status: source research memo, 2026-06-22. Source is a Paul-provided list of 20 estate-sale-company lead-generation tactics. This is not a plan change by itself; it is input for Research & Discovery, WI-086 (lead-gen CRM-lite), and future TroveSnap/TroveGo marketplace strategy.

## Executive Read

The list reinforces a core TroveSnap thesis: estate-sale companies do not only need faster cataloging. They need a repeatable demand-and-trust machine that turns relationships, listings, buyer traffic, and proof of outcomes into future seller leads.

TroveSnap can facilitate much of this without becoming a full CRM immediately. The near-term wedge is to make every sale easier to publish, share, attribute, and prove. That creates three compounding assets:

1. A better seller-facing operating system: inventory, photos, pricing evidence, reports, source-of-truth status, and post-sale outcomes.
2. A local demand surface: public sale pages, QR check-ins, buyer alerts, and eventually the TroveGo map.
3. A relationship/referral surface: realtor/attorney/senior-transition partner links, source attribution, share kits, and proof packets.

The lead-gen insight is that many channels are not separate products. They are metadata and workflows around the same sale: who referred it, which channel drove buyers, what outcomes happened, which partners should get proof, and which prospects should be nurtured next.

## Source Themes

| Motion | Source tactics | TroveSnap interpretation |
|---|---|---|
| Trusted referral networks | Realtors, probate/estate attorneys, trust officers, funeral homes, hospice, senior communities, movers, antique dealers, other liquidators | Help sellers create professional referral packets, track partner sources, and prove outcomes after each sale. |
| High-intent life-event outreach | Probate leads, downsizing, relocation, real-estate listing prep | Capture lead context, intake constraints, source consent, property timeline, and urgency without turning TroveSnap into a cold-outreach product too early. |
| Digital visibility | Website, local SEO, Google Ads, Google Business Profile, social media, estate-sale directories, email nurture, content/lead magnets | Turn each TroveSnap sale into reusable content: listings, photos, sale recap, buyer traffic, review prompts, lead magnets, and channel attribution. |
| Local/community operating cadence | Personal network, local events, senior expos, direct mail, monthly source tracking | Provide lightweight CRM-lite and reporting: lead source, follow-up cadence, referral thank-you prompts, and monthly channel ROI. |

## What TroveSnap Already Helps With

| Lead-gen need | Current or planned TroveSnap fit | Why it matters |
|---|---|---|
| Professional proof for referrals | Client reports, inventory summaries, provenance, sale outcomes, post-sale reconciliation | Realtors and attorneys refer when they trust execution. A clean after-action packet is sales collateral. |
| Faster sale prep | Vision-assisted capture, bulk ops, room/zone organization, labels, QR identity spine | Faster prep lets sellers accept more jobs and look more professional to referral partners. |
| Better listings and buyer demand | Photo/listing pipeline, marketplace/directory exports, public-safe sale/item pages | Every well-published sale becomes both buyer acquisition and seller proof. |
| Lead-source attribution | Existing event/source philosophy in P5/P8 and the competitive strategy telemetry | TroveSnap can track which partner, directory, QR, email, or social share generated visits, inquiries, or buyers. |
| Local density flywheel | TroveGo map concept, QR check-ins, buyer alerts, local-first launch | Buyer traffic makes seller acquisition easier: "we bring shoppers, not just software." |
| Partner-friendly workflow | POS interop-first, export adapters, one-door ingestion, source_import_records | Estate sellers can keep their existing tools while TroveSnap captures the data exhaust. |
| Low-cost wedge | Flat/low-priced TroveSnap positioning and token-metered premium scans | Harder for incumbents to compete, easier for sellers to trial, and creates downstream data/marketplace leverage. |

## What We Could Add

These are additive product ideas, not immediate sprint changes.

| Integration idea | Supports source tactics | Product shape | First useful version |
|---|---|---|---|
| Referral source tracker | Realtors, attorneys, movers, senior communities, personal network | Add `lead_source`, `referral_partner`, and `campaign` metadata to sales/inquiries; dashboard monthly source performance. | Manual source field + monthly report export. |
| Partner proof packet | Realtors, attorneys, trust officers, funeral homes | One-click PDF/link summarizing sale timeline, inventory count, sell-through, buyer traffic, cleanup/disposition, testimonials. | Sale recap page with shareable partner-safe link. |
| Realtor/attorney intake link | Real-estate listing prep, probate/estate counsel | Partner-specific intake form with property timeline, estate status, access constraints, contents photos, urgency. | Public/private intake form feeding candidate lead records. |
| Referral partner portal | High-ROI partnerships | Partner sees referred lead status at a safe level: received, scheduled, sale live, completed; no private pricing unless allowed. | Read-only referral status page by tokenized link. |
| Lead magnet generator | SEO/content/email nurture | Generate checklists from TroveSnap data: downsizing checklist, probate cleanout prep, what-to-keep/what-to-sell worksheet. | Static downloadable PDFs tied to seller landing pages. |
| Directory publishing kit | EstateSales.net, EstateSales.org, social | Repackage sale listing, photos, dates, terms, highlights, and map copy for each directory/channel. | Export-ready copy blocks + image ZIP. |
| Google Business Profile/social content kit | GBP, Facebook, Instagram | Turn each sale into posts: preview, last-day markdowns, sold highlights, behind-the-scenes transformation, testimonial request. | Copy/image suggestions with channel checklist. |
| QR check-in and buyer growth | Sale signage, buyer installs, TroveGo map | QR codes at sale/signs route buyers to the right app/surface, collect check-ins, enable alerts, and seed future local demand. | Public check-in page before choosing TroveGo vs TroveSnap app routing. |
| Token incentives for listing discovery | Gmail estate-sale shares, buyer map growth | Buyers earn credits/tokens by forwarding/sharing sale announcements from Gmail or public links, subject to consent and anti-spam rules. | Manual "submit a sale" flow with review; Gmail connector later. |
| Appraisal token loop at sales | In-app purchases, buyer engagement | Buyers at a sale scan items for appraisal hints; free quota plus token purchase. Seller gets anonymized demand signals. | Buyer-safe scan/appraisal microflow with clear non-certified disclaimer. |
| Partner cadence reminders | Regular check-ins every 6-8 weeks | CRM-lite reminders for referral partners, thank-you gifts, workshops, and follow-up tasks. | Simple task list tied to partner records. |
| Workshop/event kit | Senior centers, assisted living, community events | Templates for downsizing workshop slides, flyers, sign-in QR, follow-up emails, and attendee lead capture. | Downloadable kit + QR signup page. |

## What We Have Not Thought Through Enough

| Gap | Why it matters | Proposed research question |
|---|---|---|
| Buyer app routing: TroveSnap vs TroveGo | A sale QR can install either app. If TroveSnap becomes buyer-facing too early, it may blur TroveGo. If TroveGo is too early, seller workflow may fragment. | For check-in/appraisal/map use cases, what is the minimum shared identity/deep-link layer that lets one QR route to either surface later? |
| Consent and anti-spam for Gmail/share incentives | Gmail-derived sale listings could be a powerful map-growth engine, but it can become creepy or spammy fast. | What can buyers share safely: public sale emails, links, dates, addresses, photos? What needs organizer review before map publication? |
| Referral-fee compliance | Referral fees to realtors, attorneys, trust officers, funeral homes, or senior-care providers may have legal/ethical constraints. | Which referral types should TroveSnap merely track versus facilitate payment/thank-you workflows? |
| Probate data handling | Probate leads are public in many places but sensitive in context. | Should TroveSnap support probate outreach tooling at all, or only intake once a family/partner contacts the seller? |
| Partner privacy boundaries | Attorneys/realtors want proof, but estate families may not want sale details broadly shared. | What is the partner-safe proof packet: aggregate counts/outcomes only, no item-level private details? |
| In-app appraisal liability | Buyer appraisal tokens could be a goldmine, but "appraisal" language is regulated/risky. | Should the buyer feature be framed as "value hints/comps" with confidence and non-certified disclaimers? |
| Marketplace overlap between TroveSnap and TroveGo | TroveSnap needs seller inventory/sale pages; TroveGo owns buyer discovery and treasure-map behavior. | Define surface boundaries: TroveSnap = seller operating system and source-of-truth; TroveGo = buyer discovery, map, check-ins, tokens, saved hunts. |
| Lead quality scoring | Not all leads are equal: probate, realtor referral, cold directory inquiry, buyer referral, workshop attendee. | What fields predict conversion and sale quality: timeline, estate size, location, referrer type, photos, urgency, cleanout need? |
| Community event ROI | Workshops and senior events can create trust but take time. | What should Justin collect from interviews: which events actually produce signed sales, and after how long? |
| Marketplace/data moat ethics | TroveSnap can use seller/buyer activity to build a local map and marketplace, but sellers must not feel exploited. | What opt-ins and value exchange make the marketplace flywheel feel fair to estate sellers? |

## Integration Priorities

| Priority | Idea | Reason |
|---|---|---|
| 1 | Sale/source attribution and lead-source fields | Cheap, foundational, and useful across every future lead-gen feature. |
| 2 | Partner proof packet | Converts existing TroveSnap operational data into referral growth without needing full CRM. |
| 3 | Directory/social publishing kit | Directly improves seller marketing while feeding buyer demand and TroveGo map readiness. |
| 4 | Public sale/check-in QR route | Bridges TroveSnap seller workflow to TroveGo buyer discovery without deciding app boundaries too early. |
| 5 | Lightweight CRM-lite partner cadence | Good after the proof packet exists; avoid building Salesforce before the core sale loop is live. |
| 6 | Gmail/share-for-token local listing discovery | Strategically powerful but needs consent, review, abuse controls, and TroveGo boundary decisions. |
| 7 | Buyer appraisal token loop | High upside for in-app purchases, but should wait until P1/P8/P10 and disclaimers are strong. |

## Justin Interview Prompts

If Justin interviews estate sellers or liquidators, capture:

| Area | Questions |
|---|---|
| Lead source mix | Where did your last 10 seller leads come from? Which 3 sources close best? Which are time-wasters? |
| Referral workflow | Which partners send leads? Realtors, attorneys, senior movers, funeral homes, hospice, assisted living, antique dealers? How do you thank or update them? |
| Proof and trust | What do partners/families ask before referring or hiring you? Do you show reports, photos, testimonials, sell-through, or cleanout proof? |
| Directory dependence | How much do you pay/use EstateSales.net or alternatives? What do they do well? What feels expensive or limiting? |
| Digital content burden | Who writes listings, posts social, updates Google Business Profile, collects reviews, and sends emails? |
| Buyer traffic | How do buyers discover sales? Signs, email lists, directories, Facebook groups, Google, repeat buyers? |
| Check-in appetite | Would a QR check-in at signs/door be acceptable? What would buyers need in return? What would sellers want to know? |
| Appraisal at sale | Do buyers ask "is this worth anything?" at sales? Would seller-approved buyer value hints help or hurt? |
| Privacy/consent | What information should never be public? What can partners see? What can buyers share? |
| CRM-lite | Do you use a CRM/spreadsheet? What source/follow-up fields are missing? |

## Personalization and Trust Concepts

Brainstorming note: the lead-generation opportunity is not only "more leads." It is also making an estate sale feel more personal, trusted, and humane. That matters because families are not simply hiring a cataloging tool; they are choosing who will handle objects tied to memory, grief, downsizing, and identity.

### Google Visibility as a Marketing Upsell

Google Business Profile and Google Ads support look like a real estate-seller upsell because they sit directly beside the seller's pain: marketing the next sale, proving turnout, and knowing what worked.

| Concept | Seller value | Possible TroveSnap shape |
|---|---|---|
| Google Business Profile monitoring | Keeps profile fresh, catches reviews/questions, and shows whether sale content is being posted consistently. | Reputation + local visibility dashboard. |
| Google Business Profile content kit | Turns each sale into preview posts, last-day reminders, sold highlights, review requests, and before/after transformations. | Pro marketing add-on generated from sale data. |
| Google Ads attribution | Shows calls, forms, check-ins, map visits, and buyer actions tied to campaigns. | Paid marketing ROI module once event tracking is in place. |
| Local SEO sale recaps | Converts finished sales into proof pages and local search content. | Semi-automated sale recap pages with privacy-safe item highlights. |
| Review request flow | Prompts families, referral partners, and maybe buyers after successful moments. | Trust-builder workflow in the partner proof packet. |

This should not be first-core build. It becomes powerful after sale pages, QR/check-in events, source attribution, and public-safe projections exist.

### Family Provenance and Memory Notes

The emotional layer may be a differentiator competitors miss. Some items are not just inventory; they have story. TroveSnap can let families decide which items carry private memory, public provenance, or a buyer handoff note.

| Memory/provenance layer | Who sees it | Why it matters |
|---|---|---|
| Private family memory note | Family + authorized seller staff | Preserves context without exposing private details. |
| Public provenance note | Buyers | Can increase perceived value and helps an object feel cared for, not discarded. |
| Buyer handoff note | Buyer after purchase | Gives the item a story and can make the sale feel respectful. |
| Family closure report | Family after sale | "Here is what happened to meaningful items" adds emotional closure beyond financial reconciliation. |
| Archive/export packet | Family | Creates a keepsake record of selected items, photos, outcomes, and notes. |

Potential fields: `memory_note_private`, `provenance_note_public`, `family_visibility`, `buyer_handoff_allowed`, `story_source`, `sensitivity`, and `consent_status`. The default should be private/off until the family opts in.

### GCMD Card Possibilities

The GCMD card metaphor fits this layer well because it turns sterile inventory rows into human-readable artifacts. Candidate card types:

| Card | Purpose |
|---|---|
| Treasure Card | Buyer-facing item story, photo, provenance snippet, QR, and care note. |
| Memory Card | Family-facing private note attached to a treasured object. |
| Provenance Card | Evidence/history card for notable items, including source confidence and family-approved story. |
| Host Card | Sale/company card for the estate seller, realtor, or referral partner to share. |
| Partner Proof Card | Realtor/attorney-safe card showing outcome, timeline, and service proof without private item details. |
| Handoff Card | Given to the buyer after purchase, carrying the family-approved story. |
| Legacy Card | Family archive export for objects they want remembered even if sold/donated. |

These cards could be printable, shareable, QR-backed, and exportable. They also give TroveGo a more personal surface later: buyers are not only finding deals; they are finding objects with stories.

### Realtor Flavor

A realtor-specific flavor is plausible, but should start as a referral/intake surface rather than a separate product. Realtors care about clearing contents, coordinating timelines, protecting client trust, and getting proof the referral was handled well.

| Realtor need | TroveSnap surface |
|---|---|
| Contents cleared before listing | Realtor intake link with timeline, access constraints, property status, and urgency. |
| Family handled gently | Co-branded family guide and memory/provenance options. |
| Referral status without oversharing | Tokenized partner status page: received, scheduled, sale live, completed. |
| Listing prep coordination | Sale/cleanout schedule, pickup/donation/disposition milestones, and handoff notes. |
| Trust proof | Partner proof packet after completion. |

This could connect estate sellers and realtors without TroveSnap becoming a realtor CRM. The first version can be a co-branded intake/proof workflow that attributes the referral and closes the loop.

### Strategic Read

The practical wedge remains operational: scan, list, sell, reconcile. The emotional wedge is memory, provenance, trust, and closure. The business wedge is lead attribution, partner proof, local visibility, and buyer demand.

The strongest version of TroveSnap may be:

> TroveSnap helps estate sellers turn a stressful liquidation into an organized, respectful, story-aware transition.

That positioning is harder to copy than "AI cataloging cheaper," and it makes the low-cost wedge feel less like a commodity.

## Product Boundary Recommendation

Keep the product split clean for now:

- **TroveSnap**: seller operating system, intake, inventory, scan contracts, review/promotion, sale pages, partner proof, source attribution, and seller-owned exports.
- **TroveGo**: buyer discovery, map, check-ins, saved hunts, tokenized buyer appraisals/value hints, and local marketplace behavior.

The shared layer should be identity, QR/deep links, public-safe sale/item projections, event telemetry, credits/tokens, and consent. That lets one estate-sale QR route to a public web page today, TroveSnap seller context when scanned by staff, or TroveGo buyer context when scanned by shoppers later.

## Plan Hooks

- **WI-086** already captures the company-side lead-gen gap. This memo gives it concrete sub-scope.
- **Research & Discovery R6** (local prospect list) and R3/R4 (seller interviews/beta cohort) should use the Justin prompts above.
- **D4 local-density first** and the Trojan-horse strategy are reinforced: lead-gen is strongest when buyer demand, public sale pages, and referral proof feed each other.
- No immediate P&C wave reshuffle is recommended. These ideas should attach after the core scan-to-list-to-sell loop is contract-backed.