10 Lead Generation Agency Red Flags: Evidence to Request

A mid-market software company is buying an operating relationship, not a calendar screenshot. The agency will represent your offer, contact accounts that matter to your sales team, and hand conversations into an existing revenue process. Due diligence should make that work inspectable.

This is Snipe's buyer-evaluation framework, not an independent agency ranking or a statistical study of failed engagements. A warning is a reason to request evidence and resolve a gap. It is not proof that a provider is dishonest or incapable.

1. A forecast without account and funnel assumptions

A meeting target is difficult to evaluate without the addressable account universe, buyer roles, exclusions, outreach scope, qualification standard, and time period. Ask the provider to explain what assumptions connect reachable accounts to held, accepted meetings. Separate an operational target from a contractual guarantee.

Evidence to request: a written model with assumptions, downside conditions, dependencies on your team, and the remedy attached to any commercial guarantee. Use the demo pipeline calculator to explore your own assumptions, not to validate an untested promise.

2. Unclear ownership across channels and sales stages

“Full service” can mean very different things. Research, email sending, LinkedIn activity, calling, reply handling, booking, discovery, and closing are separate responsibilities. A proposal should name the owner of each included task and the point where your sales team takes over.

Evidence to request: the delivery scope and a sample handoff. Snipe's managed cold email service is email-led; do not assume a broader channel package from the term lead generation.

3. No written definition of a qualified meeting

A relevant company, a positive reply, a calendar booking, and a sales opportunity are different stages. Ask how account fit, participant role, use case, geography, exclusions, and agreement to meet are recorded. Define how unknown information is handled rather than requiring a salesperson to infer it.

Evidence to request: a completed, redacted qualification record and the rejection-review process. Use the qualified meeting criteria template to make the acceptance standard explicit.

4. Account exclusions and data controls are left to chance

Your customers, active opportunities, partners, sensitive accounts, and opt-outs need clear handling. Ask how the provider checks the approved list, applies updates, prevents conflicting outreach, and records exceptions. A database filter alone does not answer those questions.

Evidence to request: a sample approved account list, source fields, a suppression workflow, and the named owner of each update. For complex sales, ask how multiple contacts at one company are coordinated.

5. Sending infrastructure is a black box

Ask which domains and inboxes will be used, who owns them, who can access them, how they are authenticated, and what happens at termination. Dedicated sending infrastructure can help contain exposure to your primary domain, but it does not make reputation, policy, or compliance risks disappear.

Evidence to request: the documented setup and monitoring process, escalation rules, and asset-transfer terms. The cold email infrastructure guide explains the components to discuss with a provider.

6. Reporting cannot connect activity to sales outcomes

Sending volume and engagement indicators can be useful operational signals, but they do not establish pipeline. Ask to see how replies become qualified bookings, held meetings, sales-accepted conversations, and opportunities. Check how cancellations, no-shows, reschedules, duplicate events, and unknown outcomes are handled.

Evidence to request: a report with definitions, denominators, dates, and a way to inspect the underlying conversation. Live visibility can help, but the substance and traceability of the report matter more than whether it arrives in a dashboard or a document.

7. Case studies hide the stage, timeframe, or relevance

A revenue figure may actually describe open pipeline. A meeting count may include appointments that never occurred. A strong result from a self-serve product may not transfer to an enterprise evaluation with technical and procurement stakeholders.

Evidence to request: the client context, period, stage definitions, measurement basis, and limits of the result. Where confidentiality prevents a public name, ask what de-identified artifacts or approved references the provider can share. Review Snipe's published client evidence with the same standard.

8. Research and copy contain claims nobody can verify

A message that invents a buyer's pain, budget, technology, or prior interaction creates a trust problem before sales meets the account. Ask how research facts are sourced and how product claims are approved. “Personalized” should describe relevant, supported context.

Evidence to request: a sample researched account, the source behind each claim, approved copy, and the process for handling uncertain data. A polished demo of software is not a substitute for the campaign your prospects will receive.

9. Commercial terms leave important edge cases unresolved

Short terms are not automatically good, and longer terms are not automatically bad. Compare the commitment with setup work, delivery milestones, ownership, cancellation rules, and a realistic evaluation period. The risk is accepting terms without understanding what is paid for and what happens if the arrangement ends.

Evidence to request: included costs, billing triggers, handling of rejected or missed meetings, termination conditions, and access to data and assets. The appointment-setting cost guide and pay-per-meeting evaluation guide explain questions to resolve.

10. The agency cannot describe when its model is a poor fit

A provider should be able to identify the inputs it needs and the problems it does not solve. If the ICP changes every week, the product lacks proof, the account universe is too small for the planned motion, or nobody can follow up on qualified replies, adding outreach capacity may not be the right first move.

Evidence to request: a readiness assessment and explicit responsibilities for your team. Snipe's mid-market and enterprise service describes the operating boundary; the readiness checklist helps assess the prerequisites.

How should a buying team resolve red flags?

Turn each concern into a specific evidence request, assign an internal reviewer, and record whether it is resolved, unresolved, or outside scope. Distinguish a missing document from a material mismatch with your requirements. Do not let a numerical score override a requirement your company cannot compromise on.

Use the 100-point agency RFP framework and editable three-vendor workbook for a consistent comparison. Have each finalist walk through the same account scenario and show the same handoff. This makes differences in delivery easier to evaluate than another round of broad promises.