Challenge
Before anyone can send a credible first message to a local business, someone has to run a small research project. Search the name, work past directory listings and similarly named companies, and confirm the site belongs to the right business in the right city. Open it and look for what matters: a working inquiry path, a usable mobile layout, a named owner, an email address that reaches a person. Decide whether it deserves a message, then write it and log it.
In the modeled manual baseline the chain costs 18.4 operator minutes per lead, with inspection and enrichment the largest block. At a few dozen leads a month that is tolerable. At a thousand, it is a job.
Running every lookup, crawl and model call on every imported row trades one cost for another. Spend goes to duplicates and businesses with no usable site. Worse, a wrong website match fails quietly: contacts come from the wrong company, audit findings describe someone else's site, and the draft email is confidently wrong.
Volume is not the underlying problem. Applying the same effort to every record, regardless of what is already known about it, is.
Before anyone can send a credible first message to a local business, someone has to run a small research project. Search the name, work past directory listings and similarly named companies, and confirm the site belongs to the right business in the right city. Open it and look for what matters: a working inquiry path, a usable mobile layout, a named owner, an email address that reaches a person. Decide whether it deserves a message, then write it and log it.
In the modeled manual baseline the chain costs 18.4 operator minutes per lead, with inspection and enrichment the largest block. At a few dozen leads a month that is tolerable. At a thousand, it is a job.
Running every lookup, crawl and model call on every imported row trades one cost for another. Spend goes to duplicates and businesses with no usable site. Worse, a wrong website match fails quietly: contacts come from the wrong company, audit findings describe someone else's site, and the draft email is confidently wrong.
Volume is not the underlying problem. Applying the same effort to every record, regardless of what is already known about it, is.
Solution
Varilead orders its work by cost and by consequence. Six implemented stages anchor their state to the same persisted lead model (PostgreSQL through Prisma), keeping search candidates, audit findings, selected contacts and CRM activity tied to the business they describe.
Varilead orders its work by cost and by consequence. Six implemented stages anchor their state to the same persisted lead model (PostgreSQL through Prisma), keeping search candidates, audit findings, selected contacts and CRM activity tied to the business they describe.
Results
The capacity model asks what this workflow demands at 500, 5,000 and 25,000 leads a month, using the economics baseline: 8.0 operator-equivalent minutes per lead, including blocking wait, and 120 productive hours per operator per month.
In the solo scenario, 500 leads produce 3,300 automated task executions and a $101 API and compute budget, plus a $100 fixed allowance. Every lead still needs review, and 100 need extra investigation: 67 operator hours, 58.3 of them active review, or about 25 leads a day for one person.
The human side sets the plan: 667 operator hours at 5,000 leads and 3,333 at 25,000. Manual research grows by 18.4 minutes per lead; this workflow grows by 8.0, and most of those minutes are decisions rather than searches. The model names operator judgment as the likely constraint and recommends batches small enough that confirmation and draft review actually finish.
The larger scenarios need execution infrastructure beyond today's workstation workflow, and throughput, budgets and review-time assumptions still need validation through a timed operator study.
The capacity model asks what this workflow demands at 500, 5,000 and 25,000 leads a month, using the economics baseline: 8.0 operator-equivalent minutes per lead, including blocking wait, and 120 productive hours per operator per month.
In the solo scenario, 500 leads produce 3,300 automated task executions and a $101 API and compute budget, plus a $100 fixed allowance. Every lead still needs review, and 100 need extra investigation: 67 operator hours, 58.3 of them active review, or about 25 leads a day for one person.
The human side sets the plan: 667 operator hours at 5,000 leads and 3,333 at 25,000. Manual research grows by 18.4 minutes per lead; this workflow grows by 8.0, and most of those minutes are decisions rather than searches. The model names operator judgment as the likely constraint and recommends batches small enough that confirmation and draft review actually finish.
The larger scenarios need execution infrastructure beyond today's workstation workflow, and throughput, budgets and review-time assumptions still need validation through a timed operator study.