How to Run Deal Sourcing Outreach With udu and Reply.io

Key takeaways:

• udu Source builds the proprietary target list, and our new integration pushes those contacts straight into a Reply.io sequence without a CSV in the middle.
• Deal sourcing outreach is not cold email. Stanford’s search fund data puts the first signed LOI at 7.8 months, so your cadence runs over quarters, not days.
• The setup takes about two minutes: paste your Reply.io API key into udu, then upload from any udu Source project.
• The Overwrite setting decides whether a re-run of your udu project refreshes contacts or leaves them alone. Get it wrong and you re-sequence people you already spoke to.

Most outbound advice assumes you’re selling software to a buyer who already has a budget line for it. Deal sourcing is a different job. You’re emailing the owner of a profitable company that isn’t for sale, who has never heard of your firm, and who already fields a version of your email from other funds.

The list matters more than the volume, and the timeline is measured in quarters.

That’s the gap this guide covers. udu Source finds the targets, we run the conversations, and the integration between them removes the export-import step that used to sit in the middle. Below is the full setup, then the part nobody writes down: how to design a sequence that an owner-operator will actually answer.

Why Deal Sourcing Outreach Is Not Cold Email

The economics are inverted. A standard outbound prospecting motion treats names as replaceable: send more, accept a low reply rate, optimize the funnel. In origination, your list is your thesis. If you burn a good target with a clumsy email, you don’t get another one in that niche.

The competitive backdrop makes it worse. Bain & Company counted $1.3 trillion of buyout dry powder in its 2026 Global Private Equity Report, with 2025 deal value up 44% to $904 billion. But the recovery was narrow: 13 megadeals took 30% of the total. Everyone else is competing for mid-market companies, and the ones that reach a banker’s process attract a crowd.

Sourcing proprietary targets is how you avoid that crowd, and it only pays off if the outreach that follows is worth the list.

Read the right-hand column as a set of constraints rather than preferences. Fewer touches over a longer window, from a real person, asking for less. That shapes everything downstream, including how you configure the upload.

What udu Source Actually Hands You

udu is an AI deal sourcing platform. It runs live web searches across what it describes as thousands of data sources, including example companies you supply, news and press releases, government filings, map data, and your own sources, then scores and prioritizes the results against your criteria.

The point of difference is coverage of companies that don’t appear in the usual databases. udu’s own framing is that it finds “under-the-radar businesses overlooked by database tools,” which is the whole argument for proprietary sourcing.

Their customer evidence is unusually specific for a vendor page. Doni Perl, a Principal at Charter Oak Equity, describes running udu alongside a purchased list: “working in a parallel path using purchased lists, Charter Oak uncovered only 19 of the 95 names that udu turned up.”

That gap is the reason the outreach has to be good. Ninety-five names you found yourself is a different asset from a bought list, and it deserves better than a template.

What We Do Once the List Lands

Our side of the workflow is the conversation layer. Reply.io runs the sequences, handles sending infrastructure and deliverability, and keeps every reply in one inbox so a partner can pick up a thread without digging through a personal mailbox.

We’re not a CRM and don’t try to be. We sync to HubSpot, Salesforce and Pipedrive, so the deal record stays wherever your firm already tracks it.

For origination work, three things matter more than the feature list: sequences that branch on behavior rather than firing on a timer, sending from a domain you haven’t burned, and a shared view of who has already been contacted so two associates don’t email the same owner in the same week.

How to Set Up the Reply.io Integration

Setup happens on udu’s side and takes about two minutes. You need an active Reply.io account and permission to view your API key.

1. Sign in to udu, click the udu logo at the top right of the screen, and select My profile.

2. Find the Integrations pane on that page and click Add integration.

3. Choose Reply.io from the list.

4. Get your Reply.io API key. It lives in your Reply.io account under Settings > API Key.

5. Paste the key into the udu dialog box and click Save.

That’s the whole connection. udu keeps its own step-by-step page if you want it open in a second tab while you work.

One practical note before you move on: the API key is account-level, so whoever sets this up is connecting the whole workspace, not just their own seat. In a firm where several people run separate udu projects, decide up front which Reply.io account the contacts should land in.

How to Push a Target List Into Reply.io

Uploading happens per project, so you can keep a manufacturing search and a healthcare services search pointed at different sequences.

1. Open your project in udu Source.

2. Click the vertical ellipsis icon next to the search bar and select Upload… from the dropdown.

3. Click Reply.io.

4. Decide where you want your contacts to go:

• To upload to your general Contacts in Reply.io, select No sequence – Upload directly to contacts.
• To upload directly into an existing sequence, pick the sequence from the dropdown.

5. If you’re uploading to a sequence and some contacts are already there, choose how you want to handle duplicates:

• Select True under Overwrite sequence to replace existing contact details with udu Source data.
• Select False to keep the existing contact details as they are.

For a first upload on a live search, send to Contacts rather than straight into a sequence. Origination lists almost always need a human pass, and it costs nothing to review before anything sends.

Designing a Sequence an Owner Will Answer

Most integration guides stop once the data moves. That’s where the actual work starts, because the cadence that books a SaaS demo will get you ignored or blocked by the owner of a $12 million distribution business who has run it for thirty years.

The timeline is the first thing to get right. Stanford Graduate School of Business runs a biennial study of search funds, and the 2024 Search Fund Study, covering 681 funds formed since 1984, found the average searcher signed 3.6 letters of intent. The first of those was signed 7.8 months into the search.

Your sequence isn’t trying to convert someone this month. It’s trying to still be in the picture three quarters from now.

The same study found something that should change how you write: searchers “prefer deep industry focus to a broader, volume-based approach,” and they reported databases and individual research, not brokers, as the primary source for their acquisition. Depth beats volume in the sourcing, and it beats volume in the outreach too.

Six touches over ten months is a slow drip by outbound standards and about right for this audience. Build it with conditional sequences so a reply or a LinkedIn connect changes the path, instead of letting the next scheduled email fire at someone mid-conversation.

One cost note on that table: LinkedIn steps run through our LinkedIn automation add-on, which is $69 per month per account on top of your plan. Budget for it before you design around it.

Writing the First Email From udu’s Own Fields

The strongest argument for doing this properly came from a business owner rather than a marketer. In an r/Entrepreneur thread asking owners what outreach actually earns a reply, one wrote that the messages he answers are the ones where he can tell the sender researched him specifically, even when the offer doesn’t fit.

His reasoning: “a spammer would never bother learning that much about my company.” The instant deletes, he said, are the “we help businesses like yours grow revenue” openers.

Treat that as the specification. Your first email has to prove, in its first two lines, that a person looked at this specific company. Anecdotal, but it matches what the Stanford data implies about focus.

udu gives you the raw material for exactly that, because its results carry the signals it scored the company on rather than just a name and a domain. A first email built from those fields might name the two facilities they operate, the certification they hold that most of their competitors don’t, or the fact that they’ve been hiring for the same role in the same region for eight months.

Keep it under 120 words, send it from a named partner rather than a shared alias, and make the ask small enough that saying yes costs nothing. “Worth a 20-minute call” outperforms “are you open to exploring a transaction,” because the second one asks an owner to declare a position before they know who you are.

There’s a second lever worth pulling. In a Reddit discussion on outbound sourcing in PE, a CEO on the receiving end said the tactic he’s surprised more firms skip is social proof drawn from his own network: “I’m going to pay attention to you if I think people that I think are legit think you are legit.” If you’ve backed a company his peers know, name it in touch one.

Protecting Deliverability When Every Name Counts

Low volume does not mean low risk. If you send 40 emails a quarter and a handful of them bounce, you’ve told the filters something bad about a domain your firm also uses for LP correspondence.

Four practices carry most of the weight here, and none are exotic:

• Send origination outreach from a separate domain, not the one your partners use for investor relations
• Warm that domain for at least three weeks before the first real send
• Validate every address udu returns before it enters a sequence, since sourced contacts skew toward smaller companies with unusual mail setups
• Cap daily sends per mailbox well below the limit, because 12 thoughtful emails a day is the actual shape of this work

Our email infrastructure covers the warm-up and the anti-spam checks, and email validation is available as an add-on from $20 per month. The bigger point is procedural: at this volume, a bounce isn’t a rounding error, it’s 2.5% of your quarterly outreach.

Handling the Reply

A reply to a deal sourcing email is rarely a yes. It’s usually a “not right now,” a question about who you are, or a forward to the owner’s accountant. All three are wins, and all three break a sequence.

This is the moment automation should get out of the way. When someone answers, the sequence stops and a person takes over, which is why the follow-up after no response logic has to be conditional rather than scheduled.

Set up your triage so each reply type has a defined next step before the first send, not after the first reply catches someone unprepared:

1. A “not now” gets a diarized note and a return to the long-cycle list
2. A question about the firm gets a same-day answer from the partner named in the signature
3. A referral to an advisor gets a new thread with the advisor and a thank-you to the owner

Our unified inbox and meeting scheduler keep those threads in one place, and the CRM sync writes the outcome back to wherever your firm tracks pipeline.

Re-Running the udu Project Without Re-Sequencing People

udu automates every search project for the future, so new targets keep arriving in a project you’ve already worked. That’s the feature, and it’s also the trap.

Upload a refreshed project carelessly and you can push people who are already mid-sequence, or already in conversation with a partner, back through touch one. Owners notice. It reads as exactly the automated outreach you’ve spent months proving you’re not running.

Two habits prevent it. Send re-runs to Contacts rather than into the live sequence, then move only the genuinely new names across after a review. And use the Overwrite setting deliberately: True when udu has genuinely fresher data on a company and nobody has annotated the record on our side, False when an associate has been editing contacts by hand.

A quarterly rhythm suits most searches. Re-run the project, review what’s new, add the new names, and leave everyone already in flight exactly where they are.

Where Jason Fits, and Where It Doesn’t

We sell an AI SDR agent called Jason, and this is a good place to be straight about fit. Jason handles sourcing, personalization, reply handling and meeting booking across a high volume of contacts. Pricing starts at $500 per month, roughly ten times our entry plan.

For a portfolio company’s commercial team, or a business development motion working a few thousand contacts a quarter, that math works and what an AI SDR does is worth reading.

For a 40-target origination list, it’s the wrong instrument. Every name on that list is irreplaceable, the messaging depends on judgment about a specific owner, and an agent optimizing for booked meetings is optimizing for the wrong outcome. Use the sequencing, the deliverability tooling and the inbox. Leave the writing to the associate who read the company’s filings.

Getting the First Project Live

The integration removes a genuinely annoying step, and that’s worth two minutes of setup. But the CSV was never the hard part of deal sourcing. The hard part is that you’re asking a stranger to consider selling something they built, and the outreach has to earn the right to ask.

Get the list from udu, connect the two accounts, then spend your time where it counts: on the opening email, the ten-month cadence, and the discipline to send forty considered emails instead of four hundred forgettable ones.

If you don’t have a Reply.io account yet, you can start a free trial and have the integration connected before your next udu project finishes running. Our full integrations library covers the rest of the stack.