Qualify inbound leads automatically by making the routing criteria visible before a score changes someone’s priority.

Turn the ideal customer profile into observable rules.

“Good fit” is not an operating instruction.

Define the company segments, geography, size signals, use case, role, budget indicator where appropriate, and existing-customer rules. Add clear disqualifiers that a reviewer can see in the lead record or permitted sources.

Strawberry can apply the rubric consistently and show which criteria were met. Keep a separate lane for leads that need more information instead of forcing every inquiry into qualified or rejected.

Verify the details that change the sales response.

A work email domain, company website, requested use case, and existing CRM history can tell an account owner more than a generic form score. Use the sources your team approves and retain links or record references for claims that affect priority.

Strawberry can prepare a compact account brief with what was submitted, what was verified, and what could not be confirmed. This keeps qualification grounded when websites are sparse or a form contains incomplete information.

Route the lead and prepare the next step without sending it blindly.

Qualification should lead to a clear path: fast sales review, a personalised response draft, a nurture queue, partner handoff, support route, or a respectful disqualification. The proposed route needs a reason, an owner, and a point where the recipient and message are verified.

Strawberry can prepare the handoff material and a draft tailored to the submitted context. It should not quietly send an email or change a CRM owner without the team’s approved boundary.

Improve the rubric from the outcomes, not from a hunch.

Review the routed leads against what happened next: meetings held, opportunities created, deals won, disqualified accounts, and false negatives. That feedback reveals whether a criterion is predictive, unfairly excluding useful demand, or simply collecting noise.

Once the method is stable, save it as a qualification skill and run it as a routine. Revisit the rules when your ICP, territories, product, or pipeline capacity changes.

Frequently asked questions