Chris Cilino - Founder of PetranWay

I will work with your software organization to achieve your business objectives by:

  1. Designing solutions with long-term perspective that deliver immediate value.

  2. Asking insightful questions and suggesting solutions that produce concrete and constructive results.

  3. Building a network of experts to collaboratively create your applications.

My passion is teamwork. In our world of growing complexity, I believe it takes a diverse team of experts to create the powerful and meaningful solutions that drive innovation.

My vision is to build and evolve software organizations into healthy business units that create meaningful software and that deliver immediate value with a long-term perspective.

PetranWay was founded in 2020 by Chris Cilino and is located in Austin, Texas.

Certifications and Qualifications

Career History

2020 - Present


  • Project Engineer

2019 - Present


  • Founder

  • President

  • Treasurer

2020 - Present

PetranWay LLC

  • Founder

2019 - 2020

Composed Systems

  • Partner

2016 - 2019

Cirrus Logic

  • LabVIEW Framework Architect

  • Center of Excellence Technical Lead

2005 - 2016

National Instruments

  • Marketing

  • R&D LabVIEW Developer

  • Customer Support

Origin of PetranWay's Name

I'm often asked about the name "PetranWay". I was inspired by Jesus' words in Matthew chapter 5 through 7 which end with His famous saying:

"Therefore everyone who hears these words of mine and puts them into practice is like a wise man who built his house on the rock ["rock" in Greek is PETRAN]. The rain came down, the streams rose, and the winds blew and beat against that house; yet it did not fall, because it had its foundation on the rock."

In this story the builder recognized true value: a house that could stand against the storms for a lifetime. As a result, the builder invested time and effort to build a house that would last.

In the same way the PetranWay is to first identify true value and then invest time and resources to achieving the objective. Your software organization's purpose and the software it makes should be used to guide your investment. For example, if your software's purpose is to run a tester for 6 months, then there is no need to create detailed design documentation because the software has such a short life span and no one will need to maintain it. However, if your software is going to be in use for years and many people will add features, then more rigor in methodology, architecture, documentation and process should be employed so it stands the test of time.

The PetranWay is to build software organizations that create valuable software using long-term perspective.