Ben Congleton said he wasn’t selling before his co-founders had agreed that they weren’t selling. A meeting about a partnership had become a meeting about an acquisition. He understood what was happening, answered on instinct, and left his colleagues to catch up. For a founder building a company around communication, it was an awkward piece of timing.
The episode happened in 2013. Congleton later described the walk back to the office in the dark, the objections from his team, and the conciliatory email he sent afterward. Two of Olark’s four original founders eventually moved on, partly because of disagreements over the decision. Independence survived. Agreement took more work.
He has never presented that choice as a rule every entrepreneur should follow. Selling could have led somewhere worthwhile, too. What he wanted was the chance to keep shaping a business he would enjoy joining as an employee. The interesting question in his career is how someone learns to preserve that freedom while sharing it with other people.
A business before a driver’s license
Congleton grew up around Washington, DC, where government work supplied a familiar picture of adult life. His father, a professor, offered another: a flexible schedule and time to think and write about subjects that interested him. The attraction was control over the working day. Entrepreneurship would become his way of pursuing it.
In 1997, he and his cousin Roland started Nethernet Consulting with a $100 family loan. Web development led to web hosting, and their friend Kevin joined them. They bought a server they called Davinci, following the habit of naming machines after Renaissance painters. A teenage technology company evidently needed a little artistic patronage.
The business gave them hardware to explore and real problems to solve. At college, they rented an office at Virginia Tech’s corporate research center, furnished with cheap chairs and folding tables. It looked more official. But handing customer service to other people also separated the founders from the customers they were supposed to be serving.
The student who liked both paths
Virginia Tech gave Congleton a BS in Business Information Technology, another BS in Computer Science, and an MS in Computer Science. He then spent three years pursuing a doctorate at the University of Michigan’s School of Information. The academic route was a serious interest, rather than a holding pattern while he waited to start a company.
That distinction matters when telling his departure story. He objected when interviewer Andrew Warner tried to introduce him principally as a PhD dropout. Congleton liked the program. He had spent years dividing his attention between school and business, and the problem was that both activities could keep absorbing more of his time.
His reasoning was practical: try the startup before the doctorate created still more momentum toward an academic career. If the business failed, returning to study remained an option. He chose the sequence that, in his judgment, left more possibilities open. For someone interested in freedom, even the order of commitments deserved examination.
A small question in a large seminar
The idea behind Olark connected an academic discussion to an old business irritation. In a Michigan seminar, Congleton encountered Shoshana Zuboff’s work on disintermediation: the prospect of producers and buyers dealing directly over the internet. He wondered how those people would actually speak to one another once the intermediaries were gone.
He already knew live chat from the hosting business. The available tools had tended toward enterprise customers, with prices and assumptions that made less sense for a small team. A direct relationship between buyer and seller sounded promising; providing a manageable way to conduct it was a more concrete assignment.
The early product was called Habla. By 2009, the team had entered Y Combinator and launched a paid version under the Olark name. They used their own software to support their own customers. Each conversation could expose a difficulty that the people building the product were in a position to fix.
Enough capital to begin, enough customers to continue
Olark’s independence did not mean it had never accepted outside money. In a 2014 interview with Omer Khan, Congleton discussed a business that had taken $85,000 in outside capital and grown through customer revenue. Bootstrapping, in this case, describes how the company supported its growth after that small initial investment.
At the time of that interview, Olark served more than 5,000 customers across 151 countries. Those are historical figures, and their date is part of their meaning. A product aimed at modestly sized teams had found users far beyond the place where its founders lived. A local irritation had become an international business.
Congleton also described enjoying learning, team sports and rock climbing. There is a recognizable continuity between those interests and the business: unfamiliar problems, people working together, and a reason to keep trying. The company offered a setting for that appetite, provided it could continue paying its own way.
The support desk comes around again
One of Olark’s operating habits emerged when an employee went back to college. Andrew had handled support so effectively that the founders rarely heard customer problems directly. When he left in fall 2009, the four founders took turns answering chats and emails. Wufoo’s approach helped inspire the arrangement.
The change altered what reached them. Instead of receiving a ticket or someone else’s summary, they encountered a customer’s difficulty as it happened. As the product team, they could also act on what they learned. Olark extended those rotations as it grew, making customer service a shared responsibility across the organization.
Congleton has acknowledged that this creates coordination work. Knowledge has to circulate; complicated issues need the right specialist; scattered observations need a path into product decisions. The value lies in giving more people firsthand understanding. A support rotation is a recurring appointment with the consequences of the company’s work.
Words on windows, decisions in meetings
Olark drafted its company values together at an August 2012 retreat. Congleton remembers large sheets of paper taped to windows, with the group sketching ideas. The founders had been accustomed to consensus, and the team participated in defining the principles it would be asked to follow.
The values subsequently entered interview practices and hiring decisions. They changed, too: Congleton described replacing “Push each other” with “practice Empathy.” Changes went back to the company for approval. The wording mattered because it influenced behavior, although he also admitted that assuming good faith could delay candid discussions about performance.
There is some useful friction in that admission. A generous principle can become an excuse to postpone a difficult conversation. Congleton’s account treats values as things to apply and examine, with consequences for hiring, rewards and decisions. A pleasant phrase earns its place only when people can recognize it in the working day.
“Values give you a guide on how to hire, and make tough decisions.”Ben Congleton
Lessons he could not delegate
Congleton has also written about a conflict he handled poorly. Impatient with a dispute between two teammates, he made an executive decision and assumed the matter was settled. Then he left for vacation. His co-founders inherited the unresolved problem, and their response on his return was understandably direct.
He used the experience to argue for structured feedback from colleagues. Olark developed an internal tool, Wulu, for collecting written peer feedback and later made it available to other teams. His own example asked people to reflect on the positive and negative effects he had at work. That is a fairly demanding invitation to put in writing.
In a conversation with Claire Lew, he identified self-awareness as a leadership lesson he wished he had learned earlier. Together, these accounts give his idea of independence a necessary complication. A founder may choose where the company goes, but other people experience how he gets it there. They have information he cannot supply for himself.
A T-shirt opens a door in Mumbai
In 2013, a woman at a Mumbai Starbucks commented on Congleton’s Virginia Tech T-shirt. She turned out to be Aditi Avasthi, founder of the education company embibe and an early Olark customer. A casual exchange became a visit to her office and an impromptu presentation.
He had flown to India for a wedding. The conversation was absorbing enough that he returned to his hotel with only an hour to spare. Seeing the team and hearing about its work gave him context that a customer record could not convey. His clothing had performed an unexpectedly productive piece of business development.
Years later, he returned deliberately to those open-ended customer conversations. He wanted to understand people’s roles, goals and larger challenges, including how Olark helped or hindered them. The connection runs through his career: tools are more useful when their makers keep meeting the people on the other side.
A company he still wants to join
At its tenth anniversary in 2019, Olark’s founders described a business that had generated tens of millions of dollars in revenue while remaining small and remote. Matt Pizzimenti’s account included a parental leave policy created years before anyone on the team had children. Some decisions were investments in a future they had not yet reached.
Today, Olark identifies itself as a fully remote, B Corp certified team serving more than 12,000 businesses. Congleton remains its Chief Executive Olarker, based in Palo Alto. Its current product offering combines human live chat with AI agents, bringing a new set of tools to the customer conversations that first interested him.
The durable ambition is a workplace worth returning to. Congleton’s record includes abandoned possibilities, awkward decisions and lessons repeated until they became practices. Freedom, for him, has required customers willing to pay, colleagues willing to disagree, and enough attention to keep hearing both. The company continues one conversation at a time.