# Vendor.Directory — Post-Launch Operational Roadmap ## Current System Status The RFQ activation funnel is now operational end-to-end: ```text Invite → Deliver → Open → Click → Claim → Verify → Pay ``` Completed phases: | Phase | Status | | ---------------------------------- | ---------- | | D-3a — SendGrid event wiring | ✅ Complete | | D-3b — Claim attribution | ✅ Complete | | D-3c — Payment attribution | ✅ Complete | | D-3d — Activation Funnel dashboard | ✅ Complete | | E-1 — Buyer RFQ activity strip | ✅ Complete | Current live visibility includes: * Vendors contacted * Delivered emails * Opens * Clicks * Claims * Verification status * Paid conversions * Funnel diagnostics * Buyer-side RFQ activity visibility --- # Immediate Post-Launch Strategy ## Goal Do NOT overbuild. The next phase is operational observation and real-world signal gathering. The system now needs: * traffic * vendors * RFQs * engagement data * funnel behavior before adding additional automation. --- # Phase 1 — Soft Launch ## Objective Launch Vendor.Directory in a controlled environment using real users and real vendors. ## Recommended Approach ### Initial Traffic Sources * Existing vendor relationships * Direct outreach * Small ad campaigns * HOA/property management contacts * Local service verticals * Organic testing traffic ### Recommended Initial Categories Start with categories that: * already have enriched vendors * already have email coverage * have strong buyer demand Examples: * Auto Insurance * Roofing * HVAC * Plumbing * Security * Landscaping * Legal Services --- # Phase 2 — Controlled RFQ Monitoring ## Submit Real RFQs Run: * 3–10 real RFQs per category * Multiple geographic regions * Multiple vendor densities ## Observe These Systems ### Buyer Side ```text /admin/rfqs ``` Watch: * contacted count * delivered count * opened count * reviewing count * response count ### Vendor Funnel ```text /tenant/funnel ``` Watch: * Open % * Click % * Claim % * Verified % * Paid % * Funnel timing * Diagnosis flags --- # Phase 3 — Identify Funnel Bottlenecks ## Questions To Answer ### Are vendors opening emails? If NO: * improve subject lines * improve sender trust * improve timing ### Are vendors clicking? If NO: * improve email copy * improve CTA clarity * improve RFQ value messaging ### Are vendors claiming? If NO: * simplify claim process * improve trust * reduce friction ### Are vendors paying? If NO: * improve onboarding value * improve marketplace explanation * improve plan positioning --- # Phase 4 — Monitor Idle RFQs ## Important Do NOT manually trigger acquisition yet. Instead: * observe how many RFQs stall naturally * identify geographic gaps * identify category gaps ## Watch For RFQs where: ```text contacted = 0 OR opened = 0 OR claim = 0 ``` These become candidates for automated expansion. --- # Phase E-2 — Automated RFQ Expansion (Next Major Phase) ## Purpose Automatically widen vendor discovery when RFQs lack activity. ## IMPORTANT This should happen automatically. NOT through buyer buttons. --- # Proposed Escalation Model ## Pass 1 ```text 10 mile radius Exact category ``` ## Pass 2 ```text 25 mile radius Exact category ``` ## Pass 3 ```text 50 mile radius Adjacent categories ``` ## Pass 4 (optional future) ```text Statewide/regional fallback ``` --- # E-2 Operational Rules ## Required Safeguards ### Prevent Duplicate Invites Never reinvite vendors already contacted for the RFQ. ### Respect Cooldowns Honor invite cooldown periods. ### API Cost Control Cap: * DataForSEO usage * enrichment calls * acquisition bursts ### Queue-Based Only Expansion must: * run asynchronously * never block user flows * never slow RFQ submission --- # Operational Metrics To Watch ## Marketplace Health ### Healthy Funnel Targets | Metric | Healthy Target | | --------------- | ---------------- | | Delivery Rate | >90% | | Open Rate | >30% | | Click Rate | >10% | | Claim Rate | >5% | | Paid Conversion | Growing steadily | --- # High Priority Future Enhancements ## Vendor-Side ### RFQ Inbox Improvements * threaded communication * attachment support * vendor response workflow ### Verification Expansion * insurance validation * contractor license validation * trust scoring ### Listing Enhancements * videos * galleries * coupons * service areas * CTA links --- # Buyer-Side Future Enhancements ## RFQ Media Uploads Allow buyers to: * upload images * upload videos * upload documents * update project details after submission ## Recommended Stack * FFmpeg processing * queued media encoding * mobile-first uploads * storage optimization --- # Security & Anti-Spam ## Current Protections * reCAPTCHA * content filtering * email verification * SendGrid tracking * funnel attribution ## Future Protections * honeypot expansion * behavioral scoring * rate limiting * IP reputation * AI spam analysis --- # Strategic Reminder Do NOT optimize prematurely. The platform is now in: ```text signal collection mode ``` The next phase is: * observing behavior * identifying friction * validating marketplace mechanics * refining conversion points before introducing larger automation systems. --- # Core Principle Going Forward The marketplace should feel: ```text alive automatic responsive persistent trustworthy ``` without overwhelming: * buyers * vendors * operators * infrastructure * acquisition budgets --- # Current Priority Order | Priority | Item | | -------- | ----------------------------- | | 1 | Soft launch | | 2 | Observe real RFQs | | 3 | Monitor funnel behavior | | 4 | Identify idle RFQs | | 5 | Build E-2 scheduled expansion | | 6 | Add RFQ media uploads | | 7 | Expand vendor onboarding | | 8 | Scale categories + regions | --- # Current System State Vendor.Directory is no longer a prototype. The marketplace activation pipeline is operational and observable end-to-end.