Gojiberry Lead Generation: Turn Signals Into a Qualified List

Discovery is the start of qualification

Gojiberry lead generation combines a target audience with evidence that may make a prospect timely. Its public documentation describes ongoing discovery through agents and on-demand research through AI Search. That can help assemble a candidate list; it does not replace checking whether your offer solves a problem for the people found.

This guide uses public sources checked November 9, 2026. We have not tested data accuracy or run a customer acquisition campaign. The framework, scorecard, and example below are original editorial recommendations. They should help you design an evaluation without treating vendor descriptions as measured results.

Translate an ideal customer into observable rules

Start with customers whose needs you understand. Describe the company type, operating context, role involved, and reason your product matters. Then separate must-have rules from preferences. Geography may be essential because of service coverage, while company size may only be a rough proxy for complexity.

Write explicit exclusions before searching. These might include agencies when you serve internal teams, businesses outside your delivery region, existing customers, or roles that cannot influence the purchase. Keep an uncertain category for people whose fit cannot be judged from available evidence. Forcing every prospect into yes or no hides data gaps.

Choose between an ongoing feed and a specific search

The AI Search help article distinguishes continuous agent discovery from building a list on demand. It describes audience prompts, filters, and optional web research. When the search interprets a natural-language request, inspect the resulting criteria; a plausible prompt can still produce a broader audience than intended.

Use a continuous feed when the same audience and recurring event matter over time. Use a bounded search when answering a specific question, such as finding suitable accounts in a region before an event. Review the results before adding them to a live outreach destination. A research task and permission to begin contacting people are separate decisions.

Evaluate what a signal can and cannot tell you

Gojiberry documents signals including funding, hiring, recent activity, and role changes. Check the definition and timestamp in the current interface. A funding event several months ago and an active vacancy today can imply different follow-up questions, even when both are described as timely.

Match evidence to your actual offer. A new engineering vacancy may matter to a developer recruitment firm but say little about demand for an accounting tool. Two related signals can strengthen a research hypothesis, yet stacking filters can also shrink the audience too far. Compare a simpler segment with a more restrictive one before assuming additional conditions improve quality.

Use the score to order review, not certify demand

The official qualification guide describes a one-to-three-flame score based on audience fit and intent signals. Treat it as the vendor’s prioritization label rather than a probability that someone will buy. The documentation does not establish a conversion forecast for your business.

Review examples across score levels. If lower-scored people fit your offer better than highly ranked ones, investigate which assumptions differ: perhaps your buyer role is narrower, a signal is irrelevant, or an industry label is misleading. Preserve those observations in a short review log rather than changing every setting at once.

Build a repeatable human qualification sample

As an illustrative evaluation method, review 30 candidates drawn from more than one batch. This is a manageable editorial suggestion, not a statistically conclusive sample or a product limit. Apply the same written rules to each person and record one primary reason for every rejection.

Useful rejection categories include wrong business model, wrong role, weak timing evidence, outdated information, existing relationship, and insufficient information. If possible, have a second reviewer inspect a subset without seeing the first decision. Disagreement often reveals a vague ideal-customer definition rather than a software defect.

Gojiberry documents lead review actions, including removal, moving contacts to lists, and marking leads out of scope. Confirm what each action changes before using it. Your internal quality log can remain separate from product labels so that another reviewer can understand the decision later.

Illustrative scenario: security onboarding software

Imagine a company selling security onboarding software to midsize professional services firms. The team initially searches for operations leaders at organizations that are hiring. Review reveals that many candidates work at recruitment firms, which the product does not serve. The first improvement is an exclusion rule, not a more aggressive message.

Next, the reviewer checks whether vacancies suggest internal staff growth and whether the selected person owns onboarding. A relevant role change supplies context for additional research, but the team does not infer that a new leader has budget. Unclear contacts remain in a research list until their responsibilities can be verified.

The team compares later batches against the same criteria. A smaller list with clear business fit may be more usable than the original feed. This hypothetical example demonstrates decision logic; it reports no customer result, accuracy percentage, or revenue gain.

Measure the cost of a usable lead

Track approved prospects divided by reviewed prospects as a review acceptance rate. Also record research minutes, missing information, duplicate relationships, and the share rejected for each reason. These measures reveal whether the workflow reduces work or simply moves work into a cleanup queue.

Estimate cost per usable lead by dividing relevant subscription, enrichment, and review labor costs by approved prospects. Define the cost period and what qualifies as approved. Do not compare that number directly with cost per customer: a reviewed prospect has not yet replied, become an opportunity, or purchased. Keep downstream results as separate stages with clear definitions.

Decide what to change before expanding

When quality is low, change the assumption linked to the largest rejection category. Narrow titles for role mismatch, refine business descriptions for sector mismatch, or investigate evidence freshness for timing problems. Allow the workflow to produce a new batch before judging the adjustment, and keep the comparison criteria stable.

Gojiberry is worth considering when your team has a defined B2B audience and someone owns lead review. A tool cannot supply a proven offer, a clear buyer, or an agreed qualification standard. If those are missing, first use customer conversations and account research to sharpen the problem you want the software to help solve.

Frequently asked questions