Carlos Alberto Peña Molina combines experience in technology infrastructure, cybersecurity, business continuity, and field-service operations to design practical systems that help organizations coordinate people, information, and execution more effectively.
Carlos Alberto Peña Molina is an operator-technologist whose career connects information technology, cybersecurity, business continuity, and business operations.
His professional experience began with the design and direction of technology environments for organizations requiring reliable infrastructure, secure connectivity, information protection, and continuity of operations. After establishing and operating Be2Clean LLC in the United States, he gained direct exposure to the coordination challenges faced by field-service businesses: fragmented systems, workforce visibility, scheduling, service verification, customer communication, billing, and operational follow-through.
That combination of technical and operating experience now informs his work as Software Architect and Product Developer for the Runox initiative.
"Technology creates lasting value when it strengthens the organization behind the interface—its people, processes, information, controls, and ability to continue operating when conditions change."
Carlos approaches technology as operational infrastructure rather than as an isolated collection of features.
Security must be designed into operations.
Business continuity must be practical and testable.
Technology should reduce fragmentation.
Systems must reflect how people actually work.
Many small and growing field-service businesses perform operationally complex work without having a true operational infrastructure behind the business. Customer commitments, workforce availability, travel, service execution, quality evidence, labor records, billing, and collections may exist in different systems without sharing a consistent operational state.
The result is not simply administrative inconvenience. It is a coordination gap that becomes more consequential as the company adds employees, crews, customers, service areas, and recurring obligations.
Office personnel, field teams, customers, and financial workflows often operate from different information. A schedule change may not automatically update workforce expectations, customer communication, route planning, service evidence, or billing.
In many service businesses, adding one employee or field team creates more than one additional unit of administrative work. It introduces new scheduling dependencies, travel combinations, time records, communications, exceptions, supervisory requirements, and payroll consequences.
This causes coordination complexity to grow faster than management capacity.
The operational record is frequently broken across scheduling systems, text messages, photographs, timekeeping tools, GPS records, invoices, and payment systems.
Without a continuous and trustworthy chain of operational evidence, managers may struggle to determine:
Traditional systems frequently record activity without identifying its operational significance.
Managers may discover excessive labor hours, unprofitable service patterns, customer disengagement, scheduling conflicts, route inefficiencies, recurring cancellations, or delayed collections only after the financial or customer impact has occurred.
The deeper requirement is not more data. It is earlier operational awareness.
Small service businesses often depend on individual employees, informal knowledge, external providers, connectivity, and manually coordinated processes.
Employee absence, communication failure, loss of connectivity, system unavailability, or a cybersecurity incident can therefore interrupt multiple parts of the operation simultaneously.
Operational infrastructure should preserve essential workflows, evidence, and decision-making capacity when normal conditions are disrupted.
Enterprise operational systems may offer depth but remain too expensive, complex, or implementation-intensive for smaller service organizations.
At the opposite end, conventional CRM and scheduling products may be accessible but fail to connect field execution, workforce controls, operational evidence, financial workflows, continuity, and management intelligence.
This creates an underserved middle: businesses whose operational complexity has exceeded basic tools but whose resources do not support enterprise infrastructure.
Artificial intelligence cannot safely improve an operation when the underlying information is fragmented, inconsistent, or missing operational context.
Useful operational agents require:
Present AI as a governed operational capability—not as an autonomous replacement for management judgment.
"Carlos Alberto Peña Molina approaches these challenges from both sides of the problem. His previous work in technology infrastructure, cybersecurity, server environments, information protection, and business continuity showed him how organizations depend on reliable systems during disruption."
His experience operating Be2Clean in the United States then exposed him to the daily coordination pressures faced by field-service businesses: balancing customer commitments, workforce availability, travel, service execution, quality, labor, billing, and collections.
This combined perspective led him to identify a broader operational infrastructure gap. The challenge is not simply to digitize individual tasks, but to preserve continuity and context across the complete operating cycle.
The Runox initiative is being developed to explore how a shared operational infrastructure can connect customer commitments, workforce capacity, field execution, service evidence, communications, and financial outcomes.
Its direction is to help management understand not only what has already happened, but what requires attention, what may create operational risk, and which opportunities can be acted upon responsibly.
Runox remains in active development and testing. Its broader potential lies in making deeper operational capabilities more accessible to small and growing field-service businesses without requiring enterprise-level resources.
Carlos developed his professional foundation in technology infrastructure and systems integration: LAN/WAN/MAN environments, servers, virtualization, secure connectivity, firewalls, communications, physical-security technology, monitored backups, redundancy, and business continuity.
Through Ambientes Tecnológicos Integrados S.A.S., known professionally as ATIC Ingeniería, where he served as Founder and CEO, he directed technology solutions for organizations in financial services, accounting and professional services, education, and rural-development environments.
During the COVID-19 period, Carlos directed and supported technology initiatives that helped organizations maintain secure access, information availability, communications, and continuity under highly disrupted working conditions.
His experience included multi-location technology environments serving a Colombian financial cooperative with 51 branches nationwide, as well as infrastructure supporting accounting operations for more than 100 clients. These projects required the coordination of centralized information, secure remote access, monitored continuity systems, communications, physical-security technology, and incident response.
Carlos's business-continuity experience also includes leading the response to a serious cybersecurity incident that affected critical server availability. Under pressure, he coordinated containment, infrastructure restoration, data recovery, and the reestablishment of operations within the required business-continuity window. The experience reinforced his conviction that resilience depends on preparation, isolation, recoverability, and disciplined execution—not simply on having backup technology.
Carlos founded Be2Clean LLC in Florida and moved from advising organizations about systems to operating a field-service company directly.
At Be2Clean, Carlos became responsible for the realities that operational systems are expected to support: customers, employees, field teams, recurring services, scheduling, quality control, documentation, communications, invoicing, collections, and administrative follow-up.
That firsthand experience allowed him to observe where conventional software often fails small and growing service businesses—not because the businesses lack effort, but because their information and workflows remain distributed across disconnected tools and informal processes.
The Runox initiative emerged from operational challenges experienced inside Be2Clean. Carlos defined the business requirements, operational logic, workflows, product direction, and technical architecture needed to connect office administration, field execution, workforce coordination, customer information, service documentation, communications, and financial processes.
As Software Architect and Product Developer for the initiative, Carlos directs product requirements, architecture, operational logic, iterative development, review, testing, and production validation. Be2Clean provides a related real-world operating environment in which the platform can be evaluated and refined.
Runox remains in active development and testing.
Designing technology environments that support information availability, access control, reliability, and organizational continuity.
Connecting preparation, redundancy, recovery planning, and operational decision-making so organizations can continue functioning through disruption.
Understanding the practical coordination of customers, schedules, employees, teams, service execution, quality, documentation, and financial follow-up.
Turning fragmented operational activity into structured information that can support visibility, accountability, and better decisions.
Translating real operating requirements into integrated workflows, controls, data structures, and technology capabilities.
Carlos's current professional direction builds upon experience gained while supporting distributed organizations and continuity-critical technology environments in Colombia.
During the COVID-19 period, he directed and supported initiatives involving secure access, information availability, communications, infrastructure resilience, and operational continuity across disrupted and geographically distributed environments. His experience included technology supporting a financial-services organization with 51 branches across Colombia and infrastructure serving accounting operations connected to more than 100 clients.
These experiences taught Carlos that continuity does not depend on technology alone. It depends on whether people, information, controls, communications, and recovery capabilities remain coordinated when normal operating conditions are disrupted.
After establishing and operating Be2Clean LLC in the United States, Carlos encountered a different but related challenge: the growing structural gap between the complexity of field-service operations and the operational infrastructure available to small and midsize businesses.
The challenge facing U.S. field-service businesses is not merely that they use spreadsheets, messages, or disconnected applications. Those are visible symptoms of a deeper operational infrastructure gap.
Service companies must continuously coordinate:
Many existing systems capture individual parts of this activity, but they do not preserve a consistent operational chain connecting the original customer commitment to workforce capacity, field execution, service evidence, labor cost, invoicing, collection, and management review.
As a result, owners and managers frequently become the manual integration layer between systems. Critical operating knowledge remains dependent on particular individuals, communication channels, and informal procedures.
This creates several structural risks:
This is a distributed challenge across the United States. It appears locally, company by company, but is repeated across regions and service industries wherever organizations coordinate mobile workforces, recurring customer commitments, physical service delivery, and time-sensitive financial processes.
Carlos approaches this challenge from two complementary forms of experience.
His technology and business-continuity work in Colombia gave him experience with distributed infrastructure, secure systems, information availability, organizational resilience, and operations that could not simply stop when conditions changed.
His leadership of Be2Clean in the United States gave him direct responsibility for the daily realities of a field-service company: customers, employees, teams, schedules, travel, service execution, quality control, documentation, communication, billing, collections, and administrative follow-through.
This combination led him to identify that the central problem is not the absence of software. The deeper problem is the absence of a shared operational infrastructure capable of preserving context, accountability, and continuity across the complete service lifecycle.
His work now focuses on translating these combined experiences into security-conscious operational systems for field-service businesses.
Carlos is focused on developing an operational-infrastructure approach that may help small and growing field-service businesses in different regions of the United States strengthen five interconnected capabilities:
Connecting customer commitments, workforce capacity, scheduling, field execution, and administrative follow-up within a consistent operating context.
Creating continuity between who performed the work, what was completed, how the service was documented, how labor was recorded, and how the customer was billed.
Helping management identify exceptions, capacity constraints, customer risks, labor variance, collection issues, and operational opportunities before their consequences become more difficult to correct.
Reducing dependence on fragmented information and individual knowledge so that essential workflows can continue through employee absences, connectivity limitations, provider disruptions, and other operating interruptions.
Establishing the structured information, role boundaries, business rules, traceability, and human oversight required for artificial intelligence to support operational decisions responsibly.
Through the Runox initiative, Carlos is exploring how these capabilities can be integrated into an accessible operating environment for field-service organizations that have outgrown basic administrative tools but do not have the resources to implement enterprise-scale infrastructure.
The intended contribution extends beyond digitizing individual tasks. It is directed toward helping service businesses build stronger operational capacity: the ability to coordinate growth, protect information, preserve service continuity, understand financial consequences, and make better-informed decisions from a connected operational record.
Runox remains in active development and testing. Its broader potential lies in translating operational experience, continuity principles, and systems thinking into adaptable capabilities that may serve field-service businesses across different industries and regions of the United States.
Carlos's leadership style is based on understanding the complete operating environment before introducing technology. He studies how people perform the work, where information is lost, which dependencies create risk, and how decisions affect customers, employees, and financial outcomes.
His approach combines strategic direction with direct validation. He defines the problem, establishes the operating logic, evaluates the implementation, and refines the system based on real use.
In 2013, Carlos received scholarship support from the Organization of American States and participated in an international-student program associated with George Washington University in Washington, D.C.
Carlos has also shared practical technology knowledge through online instruction. His Spanish-language Udemy course, "Aprende Virtualización con Proxmox," introduces virtualization concepts, virtual machines and containers, storage approaches, backups, and restoration within a practical learning environment.
Why Adding One Employee Breaks Most Field-Service Businesses
An operations-based perspective on why service businesses often encounter fragmentation as their workforce and customer base grow.
Read on MediumA practical reflection published by ISSA on the role of trust, professionalism, systems, and accountability in building a service organization.
Read on ISSACarlos continues to work at the intersection of technology, security, continuity, and field operations. His focus is not technology for its own sake, but the creation of operating environments that help organizations coordinate work, protect information, maintain continuity, and grow with greater discipline.
