A lead-gen agency needs four tools, not eight: a data and enrichment layer, a CRM that handles multiple clients, a parallel dialer with per-client number pools, and a light sequencing tool for the touches around the call. The dialer is where the margin is made, because an agency sells meetings and meetings come from conversations. Here is the stack we see working for French and European agencies, and the integrations that make or break it.

Why agencies have a different outbound problem

An in-house SDR team has one ICP, one CRM and one brand on the caller ID. An agency has 8 clients, 8 ICPs, 8 ways of reporting, and the same 5 SDRs switching between them several times a day.

That changes the stack in three ways. Every tool must be multi-client by design, not by workaround. Reporting per client must come out of the tools, not out of a Friday afternoon spreadsheet. And cost per meeting is the agency's only real metric, so every tool must be judged on meetings per SDR, not on features.

The four layers of an agency outbound stack

Layer 1: data and enrichment

Each client brings a different target list, and the quality of that list caps everything downstream. A list with 40% wrong or missing mobiles wastes 40% of the dialer. For French targets, mobile coverage varies widely by provider; in our experience, waterfall enrichment (several providers in sequence) is the only way to hold match rates above 50%. Build the enrichment step into client onboarding, before the first call, and document the data source for GDPR.

Layer 2: the CRM, one per client or one with strict partitions

Two models work. Either the agency works inside each client's CRM (cleaner for the client, more switching for the SDR), or the agency runs one CRM partitioned by client and syncs meetings out. What does not work is a shared CRM with no partitions, where a SDR dials a contact that another client already closed.

Layer 3: the parallel dialer with per-client number pools

This is the layer that pays for the others. Our benchmark of 1,000,000 B2B cold calls in France puts the average connect rate at 11.3%. On one line, a SDR gets 5 or 6 conversations a day. A parallel dialer gives 5x more conversations for the same hours, and for an agency that means 5x more raw material for meetings without a single hire.

Agency-specific requirements: a separate number pool per client (so client A's reputation does not burn client B's connect rate), caller ID that matches the client being represented, call recording per client for proof of work, and outcome logging that routes to the right CRM.

Layer 4: sequencing, lightly

Email and LinkedIn touches warm an account before the call and follow up after. Agencies tend to over-invest here because it looks like scale. Keep it light, make sure the sequence pauses when a call connects, and judge it on meetings, not on reply rates.

Three stacks by agency size

• Starting out (1-3 SDRs): enrichment, a partitioned CRM, a parallel dialer. Three tools. Sequencing can wait.
• Growing (4-10 SDRs): add sequencing and a signals feed per client (job posts, website visits, funding) so the daily list is sorted by reason to call. Trigger-based openers reach a 7-10% meeting rate in our data, versus 2-3% for pitch-first openers, and for an agency that difference is the difference between a profitable account and a churned one.
• Scaling (10+ SDRs): add AI coaching and a manager floor. The variance between SDRs is now the largest lever, and coaching is how you move a 12-meeting-a-month SDR toward the 30-meeting one.

The integrations that make or break an agency stack

1. Dialer to CRM, per client. Outcomes, recordings and next steps must land in the right client's system automatically. Manual re-keying across 8 clients is where SDR hours vanish.
2. Enrichment to dialer. New numbers should appear in the calling list without an export.
3. Dialer to sequencing. A connected call should pause the email sequence. Otherwise the client's prospect gets an email that ignores yesterday's conversation.
4. Dialer to client reporting. Conversations, meetings and recordings by client, exportable, weekly. This is the agency's proof of work and its renewal argument.

Prefer native integrations. Connectors built on third-party automation platforms break the week a client renames a field, and the agency is the one explaining the missing data.

The mistakes we see agencies make

• Stacking 7 or 8 tools because each client had a preference. Standardise the stack; adapt the list and the script per client.
• One number pool for all clients. One bad campaign flags every number.
• Choosing tools on subscription price rather than on cost per meeting. A dialer that doubles meetings per SDR pays for itself in the first week of the first client.
• No per-client prep. A SDR switching from a fintech client to an HR-tech client at 2pm needs a 60-second brief, not a shared doc.
• Calling every client's list in the same slot. Founders pick up around 10am in our data, marketing around 4pm, HR around 1pm. Schedule campaigns by persona.

How Sonik approaches the agency outbound stack

Sonik's parallel dialer is used by lead-gen agencies in France with per-client number pools, per-client caller ID and recording, and outcome logging routed to each client's CRM. AI call prep builds the brief per client and per contact before each call, so a SDR switching accounts mid-afternoon gets the context in the dialer rather than in a shared document.

The signals layer can run per client, sorting each list by job posts, website visits and other triggers, and reporting is per client by default. We are French, so number provisioning, caller ID authentication and GDPR-compliant recording are defaults.

Conclusion

Four layers, native integrations, per-client everything, and the dialer at the centre because that is where the meetings are. Judge each tool on meetings per SDR per month and nothing else. This week, count the tools your agency pays for and the number of clients each one can report on separately; any tool that cannot report per client is costing you a Friday afternoon.