Building Tech From Scratch: What I Learned as a Founder

When I decided, alongside my partner, to build a technology company from scratch, I didn’t think the greatest challenge would be the product, the market, or even funding. I assumed the real difficulty would lie in validating a solution, convincing clients, and developing robust technology. And yes, all of that was complex. But there was an additional layer no manual prepares you for: learning to lead in an environment shaped long before you arrived.

This is not about confrontation. It is about awareness.

For decades, the technology ecosystem has operated under well-established dynamics. The unwritten rules, negotiation spaces, standards of authority, and even the narrative of success were built within a specific historical context. Entering that space is not impossible, but it does demand strategic awareness.

Very early on, I understood something essential: No one grants you authority in technology. You build it. Every single day. And building it requires mastering the technical conversation, understanding your business model in depth, and making decisions with clarity, even when skepticism sits across the table.

I have been in meetings where my role was misinterpreted before I introduced myself. In others, validation only arrived after I supported, with data, what I had already articulated strategically. Instead of discouraging me, those experiences sharpened my discipline. They pushed me to communicate with precision, decide with evidence, and defend positions with structured reasoning rather than emotion.

Building technology from scratch also means accepting that uncertainty is permanent. In the case of Getin, creating a specialized Retail Analytics platform meant developing our own methodologies, understanding physical human behavior inside stores, and translating it into actionable metrics for decision-making. Nothing about that process was predefined. We had to design, test, correct, and refine continuously.

And through that process, I learned that true innovation is not driven by urgency, it is driven by depth.

Many startups obsess over scaling quickly; far fewer obsess over building correctly. We chose to deeply understand the structural challenges of physical retail before aggressively expanding our solution. We chose to validate the quality of our data before amplifying our commercial narrative. That decision defined our trajectory.

Another important lesson was understanding that the margin for error in technology is not merely financial, it is reputational. When you provide data that influences strategic decisions for brands, every metric carries weight. Every insight can alter operational direction. That responsibility changes how you lead.

Preparation became my competitive advantage. Every significant decision had to be supported by thorough analysis. Every strategic conversation required clarity and structure. Not because I doubted my capability, but because leadership in technology demands intellectual rigor.

Over time, I realized that leading in this environment does not require replicating existing leadership styles. It requires developing your own.

For years, technology leadership was often associated with aggressive negotiation, extreme assertiveness, and growth-at-all-cost narratives. My experience taught me that sustainable leadership can also be grounded in consistency, long-term vision, and disciplined value creation.

Building technology is not simply about coding. It is about understanding structural problems and designing solutions that transform industries. In our case, that meant bringing visibility to physical retail at a time when public discourse seemed almost exclusively focused on e-commerce. We believed that brick-and-mortar stores were not obsolete, they were misunderstood. With accurate data and proper analysis, they could become strategic growth engines.

That conviction was not trend-driven. It was analysis-driven.

Another critical realization was that context should not become an excuse. It should become training. Operating in a demanding environment sharpens your ability to anticipate risk, read dynamics, and build strong networks. These are not automatic advantages; they are capabilities developed through resilience and reflection.

I have seen professionals in technology reduce their voice or soften their ambitions in an effort to fit into perceived expectations. My experience was different. I learned that strategic clarity can feel disruptive only when it challenges established inertia. True leadership is not about constant approval but achieving sustainable results.

Team building became another defining pillar. Technology companies are not sustained by isolated talent, but by coherent cultures. From the beginning, I understood that we needed strong technical profiles, but also critical thinking, professional integrity, and the courage to challenge our own assumptions.

Diversity of thought stopped being an aspirational concept and became a competitive advantage. When multiple perspectives are integrated into problem-solving, the quality of the solution improves. The questions become sharper. The analysis becomes broader. The understanding of the end user deepens. In sectors like retail, where interpreting human behavior is fundamental, this breadth of perspective is decisive.

Building from scratch forces you to make decisions no one else can make for you: when to pivot, when to persist, when to decline an attractive opportunity that misaligns with your vision. These decisions are shaped by the context in which you develop as a leader. In my case, that context strengthened a balance between firmness and empathy, rigorous analysis and active listening.

Looking back, I recognize that my most valuable lessons were not purely technical, they were strategic.

I learned that building technology is, at its core, about building trust. Trust in the data. Trust within the team. Trust in the vision. And trust is not established through inspirational speeches; it is built through consistent execution.

The Mexican technology ecosystem is evolving rapidly. We are seeing more specialized solutions, increased capital interest in innovation, and more talent willing to build rather than follow. But real progress is not measured by the number of startups launched, it is measured by the solidity of companies that consolidate, generate impact, and professionalize entire industries.

Building technology from scratch within historically established dynamics did not require me to redefine myself. It required me to refine myself — to become more strategic, more disciplined, and more resilient. And that demand ultimately became a structural strength.

Because leadership is not defined by who designed the system before you arrived. It is defined by the clarity with which you understand the problem, the discipline with which you execute the solution, and the strength of the structure you leave behind.

In technology, that is what endures.