The Spark That Became Lighthouse
Growth often begins with early memories that seem simple at the time yet reveal themselves years later.
For Dimitri Trembois, that beginning can be traced back to a childhood in the Bay Area where he watched companies rise and reshape the world around him. He remembers seeing the Google IPO as a kid and feeling fascinated by the idea that something so powerful could be created by a small group of people with a vision. He recalls telling his parents to put all their money into Google simply because it felt exciting. He had no understanding of what an IPO truly meant, but the spark was real. It blended curiosity, imagination, and a growing interest in business that would later guide him toward Lighthouse.
The environment he grew up in shaped him. Dimitri lived through the shift from slow, dial up connections to a world where the internet expanded at the same speed he did. As a child, he spent much of his time offline because getting online was not easy. Then as he entered his teenage years, the internet arrived with new energy and possibility. He felt as if he was learning and maturing at the same pace as the technology around him. It created a sense of alignment between his curiosity and the world he watched come alive. He admired products that were simple and intentional. Companies like Apple inspired him because they focused on quality and thoughtful design instead of clutter. Something in him recognized that good ideas deserved clarity. That sense of clarity would eventually become central to his work.
After college, Dimitri wanted to start a business but quickly discovered that the tools available at the time were not built for someone without technical experience. The best option was a drag and drop website builder, but that could not support the depth of what he hoped to create. He tried to learn to code. He devoted three months to real effort. He practiced until he reached simple outcomes like a hello world program and a few basic containers on a site. Yet something felt misaligned. He could feel that coding did not bring energy or possibility to him. As he recalls, he reached a point where he said to himself, “This is just not for me.” That realization guided him toward a different direction.
Since he had a strong interest in business and valued performance based work, Dimitri moved into sales. He entered as an SDR and aimed to become an AE who could sell into major accounts. He wanted a path where he could leverage his ambition rather than trade hours for progress. Sales gave him that opportunity. He rose through two companies until he reached the top of the sales organization. It affirmed that he had the discipline and mindset to grow without limits. At the same time, new tools were emerging that caught his attention. He tried early versions of chat based models and thought they were helpful but not transformational. Then he tried Claude and encountered something entirely different.
The moment he used Claude artifacts, something shifted. He could type out a description of a website or application and watch the system build a functional version. He describes it as a “magical moment” because it allowed him to see code appear before his eyes in a way that made creation feel possible. It was not perfect, but it revealed a path he once believed was closed. He realized he could build without being a traditional developer. This gave him the confidence to pursue his first product idea.
Meeting IQ grew directly from a challenge Dimitri faced as a sales rep. In the early years, he would spend extensive time researching each person he met with, learning about their company, anticipating objections, and preparing thoughtful questions. As his schedule became full, this research became difficult to maintain. He still needed it, but he had less time to give. So he built a tool that scanned the user's calendar, gathered information about the prospect through their email address and LinkedIn, and created a detailed report that included background, possible objections, recommended questions, and relevant tips. It then delivered this report automatically moments before each meeting. A process that once consumed twenty minutes now required only a few minutes to review. Meeting IQ solved a real problem because it came from his own lived experience.
To build the first version, Dimitri used automation tools like Relay. They helped him get most of the way toward his vision but also revealed a barrier. He wanted a product that users could adopt easily, yet these platforms required people to create their own accounts, connect their own systems, and adjust prompts themselves. He needed a true product, not a collection of manual steps. With help from developers, he created a front end that allowed people to sign in through Google and a back end that handled data and system logic. The automation layer remained his work. Together these elements created a cohesive version of Meeting IQ that could be used at scale.
Although Meeting IQ had strong potential, Dimitri realized something important about himself. He enjoyed teaching and guiding others just as much as building his own tool. Many of his friends wanted to start projects but felt uncertain about how to begin. Dimitri discovered that he loved helping people go from zero to one. He understood their questions because he had lived the same experiences. At the same time, he joined a group of peers who supported him in moving from one to one hundred. They helped him understand the ongoing responsibilities that arise once a product exists. Bugs appear. Tickets accumulate. Features require iteration. The reality of building becomes clearer as the process unfolds. This community encouraged him and reinforced the value of working alongside others.
Claude Code became his main tool, and he believes deeply in its potential. He sees it as something far broader than a technical resource. He uses it for everything from building applications to creating blog posts and deploying them to custom sites. He believes the tool can serve anyone if they approach it with openness and consistency. Through this approach, he found a new level of agency.
Through his early projects, Dimitri learned that even simple ideas require a surprising number of steps. Publishing a website involves hosting, domain configuration, search indexing, sitemaps, and ongoing updates. He discovered that what appears effortless from the outside is built on layers of detail. Rather than discourage him, this gave him respect for the craft of building. It also shaped how he advises others who underestimate the process.
There was a point in his journey that required creativity in how he assembled a team. He wanted to continue improving Meeting IQ but did not want to hire freelancers without trust in the outcome. Instead he explored Acquire.com and found small teams who were selling their products. He aqua-hired a group that included two developers and two designers. He viewed this as a more efficient and reliable way to gain support from people who had already proven their ability to create.
As his skills evolved, Dimitri began to appreciate the value of collaboration more deeply. At first he preferred to work alone because no one else occupied the same stage of the learning curve. If he turned to people who were further along, he feared he was asking too much. If he shared ideas with people who were behind him, he often found himself teaching instead of collaborating. Now that he can design and deploy full applications, he enjoys working with others. He advises a company founded by friends who trust his perspective. When they write messaging for their product, he sees their challenges clearly because he made many of the same mistakes. He guides them toward language that communicates outcomes instead of features. He encourages them to share value rather than focus on what they built.
Dimitri believes that this moment is a powerful time for non technical founders. As he puts it, he made more progress once he stopped experimenting with many tools and went all in with one. He encourages new builders to learn the fundamentals of front end, back end, and deployment. Even simple projects teach essential lessons. Asking questions through tools like Claude or ChatGPT can carry someone through any moment of confusion. Progress comes from immersion rather than hesitation.
As Lighthouse continues to take shape, Dimitri moves forward with a sense of purpose formed over many years. He carries the curiosity of the kid who watched companies grow around him. He carries the discipline he built through sales. He carries the excitement he felt the first time he saw code appear line by line during a hike. He carries the patience he gained through building, teaching, and advising.
His journey reflects the belief that creation becomes possible when someone follows the spark that refuses to fade. Lighthouse grows from that spark. It grows from Dimitri’s desire to help others build the ideas they carry within them.
Thrive builds highly vetted peer groups for founders. Want to learn more?
