EVANS LIST

Proposal: AI-Driven Lead Generation Engine

Prepared forNick Lassor, VP of Sales
Prepared byEvan Foster
DateApril 17, 2026

Objective

Build an internal, automated lead generation system that replaces reliance on external partners by leveraging Amazon marketplace data to identify, segment, enrich, and activate high-fit brand prospects — resulting in a repeatable pipeline of qualified outreach targets on a weekly cadence.

Project Snapshot
194estimated hours
7–8week timeline
$15,900not-to-exceed
7project phases

Scope of Work

Discovery & Data Access
Week 1
26 hrs

Establish access to all required systems and data sources. Understand the Smart Scout API schema, available fields, and rate limits. Align on segmentation criteria and campaign logic with Nick and the sales team. Initialize the TypeScript project and trigger.dev environment so the dev setup is correct before any pipeline code is written.

TaskHours
Kickoff meeting & requirements alignment2
Smart Scout API access, documentation review & data exploration6
Coordinate with Justin on internal tools & system access2
Map data fields to segmentation criteria4
Evaluate enrichment platforms (Apollo.io, LinkedIn)4
Evaluate Go High Level setup & configuration3
Initialize TypeScript project + trigger.dev CLI setup (project, tunnel, env vars, task structure)4
Verify sending domain setup — confirm outreach subdomain, SPF/DKIM/DMARC records, and domain warming plan in place before Phase 51
Data Ingestion Pipeline
Weeks 2–3
33 hrs

Build the automated pipeline that pulls Amazon data from the Smart Scout API, normalizes it, stores it in Supabase, and fans out to per-brand segmentation tasks. The weekly schedule is owned by trigger.dev — the GitHub Actions workflow is disabled at this point.

TaskHours
Design data model — Supabase schema (brands, scores, contacts, campaign_logs, pipeline_runs)4
Add conversion tracking fields to brands schema (converted_at, score_at_conversion, signals snapshot)1
Build SmartScout API ingestion task in TypeScript12
Implement pagination, data validation & normalization4
Deduplication at ingestion — skip existing partners before segmentation to avoid wasting Apollo credits2
Configure trigger.dev weekly schedule + fan-out via batchTrigger()4
Testing & iteration against live data6
Brand Segmentation Engine
Weeks 3–4
28 hrs

Implement the logic that scores and buckets brands based on the agreed-upon criteria, automatically assigning them to prospect segments. Each brand runs as its own trigger.dev task — if one fails, only that brand retries, not the whole pipeline.

TaskHours
Build scoring rules (revenue tiers, market share trends, ad spend signals)10
Implement 1P vs. 3P seller classification4
Bucketing logic — auto-assign brands to hot / warm / cold / disqualified4
Conditional chaining — hot/warm brands automatically trigger enrichment task2
Backtest scoring against existing partners — validate known clients surface as hot before going live4
Unit testing & validation against known brand examples4
Contact Enrichment
Weeks 4–5
22 hrs

Enrich segmented brand leads with real contact information for decision-makers at target companies. Apollo.io rate limits are handled automatically via trigger.dev's concurrency limiting and exponential backoff retry — no manual intervention needed if Apollo throttles.

TaskHours
Build Apollo enrichment task with concurrency limit + retry config8
LinkedIn data discovery & integration (if viable)6
Match enriched contacts to segmented brands4
Data quality checks & deduplication4
Campaign Triggers & CRM Integration
Weeks 5–6
33 hrs

Connect the segmented, enriched lead data to the outreach platform so campaigns fire automatically based on segment assignment. For the first 2–3 weeks post-launch, hot/warm brands land in a human review queue before GHL enrollment — giving Nick a chance to sanity-check output before campaigns fire at scale.

TaskHours
Set up Go High Level (or chosen platform) integration8
Build campaign trigger logic (segment → campaign mapping)6
Human review queue — hot/warm brands held in pending state for 24hrs; one-click approve/reject before GHL enrollment fires5
GHL webhook → Supabase — Cloudflare Worker writes email events to campaign_events table; auto-pause if bounce rate exceeds 5%6
Template coordination with sales team2
End-to-end testing of segment → enrich → trigger flow6
Dashboard & Deployment
Weeks 6–7
34 hrs

Build an internal-facing dashboard at prospects.navira.io giving the sales team real-time visibility into the pipeline and customizable hit lists. Nick can also be given view-only access to trigger.dev to monitor pipeline health directly.

TaskHours
Dashboard design & layout (brand lists, segment views, key metrics, hit list)4
Build dashboard frontend (D3 / Cloudflare Pages)12
"Mark as Partner" button — sets converted_at, snapshots score + signals at conversion, moves brand to Partners view3
Partners view — all converted brands, conversion date, score at conversion2
Disqualification filters — minimum revenue, seller type, suppress/snooze per brand3
Deliverability health panel — bounce rate, open rate, unsubscribe rate per cohort; warning at 5% bounce3
"Pipeline status →" button linking to trigger.dev runs page (opens in new tab)1
Deploy trigger.dev tasks to production2
Cloudflare Pages deployment & domain configuration (prospects.navira.io)2
User access setup — trigger.dev view-only for Nick + dashboard access2
QA, Handoff & Documentation
Weeks 7–8
18 hrs

Final testing, documentation, and knowledge transfer to ensure the system runs reliably without ongoing intervention.

TaskHours
Full pipeline integration testing6
Bug fixes & refinements6
Documentation (system overview, runbooks, troubleshooting)4
Handoff walkthrough with Nick & team2

Investment Summary

PhaseDescriptionHours
1Discovery & Data Access + trigger.dev Setup26
2Data Ingestion Pipeline33
3Brand Segmentation Engine28
4Contact Enrichment22
5Campaign Triggers & CRM Integration33
6Dashboard & Deployment34
7QA, Handoff & Documentation18
Total Estimated Hours194
Rate$100/hr
Not-to-Exceed Total$15,900

Timeline

Estimated duration: 7–8 weeks

Phases overlap where possible. With ~40 hours available in Week 1, Phase 1 can be completed and Phase 2 can begin immediately. Final delivery targeted by mid-June 2026.

What I Need from Your Team

Email to Team

Estimated Platform & Software Costs

These are third-party costs separate from development fees. Final recommendations will come out of Phase 1 discovery.

PlatformEst. Monthly CostNotes
Smart Scout APITBDExisting subscription assumed
Apollo.io$0Existing base tier sufficient for integration
Go High Level$97–$297/moCampaign automation (Starter or Unlimited tier)
trigger.dev$10/moNick's account — Hobby tier required for 7-day log retention; Evan added as team member
Supabase$0–$25/moNick's account — free tier to start; Pro tier if data grows beyond free limits
Domain warming tool$30–$49/moTemporary — first 2–3 months only (e.g. Mailreach or Warmy); cancel after warmup
AI Agent Tokens$0Covered by Evans List — no cost to client

Payment Schedule

Billed hourly at $100/hr with a not-to-exceed cap of $15,900. If the project completes under the estimated hours, you pay less. Invoiced at each milestone — no payment is due until the corresponding deliverables are complete and reviewed.

MilestoneTriggerAmount
DepositProposal approval — kick off Phase 1$4,000
MidpointPhases 1–4 complete & reviewed$6,000
FinalDelivery, handoff & documentation complete$5,900
Not-to-Exceed Total$15,900

Ongoing Support

This proposal covers the initial build. After launch, I'm available for:

Ready to Move Forward?

If everything looks good, approve below and we'll kick off Phase 1 immediately. Have questions? Let's talk.

Copied to clipboard