Michael Kansky and the price he almost corrected

Michael Kansky began composing an irritated email. A review site had looked at his live chat software, liked it, and published the wrong price. He charged $9 a month. The reviewer had written $21. For someone trying to keep a tool affordable for small businesses, this was a rather unhelpful compliment.

Then he stopped typing. He could correct the number, or wait and see whether anyone objected. He waited. Customers were willing to pay the higher amount. A stranger’s mistake had supplied an experiment he had not thought to run himself. The price stayed. His imagined ceiling had turned out to be considerably lower than his customers’.

There is something pleasingly untidy about this episode. Nobody conducted a grand pricing exercise. Nobody announced a transformation. A founder nearly sent an email, reconsidered, and learned something. Kansky’s career contains several such moments, when a useful answer arrived disguised as an inconvenience. The difficult part was allowing it to remain inconvenient long enough to understand it.

01 /A chat window looking for a business

He arrived in the United States from Ukraine as a refugee in 1997, bringing an interest in information technology and an unfinished college education. Consulting became his route into American working life. Between 1998 and 2006, he worked with roughly two dozen companies, moving across industries and seeing how different organizations handled the same ordinary problem: somebody needed help.

A dating website supplied an unexpected beginning. Kansky built one for fun and added a chat feature so users could communicate. Then another use became apparent. Visitors might also want to speak to the person running the website. Technical support was sitting inside the same little window as social conversation. Other website owners could presumably use such a window too.

His consulting work gave the idea a practical setting. He had seen customers held up by inefficient service operations. After dinner, he went to his basement and wrote software. The early product was free. This made it easy for businesses to try and left him with a harder question: would its users value it enough to pay?

LiveHelpNow’s product story is usually dated to 2005 in his interviews. In 2009, he introduced a paid option. The response persuaded him that the project could support a business. Leaving salaried work was the personal decision behind that commercial result. A tool could have enthusiastic users indefinitely; a founder still had to decide when to trust it with the rent.

1. 1997Arrives in the US from Ukraine
2. 2005Begins the live chat project
3. 2009Introduces a paid option
4. 2026Leads AEO Content as co-founder and CEO

02 /An inexpensive seat at a bigger table

By his February 2019 conversation with Nathan Latka, Kansky was explaining a business whose customers were not confined to the small firms suggested by its low entry price. He described a substantial enterprise clientele. The interviewer pressed him to distinguish the price of one seat from what an organization paid across a whole deployment. It was a useful distinction, and a revealing exchange.

A cheap individual license can belong to a sizeable account. Count the agents, the systems and the recurring payments, and the apparent scale changes. Kansky had financed the company himself, using money earned through consulting. The business had grown around people choosing the software, rather than around an outside investment story. Its economics required a closer look than the first price tag invited.

The product also became broader than the chat window that started it. LiveHelpNow’s knowledge base describes linked chat, ticketing and information tools, with previous conversations available to agents. Its current platform brings support channels and automation together. For a customer, those connections can mean fewer attempts to explain the same problem. For an agent, they can mean finding an answer without starting the investigation again.

That is the work hidden behind the familiar little chat button. The visitor sees a box and a blinking cursor. Behind it, somebody needs a history, an answer, a colleague or a route to the right person. Kansky’s technical career has repeatedly returned to that backstage machinery. A pleasant greeting is easy to type. Making the next exchange useful takes rather more engineering.

03 /The customer needed somebody at the keyboard

Software created a second request. LiveHelpNow customers wanted round-the-clock service but lacked the people to provide it. Kansky responded by creating HelpSquad. Before building the operation, he visited six customer call centers and studied how they worked. For a software founder, it was a sensible change of classroom: the answer was being practiced in somebody else’s office.

He described HelpSquad in 2020 as a collection of six-person squads, each with a coach. Coaches learned what clients needed and passed that understanding to their teams. There were twelve teams in the structure he described then. The name had an organizational meaning. Smaller groups gave the work a manageable unit, with an identifiable person responsible for understanding each client.

The challenge was trust. A business might happily install another company’s software while hesitating to let its people speak to customers. HelpSquad had to prove it could represent the client appropriately. A trial gave customers a way to watch that happen before committing. Here, the product demonstration was an actual conversation, with the client’s reputation attached.

The progression is unusually concrete. First, give a business a way to answer. Next, recognize that the business still needs someone available to answer. Solving the first problem exposed the second. It also widened Kansky’s responsibilities from what software could do to how a group of people would use it, hour after hour, when the founder was elsewhere.

04 /The inventor behind the conversation

There is a formal engineering record alongside these company stories. United States patent 9,178,950, granted on November 3, 2015, names Michael Kansky as inventor and LiveHelpNow as assignee. It concerns establishing and monitoring client sessions over a communications network. The language is dry enough to discourage casual conversation, which is unfortunate given the subject.

Its description deals with an operator working across chat, email or tickets and knowledge base information. It also describes private messages between operators during a customer conversation. These are practical details of helping: finding something, asking a colleague, keeping the exchange moving. The technical document makes visible the number of small arrangements required before a simple interface can feel simple.

Further grants in the same area followed, including patents issued in 2017 and 2019. They place Kansky’s name on specific technical work, beyond the more elastic vocabulary of entrepreneurship. A founder can speak eloquently about customers and still leave the engineering to others. In this part of his record, there is a named inventor and a set of described mechanisms.

05 /A founder can become the queue

Growth presented a different kind of service problem inside the company. In his 2021 SaaS Podcast conversation with Omer Khan, Kansky described LiveHelpNow spending several years around $3 million in annual recurring revenue. He also described spreading himself across six businesses. Those are historical figures from that conversation. They capture a period when having customers and knowing how to expand had become separate questions.

He brought in Jason O’Neill to run operations. The admission underneath that decision is more interesting than another growth claim: routing decisions through the founder can leave everybody waiting. The engineer who wanted to shorten customer queues had encountered a queue of his own making. Delegation became part of the design problem. The organization needed a route around his personal availability.

His later role listings reflect that division of work. LiveHelpNow identifies him in executive directories as founder and CTO, while O’Neill is listed as CEO. The title change gives the story a useful punctuation mark. Building the thing and running every part of the thing had become different jobs, with different claims on the same limited working day.

06 /The next intermediary has no face

By October 2026, another venture appears prominently in Kansky’s work. AEO Content names him co-founder and CEO, alongside CTO Alex Shortov. The company works on how websites appear in AI-generated answers. It describes Kansky as leading research that informs its scoring system, while Shortov turns that work into software and content infrastructure.

The familiar problem now has an unfamiliar gatekeeper. A business can publish information and still fail to appear when a prospective customer asks a question. AEO Content audits websites for whether answer engines can find, understand and cite their material. The ambition moves an earlier step into the exchange: help the business become part of the answer before anyone opens a support conversation.

On October 17, 2026, Kansky published an article about what ChatGPT tells buyers about software pricing. His argument concerns old prices resurfacing from third-party material and the need to make current prices readable. He advises comparing the number a buyer hears with the live pricing page, then tracing the discrepancy. After the $9-and-$21 episode, the subject has a certain comic persistence.

The situations differ, of course. One mistaken price revealed room to charge more; a stale price can confuse a purchase. But both involve the gap between what a business says and what someone else repeats. Kansky is still working near that gap. The messenger has become more complicated. The business owner still has to discover what the customer has been told.

“Always start with a need and then come up with a solution.”

Michael Kansky · 2021

07 /People, with names

His own explanation of what drives him is restrained: “curiosity, open mindedness, and empathy to the end user.” He has resisted the more theatrical account in which relentless grit explains everything. Curiosity fits the available episodes rather well. It leaves room for the reviewer’s error, the customer’s staffing request and the possibility that a founder’s first answer needs revising.

Away from the companies, he has spoken about enjoying a small, secluded mountain cabin near a lake. It is an appealing counterpoint to a career arranging conversations. A person can spend his working life improving access to other people and still appreciate a place with fewer interruptions. The chat window may remain open for customers. Its inventor is allowed an afternoon without one.

The price he almost corrected remains a useful place to leave him. His initial instinct was perfectly understandable: fix the error. What followed required a little patience and a willingness to be surprised. For someone who has built businesses around listening, it was a particularly economical demonstration. This time, the important part of the conversation was the email he never sent.