Updated roadmap · May 2026

Linda is now moving from channel setup into a full prospecting, routing, and follow-up system.

This version reflects the recent OpenClaw gateway stabilization, Twilio/WhatsApp activity, Rethink CRM direction, automated reporting, lead assignment goals, stronger scraping architecture, and the missing Gmail connection that still needs confirmation.

What changed

Recent progress already achieved

Confirmed

OpenClaw is running correctly as a user service, which removes the earlier systemd conflict.
WhatsApp activity was observed in the gateway logs, which confirms the communication layer is active.
Linda is already framed around automated prospecting, daily reporting, and CRM delivery to Rethink.
The reporting style needs to shift from technical failure-by-source language to outcome-first summaries for Omar.

Core confirmations

Decisions still needed from CEI

Open

Confirm Gmail account to connect for outbound nurturing, alert copies, and mailbox ownership.
Confirm whether Gmail will be used directly or only as SMTP/Google Workspace sender infrastructure.
Confirm final lead assignment rules in Rethink, for example source, geography, language, or owner rotation.
Confirm which prospecting sources can be used operationally and which require manual review or rate limiting.

Execution roadmap

Adjusted to match the real implementation path

Phase 1 · Infrastructure and channels

Server, AI gateway, bot runtime, WhatsApp/Twilio baseline

Complete / Stable

Task	Responsible	Status
Cloud server configured and running	Blitz Agency	✅
OpenClaw gateway installed and stabilized under user systemd service	Blitz Agency	✅
OpenAI key connected	Both	✅
Telegram bot created and linked	Blitz Agency	✅
Twilio / WhatsApp communication layer tested at runtime	Blitz Agency	✅ / under ongoing validation

Phase 2 · Inbound capture and qualification

Conversation flow, data capture, qualification logic

In progress

Task	Responsible	Status
Refine Linda conversation script for intake and qualification	Both	🔄
Standardize captured fields: name, phone, property type, timing, budget, area, source	Both	🔄
Run end-to-end intake test across active channels	Both	⏳
Define qualification threshold before CRM push	Both	⏳

Phase 3 · Rethink CRM and lead assignment

Prospects view, routing logic, ownership

In progress

Task	Responsible	Status
Push Linda-sourced leads into Rethink prospects view	Blitz Agency	🔄
Map fields and normalize source labels	Both	🔄
Configure assignment rules for the team	Both	⏳
Test pipeline: source → Linda → Rethink → assigned owner	Both	⏳

Confirmation needed: define exactly how Omar and the team want assignment handled, such as round-robin, territory, language, deal type, or manual override.

Phase 4 · Prospecting architecture

Scraping, public records, enrichment, scoring

Redesigned

Layer	Included sources	Purpose
Discovery	Brave search	Candidate discovery only, no final qualification
Verification	Clark County business license, Clark County assessor/property search, Washoe assessor where relevant	Validate existence, address, ownership context
Enrichment	OpenCorporates, Nevada Contractors Board, CRM cross-checks	Add company detail, activity clues, entity confidence
Specialized scraping	Commercial real estate scraping tools and targeted source actors	Surface listings, brokers, tenants, and market signals with less noise
Scoring	Confidence model	Only push leads that pass the threshold to Rethink

Reporting change: Omar should see outcome-first reporting, for example sources covered, qualifying signals, CRM pushes, and only a brief note on limited sources instead of a list of failures.

Phase 5 · Daily reporting and team alerts

Less noise, more signal

Task	Responsible	Status
Replace technical per-source error language with executive summary format	Blitz Agency	⏳
Send daily brief with coverage, qualified signals, pushed leads, and notable watchouts	Blitz Agency	⏳
Define who receives the report: Omar only, leadership, or full sales team	CEI	⏳
Optionally separate internal technical log from client-facing summary	Both	⏳

Phase 6 · Gmail connection and email nurturing

The missing piece that still needs to be finalized

Needs confirmation

Task	Responsible	Status
Confirm Gmail or Google Workspace account that Linda will use	CEI	⏳
Choose connection method: Gmail API with OAuth or SMTP relay	Both	⏳
Define allowed use cases: nurture emails, report copies, manual-draft assist, follow-up reminders	Both	⏳
Configure sender identity, signature, reply-to, and mailbox access rules	Both	⏳
Design first sequence: welcome, follow-up, no-response reminder, handoff trigger	Both	⏳
Test full flow: Linda trigger → Gmail send → CRM note / status update	Both	⏳

Recommendation: if CEI uses Google Workspace, connect a dedicated operational mailbox such as info@ or linda@ instead of a personal inbox. That keeps permissions, continuity, and audit trails cleaner.

Immediate next steps

What should happen next in sequence

Priority

Confirm Gmail account and connection method.
Confirm lead assignment rules inside Rethink.
Deploy the revised prospecting source configuration and probe script.
Run a controlled scraping test with the new source stack.
Only after the test passes, update the daily report format for Omar.

Confirmation checklist

Items to close with CEI

Pending answers

Which Gmail or Google Workspace mailbox should Linda use?
Should emails be fully automated, draft-first, or approval-based?
Who receives the daily report and at what detail level?
What assignment rule should determine the owner in Rethink?
Which prospecting sources are approved for continuous scraping?