From Cisco Enterprise to No-Code: My Unconventional Path

My path into no-code was not the usual one.

Before Bubble, before Moara Digital, before startup timelines and MVP launches, I spent almost a decade at Cisco. I worked in enterprise environments where reliability wasn't optional and where a small mistake could impact thousands of people.

One of the most meaningful moments in that chapter was supporting infrastructure initiatives connected to the Rio 2016 Olympics. Projects at that scale teach you something very quickly: systems are only as strong as their weakest process. Documentation matters. Monitoring matters. Communication matters. If your handoff fails, everything fails.

When I eventually founded Moara Digital, I carried that mindset with me. At first, I was focused on automation and digital transformation projects. Then I discovered Bubble, and honestly, it felt like opening a new door. I could move much faster than traditional development cycles, but I also noticed that many no-code projects were being built with short-term thinking.

That's where my enterprise background became a big differentiator.

Even in no-code, I think in layers:

• What happens when usage grows 10x?
• Can another developer understand this workflow in six months?
• Are naming conventions and data structures clean enough to scale?
• Do we have clear fallback behavior if an integration fails?

Many people treat no-code like a shortcut. I treat it like a high-leverage environment.

I've worked on projects where clients came after a "quick" build that looked good in demos but broke under real operations. Usually the issues are predictable: weak data modeling, poor workflow structure, no logging discipline, and little documentation. Those are not Bubble problems. Those are engineering mindset problems.

The interesting thing is that enterprise thinking and no-code speed are not opposites. They complement each other. Bubble gives me the velocity to ship quickly, while my Cisco years trained me to ship responsibly.

This combination is what I try to bring to every project: startup speed without startup chaos.

Today, when I help founders launch MVPs or companies modernize internal operations, I still hear echoes of that enterprise world. Be clear. Be resilient. Design for the next stage, not only the next demo.

My journey from Cisco to no-code may look unconventional from the outside, but for me it feels like a straight line. I moved from building systems for large organizations to building systems for ambitious teams that need results fast.

Different tools, same commitment: deliver work people can trust.