Code Story episode
S6 E9: Bootstrapping the Knowledge Economy: Scaling LearnWorlds to a $32M Growth Engine with Panos Siozos
Mar 15, 2022 · Season 6 · Episode 9 · 37 min
Learning platform, focused on the creator
Panos Siozos and his co-founders go back 25 years or more. They all studied Computer Science together in Greece and did their post graduate studies on educational tech. His hobbies have been on pause for the past few years, given the growth of his business, but his main passion is his family, and his 8 year old daughter. They are building a 3d printer together, and tend to create using lots and lots of legos, including lego animation. His family helps him to see the power of learning something, and recites that learning is something that no one can ever take away from you.
During their post graduate studies, Panos and his co-founders built many products in the learning space, as they were crafty and could implement the things they were imagining. During their time, they shared the passion to create products that impacted the masses, and enabled them to learn better.
This is the creation story of LearnWorlds.
Sponsors
ImmediateOrbitPostmarkStytchVerb DataWebapp.ioLinks
Website: https://www.learnworlds.com/LinkedIn: https://www.linkedin.com/in/siozos/
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.