Juan Sebastian Murga

Please introduce iPakket Corporation and describe your role as CEO and President.

I am the CEO and President of iPakket Corporation. We are a technology-driven logistics and mobility company. Our focus is on building structured systems that improve how goods and people move in cities. That includes supply chain logistics and micromobility through our Ride by iPakket division.

My role is operational oversight and long-term strategy. I set direction, approve capital allocation, manage partnerships, and ensure our systems function as designed. I stay close to execution. Titles do not run companies. Processes do.

What is iPakket’s core operating model – in-house, outsourced, or hybrid?

We use a hybrid structure. Core strategy, technology architecture, compliance standards, and partnership development are managed internally. Fleet maintenance, localized logistics, and certain technical functions are supported by regional teams and vetted third-party vendors.

For micromobility, we maintain centralized oversight of docking infrastructure, fleet monitoring systems, and municipal agreements. That cannot be outsourced. Control over infrastructure is key to operational discipline.

How does iPakket differentiate itself in the micromobility and logistics market?

Structure.

Most micromobility operators launched fleets first and addressed orders later. We reversed that. We deploy proprietary docking and charging stations before scaling vehicles. That reduces sidewalk clutter and regulatory friction.

In logistics, we apply infrastructure thinking. Every asset is part of a system. We do not treat vehicles as isolated units. We treat them as network nodes.

We prioritize partnerships with cities and universities instead of disruption. That changes the conversation.

What sectors do you primarily serve, and how has that evolved?

We began in logistics. That expanded into urban mobility through Ride by iPakket. Our primary stakeholders now include municipalities, universities, urban planners, and transportation regulators.

The evolution was logical. Logistics taught us systems management. That knowledge transferred into mobility infrastructure. We moved from supply chain movement to structured urban transport.

What are the most requested solutions from your partners?

In micromobility, cities approach us for organized fleet deployment. They want control, compliance, and clean streets.

Universities want structured campus mobility with clear docking zones.

In logistics, partners seek operational consistency and technology integration that improve visibility across supply chains.

Order and accountability are the common themes.

How do you stay ahead of industry shifts when data is often delayed?

I focus on fundamentals. Regulations, infrastructure capacity, and workforce realities move slower than headlines.

We monitor municipal policy trends closely. We study regulatory patterns city by city. We build relationships before expansion.

I also look at friction points. Where are complaints coming from? Sidewalk clutter. Fleet vandalism. Unmanaged growth. Those signals guide design improvements.

Do you have repeat institutional partners? What drives that loyalty?

Yes. Repeat partnerships come from reliability.

We deliver what we agree to deliver. We maintain fleet order. We respond to operational issues quickly.

Municipal relationships are built on trust. If a city sees compliance and reduced friction, conversations continue.

How do you measure and ensure operational satisfaction?

We track utilization rates, downtime percentages, docking compliance rates, and maintenance response times.

In micromobility, operational uptime and parking compliance are critical. A disorganized fleet signals failure.

We also monitor partnership feedback through structured check-ins with municipal stakeholders.

What post-deployment support do you provide?

Support does not stop after launch. We maintain infrastructure, software monitoring, and compliance reporting.

Cities and campuses receive operational reporting. Maintenance teams are scheduled on defined cadences. Adjustments are made based on usage patterns.

We treat deployment as the beginning of a system, not the end of a transaction.

How is your pricing structured?

Pricing depends on the scope. For municipalities, agreements may include infrastructure installation, fleet size, and service support. That is typically structured through partnership contracts rather than simple per-ride billing.

In logistics services, pricing can be milestone-based or structured around service capacity.

Exact structures vary by region and scale.

What price range have your recent projects fallen into?

Micromobility expansion represents multi-million-dollar investments, particularly in infrastructure and fleet deployment. Specific figures vary by city and size of rollout.

We balance affordability with long-term system sustainability. Underpricing leads to instability. Stability requires adequate capital allocation.

Have you turned down projects? What are your minimum requirements?

Yes.

We decline opportunities where there is no regulatory framework or no institutional cooperation. Infrastructure-first deployment requires municipal alignment.

If a city wants rapid deployment without structure, we are not the right partner.

Minimum fit includes regulatory clarity, designated docking zones, and long-term operating agreements.

What major challenges have you faced recently?

Regulatory uncertainty is constant in micromobility. Many early operators damaged trust through unmanaged fleets.

We overcame this by leaning into infrastructure and transparency. Clear communication and structured deployment reduced friction.

Scaling across different cities also requires adapting to varied ordinances. That takes discipline.

How do you foster innovation while maintaining order?

Innovation must serve structure. We invest in fleet technology, including high-torque motors and integrated charging capabilities. But hardware is secondary to systems integration.

We pilot before full rollout. We test in controlled environments. Expansion follows validation.

What role does company culture play in execution?

Culture drives discipline.

We prioritize accountability and operational clarity. Teams understand that compliance matters as much as growth.

I reinforce that infrastructure businesses fail when standards slip.

Where do you see iPakket in 5-10 years?

Integrated urban mobility systems. Not scattered fleets.

I see structured networks operating across major cities with stable institutional partnerships.

Growth will be steady, not chaotic.

How has your leadership style evolved?

I started in large-scale infrastructure. That taught me patience and risk control.

Over time, I learned to integrate digital systems into physical operations. But the core principle stayed the same: deliver what you promise.

What emerging trends are you watching?

Battery technology improvements. Smart city integration. Data-driven fleet optimization.

Structured micromobility tied into broader urban transport systems is where long-term viability sits.

What advice would you give to aspiring founders and CEOs?

Build systems, not headlines.

Execution builds credibility. Discipline builds companies.

One lesson stands out: if your operation cannot stand on its own without you explaining it, it is not strong enough yet.