LocalAmp refreshes your LinkedIn benchmark candidates from public web signals via Perplexity. Each refresh costs real money to run, so we cap how often it can fire and gate it behind plan tiers.
The 30-day window
Each Business (or agent) gets at most one Perplexity-powered refresh every 30 days, regardless of how it was triggered.
- Manual refresh — you click “Refresh now” on the LinkedIn Benchmark card.
- Auto-refresh — the cron picks up your Business at most once every 30 days when you’ve turned auto-refresh on.
Both share the same 30-day clock. A manual refresh today resets the auto-refresh clock; an auto-refresh tomorrow resets the manual one.
What’s gated, and what isn’t
The 30-day cap applies to Perplexity-powered refresh only. These actions are NEVER blocked, on any plan:
- Manually adding a profile
- Pasting a post example
- Approving / rejecting / archiving a candidate
- Regenerating the playbook from existing approved data
If you want to keep curating your playbook between refreshes, you can — without limits.
Plan matrix
| Plan | Onboarding first-run | Manual refresh | Auto-refresh |
|---|---|---|---|
| Free | ✅ once during signup | ❌ | ❌ |
| Agent Pro (active) | ✅ | ✅ once / 30 days | ✅ once / 30 days, opt-in |
Free users got a head start during onboarding (we ran discovery once before the plan gate kicked in). Those candidates stay in your library indefinitely; you can keep approving/rejecting them.
Agent Pro unlocks manual refresh — click “Refresh now” up to once per 30-day window — and the auto-refresh toggle. When you turn auto-refresh on, the cron checks for new candidates at most once every 30 days, the same cap as manual. It is off by default; you turn it on per Business or per agent from the LinkedIn Benchmark card.
If you are on a retired Starter subscription, manual refresh keeps working exactly as it did.
Why the cap?
Three reasons:
- Cost. Every Perplexity call spends real money. A 30-day cap keeps the bill bounded.
- Signal stability. LinkedIn niches don’t churn weekly. Refreshing more often just rediscovers the same accounts.
- Honest packaging. “Unlimited refreshes” would be either dishonest (we’d cap silently anyway) or expensive (real cost passed through). The 30-day window makes the deal explicit.
Auto-refresh: how it works
When auto-refresh is on for a Pro+active Business or agent:
- The hourly cron checks if your last refresh was > 30 days ago.
- If yes, it runs Perplexity discovery and persists net-new candidates as
status='candidate'(not auto-approved). - If at least 1 net-new candidate is found, an email digest is sent to the Business owner + admin/editor seats.
- If the run finds zero net-new candidates, no email — the timestamp still advances, so the next refresh won’t fire for another 30 days.
You always review and approve before any candidate becomes part of the playbook.
What if a refresh fails?
Failed runs (Perplexity API error, network timeout, parse error) do not advance the 30-day clock. The next refresh attempt — manual or auto — can fire as soon as you’d like, no waiting.