Run Your First Search

Step 1: Create Your First Search

How to Run a Candidate Search in Beesla

This page walks through exactly how to run your first search in Beesla, what happens when you do, and how to interpret the results. If you understand this page, you’ll understand 80 percent of the product.

Beesla searches are designed to be fast, predictable, and easy to refine.

Start a New Search

From the Beesla dashboard, start a new search.

You can enter:

• A plain-English role description
• A full job description
• Or both together for sharper results

Beesla treats your input as role context, not a keyword query.

Write the Role Description

Your role description should focus on signal, not completeness.

Include:

• Role title and seniority
• Core skills or technologies
• Relevant experience or industries
• Clear dealbreakers

Example:

Senior backend engineer. Strong Python experience. Has worked at early-stage startups. Avoid frequent job changes.

If you have a job description, paste it in and add a short note with priorities or exclusions.

Run the Search

When you run the search:

• Beesla retrieves candidate profiles
• Each result is evaluated against your role
• Candidates are scored and ranked
• Results are added automatically to your CRM

Each profile returned by the search costs 2 tokens.

The number of tokens used depends on how many results are returned, not how many you view.

Review Results as They Appear

Search results load progressively.

For each candidate, you’ll see:

• A relevance score
• A short explanation of fit
• Key signals used in the evaluation

At this stage, you’re reviewing results only. No additional tokens are used.

Refine and Rerun if Needed

If results are too broad:

• Add seniority
• Add exclusions
• Narrow the scope

If results are too narrow:

• Remove one constraint
• Broaden required experience slightly

Re-running a search will consume tokens again based on the new results returned.

What Happens After the Search

After a search completes:

• All returned profiles are in your CRM
• You can review and compare candidates
• Teammates can access the same results
• No additional cost applies for review or collaboration

Searches are designed to produce shortlists, not massive lists.

Common Mistakes

Being too vague

Results may be noisy and cost more tokens.

Being too strict

You may get very few results.

Re-running without adjusting input

Refine the role before re-running to avoid wasted tokens.

What’s Next

Once you’ve run your first search:

• See Review the Shortlist to evaluate candidates effectively
• See Natural Language Search to improve prompt quality
• See Tokens and Billing to understand how costs scale