Blog/Portco GTM
How I'd hire a GTM engineer if I ran the fund
/Benyamin Holley/LinkedIn/Head of GTM
If you run a fund, you are going to get pitched AI SDRs, agents, and a Clay blast. On most portcos, especially a legacy business, that is the wrong first project. The interview is how you find out whether a candidate knows that.
You are going to be tempted
If you are at a PE fund, someone is going to tell you the portco needs an AI SDR, a signal model, and a stack of agents. Sometimes that is the right project. Most of the time it is the second project, sold as the first.
The company you bought, especially a legacy business, is not a clean SaaS motion waiting for a model. The fancy layer makes a messy commercial system louder. It does not decide who you should be talking to, and it does not leave the portco with something it can run after you stop paying.
Funds get pitched the forever line all the time, and they are right to hate it. A finite build with a handoff is easier to defend because you can point at the thing. The agent work can still be in the plan. It has to sit on top of that thing.
What the portco actually looks like
A lot of these companies are still on a Microsoft Dynamics instance that came with the acquisition and has not had an owner since. Sometimes the rest of the stack is an old .NET app the last vendor left running. The CRM is where deals go to be typed in after the fact, if they get typed in at all.
Ask who you sell to and you get a vertical, not a list. Ask for the accounts that matter and every logo is somehow strategic. Ask how email goes out and it is the main domain, from the same inboxes the CEO uses. If there is a dialer, there is often no spam remediation. Numbers get burned. Carriers start treating the company like a robocall.
That is the job. Not a demo of an agent booking meetings into a pipeline the CRM cannot report.
How I'd hire a GTM engineer
If I were hiring, I would not start with agents, Clay, or a campaign plan. I would put one real company from the patch on the table and refuse to leave it. You run the interview. Not HR.
The failures I care about show up in four places: the CRM, the market, the way calls and email leave the building, and the handoff. A candidate who is good at tools has a story for each. A candidate who can do this job has a sequence, a named owner, and a reason to wait before they add volume.
The wording of those questions matters, and so does what you are listening for. Both are in the guide: seven questions against that one portco, the answers that keep the conversation going, and the answers that end it.
Month one, then the rest of the patch
Month one is not a launch. Start with the company that is most visibly broken, not the one with the loudest AI ask. The output is a written plan, not a campaign.
After that, the work is getting a CEO to accept a market, then using the same diagnosis on the rest of the patch. You are not lighting up ten motions because someone sold the fund a platform seat. You are building a way to decide which company is ready for what.
What has to be true before you add calls or email volume, what the first company should own by the time you move on, and where AI SDRs, cold email, or LinkedIn automation actually fit: that sequence is in the guide. If a candidate cannot describe that shape, they are pitching a retainer.
The interview guide
The download is the sheet I use in the room. It has the questions, the listen-fors, the walk-away signals, and the six-month portfolio plan, including the reverse-deployed owner the portco is supposed to have when the engagement ends.
If you want it for the next GTM or GTM engineering hire, put a work email in the form.
If you want to walk a portco through it, email ben@aperoadvisors.com. You can also add me on LinkedIn.
Questions
Why is an AI SDR usually the wrong first project for a PE portco?
Most acquired companies, especially legacy businesses, do not have a maintained CRM, an executive-approved market, or outbound that leaves from anywhere but the primary domain. An AI SDR makes that system louder. It does not decide who the company should talk to, and it does not leave an asset the portco can run after the checks stop.
What does a portfolio company usually look like before this work?
Often a Microsoft Dynamics instance with no owner, deals typed in after the fact, a vertical instead of an account list, every logo treated as strategic, email from the CEO's domain, and a dialer with no reputation management. Sometimes the rest of the stack is an old .NET app a prior vendor left running.
What should a GTM engineer interview at a PE fund test?
Run it yourself, on one real portco, not as an HR screen. Test four places: the CRM, the market, how calls and email leave the building across the portfolio, and the handoff to a named owner. The seven questions, what a good answer sounds like, and the walk-away signals are in the interview guide.
What should the first month of a portco GTM engagement produce?
A written operating plan for the company that is most visibly broken, not a campaign for the company with the loudest AI ask. The guide has the sequence after that: what the CEO has to approve, what has to be true before you add volume, and how the same diagnosis repeats across the patch.
When is an AI SDR a fair buy for a portfolio company?
After that company has a maintained CRM, a market a CEO will accept, tiered accounts, and sending infrastructure that will not burn the brand. The agent, the cold email program, or the LinkedIn motion sits on that base. It is not a substitute for it.
What is in the GTM engineer interview guide?
The sheet for the room: seven questions against one portco, what to listen for, walk-away signals, and a six-month portfolio operating plan through a reverse-deployed owner. It downloads on this page after a work email.
