Wilber BucardoBuild to be in control.
I build companies and systems where telecommunications, software and operations meet.
Before deciding how to grow something, I need to understand how it really works.
- Judgement — What is essential, and why
- Infrastructure — A foundation understood from within
- Product — Simple because the base is solved
- Operations — Where things are measured and improved
A method in three acts.
Not a desk philosophy. It is the order I work in when something has to function every single day.
I. Understand the system
Before building, I map how information flows, where costs originate and what depends on what. A decision is only as good as the model of the system behind it.
II. Build what is essential
Whatever defines the operation is designed and understood from the inside. The incidental can be delegated; the critical cannot.
III. Operate and improve
A system is proven in use, not in a presentation. Measure, adjust, measure again. Evidence decides what to scale.
I haven’t built a single company. I’ve built a way of operating.
My work spans telecommunications, software, health and capital. The sectors change; the craft repeats: design the infrastructure, build the product, order the operation and give it governance.
- Airtime Tech Global · Airtime Connect · Airtime Digital · Mobiconnect
- NutriMetab
- Inversiones Bucardo Zúñiga Ltda.
- What runs through it all.
Three principles I decide by.
1. Control over the essentials
Own and understand the pieces that hold the operation up. If I do not understand a critical dependency, I do not control it.
Relying on what is not understood.
2. Evidence before scale
First something works at small scale and can be measured. Then, and only then, it grows.
Scaling a hunch.
3. Quality that survives operations
A design is judged in daily use: with errors, with load and with real people. That is where you learn whether it was done well.
Designing for the demo.
A training that shows in how I decide.
My background is in computer engineering, networks and information systems management. It explains much of how I work: I think in layers, dependencies and failure points before features.
I see it less as a CV than as a habit. When I assess a company, a product or a process, I read it as a system.
- Computing
- Logic and abstraction: separating the problem from how it looks.
- Networks
- Topology and resilience: knowing what happens when something fails.
- Information systems
- Data in service of decisions — on time, and to the right person.
Let’s talk.
If you are building something where infrastructure and operations matter, I would like to hear about it. For now, the most direct way to reach me is LinkedIn.