Portfolio operations
Most operating partners spend the first half of a hold period stitching together point solutions at each company. One vendor for outbound calling at the industrial services platform, another for email at the healthcare roll-up, a third for process automation at the distribution business. The result is a fragmented set of relationships, inconsistent reporting, and no institutional muscle that carries from deal to deal. This page sets out a different approach: install one operating layer across multiple holdings, hold it to a single standard, and build something that survives exit.
The instinct to consolidate vendors is correct but the execution often breaks down for predictable reasons. The most common failure mode is assigning the relationship to a junior associate who is already stretched across three deals and has no authority to enforce process changes at the portfolio company level. Without a dedicated internal owner who can block two hours a week for pipeline review, the engagement drifts. The vendor sends weekly reports that nobody reads. The call centre agents drift off script because nobody is listening to recordings. The email domains start to decay because nobody notices the placement rates slipping from inbox to promotions.
A second failure mode is trying to install the capability at a company that cannot absorb it. If the sales team has no CRM hygiene, if the general manager cannot articulate what a qualified lead looks like, or if the business has not yet fixed its fulfilment capacity, then generating more pipeline simply creates a backlog of unworked opportunities and a frustrated salesforce. The operating partner needs to be honest about readiness and choose the first deployment carefully.
The third failure mode is scope creep before the first motion is stable. A common pattern is to launch outbound calling at one company, see early results, and immediately add email, automation, and a diligence workstream before the calling operation has reached steady state. The vendor agrees because they want the revenue. The operating partner gets a collection of half built capabilities and a team that is spread too thin to do any one thing well. The discipline that matters is refusing to add the second motion until the first one produces a repeatable outcome that the company can measure.
Start with a company where the general manager wants the help. This sounds obvious but operating partners frequently pick the business that needs the most help rather than the one that will actually use it. A sceptical GM who is forced to accept outbound support will find ways to undermine it: not returning calls from qualified leads, refusing to share CRM access, or dismissing the pipeline as low quality without reviewing a single disposition. The right first company has a GM who can name the specific problem the capability will solve and who is willing to put a sales manager on point for weekly pipeline review.
The first motion should be the one that produces a measurable outcome in the shortest time. For most portfolio companies this is outbound calling, because the feedback loop is immediate. Within the first two weeks the operating partner can listen to call recordings, review dispositions, and see whether the list is producing conversations. Email takes longer to warm domains and build reputation. Process automation requires mapping existing workflows before anything can be built. Calling provides a fast read on whether the vendor can execute and whether the company can handle the volume.
Resist the temptation to start with the largest platform in the portfolio. The first deployment is a proof of concept for the operating model, not a revenue rescue. A mid-sized company with a defined ICP and a sales team of three to five people is the right size. Large enough to matter, small enough that the operating partner can stay close to the details without getting pulled away by other priorities.
The first ninety days are about establishing a rhythm, not hitting a revenue target. Set expectations around activity and process adherence rather than closed deals. The vendor should be dialling the agreed lists during US business hours, writing dispositions back to the client CRM within the same day, and surfacing list quality issues within the first week. If a list is producing a high rate of wrong numbers or disconnected lines, the vendor should flag it immediately rather than burning dials to preserve activity metrics.
For email, the first ninety days are about infrastructure health. The vendor should provide a weekly report showing inbox placement rates by domain, any spam trap hits, and blacklist status. If placement drops below a threshold, the vendor should pause volume and diagnose the cause before resuming. The operating partner should not accept a vendor who treats email as a set and forget channel. Domain reputation takes months to build and days to destroy.
Reporting cadence should be weekly for the first six weeks, then biweekly once the operation is stable. The report should include: dial attempts, contacts reached, conversations held, qualified leads passed, and a brief narrative on what changed week over week. The operating partner should listen to at least three call recordings per week during the first month. There is no substitute for hearing the actual conversations. Script compliance, tone, and objection handling are invisible in a dashboard.
The operating partner should own the vendor relationship, not the portfolio company. When the vendor reports to the portfolio company GM, the operating partner loses visibility into what is working and what is not. The GM has incentives to make the engagement look successful, particularly if the operating partner pushed for it. A direct reporting line to the operating partner, with the GM receiving a summary, creates an honest channel.
Data access must be defined before the first dial is made. The vendor needs CRM access to write dispositions and update contact records. The operating partner needs read access to the vendor's dialler platform to verify activity independently. If the vendor resists providing platform access, that is a red flag. The operating partner should also have access to the email sending infrastructure to monitor domain health directly rather than relying on vendor provided screenshots.
At exit, the operating partner needs to be able to hand over the capability intact. This means the vendor contract should include a provision for transition support: documented processes, trained replacement personnel if the buyer wants to bring the function in house, and continued operation during a transition period. The goal is to build an asset that a buyer can choose to keep, not a dependency that unravels when the vendor relationship ends.
Ignore vanity metrics. Total dials, emails sent, and impressions are activity counts that say nothing about quality. A vendor can generate impressive activity numbers while producing no pipeline by dialling bad lists or sending to purchased contacts. The only metrics that matter are contacts reached, conversations held, qualified leads passed, and ultimately opportunities created. If the vendor leads the weekly report with activity volume, redirect the conversation to outcomes.
Ignore the vendor's proprietary methodology language. Every outbound vendor has a branded framework for how they qualify leads or structure conversations. None of it matters. What matters is whether the portfolio company sales team considers the leads worth pursuing. If the sales team is rejecting qualified leads, the problem is either the qualification criteria or the sales team's own capacity. The vendor's methodology is not the variable to optimise.
Ignore the temptation to benchmark against other firms. The operating partner community shares war stories about what worked at a previous fund or a different portfolio company. Those stories are context dependent. A calling motion that worked for a SaaS business with a thirty day sales cycle will not translate to an industrial services business with a six month procurement process. Judge the engagement on its own terms against the baseline that existed before it started.
Once the first deployment is stable and producing a repeatable outcome, the operating partner can begin installing the same capability at a second company. The second deployment will go faster because the vendor already understands the operating partner's expectations, reporting format, and escalation path. The operating partner should still insist on the same ninety day discipline: one motion, weekly reporting, call recording reviews. The temptation to accelerate because the vendor is proven is exactly what causes the second deployment to underperform the first.
The real leverage comes when the operating partner can move resources across companies without renegotiating scope. If one portfolio company has a seasonal slowdown in outbound needs, those call centre agents can be redirected to another company that is launching a new product line. This flexibility requires the vendor to maintain a pool of trained agents who understand the operating partner's portfolio, not just a single company's script. It also requires the operating partner to maintain a rolling forecast of outbound needs across the portfolio so the vendor can plan capacity.
At three or more companies, the operating partner should consider a shared services model where the vendor provides a dedicated team that works across the portfolio. This team develops institutional knowledge about the operating partner's sectors, typical buyer personas, and common objections. The onboarding time for a new portfolio company drops from weeks to days because the agents already understand the context.
Email should be added only after the calling motion is producing qualified leads that the portfolio company is actively working. The email infrastructure takes time to warm and the operating partner should not distract the vendor with a second channel while the first is still being tuned. When email is added, it should complement calling, not replace it. A common sequence is email outreach to warm a list before calling, or follow up email after a conversation. The two channels should be managed as one workflow, not two separate campaigns.
Process automation is the third motion and should only be added when there is a specific, documented process that is consuming meaningful staff hours. The operating partner should ask the portfolio company to map the current process on paper before any automation is built. If the company cannot describe the process in writing, automation will fail because the vendor will be building against an imagined workflow rather than the real one. The automation should be built to replace the documented process exactly, then iterated once it is live and the team can see what should change.
Transaction and diligence support is a separate capability that does not depend on the other motions. The operating partner can engage this workstream at any point in the deal cycle. Custom websites for the transaction process, forensic analysis of accounting data, and systems review are standalone engagements that run parallel to the ongoing outbound and automation work. The same vendor providing both creates continuity: the team that built the operating infrastructure understands the business well enough to support diligence without a learning curve.
This approach will not fix a broken sales team. If the portfolio company's salespeople cannot close, more pipeline will not help. The operating partner needs to assess sales capability honestly before installing outbound. Sometimes the right sequence is to fix the sales process first, then add pipeline. The vendor can help diagnose sales process issues by providing call recordings and disposition data, but they cannot replace a sales manager who is not doing their job.
It will not produce results in the first thirty days. Domain warming alone takes weeks. Call centre agents need time to learn the list, the script, and the common objections. The operating partner who demands pipeline in the first month is setting the engagement up to fail. The vendor will respond by cutting corners: skipping qualification steps, passing unqualified leads, or dialling without proper preparation. The operating partner should set the expectation internally that the first sixty days are an investment in infrastructure and process.
It will not work without the portfolio company's active participation. The vendor can dial, email, and build automation, but they cannot force the portfolio company to follow up on leads, provide feedback on list quality, or adopt the automated processes. The operating partner must secure a commitment from the GM before starting: a named internal owner, weekly pipeline review on the calendar, and consequences if the company does not hold up its end.
We run an eighty agent call centre in Egypt working US business hours. The agents dial lists the client approves and write dispositions back to client systems the same day. We do not provide scripts written by a copywriter who has never made a call. Our agents develop scripts from live conversations, iterating based on what actually works on the phones. The operating partner can listen to any call, at any time, without asking permission.
Our email infrastructure spans five hundred and sixty seven warmed mailboxes across one hundred and sixteen sending domains. Each domain is authenticated individually. We monitor inbox placement continuously and route replies to humans, not to an automated sequence. When placement drops, we pause and diagnose. We do not burn domains to hit a send quota.
We have built and operated twenty live properties, shipped two thousand six hundred and twenty five indexed pages, and work in sixteen languages. Our process automation work covers lead routing, quoting, scheduling, invoicing, records requests, document generation, and reporting. We build and then operate; we do not advise and walk away. For transaction and diligence support, we build custom websites and portals for the deal process itself, perform forensic analysis of accounting data and operating systems, and handle the technical work of carrying a business through diligence and transfer to new ownership.
Questions
The cost depends on the motions deployed and the number of companies covered. A single outbound calling motion at one portfolio company costs less than hiring two full time SDRs in the US, with no recruiting, training, or management burden on the operating team. Email infrastructure adds a separate cost that is largely fixed regardless of volume. Process automation is scoped and priced per workflow. The operating partner should think of this as an operating expense that scales with usage rather than a fixed headcount commitment. We provide pricing in ranges tied to specific deliverables, not bundled retainers.
This is one of the most common reasons these engagements stall. If the portfolio company sales team is not following up on qualified leads, we flag it in the weekly report and escalate to the operating partner. The fix is not a vendor problem; it is a governance problem. The operating partner needs to address it directly with the GM. We can provide call recordings and disposition data to support the conversation, but we cannot force a sales team to work leads they are ignoring. This is why we insist on a named internal owner and a weekly pipeline review before we start.
We write dispositions back to the client's CRM directly. We have integrated with most major CRM platforms and several industry specific systems. If the portfolio company uses a system we have not worked with before, we assess the integration during scoping. The one requirement we will not compromise on is that we need write access to the CRM. If the portfolio company insists on receiving leads via spreadsheet, the feedback loop breaks and the engagement will underperform. We will decline the work rather than operate without system access.
We operate on a least privilege model. Our agents access only the contact records they are dialling, not the full CRM. Email infrastructure is on domains we own and warm, which means the sending reputation travels with us, not with the portfolio company. At exit, we provide a transition plan that includes documented processes, trained replacement personnel if the buyer wants to bring the function in house, and continued operation during a handover period. The goal is to leave the buyer with a working capability they can choose to keep, not a dependency they are forced to maintain.
The engagements that fail almost always fail for the same three reasons: no internal owner at the portfolio company, an undefined process that the vendor is expected to invent, or a company with no capacity to absorb the pipeline. When the operating partner assigns a dedicated owner, defines the process before we start, and picks a company that is ready, the engagement produces a measurable outcome. We will tell you during scoping if we think the conditions are not right. Taking on work that is set up to fail costs us reputation and costs you time. Neither of us can afford that.
Related
Next step
The operating partner who installs one operating layer across multiple holdings builds something that compounds. The second deployment goes faster than the first. The third faster still. By the time the fund exits, the capability is a documented, repeatable asset that a buyer can choose to keep. The alternative is starting from scratch at every new deal, burning the first six months on vendor selection and onboarding, and never building the institutional knowledge that makes the next one easier. The choice is not between building and not building. It is between building once and building repeatedly. We work with operating teams that want to build once.
Start a conversation