Tokens and Billing
How tokens work, bundles, and plans.
Tokens and Billing
How Pricing and Tokens Work in Beesla
Beesla uses a simple, usage-based pricing model built around tokens. Tokens represent the cost of retrieving new candidate and company data. There are no per-seat fees, no exports to pay for, and no charges for reviewing or collaborating on saved data.
This page gives a high-level explanation of how tokens work before getting into specifics.
What Tokens Represent
Tokens are consumed when Beesla retrieves new data.
They are not tied to:
- Time spent in the product
- Number of users on your team
- How often you review saved profiles
- Internal collaboration or notes
Tokens are tied directly to results returned by Beesla’s agents.
The Two Ways Tokens Are Used
Tokens are applied in two cases:
Candidate search results
- Each candidate returned by a search costs 2 tokens
- Candidates are automatically added to your CRM
- Adding candidates to the CRM is free
Company details
- Each company detail request costs 1 token
- Companies are added to your CRM
- Adding companies to the CRM is free
Once data is in your CRM, you can use it without additional cost.
What Does Not Cost Tokens
These actions are always free:
- Viewing search results
- Reviewing candidates or companies in the CRM
- Reopening past searches
- Sharing data with teammates
- Notes, tags, and collaboration
You only pay when Beesla retrieves new people or company data.
Why Beesla Uses This Model
Traditional recruiting tools often charge for:
- Seats
- Exports
- Messages
- Bulk unlocks
Beesla charges for outcomes, not access.
This makes pricing:
- Predictable
- Easy to reason about
- Aligned with real recruiting work
You pay for results, not overhead.
How Tokens Fit With Plans
Your plan controls:
- Features
- Team structure
- Scope of use (internal vs multi-client)
Tokens control:
- How much sourcing and enrichment you run
Plans and tokens work together, but they serve different purposes.
For plan details, see the Pricing page.
Transparency and Control
Beesla is designed so you always know:
- Why tokens were used
- How many tokens a search consumed
- Where usage came from
Usage is visible at the workspace level.
If something looks off, support can review usage tied to specific searches or company requests.
What’s Next
For exact mechanics and examples: