Demand engine
ICP data, enrichment, email, and LinkedIn
DataBahn · Demand and outbound
Building DataBahn's demand and outbound system
I helped build the operating system behind DataBahn's prospecting: ICP development, contact data, signals, enrichment, CRM workflows, email, and coordinated LinkedIn outreach.
- Company
- DataBahn
- Role
- Marketing Manager
- Focus
- ICP, data, automation, CRM, email, LinkedIn, and campaign operations
- Scale
- 12K–15K ICP database and approximately 4,200 prospects reached monthly
The problem
Prospecting needed reliable ICP data, account and contact signals, coordinated channel execution, and a clean handoff into HubSpot.
What I owned
ICP development, database growth, enrichment workflows, campaign operations, HubSpot data management, email sequences, LinkedIn outreach coordination, and reporting.
Key decisions
- Built the database around ICP quality rather than raw contact volume.
- Used Clay and RB2B signals to improve prioritization and enrichment.
- Centralized data and lifecycle management in HubSpot.
- Coordinated Lemlist, Instantly, and HeyReach execution across seven LinkedIn accounts.
- Kept human review and account context in the workflow.
What shipped
- A 12K–15K ICP database
- Clay and RB2B workflows
- HubSpot lifecycle and campaign operations
- Lemlist and Instantly email campaigns
- HeyReach LinkedIn execution
- Sample sequences and redacted reply examples
Results
- 12K–15K ICP database
- 4,200 prospects reached monthly
- 50 → 13K+ marketing database
Deeper conversion and pipeline figures are private. I am happy to walk through them in conversation.
Evidence and artifacts
System map
- 01ICP
12K–15K account and contact database built around fit, not volume.
- 02Signals
Clay and RB2B workflows for enrichment and prioritization.
- 03CRM
HubSpot lifecycle stages, lists, and campaign operations.
- 04Email
Lemlist and Instantly sequences, roughly 4,200 prospects monthly.
- 05LinkedIn
HeyReach execution coordinated across seven accounts.
- 06Samples
Sample sequence and redacted reply thread. Available on request.
What I learned
Outbound holds up when the data, the signals, and the follow-up live in one system that a person still reviews.