Sales teams talk a lot about automation, but the hardest part of the job still happens live. A rep can prepare for a demo, memorize the pitch, and study the product inside out, then still get thrown off by one technical question at the worst possible moment. That pause matters. It breaks momentum, weakens confidence, and often turns a promising conversation into a slower and colder deal.
That gap is what makes the story behind Jun Kim and Aside interesting.
Aside did not begin as a broad, vague AI idea built to chase hype. It started from a very specific problem inside technical sales. Reps needed better answers during live calls, not just better follow-up tools after the call was already over. Jun Kim understood that problem from close range, and that gave Aside a grounded starting point. From there, the company grew into a Y Combinator backed startup and then into a much bigger vision around AI-native work, browser automation, and software that can take action instead of just generating text.
Who Is Jun Kim
Jun Kim is the kind of founder whose background makes Aside feel less accidental and more inevitable.
He has described himself as someone who started coding at nine, built his own operating system at twelve, and launched a developer community while still young. Later, he joined the founding team at Airbridge, where he helped scale the business into a serious B2B SaaS company. That stretch matters because it gave him exposure to both product building and the operational reality of how software companies grow.
A lot of startup stories sound polished in hindsight, but Jun Kim’s path feels more builder-first than image-first. He was not simply trying to attach AI to a random workflow. He had already spent years shipping products, learning how teams work, and seeing where friction actually slows people down.
That foundation shaped how Aside entered the market. Instead of starting with a giant promise about changing everything at once, the company focused on a painful moment that happens every day inside sales conversations.
The Sales Knowledge Problem That Sparked Aside
In enterprise tech sales, the most important part of the process is often the live conversation. It is also the part where many teams still struggle.
A rep can handle discovery, rapport, and high-level positioning, but when the prospect dives into security, architecture, integrations, compliance, or product edge cases, the room changes fast. Suddenly the rep is no longer judged on enthusiasm. They are judged on clarity, precision, and speed.
That is where many deals lose energy.
When a rep says, “Let me get back to you,” it may sound harmless. In reality, it creates distance. The buyer stops feeling momentum. Confidence drops. The call moves from active progress to delayed follow-up. Over time, that pattern becomes expensive because companies respond by pouring money into onboarding, sales coaching, internal training, mock calls, and enablement programs that still do not fully solve the in-the-moment problem.
Aside was built around this exact gap.
The idea was simple in the best way. What if a rep could get the right answer in real time, pulled from the company’s own knowledge, instead of relying only on memory, scattered notes, or the hope that a sales engineer would jump in at the right second?
That question gave Aside a clear reason to exist.
How Aside Started as a Live Sales Copilot
Aside first showed up as a live AI copilot for sales calls. The product’s early pitch was direct and easy to understand. It listened during calls and surfaced answers from sources like company docs, Slack threads, HubSpot data, and past conversations so sales reps could respond without losing momentum.
That positioning was strong because it stayed close to the real workflow.
Instead of asking teams to rebuild their systems or live inside yet another dashboard, Aside aimed to support the moment that mattered most. A hard question came in. The product helped the rep respond. A key pain point was missed. The system nudged the rep live. A strong answer had been used before in a winning call. Aside could bring that answer back at the right time.
This is where the company stood out from a lot of AI tools that only help after the fact. Many products summarize meetings. Many generate notes. Many write follow-up emails. Those features can be useful, but they do not fix the live performance problem. Aside went after the harder moment.
That made the product feel practical, especially for fast-moving tech teams onboarding newer reps or trying to reduce the gap between top performers and everyone else.
Why the First Version of Aside Made Sense
One reason Aside feels like a believable startup story is that the first product was narrow enough to matter.
The company was not trying to solve all of sales. It was not trying to become a giant operating layer for every team from day one. It focused on something specific, expensive, and repeatable.
Technical sales is full of hidden friction. Products change quickly. Documentation gets messy. Internal knowledge lives in too many places. New reps take time to ramp. Even experienced reps can miss details under pressure. When all of that shows up during a live call, confidence becomes uneven and conversion suffers.
Aside turned that messy environment into a simpler promise. Let the company’s best knowledge show up when it is actually needed.
That is a powerful angle because it connects AI to real business value. Better live answers can shorten ramp time, support onboarding, improve consistency, and help more reps sound sharp without needing years of product depth. For growing startups, that is not a small improvement. It can directly affect pipeline quality and close rates.
How Jun Kim’s Airbridge Experience Shaped the Startup
Jun Kim’s background at Airbridge is one of the most important parts of this story.
Aside’s YC launch materials explain that Jun and co-founder Chanhee Lee were founding engineers at Airbridge, and that Jun worked with more than fifty reps as a solutions consultant, the person responsible for answering technical questions during calls. That detail matters because it gives the company’s origin a real operating context.
This was not outsider brainstorming. It was pattern recognition from experience.
When a founder has sat close enough to the problem, the product usually sounds sharper. The pain points are more concrete. The use case is easier to explain. The first product decision tends to be more focused because the founder is not guessing where value might be. He has already seen where time is wasted, where deals slow down, and where teams depend too heavily on a handful of experts.
That seems to be the case with Aside.
Jun Kim did not just understand product. He understood the strain of technical sales support, the burden placed on specialists, and the cost of delayed answers. Aside feels like a startup built by someone who had been part of the workaround for too long and finally decided to build a better system.
The Road to Y Combinator
Y Combinator backing gave Aside a major credibility step, but the story is more interesting than the badge itself.
By the time Aside entered YC’s Fall 2025 batch, the company already had a clear narrative. It was not selling a generic AI productivity promise. It had a specific customer pain point, a clear workflow, and a founder story that matched the product.
That combination matters in early-stage startups.
Good startup ideas are often easier to trust when the product, the timing, and the founder background line up naturally. Aside was entering the market at a time when AI tools were everywhere, but most teams were still figuring out where AI created real leverage instead of just novelty. Aside’s answer was strong because it tied AI to decision moments inside revenue conversations.
YC did not create the core idea, but it helped validate that the company had found a serious starting point. It also made it easier for the market to see Aside not just as a feature, but as a company with room to expand.
That expansion became the next chapter.
From a Sales Copilot to a Bigger AI Vision
One of the most interesting parts of Aside’s story is that it did not stay locked inside its first use case.
Today, Aside’s Y Combinator profile presents the company much more broadly. Instead of describing only a live assistant for sales calls, Aside is now framed as an operating system for the AI era and an AI browser that can act on a user’s behalf.
That shift says a lot about how the company sees the future.
The original product focused on real-time answers during calls. The newer vision is about something larger. Aside wants AI to work directly inside the software people already use, across tools like Gmail, Notion, Slack, Figma, banking apps, and internal systems, without requiring heavy integrations every time.
This is an ambitious move, but it also feels like a logical one.
Once a company starts by solving knowledge access during a live workflow, the next question becomes obvious. What happens when AI moves beyond answering and starts executing? What happens when the product does not just surface information, but actually completes tasks across the browser, remembers context, reacts to events, and continues work across sessions?
That is where Aside appears to be heading.
Why the Browser Has Become the New Battleground
The browser is where modern work already happens.
People sell in browser tabs. They manage projects in browser tabs. They review documents, message teams, edit creative work, and move data across web apps all day. For years, software companies have tried to own part of that workflow through individual tools. The bigger opportunity now may be owning the layer that moves across all of them.
Aside’s newer positioning taps directly into that idea.
By framing the product as browser-native AI, the company is betting that the real value is not only in helping users think faster, but in helping them act faster inside the tools they already depend on. That includes using browser context, sessions, passkeys, and persistent memory to let AI complete work instead of stopping at suggestions.
That is a bigger vision than sales enablement alone.
It also helps explain why Aside stands out in a crowded AI market. A lot of startups are still competing to be copilots. Aside appears to be pushing toward becoming a working layer across digital tasks.
What Makes Jun Kim and Aside Stand Out
Jun Kim and Aside stand out because the company’s story has a believable progression.
First, there was a sharp entry point. A painful and familiar sales problem created a focused use case. Then came product validation, Y Combinator backing, and a broader expansion into a larger AI vision.
That sequence matters.
Many startups try to start broad and then struggle to find urgency. Aside seems to have done the opposite. It started with a clear pain point and then widened the lens after establishing why the team had the right to build in the space.
There is also something important about Jun Kim’s founder profile. He comes across as a product builder with long-range conviction, not just a trend chaser. His public bio points to years of making things, from early technical projects to scaling Airbridge to building consumer-facing work beyond SaaS. That kind of range can matter in AI because strong products in this category need both technical depth and product taste.
Aside also benefits from good timing. AI adoption is no longer limited to experimentation. Teams now want systems that fit into daily work, reduce tool friction, and save time without creating new complexity. A company that can move from real-time assistance to real execution has a strong opening in that environment.
What Founders Can Learn From This Story
There are a few useful lessons in how Jun Kim built Aside.
The first is that strong startup ideas often come from narrow pain, not broad ambition. Aside did not begin with a giant abstract mission. It began with one moment where teams repeatedly lost time, confidence, and deal momentum.
The second is that founder proximity still matters. It is easier to build something useful when you have lived close to the problem, seen the workarounds, and understand why existing solutions fall short.
The third is that a focused starting point can open the door to a much bigger company. Solving live answers for tech sales may sound specific, but it gave Aside a real wedge into a broader question about AI-native work, action-taking software, and the future of the browser.
That is what makes the story worth watching. Jun Kim did not just build a tool around a temporary trend. He appears to be using a sharp problem as the entry point into a larger software shift.
