Suggestions
Felipe S. Fernandes
Driving IoT & Software Solutions for Healthcare, Oil & Gas, and Manufacturing | Scalability, Security (HIPAA, HiTrust), Remote Monitoring, and Industrial Automation
Felipe S. Fernandes is a seasoned professional in the payment industry and technology sectors, currently serving as the CEO and Co-Founder of Pi Tech. With over 15 years of experience, he has a strong background in building and scaling early to mid-stage companies. Notably, he led the product team that executed the first mobile money transfer from the United States to Mexico. Fernandes has also successfully bootstrapped two companies and managed a product team of over 50 engineers for a startup that raised $185 million. Additionally, he has experience overseeing customer success teams responsible for generating approximately $10 million in annual recurring revenue (ARR) .123
At Pi Tech, Fernandes focuses on delivering custom software solutions using advanced technologies such as AI, machine learning (ML), and the Internet of Things (IoT), catering to various industries including healthcare, oil and gas, telecommunications, and fintech .15 He became a member of the Forbes Technology Council in June 2023, where he shares insights and expertise on technology and product development .14
Highlights
Think of AI in software engineering, like the shift from gas to electric cars.
As it becomes cheaper to drive one mile in an electric car compared to a gas car, more people start driving, not fewer.
Jevon's Paradox states that the more efficient use of a resource leads to increased consumption of that resource.
The same applies to AI in development: as AI makes software engineering faster and more efficient, the demand for software and, by extension, engineers will actually increase.
Efficiency doesn't reduce the need for experts.
It accelerates growth and creates new opportunities.
The more accessible development becomes, the more we'll see a surge in demand for skilled engineers to advance innovation.
The other day, my tenant had a leaky faucet.
I figured it was a simple fix. Probably just a worn-out washer.
But once I started taking things apart, I uncovered a bigger issue: the faucet needed to be replaced.
What I thought was a quick fix turned into a much larger project.
It wasn’t until I got hands-on that the actual problem revealed itself.
Sometimes, you don’t fully grasp the scope until you roll up your sleeves and dive in.
That was a good lesson for software projects, too.
You can’t expect to have all the details clearly defined from the beginning.
You start solving, and as you do, the nature of the problem evolves, and so does your understanding of it.
The more you engage with it, the more the true scope of the problem, not just the solution, becomes clear.
