Discovery
Identify ICP companies and decision-makers, then collect the fields required downstream.
Systems Design / PRD
A coordinated design for turning fragmented prospect research into outreach-ready records.
At Classmate360, I designed the product requirements and system architecture for a workflow that could discover, verify, qualify, personalize, populate, and track prospect records across the outbound stack.
This PRD and system architecture reflect the workflow design process I led at Classmate360 — shown here as a systems-design artifact, distinct from the shipped production build.
The problem
Preparing an outbound-ready prospect required separate discovery, verification, personalization, CRM population, sending, and tracking steps. Each handoff created delay, inconsistent fields, and avoidable quality risk.
The objective
Design a coordinated system that produces verified, qualified, personalized lead records ready for multichannel outreach—while keeping the CRM as the central operating record and preserving measurable events.
Proposed architecture / Five modules
Identify ICP companies and decision-makers, then collect the fields required downstream.
Check NeverBounce status, company match, catch-all status, and confidence. Only verified leads advance.
Required advancement gate
Draft an email subject and opening plus an individual Loom brief with summary, talking points, and CTA.
Populate the CRM record, prepare sending variables, and assign the appropriate Instantly campaign.
Central record
Shared status, ownership, fields, campaign assignment, and next action.
Unify Google Sheets, Instantly, Loom, Calendly, and GoHighLevel events; monitor LVR, PRR, and ABR.
Receives outreach and engagement events
Shows coordinated system responsibilities across five modules.
Depicts coordinated responsibilities, not strictly linear or fully autonomous execution.
PRD targets
The requirements defined measurable thresholds for data quality and preparation speed. A production build would need to prove them through controlled testing.
PRD target
PRD target
PRD target
PRD target
Phase 2 roadmap
These concepts were separated from the core design so they could be evaluated after the foundational workflow and validation gate proved reliable.
ROADMAP_01
Proposed phase 2 capability · Not shown as shipped
ROADMAP_02
Proposed phase 2 capability · Not shown as shipped
ROADMAP_03
Proposed phase 2 capability · Not shown as shipped
ROADMAP_04
Proposed phase 2 capability · Not shown as shipped
Build the operating layer