Outbound operations
The outsourced SDR model is well understood. A firm sells you a number of seats, staffs them with junior reps who work from a shared pool, and runs the programme on tooling the agency owns. For many portfolio companies the arrangement works for a while and then it does not. The problem is not the people. The problem is the structure. When the contract ends, the infrastructure, the data, and the institutional knowledge walk out the door. There is another way to build this.
Most outsourced SDR firms sell a simple package. You pay a monthly fee per rep, often on a twelve month agreement, and in return you get a person who dials and sends emails from a shared technology stack. The agency provides the licences, the dialler, the sequencing tool, and the reporting dashboard. The client provides a list, some messaging, and a target. On paper it looks like a fast way to add outbound capacity without hiring.
The model has real strengths. It removes the burden of recruiting, training, and managing entry level sales staff. It gives a portfolio company access to tooling that would otherwise require procurement cycles and vendor negotiations. And because the agency runs multiple programmes, it can often share learnings across accounts in ways a single in house team cannot. For a holding period of two to four years, these advantages matter.
The weaknesses show up later. The reps sit on the agency's infrastructure, not yours. Their mailboxes, their sending domains, their dialler history, their sequence data, all of it belongs to someone else. If you part ways with the agency, you lose the sending reputation that was built, the engagement data that accumulated, and the muscle memory of the programme. You are left with a CSV export and a decision to make about what comes next. That is a structural problem, not a performance problem.
When an agency runs outbound on its own domains and mailboxes, every positive signal, every reply, every inbox placement success accrues to the agency's infrastructure, not to the portfolio company. The domains gain reputation. The mailboxes become trusted. The IP addresses warm over months. If the relationship ends, none of that transfers. The company starts again from cold infrastructure, which is the hardest part of outbound email at scale.
This matters more than most operating partners realise. A warmed sending domain with six months of consistent positive engagement is an asset. It lands in primary inboxes. It avoids spam folders. It generates replies that feed back into the warming cycle. Building that from scratch takes time and carries risk. A new domain with no history will be treated with suspicion by receiving mail servers, and the first few thousand sends will be heavily scrutinised. If the outbound programme is contributing pipeline, losing the infrastructure means losing momentum.
The same logic applies to calling infrastructure. A dialler that has been in use for a year has a reputation with carriers. Numbers that have been flagged as spam are blocked. Numbers that have been answered and engaged are trusted. When you leave an agency, you leave that carrier reputation behind. The next provider starts from a blank slate, and call connect rates suffer until the new numbers are conditioned. This is not a small operational detail. It is a recurring cost of the seat based model.
Outsourced SDR contracts are typically priced per seat. You buy three reps, you pay for three reps. The agency has an incentive to keep those seats filled, because empty seats are lost revenue. That incentive does not always align with the portfolio company's needs. If the list is small, three reps may be overkill and the extra capacity gets wasted on low quality activity. If the list is large, three reps may be insufficient and the programme underperforms because the agency cannot add capacity without renegotiating the contract.
The seat model also encourages the agency to staff the programme with junior reps. Senior reps cost more and eat into margin. Junior reps can be effective on simple, high volume programmes, but they struggle when the product is complex, the buyer is sophisticated, or the messaging requires industry knowledge. The operating partner ends up paying for seats that are filled with people who need significant coaching, and that coaching often falls to the portfolio company's own team, which defeats part of the purpose of outsourcing.
There is a better way to think about capacity. Instead of buying seats, buy output. An operated model with a fixed team of agents working US business hours can scale effort up and down across multiple portfolio companies without renegotiating contracts. If one company needs more dialling this month and another needs less, the team shifts. The client pays for the work, not for the chairs. That flexibility is hard to achieve in a seat based contract but straightforward in an operated model.
The alternative starts with owned infrastructure. For outbound email, that means dedicated sending domains, authenticated per domain with SPF, DKIM, and DMARC, and a fleet of mailboxes that are warmed daily. The current setup includes five hundred and sixty seven mailboxes across one hundred and sixteen sending domains. Each mailbox sends a low volume per day, which protects sender reputation and keeps inbox placement high. Replies are routed to humans who read them and respond, not to an automated loop. The infrastructure is built for the client and stays with the client.
For outbound calling, the model uses a call centre of eighty agents working US business hours from a single location. They dial from lists the client approves, qualify against criteria the client sets, and write dispositions back to the client's systems in real time. The agents are not rented from a shared pool. They are a dedicated team that learns the client's businesses, understands the buyer personas, and improves over successive campaigns. Because the team is fixed, institutional knowledge accumulates rather than resetting every time a contract renews.
Behind both channels sits process automation that is built and then operated, not advised on and handed off. Lead routing, quoting, scheduling, invoicing, records requests, document generation, and reporting all run on systems that the team maintains. The automation is not a one time consulting deliverable. It is live infrastructure that the team monitors, adjusts, and improves as the programme matures. When something breaks, the people who built it fix it. That is a different proposition from buying a playbook and being told to execute it yourself.
It would be dishonest to suggest that the seat based model never works. For a portfolio company with a simple product, a large addressable market, and a holding period of eighteen to twenty four months, an outsourced SDR team can be the right call. The speed of deployment is real. The avoidance of hiring risk is real. If the programme is straightforward, high volume, and low complexity, the infrastructure ownership problem may never become acute because the company will be sold before the sending reputation matters to the next owner.
The model also works when the operating partner has no intention of building a lasting outbound capability. Some acquisitions are about cost reduction or operational improvement, not revenue growth. In those cases, outbound is a temporary need and the agency model fits the timeline. The mistake is applying that same model to companies where outbound is expected to be a durable part of the go to market engine. When the holding period is longer, or when the buyer expects to inherit a functioning revenue operation, the infrastructure question becomes central.
The key is to match the model to the outcome. If the goal is to generate some meetings for the next six months, a seat based agency will probably suffice. If the goal is to build an outbound capability that survives the sale of the business and adds value for the next owner, the infrastructure and the team need to be owned, not rented. That distinction is rarely made explicit in agency pitches, but it is the difference between a cost and an asset.
A typical outsourced SDR engagement covers dialling and emailing. It does not cover what happens after a lead responds. Routing a qualified lead to the right salesperson, generating a quote, scheduling a call, sending an invoice, requesting records, producing a report, these steps are left to the client. The agency hands off a lead and considers its job done. The portfolio company then has to build or buy the plumbing that connects the outbound activity to the rest of the business.
That handoff is where many programmes stall. A lead that is not routed within an hour goes cold. A quote that takes three days to produce loses the buyer's attention. An invoice that contains errors erodes trust. These are not sales problems, they are process problems, and they sit in the gap between the agency's scope and the company's operations. Closing that gap requires automation that is built specifically for the workflows of the business, not a generic integration that pushes data from one system to another.
The operated model includes that automation as part of the service. Lead routing rules are configured to match the client's sales territories and personnel. Quoting tools pull from live pricing data. Scheduling integrates with the calendars of the people who will take the meeting. Document generation produces clean, accurate outputs without manual formatting. Reporting is built to answer the questions the operating partner actually asks, not the questions the agency wants to answer. All of it is run by the same team that runs the outbound activity, so there is no gap to manage and no vendor to blame when something falls through.
Ending an outsourced SDR contract is rarely as clean as the agreement suggests. The agency provides a data export, typically a CSV of leads and activities. The dialler access is turned off. The email accounts are deactivated. The sequences stop. The portfolio company is left with a file and a decision: hire in house, find another agency, or abandon outbound. Each path has costs. Hiring takes time and the pipeline suffers in the interim. Switching agencies means repeating the onboarding process and losing whatever sending reputation was built. Abandoning outbound means writing off the investment entirely.
The infrastructure problem compounds during a sale process. A buyer conducting diligence will ask about the revenue engine. If the outbound programme runs on an agency's infrastructure, the buyer cannot inspect it directly. They see reports, not systems. They cannot assess the health of the sending domains, the quality of the contact data, or the effectiveness of the sequences. What should be an asset on the sell side becomes a black box that raises more questions than it answers. The operating partner is left explaining why a revenue critical function is not under the company's control.
An operated model with owned infrastructure changes that dynamic. The domains, mailboxes, dialler history, automation workflows, and data all sit with the company. A buyer can inspect them. The operating partner can demonstrate a working revenue system, not just a set of reports from a third party. When the engagement ends, the infrastructure does not disappear. It transfers cleanly because it was built for the company from the start. That is not a small advantage in a transaction where the buyer is looking for reasons to reduce the price.
The team operates in sixteen languages in production. That capability matters for portfolio companies with international customer bases or supply chains. An agency that runs everything in English will struggle with non English speaking markets. The agents are not using machine translation. They are native or fluent speakers who understand the cultural context of the markets they call. That is a hard capability to build and a harder one to fake.
Scale has limits and it is worth stating them plainly. The current infrastructure supports the volumes described, but it is not infinite. Adding a new language requires finding and training agents who speak it, which takes time. Adding a new sending domain requires a warming period of several weeks before it can carry full volume. The model works well for portfolio companies that need consistent, managed outbound capacity. It is not a fit for companies that need to spike volume unpredictably or that want to run dozens of parallel campaigns with no coordination.
The model also requires the client to provide direction. The team will build and operate the infrastructure, write the sequences, dial the lists, and run the automation, but it cannot set strategy. The client decides which markets to target, which buyers to pursue, and what message to test. The team executes and reports. Companies that want a fully hands off solution where the provider also sets strategy may find a different model more suitable. This is an execution engine, not a consulting firm.
Operating partners who are evaluating outsourced SDR firms should ask a set of questions that most agencies prefer not to answer in detail. Who owns the sending domains and mailboxes? What happens to the infrastructure if the contract ends? Are the reps dedicated to one account or shared across multiple clients? What does the data export look like, and can you see a sample before signing? How are replies handled, by the rep who sent the email or by a separate team? These questions reveal the structure of the arrangement, and the structure determines the outcome more than any sales deck.
It is also worth asking about the automation layer. If the agency only provides dialling and emailing, the portfolio company will need to build or buy the rest. That cost should be factored into the comparison. An agency that charges less per seat but leaves the company to handle routing, quoting, and reporting may be more expensive in total than a provider that includes those capabilities. The seat price is not the total cost. It is the most visible cost, which is why it gets the attention.
Finally, ask about the team. How long have the reps been with the agency? What is the turnover rate on the accounts similar to yours? Who coaches them, and how often? An agency that cannot answer these questions clearly is probably running a high churn operation where the reps are interchangeable. That can work for simple programmes. It rarely works for complex ones. The quality of the answers tells you more than the content of the answers.
Questions
The per seat price of an outsourced SDR firm often looks lower on a monthly invoice, but the comparison misses two costs. The first is the infrastructure you do not own. When the contract ends, you lose the sending reputation, the dialler history, and the engagement data. Rebuilding those costs time and pipeline. The second is the automation gap. Most seat based contracts stop at dialling and emailing. You still need to route leads, generate quotes, schedule meetings, and produce reports. If you build or buy those separately, the total cost can exceed an operated model that includes them. The question is not which invoice is smaller. It is which model leaves you with an asset at the end.
The timeline depends on what already exists. If the portfolio company has no sending infrastructure, the first step is domain setup and warming, which typically takes several weeks before the mailboxes can carry full volume. During that warming period, the calling team can begin dialling immediately. List preparation, messaging development, and automation configuration run in parallel. A reasonable expectation is that outbound activity begins within the first thirty days, with email volume ramping up as the domains warm. Full capacity across both channels is usually reached within sixty to ninety days. Programmes that require new language capabilities or complex automation may take longer.
The team is a fixed group, not a rotating pool. When an agent leaves, which happens at a normal rate in any call centre, a replacement is trained on the specific accounts the departing agent handled. Because the infrastructure, sequences, and automation are all documented and owned by the client, the replacement can pick up the work without a long learning curve. Performance is managed through the same dispositions and reporting the client sees. If an agent consistently underperforms against the agreed criteria, they are replaced. The client is not locked into a seat with a specific person. The commitment is to the output, not to the individual.
The difference is structural, not cosmetic. An agency rents you access to its infrastructure and people. This model builds infrastructure and operates a team for you. The domains, mailboxes, automation, and data are yours. The team works on your accounts, not across a shared client pool. When the engagement ends, the infrastructure does not disappear. That distinction matters most during a sale process, when a buyer wants to inspect the revenue engine. An agency relationship is a contract. Owned infrastructure is an asset. The pricing model is a consequence of the structure, not the other way around.
The cost is structured differently from both an agency and an in house hire. There is no per seat fee and no long term employment commitment. The client pays for the operation, which includes the agents, the infrastructure, and the automation. Compared to hiring in house, the operated model removes the burden of recruiting, training, managing, and retaining SDRs, and it avoids the cost of purchasing and maintaining the tooling stack. Compared to an agency, it eliminates the infrastructure loss at contract end and includes the automation layer that most agencies leave to the client. The total cost depends on the scope of the programme, the number of languages, and the complexity of the automation. A conversation about your specific situation is the only way to get a meaningful number.
Related
Next step
The outsourced SDR model has been sold to private equity operating teams for years with a consistent pitch: speed, flexibility, and lower cost than hiring. For some situations, the pitch holds. For others, the structure of the model creates problems that compound over time and become acute during a sale process. The alternative is not to abandon outbound. It is to build it on infrastructure you own, with a team that learns your businesses, and with automation that closes the gap between a lead and a closed deal. That approach takes longer to set up than signing an agency contract, but it leaves you with something that survives the engagement. In a holding period where every asset is scrutinised by a buyer, that distinction is worth more than the difference in monthly invoices.
Start a conversation