The Only Conversion That Matters Is the Call
For a founder recruiting design partners, the email is never the product. Nobody signs a design partnership from an inbox — they sign it after a conversation where you asked sharp questions, they described their problem in their own words, and both sides decided the fit was real. Which means the entire outbound sequence has exactly one job: get a 20-minute call on the calendar. Not a click, not a demo registration, not a 'reply YES for the deck.' A conversation.
Reply.io is built for that motion better than email-only tools, because the call isn't an afterthought bolted onto a drip — it's a first-class step. Multichannel sequences combine email, LinkedIn touches, and call tasks in one flow, so the channel escalates naturally from a founder-signed note to a live voice. What Reply.io doesn't supply is the sending infrastructure those emails go out from — the secondary domains, mailboxes, and dedicated IPs that decide whether step one ever reaches an inbox. That's the half ColdRelay covers, and this guide shows how to wire the two together around a single metric: conversations held.
Why Run Reply.io on ColdRelay Infrastructure
Reply.io is the orchestration layer — sequences that interleave email, LinkedIn steps, and call tasks, Jason AI to help with copy and reply handling, and a unified inbox where every channel's responses converge. It sends from whatever mailboxes you connect under its email accounts; it doesn't provision domains, assign IPs, or control whether those mailboxes land.
For the call-first motion, that gap has a specific cost: the email is the cheapest step in the sequence and everything expensive sits behind it. A call task only fires after the prospect has seen your name; a LinkedIn connection only converts a stranger into 'oh, the founder who emailed me' if the email arrived. When step one silently hits spam, you're left cold-calling people who have genuinely never heard of you — the exact motion this sequence exists to avoid.
ColdRelay closes that gap. Mailboxes on secondary domains, provisioned on isolated Azure tenants with dedicated IPs, SPF, DKIM, and DMARC pre-configured — live in about an hour, with no warmup waiting period because warmup runs continuously inside each mailbox's budget of 4 sends/day (2 outbound + 2 warmup). At 95%+ inbox placement, every downstream step in your Reply.io sequence inherits a prospect who actually read the founder's note. The pairing is additive, not competitive: ColdRelay is the infrastructure layer, Reply.io is the sequencing layer on top.
Visit Reply.io →Connecting ColdRelay Mailboxes to Reply.io
Provision a founder-scale pool on ColdRelay
Design-partner recruiting is a dozens-of-prospects motion, not a thousands motion — most founders provision 10-20 mailboxes on one secondary domain. ColdRelay supports 100-150 mailboxes per domain, so the same domain absorbs the post-PMF scale-up later. Everything lands on isolated Azure tenants with dedicated IPs in about an hour, with SPF, DKIM, and DMARC already configured, and there's no warmup period before your first sequence.
Connect the mailboxes and set per-mailbox sending limits
Add each ColdRelay mailbox as a sending account in Reply.io via SMTP/IMAP, then use Reply.io's per-mailbox sending limits to cap each account at 2 outbound emails per day. That mirrors ColdRelay's budget of 4 sends/day total per mailbox — 2 outbound + 2 warmup, with the warmup half handled continuously by ColdRelay. Don't enable additional warmup on top.
Build one multichannel sequence aimed at the call
In Reply.io's sequence builder, structure the escalation: a founder-signed email on day one, a LinkedIn connection request a day later, a second short email, then a call task. Every CTA in every step is the same — 20 minutes to compare notes on the problem. No deck attached, no demo link, no pricing. The sequence's only output is a conversation, and prospects can feel the difference between being sold and being asked.
Load prospects and let contact management track the thread
Import your design-partner shortlist — typically 50-150 hand-picked companies, not a purchased list — into Reply.io's contact management, one sequence for all of them. Each contact's record accumulates every touch across channels, so when the call task comes due you're looking at the full history: which email they opened, whether the LinkedIn connection was accepted, what they replied. You walk into the dial knowing exactly how warm it is.
Run the daily task block, with Jason AI triaging the inbox
Reply.io queues due call tasks and LinkedIn steps as tasks; block one hour each day and clear the queue in a single sitting — dials first while energy is high, LinkedIn steps after, replies last. In the unified inbox, let Jason AI categorize what came in overnight so interested replies surface to the top of the block. The founder answers those personally and books the call; everything else waits its turn in the sequence.
The Design-Partner Reply.io Playbook
Sell the 20 minutes, nothing else
Every step in the sequence asks for the same small thing: a 20-minute conversation about the problem. The moment an email starts pitching features or attaching one-pagers, you've converted a peer-to-peer ask into a vendor pitch — and founders evaluating whether to take your call can smell it instantly. Make the conversation the product; the partnership is what the conversation is for.
Survive the LinkedIn lookup
Send a founder-signed email and a meaningful share of prospects will look you up before replying — which is exactly why the sequence's LinkedIn connection step matters beyond the touch itself. Your profile is the email's references check: if it shows a founder actually building the thing the email described, the claim survives; if it's a ghost profile or reads like a sales rep, the email retroactively becomes spam. Tend the profile before the sequence launches, because it will be read.
Dial inside the sequence, not around it
The call task is where most founders flinch — and where the multichannel design pays off. By the time Reply.io surfaces the dial, the prospect has seen your email and your face on a connection request; the call opens with 'I emailed you Tuesday about X,' not a cold pitch. A two-minute voicemail-or-conversation attempt converts warm silence into either a booked call or a clear no, and both outcomes beat another week of follow-up emails.
Let Jason AI sort, never speak
Jason AI earns its place triaging the unified inbox — separating interested replies from out-of-offices and not-nows so the founder's daily hour starts with the conversations that matter. What it should never do in this motion is answer for you. A design partner is choosing whether to invest hours in your roadmap based on whether you listen; the first reply they get must be unmistakably the same human who'll be on the call.
Typical Design-Partner Outreach Benchmarks (Reply.io + ColdRelay)
| Metric | Benchmark | Notes |
|---|---|---|
| Inbox placement rate | 95%+ | Dedicated IPs and isolated tenants — every downstream call task assumes the email was actually seen |
| Reply rate | 4-8% | Founder-signed, conversation-only ask to a hand-picked list; no deck, no demo link |
| Reply-to-booked-call conversion | 30-50% | A 20-minute peer ask converts replies far better than a demo or pricing CTA |
| Outbound capacity per mailbox | 2/day | 4 sends/day total per mailbox — 2 outbound + 2 warmup |
| Founder time per day | ~60 minutes | One Reply.io task block: call tasks, LinkedIn steps, and Jason AI-triaged replies in a single sitting |
What It Costs: Reply.io + ColdRelay
You pay per mailbox per month for the infrastructure, with volume tiers that drop as you scale (see the table below). DNS, dedicated IPs, and isolated Azure tenants are included — and the 10-20 mailbox pool this motion needs keeps the line item small while you're still recruiting your first partners.
Reply.io is billed separately on its own subscription, covering the multichannel sequence builder, call tasks, LinkedIn steps, Jason AI, and the unified inbox. A single seat covers a founder running this entire motion alone.
One seat of orchestration software, one small pool of infrastructure — a stack sized for a founder's calendar, not a sales team's. Both bills grow only after the calls start converting: more mailboxes on ColdRelay when the motion scales past design partners, more Reply.io seats when outbound stops being a one-person job.
| Mailboxes | ColdRelay price / mailbox / month |
|---|---|
| 1–199 | $1.00 |
| 200–999 | $0.85 |
| 1,000–4,999 | $0.70 |
| 5,000+ | $0.55 |
Each mailbox sends 4 emails per day — 2 outbound to prospects + 2 warmup. ColdRelay provisions mailboxes on isolated Azure tenants with dedicated IPs; Reply.io handles the sending, sequencing, and inbox rotation on top.
Frequently Asked Questions
Is ColdRelay an alternative to Reply.io?
No — they're complementary layers of one stack. Reply.io handles the multichannel sequences (email, LinkedIn steps, call tasks), Jason AI assistance, contact management, and the unified inbox. ColdRelay provides the secondary domains, mailboxes, and dedicated IPs the email steps send from. You use both together: ColdRelay as the infrastructure layer underneath, Reply.io as the sequencing layer on top.
Do Reply.io's call tasks and LinkedIn steps count against the mailbox sending budget?
No. Only email steps touch your ColdRelay mailboxes and their budget of 4 sends/day each (2 outbound + 2 warmup). Call tasks go through the phone and LinkedIn steps through your LinkedIn account — separate channels entirely. That's part of why the multichannel design suits a small founder-scale pool: a 15-mailbox setup moves 30 emails a day, while calls and LinkedIn touches add pressure on the same prospects without consuming a single send.
How many mailboxes does design-partner outreach actually need?
Less than almost any other motion — most founders run it on 10-20. At 2 outbound sends/day per mailbox (4/day total including 2 warmup sends), 15 mailboxes covers a hand-picked list of 100-150 companies with multiple email touches over a few weeks, which is more design-partner candidates than most early products can absorb. ColdRelay provisions in about an hour and supports 100-150 mailboxes per domain, so when the motion graduates from design partners to pipeline, capacity is a same-week addition.
Should I let Jason AI write my replies?
Use it for triage, not voice. Jason AI is genuinely useful for categorizing the unified inbox — surfacing interested replies, filtering out-of-offices, flagging objections — so your daily block starts with the conversations that matter. But a design partner is deciding whether the founder behind the email is worth 20 minutes and a roadmap relationship; the words they read in a reply need to be the same words they'll hear on the call. Let the AI sort the queue and write the first draft if you like — the founder sends the final version.