Lead Machine planner

Compliant Public Lead Machine V1

Design a public-source lead plan around your offer, ideal customer, buying moment, source permissions, scoring rules, digest format, and next actions. RevLint keeps the first pass deterministic and no-secret by default.

Plan lead machine Run billing/access check

Plan a public-source lead machine.

Build the setup packet, keyword plan, source plan, scoring rules, digest blueprint, and action playbook without running customer crawlers.

Source boundary

V1 plans sources only. It does not run proxy scraping, CAPTCHA bypass, LinkedIn scraping, Google Maps scraping/export, hidden payload extraction, or unapproved Reddit/X commercial scraping.

OfferIdeal customer

Buying moment

Primary goalCompetitors or comparables

Positive signalsNegative signals

Keyword seeds

Optional refinement uses /api/launch-signal/keyword-assistant only when the feature flag and provider key are configured.

Allowed source types

RSS or feed URLsPublic feeds, changelogs, launch feeds, and alert feeds the operator is allowed to read.Official APIsProvider-approved API access, partner APIs, and contract-approved data providers.Customer-owned exportsCRM tags, support labels, inbound forms, and opt-in lists owned by the customer.Manual upload or pasteHuman-reviewed CSVs, pasted notes, and source links gathered outside the product.Owned email/F5bot alertsSummaries from alert inboxes or monitoring accounts the customer controls.Authorized workspace dataSlack, Discord, or community exports where the customer has explicit permission.Research-only sourcesPartner directories, homepages, public docs, and account-fit research inputs.Restricted or unknownUse only to surface a blocked/review state, not as an actionable source.

Source permission notes

Planner styleVoice/tone

Desired Launch Credit asset mix

Buyer pain report3 scripts + promptsCampaign assembly/review

ImagesImage typeVideo secondsVideo type

Voiceover sourceVoiceover characters

Launch Credit estimate

245 credits, about $2.45 at 1 credit = $0.01.

Email to save previewCompany or project

Planner preview

Revenue leak setup packet Lead Machine digest

245 credits

Billing/access drift: show the mismatch before it becomes a support or revenue issue. Launch readiness: make the launch risk visible before the public push. Proof gap: turn scattered screenshots and guesses into a proof-backed next step.

Creation Hub script summary

Open Creation Hub

Offer: Revenue leak setup packet
Ideal customer: AI-built SaaS founders with launch, billing, or access risk
Buying moment: when launch, billing, access, or proof gaps are blocking customer acquisition.
Lead Machine alerts: Billing/access drift: buyers worry that money, access, and support state do not agree | Launch readiness: buyers are close to shipping but are not sure the critical path holds | Proof gap: buyers need evidence they can share with a founder, operator, or engineer
Positive signals to echo in the script: asking for recommendations, switching tools, failed payment access, public launch blocker, integration request
Negative signals to avoid or suppress: job seekers, student projects, consumer refund complaints, scraping bypass requests, private account issues
Keyword angles: Revenue leak setup packet, recommend launch checklist, failed payment access, billing access drift, launch blocker, AI-built SaaS founders with launch, billing, or access risk, ai-built saas founders with launch, billing, or access risk, when launch, billing, access, or proof gaps are blocking customer acquisition., Billing/access drift, Launch readiness, asking for recommendations, switching tools, failed payment access, public launch blocker, integration request
Source and permission notes: Allowed: Manual upload or paste (Treat as human-provided research notes and keep actions manual.) | Allowed: RSS or feed (Use feed items as market-signal context and route any response back to the original public context.) | Allowed: Owned alerts (Use summaries from alerts the customer owns; verify source context before recommending action.) | Allowed: Official API (Use only the provider's allowed API surface and respect commercial-use terms.)
Safe next actions: Start with the allowed/review-required sources and keep every next action manual. | Build a manual hot list from explicit-need, urgency, fit, and allowed-action rules. | Suppress duplicates and any signal with restricted collection basis.
Script instruction: turn the Lead Machine alerts into a concise video script. Do not expose private data, imply automated outreach, or reference restricted sources as approved.

Billing/access driftMatched

buyers worry that money, access, and support state do not agree

Launch readinessMatched

buyers are close to shipping but are not sure the critical path holds

Proof gapWatch

buyers need evidence they can share with a founder, operator, or engineer

Keyword groups

Offer keywords

Terms that anchor the offer and product promise.

Revenue leak setup packetrecommend launch checklistfailed payment accessbilling access driftlaunch blockerpricing page issueintegration complaintasking for recommendationsswitching toolspublic launch blockerintegration request

Customer keywords

ICP and buying-moment language to match against.

AI-built SaaS founders with launch, billing, or access riskai-built saas founders with launch, billing, or access riskwhen launch, billing, access, or proof gaps are blocking customer acquisition.Billing/access driftLaunch readinessProof gapfailed payment accessbilling access driftaccessbillingfailed paymentpayment

Positive signals

Signals that can raise lead priority.

asking for recommendationsswitching toolsfailed payment accesspublic launch blockerintegration requestlooking forrecommendalternative toneed helpblockedlaunchingproduction issue

Competitor context

Alternatives and migration language to monitor.

syftenalternative to syftenswitching from syftengoogle alertsalternative to google alertsswitching from google alertsmanual spreadsheet trackingalternative to manual spreadsheet trackingswitching from manual spreadsheet tracking

Exclusions

Terms that suppress outreach or force review.

job seekersstudent projectsconsumer refund complaintsscraping bypass requestsprivate account issuesjob seekerstudent projectcoupongiveawayconsumer refund complaintscraping bypass

Query templates

Starting points for approved manual or API-backed research.

"asking for recommendations" "Revenue leak setup packet""recommend" "ai-built saas founders with launch, billing, or access risk" "Revenue leak setup packet""need help" "Revenue leak setup packet" "when launch, billing, access, or proof gaps are blocking customer acquisition.""alternative to syften" "Revenue leak setup packet"

Source plan

Allowed

Manual upload or paste: Treat as human-provided research notes and keep actions manual.
RSS or feed: Use feed items as market-signal context and route any response back to the original public context.
Owned alerts: Use summaries from alerts the customer owns; verify source context before recommending action.
Official API: Use only the provider's allowed API surface and respect commercial-use terms.

Review required

No review-required sources.

Blocked

No blocked sources.

Use only customer-owned data, public feeds, official APIs, manual uploads, owned alerts, or explicitly authorized workspaces. Do not use proxy scraping, CAPTCHA bypass, Google Maps scraping/export, LinkedIn scraping, hidden payload extraction, or unapproved Reddit/X commercial scraping.

Gatekeeper rules

Reject any signal from blocked or unknown sources before scoring. Current source status: allowed.
Block proxy_evasion, captcha_bypass, waf_bypass, hidden_payload_extraction, restricted_platform_automation, linkedin_scrape, Google Maps scraping/export, and unapproved Reddit/X commercial scraping.
Keep only signals that match at least one positive keyword or buying phrase for Revenue leak setup packet.
Downrank signals matching exclusions: job seekers, student projects, consumer refund complaints, and scraping bypass requests.
Never ask for or store API keys, tokens, card data, private exports, or credentials.
Route public/community signals to manual public-context review; do not generate cold DMs or automated replies.

Scoring rubric

Explicit need - 30 pts: looking for, recommend, need help, alternative to
Urgency - 15 pts: blocked, launching, production, this week
Account fit - 15 pts: matches ICP, right company stage, relevant tool stack
Budget or maturity - 10 pts: paid, budget, revenue, team-owned problem
Authority - 10 pts: founder, owner, operator, decision maker
Source reliability - 10 pts: owned, official API, authorized workspace, manual review
Evidence quality - 10 pts: direct link, clear context, recent timestamp, specific pain
Compliance penalty - -100 pts: proxy bypass, scraping export, unknown rights, restricted platform

Digest blueprint

Cadence: daily during active launch
Lead signal: source, matched keywords, buyer pain, customer moment
Qualification: ideal customer fit, positive signals, negative signals, score
Compliance check: source category, permission notes, restricted-source flags, review status
Safe next step: recommended action, allowed source note, human review owner

Action playbook

Start with the allowed/review-required sources and keep every next action manual.
Build a manual hot list from explicit-need, urgency, fit, and allowed-action rules.
Suppress duplicates and any signal with restricted collection basis.
Review the original source before taking any action.

Compliance boundary

V1 generates a keyword/source/scoring packet; it does not run customer crawlers or proxy scrapers.
Use RSS, official APIs, owned exports, manual uploads, authorized workspaces, or approved providers as source foundations.
Treat Reddit, X, Google Maps, LinkedIn, and similar platforms as restricted unless the customer has approved API or contract rights.

Credit breakdown

Campaign Image20 credits2 x 10 credits

Uploaded voiceover0 credits1 x 0 credits

Buyer pain report125 credits1 x 125 credits

3 scripts + prompts100 credits1 x 100 credits

Before outreach

Keep the lead machine useful and permission-aware.

Source promiseEvery lead needs an allowed source type, source URL, fit reason, and permission note.
Scoring promisePositive signals raise priority, while negative signals suppress outreach or force review.
Digest promiseOperators should see what changed, why it matters, and which action is safe to take next.
Safety promiseThe plan is a workflow brief, not legal advice or a claim that a source has been cleared.