Example: owner plus two salespeople
Imagine a five-person company where the owner oversees sales, two people actively sell, one person handles operations, and one person handles finance. The owner or an authorized user runs LeadGen for a defined market. The team reviews the returned prospects and moves the useful ones into Sales. Each Sales user then receives the records they are expected to work. Finance and operations do not need LeadGen access simply because they belong to the same company.Step 1: control who can run LeadGen
LeadGen run access is separate from ordinary navigation. Givelead_gen.run capability only to the people who should consume the workspace’s prospecting allowance.
That can be the owner, a sales manager, or selected sellers depending on how your business works.
Step 2: review before assigning
Do not distribute every generated record simply to clear the result screen. Review fit first. A smaller list of real prospects gives your team a manageable follow-up queue and keeps conversion reporting meaningful.Step 3: assign a CRM owner
Once a prospect becomes a Lead, assign the person responsible for the next action. Ownership helps answer:- Who should contact this prospect?
- Whose queue should contain the record?
- Which user should automation nudge?
- Which records appear under Mine scope?
Step 4: keep scope appropriate
A salesperson can work their own Leads without needing workspace-wide visibility. A manager can receive team scope when the access model allows it. The owner can keep broader oversight without turning every member into Admin. See Product access and record scope before expanding visibility.Step 5: qualify consistently
Each seller should use the same basic qualification logic. Lynka’s qualification flow confirms need, decision maker, budget, timeline, and next action before creating the Deal. That consistency makes LeadGen quality easier to evaluate. If one salesperson creates Deals for every generated prospect while another only creates real opportunities, their pipeline numbers are not comparable.Step 6: review outcomes, not activity volume
A team can run many searches and send many messages without creating useful pipeline. Review:- generated prospects accepted into Sales
- first follow-up speed
- qualification rate
- pipeline created
- won deals
- revenue or collected cash where reporting allows it
Avoid a shared spreadsheet after generation
If the team exports the result to a spreadsheet, assigns names there, and then re-enters only some prospects in Lynka, you lose the main benefit of embedded LeadGen. Keep the operational record in Lynka whenever the prospect becomes work. That preserves ownership, activity history, qualification, duplicate review, reporting, and later quote or invoice relationships.Run Lynka with a small team
Set up access and responsibilities for a small business.
Measure LeadGen
Judge the source by qualified pipeline and outcomes.