LeadLint Revenue Kits

Tell LeadLint what you sell and where. It returns complete, evidence-backed prospect packages—not another spreadsheet of names.

Each delivered Revenue Kit contains a real business record, a timestamped and specifically verified website problem, observable activity evidence, a private white-label concept preview, a proposal, a three-touch outreach sequence, and seller-entered deal math. LeadLint prepares these assets but never contacts anyone.

Why a Revenue Kit is different

A business is delivered only when every mandatory gate passes:

• a business name and public phone are present;
• the record has at least the requested number of public reviews;
• the quality score meets the chosen threshold;
• the source record has no listed website, or the listed site produced a confirmed 404, 410, DNS-resolution failure, or TLS-certificate failure;
• the business is not a duplicate in the current run; and
• unless repeat delivery is explicitly enabled, the business was not delivered in an earlier run for the same Apify account.

Timeouts, rate limits, protected sites, low ratings, and generic network errors are not treated as definite website problems. Weak or ambiguous prospects do not become Revenue Kits.

What the customer receives

• Revenue Kit dashboard: a polished index of every qualified kit in the run;
• private concept preview: a responsive, white-label HTML page using only supplied public facts and the seller's actual offer;
• timestamped proof: the exact observed issue, status, and verification time;
• proposal: public facts, evidence boundary, seller-entered scope, price, and cost math;
• three-touch outreach sequence: first message, day-three follow-up, and day-seven close-out, all labeled prepared_not_sent;
• machine-readable kit: structured JSON in the run dataset for CRM or workflow use;
• asset manifest: stable keys for each preview and proposal;
• repeat protection: persistent delivery history prevents paying for the same business on routine reruns.

The preview is prominently labeled PRIVATE CONCEPT PREVIEW — NOT A LIVE BUSINESS WEBSITE. It is never published as the prospect's website and never claims the business approved it.

Input

Provide exactly one business source:

1. searchTerms plus location, locations, or both for current Google Maps results through the maintained source Actor;
2. sourceDatasetId for an existing Apify dataset; or
3. records for a non-empty array of business records.

For Revenue Kits mode, also enter:

• sellerBrandName;
• serviceOfferName;
• serviceOfferSummary containing the actual scope you sell;
• optional sellerContact;
• optional offerPriceUsd; and
• optional estimatedFulfillmentCostUsd when a price is supplied.

LeadLint uses the offer text and amounts exactly as entered. It does not invent services, pricing, contacts, performance claims, or revenue forecasts.

Bulk territory search

• Enter up to 10 business types in searchTerms and up to 25 places in locations.
• LeadLint searches every business-type/location combination in one run, so 10 terms across 25 locations creates 250 searches.
• location remains available for a single market and can be combined with locations; duplicates are removed automatically.
• maxResultsPerSearch applies to each combination, while maxRecords limits the combined run to 25,000 records.
• sourceLocationConcurrency runs up to five locations at once to reduce elapsed time without launching unbounded child runs.
• Before starting any paid source run, LeadLint fails if the requested combinations could exceed maxRecords.

Output

Open Revenue Kit dashboard from the run output page for the human-friendly delivery. Use the default dataset for structured records and Revenue Kit manifest for downstream automation.

Each qualified dataset row preserves the original source fields and adds normalized and duplicate-control fields, website verification evidence, Revenue Kit quality and problem fields, the complete leadlint_revenue_kit object, private asset keys, and leadlint_outreach_status: prepared_not_sent.

If no business passes, the dashboard says so plainly. LeadLint does not manufacture substitute prospects.

Safe website evidence

Website checks allow only public HTTP and HTTPS destinations. LeadLint blocks loopback, private, link-local, multicast, and reserved IP ranges before every request and redirect; pins the resolved public address; limits redirects to five; and bounds concurrency and timeouts.

A missing website means only that no website appeared in the supplied public record. It does not claim that no website exists anywhere. Recheck every fact before use because public listings and websites can change.

Cost and billing controls

• Direct search uses compass/crawler-google-places, which has its own usage charge.
• Direct search requires the Apify account running LeadLint to have access to that public Store Actor. Creator-plan accounts can still use sourceDatasetId or records, but the direct-search option requires a plan with access to all Store Actors.
• sourceActorMaxChargeUsd is one combined hard ceiling for the entire run. LeadLint divides it among the location child runs; adding locations cannot multiply the authorized cap.
• maxRecords, per-search results, concurrency, and timeouts are bounded.
• No external AI API, enrichment subscription, image source, or domain is required.
• In pay-per-event mode, only a complete Revenue Kit uses the revenue-kit event. Rejected candidates are not Revenue Kit events.
• The Actor respects the customer's Apify spending limit.

Pricing must be set only after a private cloud run measures source, compute, storage, and transfer cost. LeadLint does not promise replies, sales, or profit.

Retention without lock-in

Customers can save an input and schedule it for a recurring multi-market territory scan. Persistent delivery history filters already delivered businesses across the combined run, so each recurring run focuses on newly qualifying opportunities. Customers can disable history or deliberately allow repeat delivery in the input.

LeadLint does not send email, text messages, direct messages, or proposals. That boundary keeps prospecting decisions and legal outreach compliance with the customer.

Limitations

• Source records can be incomplete or stale.
• Public websites can change immediately after verification.
• A protected, slow, or temporarily unavailable site may be a poor prospect and is excluded from Revenue Kits.
• Generated copy must be reviewed for accuracy, brand fit, and applicable outreach laws before use.
• LeadLint prepares sales assets; it cannot guarantee contact, response, conversion, revenue, or profit.