Portfolio wide outbound
Most portfolio companies buy outbound piecemeal. One agency for calling, another for email, a third for the CRM work. The operating partner ends up managing three vendors per company, each with different reporting, different definitions of a lead, and different incentives. Rolling Sentiment installs a single outbound capability that covers calling, email at scale, and the process automation that ties them together. It is built once and repeated across holdings, so the playbook sharpens with each deployment.
When a private equity firm acquires a company, the first ninety days usually involve a long list of commercial priorities. Outbound lead generation is often on that list but rarely at the top. The operating partner knows the company needs more pipeline, but building an outbound function from scratch inside a newly acquired business is slow and fragile. Hiring a sales development manager, buying lists, setting up diallers, warming mailboxes, and writing sequences takes months before the first qualified meeting is booked. By then the hold period is already shrinking.
A shared outbound capability changes the arithmetic. Instead of standing up a new outbound function inside each portfolio company, the firm installs one capability once and directs it at whichever holding needs pipeline next. The call centre agents already know the playbook. The email infrastructure is already warm. The routing rules and CRM writeback are already configured. When a new company joins the portfolio, the outbound engine starts producing meetings within weeks rather than months.
This approach also solves a reporting problem. When each portfolio company hires its own outbound agency, the operating partner receives a different dashboard from each one. One agency counts a meeting booked as a lead, another counts a reply. Aggregating that into a portfolio level view is manual and error prone. With a single capability, every disposition is written back to the client's own systems in a consistent format. The operating partner sees pipeline movement across every holding from one place.
There are limits. This model works best when the portfolio companies share some commercial logic: similar buyer profiles, similar deal sizes, similar sales motions. If the portfolio spans a two hundred dollar SaaS product and a two million dollar industrial equipment sale, the same outbound playbook will not serve both. In that case we scope separate motions under the same infrastructure, which is still more efficient than separate agencies but requires honest upfront scoping about what transfers and what does not.
The call centre operates from Egypt with eighty agents working United States business hours. Agents dial lists the client approves in advance. Lists are scrubbed against do not call registries and the client's own suppression files before any agent touches a phone. Every call disposition is written back to the client's CRM or system of record in real time or near real time, depending on the integration. No disposition sits in a spreadsheet that someone emails on Friday.
Agents are trained on one motion at a time. When we begin work with a new portfolio company, the first engagement is scoped to that single company and a single outbound motion. That might be cold calling into a specific buyer persona with a specific offer. Agents learn the product, the objections, and the qualification criteria before they dial. Calls are recorded and reviewed. Scripts are adjusted based on what actually happens on calls, not what sounded good in a planning document.
The centre is not a shared pool where agents jump between twenty different campaigns in a single shift. An agent working a portfolio company's motion stays on that motion for the duration of the engagement. This matters because outbound calling degrades quickly when agents lack context. An agent who has heard the same objection forty times and knows the answer will outperform an agent encountering it for the first time. Consistency of assignment produces consistency of results.
What this will not do is replace a field sales team. Cold calling at this scale is effective for qualifying inbound leads, re-engaging dormant accounts, and running top of funnel outreach into defined territories. It is not a substitute for a senior salesperson who closes enterprise deals. We tell clients this upfront because the disappointment is worse than the lost sale. The call centre generates qualified conversations. The client's own team converts them.
Most outbound email is sent through shared platforms where hundreds of companies share IP addresses and sending reputations. One company's poor list hygiene damages another company's deliverability. Rolling Sentiment operates owned infrastructure: five hundred and sixty seven warmed mailboxes across one hundred and sixteen sending domains, with per domain authentication configured and inbox placement monitored continuously. When a portfolio company runs outbound email through this infrastructure, it is not sharing reputation with anyone outside the portfolio.
Warming is not a one time event. Mailboxes are warmed daily, not just when they are first provisioned. Sending volume ramps gradually. Reply rates and bounce rates are tracked per mailbox and per domain. A mailbox that shows declining engagement is rested before it damages the domain. A domain that accumulates bounces is rotated out. This is maintenance work that most agencies skip because it is invisible to the client until deliverability collapses.
Replies are routed to humans, not to an unmonitored inbox. When a prospect replies to an outbound email, that reply lands with someone who can read it and decide what to do. If it is an objection, it goes to the team handling objections. If it is a meeting request, it goes to the calendar owner. If it is an unsubscribe request, it is processed immediately. No reply sits unread for three days while the prospect's interest fades.
The infrastructure is set up so that a portfolio company's sending reputation is portable. If the company is sold, the domains and mailboxes can be transferred to the new owner or wound down cleanly. The sending history is not entangled with other portfolio companies. This matters at exit, when a buyer's due diligence will examine whether the company's pipeline was built on sustainable practices or on a rented email platform that will be turned off at close.
A first engagement begins with one portfolio company and one outbound motion. We do not start with a portfolio wide rollout. The operating partner selects a single holding where outbound pipeline is the binding constraint and where the buyer profile is well enough understood that we can build a list and a qualification framework without months of discovery. That company becomes the proving ground.
Scoping takes roughly two weeks. We work with the portfolio company's commercial lead to define the ideal customer profile, the offer, the qualification criteria, and the data sources for list building. We review the company's existing CRM data to understand what has been tried before and what worked or did not. We set a target for qualified meetings per month and agree on what qualified means in that specific context. Then we build the lists, train the agents, configure the email sequences, and begin outreach.
The first thirty to forty five days of a new engagement are deliberately measured. We send at lower volumes than the infrastructure can support. We call at lower intensity than the centre can sustain. This is not caution for its own sake. It is because the first weeks produce data about list quality, message resonance, and objection patterns that inform the next stage. Ramping too fast burns list and reputation before the learning happens.
After sixty days, the operating partner has enough data to decide whether to expand the motion within that company, add a second motion, or begin scoping the next portfolio company. The infrastructure does not need to be rebuilt. The integration patterns are documented. The reporting format is familiar. The second deployment takes less time than the first, and the third less than the second.
Every list is approved by the client before a single call is placed or a single email is sent. We build lists from sources the client agrees to: their own CRM, third party data providers, trade show registrations, public filings, or a combination. We do not buy lists from unknown brokers and start dialling without the client's review. The operating partner or the portfolio company's commercial lead sees the list, removes any accounts that are off limits, and signs off.
Scrubbing is continuous, not a one time pass before the first send. Lists are checked against do not call registries, suppression files, and previous opt out requests on a recurring schedule. An address that unsubscribes from email is suppressed immediately. A phone number that requests removal is blocked from future dialling. These controls are built into the automation layer so they execute without an agent needing to remember.
Data hygiene extends to the writeback. When an agent marks a contact as wrong number, disconnected, or changed company, that disposition updates the client's CRM. When an email bounces, the contact record is flagged. Over the course of an engagement, the client's own data improves. This is a secondary benefit that compounds across the portfolio. Each outbound cycle makes the next one cleaner.
Between the call and the closed deal sits a layer of process work that most outbound agencies ignore. Lead routing, quoting, scheduling, invoicing, records requests, document generation, and reporting. Rolling Sentiment builds and operates this layer, it does not advise on it. The distinction matters. An advisor tells the portfolio company what to build and leaves. We build it, run it, and maintain it as part of the outbound engagement.
Lead routing is the most common starting point. When an agent qualifies a lead, the system routes it to the correct salesperson based on territory, deal size, or product line. If that salesperson does not accept the lead within a defined window, it escalates. No lead sits in a queue while the prospect waits. Scheduling works the same way: when a prospect agrees to a meeting, the system checks calendar availability and books it without a chain of internal emails.
Document generation covers the repetitive paperwork that follows a qualified conversation. Quotes, proposals, records requests, and follow up summaries are generated from templates and populated with data from the CRM. An agent or salesperson triggers the document, the system produces it, and it is sent. This removes hours of manual work per week from the portfolio company's commercial team and reduces the error rate that comes from copying and pasting between systems.
Reporting is built into the automation, not bolted on afterwards. The operating partner can see, for any portfolio company, how many calls were placed, how many contacts were reached, how many meetings were booked, and how many opportunities were created. The data is drawn from the same systems the agents use, so there is no reconciliation between an agency spreadsheet and the CRM. What the agent sees is what the operating partner sees.
Honesty about limits is more useful than promises that cannot be kept. Outbound calling and email at this scale will not fix a product that the market does not want. If the portfolio company's value proposition is unclear or its pricing is uncompetitive, outbound will surface that problem quickly but it will not solve it. We will tell the operating partner what we are hearing from the market, and that feedback is often valuable, but it is not the same as fixing the underlying issue.
This capability will not replace a strategic sales function. It generates qualified conversations and meetings. It does not negotiate terms, manage procurement processes, or close enterprise deals. The portfolio company still needs someone who can sell. What changes is that the salesperson spends more time selling and less time prospecting.
It will not work equally well for every portfolio company. Companies with very small total addressable markets, companies where the buyer is impossible to identify from external data, and companies where the sales cycle is measured in years rather than months will see less benefit. We identify these cases during scoping and say so. Deploying outbound into a company where it will not work wastes the firm's money and our time.
It will not produce results in the first week. The infrastructure is warm and the agents are trained, but every new motion requires a learning period. Message resonance, list quality, and objection handling all improve with data. An operating partner who expects fifty qualified meetings in the first fortnight will be disappointed. An operating partner who measures progress over ninety days will see a trajectory that informs a real decision about expansion.
The call centre operates in sixteen languages in production. English is the primary language for United States business hours outreach, but the centre also covers Spanish, French, German, Portuguese, and others. When a portfolio company needs outbound in a language the centre already supports, the ramp is faster because trained agents are available. When a portfolio company needs a language not currently in production, we assess whether the volume justifies building that capability.
Email sequences are written and reviewed by native speakers, not machine translated. A sequence that reads like it was run through a translation tool damages credibility with the prospect. We maintain a network of writers who produce original sequences in each language, reviewed by a second native speaker before deployment. This is slower and more expensive than automated translation, but the reply rates justify it.
Time zone coverage follows the client's market. For United States based portfolio companies, agents work United States business hours regardless of where the centre is physically located. For European portfolio companies, agents work European hours. The centre's shift structure is built around the client's prospects, not the agent's convenience. This means prospects receive calls during their working day, not at six in the morning.
Cultural fit matters as much as language. An outbound call that uses the right words but the wrong tone will fail. Agents receive training on the business culture of the markets they call into. This includes pacing, formality, objection handling norms, and the appropriate level of persistence. A call that would be acceptable in one market may be considered aggressive in another. Training adjusts accordingly.
Outbound is one part of a larger set of services built for private equity operating teams. The same team that runs the call centre and email infrastructure also builds the process automation that routes leads and generates documents. The same team builds transaction microsites and data rooms during diligence. The same team performs the forensic data and systems analysis that supports the client's own accountants and licensed advisors during a deal.
This integration matters because outbound does not exist in isolation. The lead that an agent qualifies today may become part of the revenue data a buyer examines during due diligence in two years. The CRM structure built for outbound today may become the system of record examined during a sale process. When the same team builds both, the outbound infrastructure is designed with an eye toward eventual exit, not just toward this quarter's pipeline.
For the operating partner, the practical benefit is a single relationship that spans multiple workstreams. The same people who understand the portfolio company's outbound motion also understand its data architecture and its transaction history. When a new diligence request arrives, the context is already there. When a portfolio company is being prepared for sale, the outbound data is already structured in a way that supports buyer review.
This is not a bundled upsell. Most engagements begin with a single workstream, usually outbound or a specific automation project. The broader capability becomes relevant as the operating partner sees how the pieces fit together. Some firms use only the outbound capability and nothing else. That is fine. The infrastructure is built to stand alone. But for firms that want more, the same team and the same systems extend into the other areas without starting over.
Questions
Scoping takes roughly two weeks. After that, list building, agent training, and email sequence configuration take another two to three weeks. The first qualified meetings typically appear in week four or five. Volume ramps over the first sixty days as we gather data on message resonance and list quality. An operating partner should measure progress over ninety days, not the first fortnight. The infrastructure is warm and the agents are trained, but every new motion requires a learning period where we adjust scripts, refine lists, and improve qualification criteria based on live responses.
The cost structure depends on scope: the number of agents dedicated, the volume of email sending, and the complexity of the automation layer. A single company engagement with a dedicated calling team and email infrastructure typically costs less than hiring an internal sales development team and buying equivalent technology separately. The portfolio wide model compounds the savings because the infrastructure, integrations, and reporting are built once and reused. The second and third deployments cost less than the first. We scope and price each engagement individually after a two week assessment. We do not publish a rate card because the variables differ too much across companies and motions.
Agents are trained on one motion at a time and stay on that motion for the duration of the engagement. Training includes product deep dives, objection handling specific to the industry, and live call review. Calls are recorded and reviewed daily during the ramp period. If an agent cannot answer a prospect's question accurately, the script is updated and the agent is retrained. The operating partner or the portfolio company's commercial lead can listen to call recordings at any time. If an agent consistently fails to represent the company well, they are replaced on that motion. This is not a shared pool model where agents jump between unrelated campaigns in a single shift.
The domains and mailboxes used for that portfolio company's outbound email are isolated from other portfolio companies. When a company is sold, the sending infrastructure can be transferred to the new owner or wound down cleanly. The sending history and reputation are not entangled with other holdings. This matters during due diligence, when a buyer will examine whether the company's pipeline was built on sustainable practices or on a rented platform that disappears at close. We structure the infrastructure so that the portfolio company's sending reputation is a portable asset, not a shared liability.
Some companies are not good candidates for outbound at scale. If the total addressable market is very small, the buyer is impossible to identify from external data, or the sales cycle is measured in years rather than months, outbound will produce less benefit. We identify these cases during scoping and say so. If we begin an engagement and the data shows that message resonance is poor despite adjustments, or that list quality cannot support the required volume, we tell the operating partner and recommend either a different motion or stopping the engagement. We would rather lose a client than run an outbound programme that we know is not working. The operating partner's time and the firm's capital are better spent elsewhere.
Related
Next step
Outbound is a capability that compounds when it is installed across a portfolio rather than bought company by company. The call centre agents, the email infrastructure, the automation layer, and the reporting format are built once and sharpened with each deployment. The operating partner gets consistent data across holdings, faster ramp times for new portfolio companies, and an outbound asset that survives exit rather than vanishing with a terminated agency contract. Rolling Sentiment begins every engagement with a single company and a single motion. That first deployment proves whether the model works for the portfolio. If it does, the second and third deployments are faster and cheaper because the foundation is already in place. Contact zach@lawlessllm.com to discuss scoping a first engagement.
Start a conversation