Code Story episode
S7 E8: The Tech-Enabled Empire: Scaling a 3x Founder's Financial Engine with Waseem Daher, Co-Founder & CEO of Pilot
Oct 11, 2022 · Season 7 · Episode 8 · 27 min
Your back office accounting team
Waseem Daher had two immigrant parents from Lebanon. He was born in the states, after the migrated to the states in the 80's. With his relatives around him, he saw that it was possible to run your own business, and do it well. His love for computer science really culminated when he went to MIT to complete is undergraduate studies, where he actually met his current co-founders. He is married with a 2 year old - so all additional time he has outside of work is spent with his young family.
Waseem and his co-founders have done many startups together. Inevitably, with every business they started, they found the back office type processes were important to have each time, but not the area of expertise for the founders - and much less, not the focus of said business. So, they built the service they wished they had in prior ventures.
This is the creation story of Pilot.
Sponsors
AirbyteDopplerHost.ioIPInfomablLinks
Website: https://pilot.com/LinkedIn: https://www.linkedin.com/in/wdaher/
Checkout our episode stacks on Stacklist! https://stacks.codestory.co/
Advertising Inquiries: https://redcircle.com/brands
Privacy & Opt-Out: https://redcircle.com/privacy
More episodes
Keep listening
Topics
Explore related conversations
Technical due diligence checklist for startups
A technical due diligence checklist for founders and investors: what reviewers examine across architecture, security, team and process, and how to prepare before a raise.
Fractional CTO vs full-time CTO: which does your startup need?
A practical comparison of a fractional CTO and a full-time CTO: cost, scope, when each makes sense, and the questions to ask before you hire either one.
CTO vs VP of Engineering: how the two roles actually differ
CTO vs VP of Engineering explained: who owns architecture, who owns delivery, when to split the roles, and how to avoid the overlap that breaks engineering teams.