the founder
Jorge Pablos has been building software for over 20 years — across Mexico, Phoenix, London, and Lisbon. Not as a manager who lost touch with the code, but as a hands-on technologist who kept coding while leading.
Over two decades, he founded a real estate platform from scratch, managed high-traffic websites, and then spent 11 years at one e-commerce company — growing a team from 3 to 30, architecting a platform that generated tens of millions in revenue and shipped to over 180 countries, and leading cloud transformations across continents. He earned certifications across AWS and Scrum. He built things that lasted.
The stretch
During his 11-year tenure at a US-based e-commerce company, Jorge’s responsibilities never stopped growing. He went from coding to architecting, from
architecting to leading distributed teams across Arizona, Mexico, India, and Ukraine — while based in London as the communication bridge across three time
zones. He founded the DevOps function. He stood up a data team, partnering with external firms to fill gaps. He introduced Scrum, led initiatives to break the monolith into services, and drove the migration to AWS — some succeeded, some stalled when the organizational alignment wasn’t there to support them. He managed vendors, hired internationally, and coordinated with C-suite stakeholders — building and integrating the e-commerce platform with fulfillment, inventory, and international shipping systems across 180 countries.
He wore every hat the growing organization needed — product thinking, cloud strategy, team dynamics, process design — because he felt responsible for making it work.
But something was always nagging. The bigger the operation got, the harder it became to keep strategy connected to execution. Knowledge lived in people’s
heads. Decisions made in one room never reached another. Without clear structure and responsibilities, misalignment grew naturally. People optimized for
their own context instead of shared outcomes. Everyone was working hard — but not always in the same direction.
Jorge pushed for better processes, better communication, clearer ownership. He studied everything he thought would help — Scrum, cloud architecture,
microservices, team topologies. Some of it worked. But the dysfunction ran deeper than any one fix could reach — it was structural, not personal.
Eventually, the chapter closed. Not with a clean ending, but with an honest one: the problems were real, the environment couldn’t solve them, and the
questions they raised were too important to let go.
The questions That stayed
After leaving, the questions got louder. How do you keep strategy connected to execution as a company grows? What’s the connective tissue that makes an
organization actually work — and why doesn’t it exist as a tool?
Jorge sharpened his technical edge — certifications, independent consulting, reconnecting with the craft. But the real work was thinking. Reflecting on
years of patterns, trying to see what he’d been too close to see from the inside.
In October 2025, he joined the Cambridge University CTO Programme — a year-long executive programme focused on technology strategy, innovation portfolios,
and leadership. Now almost halfway through, every module lands differently because Jorge has lived the problems Cambridge is teaching. The gap he’d felt for years finally has names: strategy-to-execution flow. Organizational structure driving behavior. Feedback loops that connect every layer.
The missing piece wasn’t effort or talent — it was the system itself.
why now
Then AI changed the game. The cost of building collapsed. The speed exploded. And everything Jorge had learned — architecture, strategy, team dynamics, and
a decade of unanswered questions — suddenly had a multiplier.
Labinhood became an AI-native product studio. Not to ride a trend, but because the founder spent a decade learning what to build — and AI gave him the means to build it.