A $3,000 roaming bill is an unusually expensive souvenir. For Yury Yakubchyk and his friends, returning from Austria, it also became an invitation to investigate the business that had produced it. The charge was sufficiently irritating to suggest that other people might appreciate a different arrangement. Wing, the wireless company he cofounded, grew out of that complaint. There are cheaper ways to find an idea, though few come with such an explicit invoice.
The episode offers a useful entrance to a career whose company names can otherwise seem unrelated. Wing sold phone service. Life House brought software into hotels. Elemy became another substantial undertaking. Later came the investment and company-building work of Cold Start. Read as a list of sectors, the sequence looks restless. Read as a succession of encounters with awkward services, it begins to have a recognizable logic.
Yakubchyk was born in Belarus, moved to Canada as a child, and went to high school in Queens. There, neighborhood businesses supplied a practical education in making a living independently. Shops, jewelers, and other small enterprises made ownership visible. Entrepreneurship had addresses and opening hours. It was something a person could do on the next block, long before it became a vocabulary of rounds, valuations, and exits.
College widened that sense of possibility. At Johns Hopkins, he encountered people whose families had built businesses. The attraction was becoming concrete: choose a problem, assemble the resources, and accept responsibility for what happens next. The recurring interest in consumer businesses with dissatisfied customers would eventually give that attraction a commercial shape. An unpleasant experience could be an opening, provided someone was willing to do the work behind a more pleasant one.
Two founders, two kinds of expertise
Life House took form in 2017, with Rami Zeidan as Yakubchyk's cofounder. The partnership joined a hotel and real estate executive to a software entrepreneur. That division mattered. A hotel contains a surprising number of businesses in miniature: reservations, housekeeping, pricing, staffing, property, marketing. Improving the guest's evening requires those businesses to cooperate before the guest ever asks for a key.
The early proposition combined the sociability associated with hostels with the comfort and convenience of a hotel. Communal space had a purpose beyond looking handsome in a photograph. It gave travelers somewhere to meet. The company also planned a digital social layer so that guests could connect before arrival. The experience was meant to begin before anyone stood in a lobby deciding whether to approach a stranger.
The finances revealed a second design choice. In May 2018, Life House announced $40 million across two different pools: $10 million in venture funding and $30 million in real estate capital. Those figures paid for different kinds of work. The operating business and its technology needed one form of backing; the properties needed another. A room can be booked through software, but its walls still require a building.
Keeping those pools distinct allowed the operating company to pursue an asset-light structure while property capital supported development. The distinction is easy to lose beneath a single funding headline. It is also central to understanding the enterprise Yakubchyk helped build. The ambition depended on making a repeatable operating system coexist with places that were meant to feel individual.
The hotel behind the screen
By the October 2018 launch, Life House reported $70 million in combined venture and real estate funding. The first properties were planned for Miami's Little Havana and South Beach. Yakubchyk was chief technology officer. His earlier role at Wing had also been technical, placing him in the less photogenic part of consumer businesses: the machinery that makes a promise possible.
The launch included a direct-booking system, a mobile app, and a social network for travelers. Room choices ranged from private accommodation to shared rooms designed for groups. Full-size bunk beds made an appearance. The details put the company somewhere between familiar categories, with software helping to connect arrangements that a conventional hotel might handle through separate systems and separate queues.
Zeidan described an architecture built around the business from the start. Accounting, digital marketing, guest profiles, and communication were part of the design. Guests could use the app for room access and requests. The point was to bring routine transactions into a common system, leaving the property's character to do more of the work of hospitality.
For a technologist, a hotel is an exacting place to test an abstraction. A reservation has a date. An unsold night disappears. A guest notices a failed handoff immediately. The room cannot be patched after checkout in quite the way a web page can. That tension makes Life House a revealing chapter in Yakubchyk's story: software had to answer to a physical experience, with people present to judge it.
A business can begin on a couch
Before those funding announcements, Yakubchyk had been renting out his own bedroom in Manhattan while sleeping on a couch. He recalled charging $180 a night. The arrangement expanded into more apartments and, eventually, an interest in hospitality. He also tutored and learned to code for freelance work. The early career contained several ways to pay the bills, with very little resemblance to a polished founder biography.
The social cost stayed with him. He remembered pressure to take a conventional banking job. He also remembered enjoying conversations with international guests. Those encounters helped make hospitality attractive. The couch was uncomfortable enough; the visitors, apparently, were interesting. A temporary way to support one venture supplied material for another.
There is a temptation to tidy such episodes into inevitability. The more useful reading leaves the uncertainty intact. At the time, an apartment rental was income. A wireless startup was work in progress. The relationship between them became clearer as opportunities appeared. Early business life often has this untidy quality: survival arrangements and promising experiments occupy the same calendar, and sometimes the same living room.
The people who stayed in the picture
Yakubchyk graduated from Johns Hopkins in 2013. The university continued to matter well beyond the credential. When he discussed Elemy in February 2022, he said its six founding team members were friends from his Hopkins years. An alumni network can sound like an institutional abstraction. Six friends taking on a company together is a more tangible description.
He also identified economist Steve Hanke as a significant mentor, crediting Hopkins with developing his habit of reasoning from first principles. Those two influences sit comfortably together: a way of examining problems and a group of people with whom to examine them. One supplies a discipline; the other supplies relationships that have already survived something longer than an introductory meeting.
His description of the difficult part of starting a business was refreshingly workmanlike. Moving an idea from inside his head into a viable company demanded resources, patience, and setbacks. The surprise was how consequential college friends became. Even with the benefit of hindsight, he did not describe their eventual collaboration as something they had all foreseen.
His advice to students began with three words: “Focus on action.” He urged them to put concepts in front of customers and allow the first version to change. That makes friendship only part of the explanation. Familiar colleagues may help a team begin; contact with customers determines what the team should actually build. Both relationships require listening.
“Focus on action.”Yury Yakubchyk / February 2022
Leaving room to think
Yakubchyk's account of his working style complicates the picture of a founder permanently performing enthusiasm. He has described himself as inward-oriented, with a relatively open calendar and a preference for time to think. The story is a useful counterweight to the public milestones. A full schedule makes an impressive screenshot. It does not, by itself, show whether a difficult question has received an answer.
By fall 2022, he was also speaking about supporting students who wanted to pursue entrepreneurship, including through Hopkins' Demo Day and summer incubator. He wanted innovation to be treated as a viable career choice. His argument concerned the difference between a university's linear structures and the less orderly work of starting something. A syllabus can tell a student what comes next. A customer has no obligation to follow it.
He resisted prescribing a single route. His examples included founders who changed direction and founders who drew on long experience within one field. Both paths could produce a functioning company. His own career makes that openness understandable. Telecommunications and hospitality did not require identical knowledge. They did require a willingness to notice what customers disliked and learn enough to attempt a response.
This is a modestly subversive position for someone asked to give career advice. People usually want a sequence they can copy. Yakubchyk's answer leaves more room for judgment, accident, and revision. It also places responsibility back on the prospective founder. An example can make a path imaginable; it cannot decide whether that path fits the person standing at its beginning.
Now, on the other side of the table
Today, Cold Start's team page identifies Yakubchyk as chairman. The firm presents itself as an active company-building partner, bringing operating experience as well as capital. Its portfolio spans consumer businesses, financial technology, and artificial intelligence, including names such as Blank Street, Finom, and Vercel. These are the firm's listed relationships, rather than a measure of any one individual's ownership.
The shift puts his earlier experiences in a different context. A founder who has worked across businesses can become useful to other founders because the practical questions recur. Who should join? What needs to be built first? Which customer complaint deserves a company, and which deserves a better support response? Capital gives those questions consequences. Operating experience offers some material with which to answer them.
The investor’s role extends his work beyond the boundaries of one operating company. The industries and titles keep changing, but a familiar question carries through the story: where does an awkward experience suggest an opportunity to organize things differently? It is a question that can keep a company builder occupied for quite some time.
The roaming bill is still a good place to end. It was a small encounter with a large system, sufficiently annoying to prompt a closer look. Most people have plenty of those encounters. Yakubchyk's career has repeatedly continued past the complaint, into the particulars of a business. Somewhere between the invoice, the couch, and the hotel booking sits the question that makes the story interesting: what would it take to do this better?