The Underdog Show / 8 min read
Are Cold Calls Dead? Ryan Left Sales to Build a More Human Outreach Tool
Ryan moved from Chicago to Brazil and turned a lead-generation service into Zenith. On The Underdog Show, he explains why he still believes in cold outreach, what AI should handle, and why a real conversation needs a person behind it.

Ryan's first sales interview came with a test: three hours, a list of phone numbers, and a target of three meetings with strangers.
For the first two hours, he booked nothing. In the last hour, he booked four.
He credits a change in strategy and a fair amount of luck. That job became the start of a career in cold calling and lead generation. Years later, the experience would shape the software he decided to build.
When Ryan joined me on The Underdog Show, he had just returned from rock climbing in Brazil. He had moved there from Chicago after leaving his job, and he was running Zenith, an AI-assisted LinkedIn outreach product that grew out of his own service business.
I asked him a question I hear often from builders struggling to find users: is outreach dead?
Ryan believes cold calling is making a comeback. The provocative line on this episode's cover sets up that discussion; it isn't his verdict on the channel. His frustration is with generic automated messages that ask for attention without earning trust.
From making calls to building the tools behind them
Ryan described himself as assertive and willing to face rejection, though he does not consider closing deals his strongest skill. His early work taught him how to get a stranger interested enough to agree to a meeting.
Over time, his role expanded into sales enablement. He worked on small automations, web scrapers, CRM improvements, and data cleaning. He enjoyed the sustained concentration that work allowed. Sales conversations could be rewarding, but they also drained his social battery.
He was dissatisfied with the tools he used. He could see how he wanted an outreach system to behave, and he thought his experience could help him build something better.
Ryan described teaching himself programming while building the company, including object-oriented programming. Later, AI coding tools became a larger part of his workflow. He still considers systems thinking essential: he wants a clear picture of the interface and the underlying behavior before asking AI to implement it.
That part of the conversation interested me as a developer. Ryan came to software through years of using sales tools and noticing what made the work harder. He had a specific problem in mind before he had the technical skills to solve it.
Leaving a comfortable job and moving to Brazil
Ryan said his job in sales and sales enablement paid six figures, but the work had begun to feel meaningless to him. He had wanted to become an entrepreneur for a long time.
He also wanted to live abroad. Brazil appealed to him through its music, food, language, and culture. He had studied Portuguese before moving and arrived without friends or family there. By the time we spoke, he felt settled and had no plans to leave.
Leaving his job, starting the company, and moving countries happened together. He spoke warmly about his life in Brazil, while also describing long working days spent developing the business. Moving had changed where and how he lived; building the company still demanded substantial effort.
Zenith began as a service
For roughly the first two years, Ryan provided lead-generation and outreach services himself. The software was something he built in the background to support that work.
That gave him repeated exposure to the actual task: researching prospects, preparing messages, and managing conversations. The backend developed around work he was already doing for clients.
He said Claude Code later helped him turn that backend into an application other people could use. He spent time iterating on the frontend, onboarding, and user experience rather than treating the first generated interface as finished.
The workflow he described has a deliberate review step. AI reads a prospect's bio and posts, helps with research, and prepares messages. The user reviews and approves the messages before they go out.
Ryan readily admitted that the drafts can sound like AI. His expectation is that a person will edit them: remove awkward phrasing, make the tone more natural, and check that the message reflects what they actually want to say.
His argument for the product is that it reduces the administrative effort around a conversation while keeping the sender involved in the conversation itself.
What he shared about the business
At the time of the interview, Ryan reported about 5.5K in monthly revenue. He also said no clients had left the platform during the seven-month period he described.
Those are his reported figures from the conversation, not independently verified results or a guarantee of future performance. Prospects trying the software were part of his pipeline, so I have kept them separate from revenue already earned.
He shared one customer example: a user who, he said, closed a $6,000 deal during a two-week free trial. That story helps explain his enthusiasm, but it does not establish what a typical customer should expect.
The more useful part for me was understanding the process he believes led to those conversations.
Give the other person a reason to reply
When I asked what someone could do without his software, Ryan's first answer was to focus on the recipient.
He distinguished a thoughtful opening from a superficial compliment immediately followed by a pitch. A detail from someone's work can be a starting point, but the sender has to be interested enough to keep listening after receiving a reply.
He also warned against treating the second message as automatic permission to sell. If the conversation turns straight into a pitch, the first message can feel like a pretext.
His preferred progression is to ask a specific question, learn more, and gradually introduce relevant experience or a useful example. A meeting becomes an option once there is a reason for both people to continue.
I wouldn't turn that into a rigid four-message formula. The response matters more than the count. What I took from Ryan's explanation was the need to read what the other person says and decide whether there is a useful conversation to have.
He described attention and trust as two separate needs in sales. Getting noticed gives you an opening. It doesn't, by itself, give someone a reason to spend time with you.
Make the first useful experience small
I asked how a new founder can earn trust when they do not yet have much of a reputation.
Ryan brought up the requests he receives to test applications. Some ask for a large investment of time before the benefit becomes clear. He may be willing to visit a signup page, but spending hours learning an unfamiliar tool is a different commitment.
He is more likely to try something that delivers a small, understandable result in a few minutes. He pointed to free tools as one way to let people experience a creator's work before considering a larger product.
For a builder, that is a practical way to review an onboarding flow. What does the visitor have to do before seeing anything useful? Can they tell what they will get, and how long it will take?
Ryan also distinguished his audiences. Zenith was aimed more at small businesses doing B2B outreach. Other ideas he was developing were intended to be easier for individual founders to try. He did not expect every product to have the same entry point or sales process.
His own AI content needed editing too
Ryan had experimented with using AI to generate posts for X. He said the results often felt empty, even when he tried to avoid obvious AI phrasing. Generic posts about working hard as a founder weren't giving him the kind of presence he wanted.
He attributed much of his audience growth to a few posts that spread more widely, including one about his background and move to Brazil. He also acknowledged the role of timing and luck.
He was exploring tools to make drafting and scheduling easier, while keeping a final human review. Alongside that, he described an immersive storytelling idea in which people would direct AI-generated environments for fantasy experiences and public-domain literature. These were projects and plans he discussed, not established results from launched businesses.
The connection to Zenith was clear: he enjoys using AI to prepare material, but he still wants a person deciding what the finished experience should be.
What I took from the conversation
Ryan's path started with learning to talk to customers, then gradually building software around that experience. The service business gave him a working process to improve before he opened the tool to other users.
For me, the useful question from this episode is what we ask of people when we contact them. A signup, a demo, or a feedback call costs them time. A specific reason to care and an early useful result make that request easier to consider.
Ryan is still building his company and exploring new ideas. His experience offers a view of outreach from someone who has both made the calls and spent years trying to improve the tools behind them.
More from The Underdog Show
This article is based on episode 6, my conversation with Ryan. Business figures and customer examples reflect what he shared during the interview.
Explore The Underdog Show on YouTube
In the next episode, Steven and Cesare discuss finding customers before building and staying consistent with marketing.