Efe and Yesglot: Automating Multilingual Apps for Developers

Efe, a developer, transformed a personal frustration with traditional translation workflows into yesglot.com, an AI-powered tool that integrates seamlessly into Git-based development, redefining internationalization for modern applications.

Cold Open

In the spring of 2026, after a year spent on evenings and weekends, Efe launched yesglot.com. The initial reception on platforms like Reddit and Hacker News was positive, but the true validation arrived within seven days: a paying customer. This moment, a quiet confirmation of a year's sustained effort, marked the transition from a personal project born of frustration to a nascent business addressing a pervasive developer problem.

Thesis

Efe's journey with yesglot.com illustrates a founder's commitment to solving a deeply felt personal pain point through elegant, workflow-native automation. The project represents a deliberate departure from established, cumbersome translation paradigms, instead prioritizing developer experience and seamless integration within existing Git-based workflows, leveraging AI to streamline a historically manual and expensive process.

Origin / Background

Efe's path to building yesglot.com began not with an entrepreneurial spark, but with a practical frustration encountered in a prior role. "I was working at a company where we had to support multiple languages," Efe recounted in a blog post detailing the project's genesis. The process of internationalizing software, a common requirement for many applications, proved to be a significant bottleneck. It involved a series of manual steps: exporting text, sending it to human translators, waiting for their work, and then re-importing the translated content. Efe described this cycle as "a nightmare," highlighting the inefficiency and cost inherent in systems designed for an era before advanced artificial intelligence. This direct experience with the limitations of traditional translation workflows provided the foundational insight for what would become yesglot.com. The problem was not abstract; it was a recurring operational challenge that demanded a more integrated and automated solution.

The Build

The conceptual groundwork for yesglot.com began in late 2024, when Efe started exploring how AI could alleviate the translation headaches experienced firsthand. The initial phase involved extensive research into existing solutions, which Efe found to be "clunky and expensive," reinforcing the conviction that a new approach was necessary. The core principle guiding the development was a focus on the developer's workflow. Efe aimed to create a tool that felt "natural to a developer's workflow," rather than imposing new processes or requiring constant context switching.

This led to the decision to build yesglot.com around a Git-based integration. The vision was simple: a developer would drop a yesglot.toml configuration file into their repository, and the system would automatically open pull requests with AI-generated translations. This approach eliminated the need for separate dashboards, manual exports, or waiting periods, promising a seamless experience.

The technical implementation presented several challenges. One significant hurdle involved the selection and integration of appropriate AI models. Efe initially considered fine-tuning proprietary models but quickly recognized the "cost and complexity" associated with such an endeavor. The strategy shifted to leveraging existing large language models (LLMs) through their APIs, a pragmatic decision that allowed for faster iteration and reduced overhead.

Another complex aspect was the robust integration with Git. Developing a system capable of reliably opening pull requests, intelligently handling potential merge conflicts, and ensuring translations remained synchronized with source code changes proved to be "probably the trickiest part" of the entire build. This required meticulous engineering to ensure the automation was both powerful and dependable, without disrupting a developer's existing version control practices.

Beyond the technical architecture, Efe also grappled with the commercial model. Early considerations included a per-word pricing structure, a common model in the traditional translation industry. However, this felt too much like "the old way" and was ultimately discarded in favor of a subscription-based model tied to factors like repository activity or the number of supported languages. This pricing pivot reflected the product's core value proposition: a continuous, integrated service rather than a transactional one-off translation. Over the course of a year, working predominantly during "evenings and weekends," Efe steadily brought yesglot.com from concept to a functional, deployable product.

The Break

After a year of development, yesglot.com officially launched in the spring of 2026. Efe shared the project on developer-centric platforms, including Reddit's r/SideProject and Hacker News, seeking initial feedback and early adopters. The public response was "overwhelmingly positive," indicating a clear market resonance for a tool addressing a long-standing pain point. This initial validation quickly translated into tangible traction. "A few early adopters signed up," Efe noted, providing crucial real-world usage data and feedback that would inform future development. The most significant early milestone arrived within a week of the launch, when yesglot.com secured its "first paying customer," transforming the side project into a revenue-generating venture. This moment underscored the viability of Efe's automated, developer-centric approach to multilingual app development.

The Present

In the period following its launch, yesglot.com continues to evolve. Efe's current focus is directed towards enhancing the core product, specifically improving the accuracy of the AI-generated translations and expanding the range of supported languages. Beyond technical refinements, there is an emphasis on fostering a community around the tool, suggesting a long-term vision that extends beyond pure automation to include collaborative development and shared best practices. While yesglot.com has moved beyond its initial prototype phase and secured its first customers, it remains, as Efe described it, a "side project," albeit one experiencing growth. The ambition is clear: to establish yesglot.com as "the default way developers handle internationalization." Efe reflected on the journey, stating, "The satisfaction of seeing something you built from scratch solve a real problem for people is immense."

The Unanswered

Efe's narrative of building yesglot.com highlights the challenges and rewards of a year-long side project, yet it also surfaces inherent tensions. The ambition to become "the default way developers handle internationalization" suggests a significant scaling effort, which contrasts with the current status as a "side project." This raises questions about the long-term strategy for growth and resource allocation, particularly given the demands of a full-time role alongside the continuous development of a complex AI-driven product. Furthermore, while the tool aims to streamline translation, Efe acknowledges that the goal is not to "replace human translators entirely." This balance between AI automation and the necessity of human oversight presents an ongoing challenge, particularly as the product scales and the nuances of language quality become more critical across a broader user base.

Pull quote: “The satisfaction of seeing something you built from scratch solve a real problem for people is immense.”