Skip to main content
LeadGen has limited run capacity because each generation run consumes a metered resource. Lynka tracks that capacity separately from ordinary CRM record creation. This page explains the behavior and the current commercial rules.

​
Included credits and purchased top-ups

LeadGen capacity can come from the allowance included with a plan or from purchased top-up credits. They are separate balances.

​
Current LeadGen credits by plan

Free Forever: 3 LeadGen credits once. Free users can buy additional LeadGen credit top-ups. Pro: 15 LeadGen credits each month. Teams: 50 LeadGen credits each month. Pro and Teams included credits renew monthly, whether the subscription is billed monthly or annually. Purchased top-up credits are separate from these recurring plan allowances. Lynka keeps the balances distinct so plan-included and purchased credits are not confused.

​
A run can have a cost greater than one

Lynka records the number of credits charged for a run rather than assuming every run costs exactly one credit. Check the current product UI for the credit cost of a particular run mode. Do not build internal team procedures around an old copied number from documentation.

​
When capacity is charged

The backend validates access and consumes the required capacity as part of the run lifecycle. Browser counters are helpful for the user, but the backend remains authoritative if another run has already used the remaining allowance.

​
Refunds

The current finalization logic refunds a charged run when its final status is:
  • failed
  • no_results
  • canceled
and the run has not already been refunded. If the charge came from the plan, Lynka restores the applicable plan or bonus ledger. If the charge came from a credit grant, Lynka restores that grant’s remaining balance. This protects customers from losing charged capacity when a run does not complete as usable prospecting work.

​
What is not a refund condition

A completed run that returns prospects you personally decide not to use is different from a backend run finalized with no results. Targeting quality is still your responsibility. If the run completed normally, changing your mind about the market is not the same as a failed job.

​
Why the balance can differ between two screens

If you ever see a stale number immediately after a run, refresh the relevant LeadGen state before assuming the backend charge is wrong. The server-side balance is the authoritative value. If the mismatch persists, keep the run identifier and report the issue through Support so the charge source and refund state can be inspected.

View current plans

Check current prices, included users, and plan packaging on the website.
Last modified on September 28, 2026