Skip to main content
LeadGen is Lynka’s built-in lead generation workflow. Its value is not only that it can start a prospecting run. The larger benefit is what happens after the search: the people you decide to work can continue inside the same customer and sales system instead of being exported to another CRM. For a small business, that can remove an entire handoff between prospecting and sales.

​
Where LeadGen fits

LeadGen sits before qualification. A useful sequence is: Target market → LeadGen run → prospect review → Lynka Lead → assignment and follow-up → qualification → Deal → Quote → Invoice → Payment → reporting The generated prospect is not automatically a qualified opportunity. Lynka keeps discovery and qualification separate so your sales reports do not treat every search result as pipeline.

​
What a LeadGen run can use

The current backend run contract supports targeting inputs that include search terms, geography, industries, and enrichment options. The exact controls presented in the UI can vary with the current run mode and feature availability, but those are the core dimensions the lead generation workflow is built around. Use them to describe the businesses you actually want to find instead of starting with a very broad search and hoping the results are useful.

Target a useful search

Turn an ideal customer description into practical LeadGen inputs.

Run LeadGen

Understand what happens when a run starts, completes, returns no results, or fails.

​
LeadGen has separate run access

Seeing the LeadGen area and being able to consume LeadGen capacity are related, but they are not the same check. A user needs the required workspace capability and the lead_gen.run access used by the backend. The workspace also needs valid remaining run capacity from its plan allowance or another valid credit source. The backend is authoritative. A stale counter in the browser cannot force a run after the available capacity has already been used.

​
Runs can use plan capacity or bonus credits

Lynka tracks the source and cost of each run. The current data model can charge plan allowance and separate credit grants. It also tracks the amount charged, the period of the charge, and whether a refund occurred. If a charged run is finalized as failed, no results, or canceled, the backend refund path restores the charged capacity according to its original source. LeadGen credits and allowance explains this without relying on hardcoded plan numbers that may change.

​
Why this matters for a small team

A team can discover prospects and work them without maintaining a private spreadsheet outside the CRM. Once a prospect becomes a lead, normal ownership and access rules can take over. For example, an owner can run the search, assign promising leads to two salespeople, let each salesperson work their own records, and still review team-level pipeline when their permissions allow it.

LeadGen with a team

See how prospecting, ownership, team scope, qualification, and reporting fit together.

​
What LeadGen does not decide

LeadGen does not decide whether a prospect is qualified, whether a deal is likely to close, or whether you should contact someone in a way that violates applicable law or platform rules. The business still owns:
  • its targeting criteria
  • its lawful basis and outreach practices
  • qualification decisions
  • record ownership
  • follow-up quality
  • final commercial outcome
Lynka helps keep that work connected and measurable.

​
Measure the full journey

Do not judge LeadGen only by the number of prospects a run returns. A smaller set that becomes qualified pipeline can be more useful than a large list nobody follows up. The stronger questions are:
  • Which generated prospects became real leads?
  • How quickly did someone follow up?
  • Which leads qualified?
  • Which deals were won?
  • Which source or target market produced useful revenue?
Use Measure LeadGen results to connect prospecting to Sales and Reports.

How a LeadGen run works

Understand the lifecycle of a Lynka LeadGen run, including targeting, workspace access, capacity charging, completion, no-result behavior, failures, and refunds.

Target the right prospects with LeadGen

Use search terms, geography, industries, and enrichment options in Lynka LeadGen to describe the businesses you actually want to find.

Move LeadGen prospects into your CRM workflow

Understand how a generated prospect becomes a Lynka lead, why discovery is separate from qualification, and what your team should do before creating a deal.

LeadGen credits, allowance, charges, and refunds

Understand how Lynka tracks LeadGen run capacity, plan allowance, bonus credits, run cost, remaining balance, and automatic refunds for failed, canceled, or no-result runs.

Use LeadGen with a small sales team

Run prospecting in Lynka, review generated prospects, assign leads, control record scope, follow up, qualify deals, and measure team results without exporting lists between tools.

Measure whether LeadGen is creating real pipeline

Evaluate Lynka LeadGen by prospect quality, follow-up, qualification, pipeline, won deals, and revenue outcomes instead of only counting generated records.

Use LeadGen responsibly across your markets

Understand the business responsibility around generated prospect data, outreach, verification, privacy, and regional rules when using Lynka LeadGen.

Troubleshoot LeadGen runs and access

Fix common Lynka LeadGen problems including missing access, disabled Run actions, exhausted allowance, no-result runs, failed runs, stale balance, and duplicate prospects.

LeadGen FAQ: common questions about prospecting in Lynka

Answers to common questions about Lynka LeadGen, generated prospects, qualification, credits, team access, geography, enrichment, duplicate records, and plan availability.

Last modified on September 7, 2026