Pipeline Best Practices

This page collects the judgment calls that don't fit a single feature: how tight to make your criteria, when to cast wide, and how to keep a pipeline healthy over weeks of use. Read it after your first batch or two, since the advice lands better once you've seen real results.

Set up for success

Start with your purpose

Your stated purpose powers Pioneer's recipe suggestions, so a clear purpose pays for itself before you've built anything.

Vague: "Sales stuff" Clear: "Finding enterprise customers in financial services for our compliance automation platform"

Use recipes as starting points

Recipes aren't final; they're starting points. Click Try this to pre-fill a pipeline, then:

• Adjust the description to be more specific
• Modify criteria based on what you know about your market
• Add or remove criteria as needed

Don't over-engineer upfront

Start with 3–5 criteria, let Pioneer find a batch, and adjust based on what arrives. Iterating against real results is faster than theorizing, and Pioneer's refinement tools are built for exactly that loop. The loop itself: Refine Your Pipeline.

Choose your quality/quantity tradeoff deliberately

When to cast a wide net

Broad criteria make sense when:

• You're exploring a new market
• Your targets are abundant
• You have time to review and filter

How to do it: more SHOULD criteria, fewer MUST; general descriptions; accept that you'll reject many leads, because rejections are cheap and they teach.

When to focus on quality

Tight criteria make sense when:

• Your time is limited
• Your targets are specific
• False positives are costly (bad outreach hurts reputation)

How to do it: more MUST criteria, specific and verifiable; accept that you might miss edge cases.

The 70% rule

A good heuristic: if roughly 70% of your leads are worth pursuing, your criteria are well-tuned.

• Much higher (90%+)? You might be too restrictive: strong matches are being filtered out before you see them.
• Much lower (50%-)? You're wasting time on noise. Tighten criteria.

Use MUST and SHOULD strategically

MUST criteria are gates:

• "Must have raised Series A": no seed companies at all
• "Must be B2B": no consumer companies

SHOULD criteria are preferences:

• "Should have 50+ employees": prefer larger, but consider smaller
• "Should be in the US": prefer domestic, but consider international

Strategy: start with MUST for absolute deal-breakers only, SHOULD for everything else. If results are too noisy, promote your most important preference to a MUST, one promotion at a time, so you can see what each change does. The mechanics behind the tiers: Teach Pioneer What a Great Lead Looks Like.

Keep the board working for you

Process the Leads column regularly

Don't let leads pile up:

1. Quick scan for obvious strong matches → approve them
2. Quick scan for obvious non-matches → reject them
3. Deeper review for the uncertain ones

Make custom stages match your real workflow

Sales workflow: Relevant → Researching → Contacted → Meeting → Proposal → Done

Partnership workflow: Relevant → Evaluating → Reached Out → In Discussion → Done

Stages you actually move leads through beat aspirational ones you'll ignore.

Reject aggressively

Rejected leads aren't deleted; rejecting the barely relevant matches keeps your Leads column focused, and your rejections teach the next discovery run what to stop finding: Pioneer reads which leads you rejected on sight, and the deal-breaker each one failed, before it searches again. A board where everything is "maybe" teaches nothing.

Get more from properties

Only extract what you'll use. Every property adds a column to your board and exports. Add fields for your workflow, not "just in case."

Use Person properties for people. Need to reach the CEO, a founder, or the head of partnerships? Don't build separate text properties for their name, email, and LinkedIn. Add a single Person property and get the researched human with verified contact details. See Find the Right People.

Use dependencies for data that builds on data. For non-person data, chains help when one property needs another as context:

1. Company Name
2. Headquarters City (depends on Company Name)
3. Local Incentive Programs (depends on Headquarters City)

Details: Enrich Leads with Properties.

Avoid the common mistakes

Too many criteria restricts results toward zero. Start simple, add criteria as needed.

Too-vague descriptions: "Find good companies" gives Pioneer nothing to aim at. Specificity compounds: "B2B SaaS" → "B2B SaaS building developer tools" → "B2B SaaS building API observability tools".

Ignoring results: if results aren't what you expected, the fix is a refinement pass, not patience. Pioneer follows your words; make the words match your intent.

Not rejecting: hundreds of unprocessed leads make a pipeline unwieldy and starve the feedback loop.

Next steps

• Refine Your Pipeline: the loop these practices feed into
• Example Pipelines: full setups for six common goals
• Enrich Leads with Properties: the data side of a great pipeline

Need help?

If you have questions, reach out to us at support@pioneerclimate.com