What Startups Actually Taught Me

I have started things that failed publicly. I have won things nobody thought I would win. I am building three things right now that didn't exist two years ago. None of this followed a plan. All of it followed a pattern.

The pattern is not resilience. It is not hustle. It is something more structural than that — and more useful.

2Move and Shark Tank Mexico

2Move was a co-founded startup. The idea was real, the team was committed, and we made it to Shark Tank Mexico. That sounds like a highlight. It was not.

We walked into the tank believing in our product. We asked for too much money at a fantasy valuation. The sharks saw right through it. We did not get funded. The appearance was not a success — it was a public lesson in what happens when you confuse conviction for valuation.

The business did not survive. The public nature of the failure — national television, millions of viewers — makes it the kind of thing most people either hide from their resume or reframe as a "learning experience" with vague language about growth and character.

I will not do that. Here is what actually happened: we came in so in love with what we had built that we lost perspective on what it was worth to the market. We raised funding from investors, built the product, and went to market — but the demand was not there at the price point we needed. The investors lost their money. The company shut down.

The lesson was not "failure teaches you things." The lesson was specific: do not scale distribution before you have proven that someone will pay, repeatedly, at a margin that sustains the business. That is not a motivational quote. That is an operational principle I now apply to everything I build.

Deco Green — Winning What You Were Not Supposed to Win

Deco Green is not a startup. It is a $44 million development project that we won through a public RFP process — Request for Proposal, competitive bid, evaluated by a selection committee. We raised $13.5 million in equity to capitalize it.

I include it here because the pattern is the same. Most people assumed we would not win. The incumbent players had more history, more name recognition, more institutional relationships. What they did not have was a submission that was structurally better — more precise financials, a clearer development thesis, a more disciplined operating plan.

We won because we out-prepared everyone in the room. Not with charisma. Not with connections. With a document that left no question unanswered and a capital stack that was already in motion before the award was announced.

The startup lesson embedded in Deco Green is this: preparation compounds invisibly until the moment it becomes visible — and by then, the outcome is already decided. The work that wins the RFP happens in the months before anyone reads the submission. The same is true for product launches, fundraising rounds, and client proposals.

What I Am Building Now

I am building three things simultaneously. They are different products in different markets, but they share the same architecture underneath — and that architecture is what 2Move taught me and Deco Green confirmed.

MiCasaTuCasa is a real estate platform for the Venezuelan and Latin American market. It exists because the real estate transaction layer in those markets is broken — fragmented listings, no trust infrastructure, no standardized process. We are about to launch. I built the entire ecosystem — platform, workflows, brand, operational architecture — with zero cash investment. No funding round, no runway burn. The system was designed to be capital-efficient from day one because 2Move taught me what happens when you raise before you validate. This time, the product comes first. The capital comes when the market confirms it.

Hombre Vértice is a leadership and personal development platform designed for universities across Latin America. It is still being built. The pilot project is about to be deployed at Universidad Monteavila — the first institutional test of the curriculum and delivery model. The insight was not "I should build a personal brand." The insight was that there was a gap in the market for leadership content in Spanish that was not motivational noise — content grounded in operational experience, not theory. The pilot will validate the demand before I build the infrastructure. That sequencing matters.

BuildFire Spec Engine started as an internal tool. It reads fire protection construction plans and produces a bill of materials — NFPA 72 and Florida Building Code compliant. I built it for BuildFire, our fire protection operation, to solve our own estimating bottleneck. It worked so well that I ended up transforming our entire website into our operating system — the Spec Engine now generates our bid proposals, manages our project pipeline, and runs our internal workflows. What started as an AI tool became the company's operating layer. Now I am working on migrating it to a wider public product — making the same capability available to other fire protection contractors. I wrote about the architecture in detail in another post.

The Thread

People ask how I go from Shark Tank to real estate development to AI in construction. The honest answer is that the thread is not the industry. The thread is the operating system.

Every venture I have started or joined shares three characteristics:

1. The problem was structural, not cosmetic. I do not build things that make existing processes slightly prettier. I build things that replace a broken process with a system. MiCasaTuCasa replaces a fragmented transaction flow. The Spec Engine replaces a 16-hour manual BOM process. Hombre Vértice replaces motivational theory with operational content grounded in real experience.

2. Validation came before scale. After 2Move, I never again poured resources into distribution before confirming that the demand was real and repeatable. MiCasaTuCasa was built with zero cash investment — the entire ecosystem was designed before a dollar was raised. Hombre Vértice starts with a single university pilot before expanding. The Spec Engine proved itself internally at BuildFire before I began building the public product.

3. The system is the product. Not the interface, not the brand, not the pitch deck. The system underneath — the compliance database, the transaction protocol, the content delivery architecture — is what makes the thing work. Everything else is a layer on top. If the system is right, the layers compound. If the system is wrong, no amount of marketing saves it.

What This Means If You Are Building Something

If you are a founder, an operator, or someone who is about to start something — the advice I would give is not inspirational. It is structural.

Do not raise money before you know someone will pay. Do not build distribution before you have something worth distributing. Do not layer AI on top of a process you have not mapped. Do not pitch before the document is airtight.

And when something fails — as it will — do not extract a vague lesson about perseverance. Extract the specific operational error that caused the failure. Write it down. Build the next thing differently because of it.

That is the only thread that matters.