Skip to main content

How to Build an Automated Lead Pipeline with CronDB Workflows

· 8 min read
Alex Ciachir
Alex Ciachir
Founder, CronDB

Most B2B teams spend 30-40% of their prospecting time on manual research — looking up companies, checking tech stacks, verifying fit, and entering data into their CRM. CronDB Workflows let you automate the entire chain from domain discovery to CRM handoff, so your team spends time selling instead of researching.

What We're Building​

By the end of this guide, you'll have a fully automated pipeline that:

  1. Discovers new domains matching your ideal customer profile (ICP)
  2. Enriches each domain with 50+ data points
  3. Scores leads based on your custom criteria
  4. Routes high-scoring leads to your CRM or outreach sequence automatically

No code required for the basic version. For teams that want deeper customization, we'll cover the API approach too.

Step 1: Define Your Ideal Customer Profile​

Before building any automation, you need a precise ICP. Vague targeting like "B2B SaaS companies" produces noisy results. CronDB lets you define your ICP using over 50 data points, so get specific.

Here's an example ICP for a company selling developer tools:

SignalCriteriaWhy
TechnologyUses React or Next.jsThey're building modern web apps
TechnologyUses Stripe or PaddleThey monetize their product
Employee range10-200Big enough to buy, small enough to move fast
IndustrySaaS, Developer ToolsCore target market
Domain age1-5 yearsEstablished enough to have budget, young enough to adopt new tools
Traffic tierMedium-HighActive product with real users
Content signalsBlog active in last 30 daysCompany is investing in growth

The more precisely you define your ICP, the higher quality your pipeline output will be. Think about what separates your best customers from your worst, and encode those differences as filterable signals.

For a deeper dive into turning these signals into scores, see Building Custom Lead Scoring Models.

Step 2: Set Up Audience Filters​

In the CronDB dashboard, navigate to Audiences and create a new audience. This is where you translate your ICP into filters.

Basic filters:

  • Technologies detected: Select specific technologies from CronDB's library of 1,500+ detected technologies. You can combine with AND/OR logic — e.g., "uses React AND (Stripe OR Paddle)".
  • Company size: Filter by estimated employee count range.
  • Industry classification: Use CronDB's AI-powered industry tags.
  • Geographic region: Filter by headquarters location or TLD.
  • Domain age: Set minimum and maximum domain registration age.

Advanced filters:

  • Technology changes: "Recently adopted [technology]" — catch companies in active buying cycles
  • Traffic growth: Domains showing month-over-month traffic increases
  • Content velocity: Domains publishing new content frequently (a proxy for growth investment)
  • Hiring signals: Domains with active careers pages mentioning specific roles

These advanced filters are powered by CronDB's intent signals engine, which tracks behavioral changes across domains over time.

Save your audience. CronDB will run this filter set continuously and surface new matching domains as they're discovered or as existing domains change to match your criteria.

Step 3: Create the Workflow​

Now connect the pieces. Go to Workflows and create a new workflow with the following steps:

Trigger: New Domain Matches Audience​

Select your audience from Step 2 as the trigger. Every time a domain enters your audience — either because it was newly discovered or because its attributes changed to match your filters — the workflow fires.

Action 1: Full Enrichment​

Add an Enrich Domain action. This pulls the complete data profile for the domain, including:

  • Full technology stack (frameworks, analytics, payments, hosting, CDN, marketing tools)
  • Business classification (industry, business model, company size)
  • Social profiles and contact pages
  • Traffic and engagement estimates
  • Content analysis (blog frequency, topic clusters)
  • Domain health metrics (SSL, performance, mobile readiness)

Action 2: Lead Scoring​

Add a Score Lead action. CronDB's scoring engine lets you assign point values to each signal:

Technology match (React/Next.js):     +20 points
Payment tech (Stripe/Paddle):         +15 points
Employee range 10-200:                +10 points
Traffic tier Medium+:                 +10 points
Blog active last 30 days:             +10 points
Domain age 1-5 years:                 +5 points
Recently hired engineers:             +15 points
Recently adopted new tech:            +10 points
---
Max possible score:                   95 points

Set your threshold. For most teams, a score of 50+ is worth routing to a sales rep, and 70+ should trigger immediate outreach.

Action 3: Route by Score​

Add a Conditional Branch:

  • Score >= 70: Route to your high-priority outreach sequence
  • Score 50-69: Add to your nurture list in CRM
  • Score < 50: Log for review but don't auto-route

Action 4: CRM Handoff​

For the high-priority branch, add a Send to CRM action. CronDB integrates natively with Salesforce and HubSpot, or you can use the Zapier integration for any other CRM.

The handoff includes all enriched data — technology stack, scoring breakdown, intent signals, and the domain profile link — so your sales rep has full context without doing any additional research.

Step 4: Connect with Zapier for Extended Automation​

For teams using CRMs or tools beyond our native integrations, Zapier unlocks the full pipeline. Here's a practical Zapier setup:

Zap 1: High-Score Lead to CRM + Slack

  • Trigger: CronDB Webhook (score >= 70)
  • Action 1: Create/update contact in your CRM (Pipedrive, Close, Copper, etc.)
  • Action 2: Post to Slack channel with lead summary and score

Zap 2: Medium-Score Lead to Email Sequence

  • Trigger: CronDB Webhook (score 50-69)
  • Action: Add to email sequence tool (Instantly, Smartlead, Apollo)

Zap 3: Weekly Pipeline Digest

  • Trigger: Schedule (every Monday at 9 AM)
  • Action 1: CronDB API — fetch all leads scored 50+ in the last 7 days
  • Action 2: Send formatted email digest to your sales team

For teams using the API directly, the webhook payload includes the full enrichment profile:

# Example: CronDB sends this to your webhook URL
POST https://your-app.com/webhooks/crondb
Content-Type: application/json

{
  "event": "lead.scored",
  "domain": "acme.dev",
  "score": 82,
  "matched_audience": "developer-tools-icp",
  "enrichment": {
    "technologies": ["React", "Next.js", "Stripe", "Vercel"],
    "industry": "developer_tools",
    "employee_range": "50-100",
    "traffic_tier": "high",
    "intent_signals": ["recently_hired_engineers", "new_tech_adopted"]
  }
}

See CronDB API Best Practices for webhook configuration details, retry handling, and authentication.

Real ROI: What to Expect​

Teams using CronDB Workflows report consistent improvements across their pipeline:

Time savings:

  • Manual domain research: ~8 minutes per lead (technology lookup, company research, CRM entry)
  • With CronDB Workflow: 0 minutes per lead (fully automated)
  • At 100 leads/week, that's 13+ hours saved per week — nearly two full working days

Pipeline quality:

  • Lead-to-opportunity conversion rates typically improve 2-3x when using multi-signal scoring versus single-attribute filtering
  • Sales reps report higher confidence in outreach because every lead comes with a full enrichment profile and score explanation

Pipeline velocity:

  • Time from domain discovery to first touch drops from days (manual research backlog) to minutes (automated routing)
  • Teams consistently report 30-50% more pipeline generated in the first month after automating

Cost efficiency:

  • A CronDB Pro plan ($149/month) replaces a combination of tools that typically costs $500-1,000/month (separate enrichment, tech detection, and intent data subscriptions)

Pro Tips for High-Performing Pipelines​

Start narrow, then expand. Begin with a tightly defined ICP and a high score threshold. It's better to route 10 perfect leads per week than 200 mediocre ones. Once your conversion rates stabilize, gradually loosen filters.

Use technology changes as triggers. A company that just adopted HubSpot is more interesting than one that's been using it for three years. Technology changes signal active buying decisions.

Layer intent signals. A domain that matches your tech stack filter AND shows traffic growth AND recently posted engineering job listings is a much stronger signal than any one of those alone. CronDB's scoring model lets you weight these combinations.

Review and tune monthly. Check which scored leads converted and which didn't. Adjust your scoring weights based on real outcomes. The best pipelines are iterative.

Don't skip warmup. If your pipeline routes leads to cold email sequences, make sure your sending domains are properly warmed up first. CronDB's Smart Warmup handles this automatically — protecting your sender reputation while your pipeline scales.

Getting Started​

  1. Sign up for CronDB (free tier includes 500 lookups/month)
  2. Define your ICP using the audience builder
  3. Create your first workflow with the trigger-enrich-score-route pattern
  4. Connect your CRM via native integration or Zapier
  5. Monitor results and tune scoring weights

The entire setup takes about 30 minutes. Once it's running, your pipeline works 24/7 — discovering, enriching, scoring, and routing leads while you focus on closing deals.