Code Story episode
S10 Bonus: Overcoming the 75% Failure Rate with Rigid Process Mapping and Strategic Co-Sourcing Architecture with Elkhan Shabanov, CEO of Digicode Americas
Oct 17, 2024 · Season 10 · 29 min
Software development partner, not shop
Elkhan Shabanov was born in the Soviet Union, and started out in the tech world. He eventually left tech to try some other types of businesses, but eventually returned. He has done a few early stage startups in the past, in particular in the 3d printing space before it was cool. Six years ago, he joined his current venture. Outside of tech, he enjoys traveling, and is in a competition with his daughter to see how many countries he can visit. When he reads, he prefers to go back to the books he has read and enjoyed before, and being in Texas, he is a big fan of grilling out on his big green egg.
As I mentioned, six years ago Elkhan joined a company that wanted to be more than a software development shop. He and the founder of the company wanted to build a company that did more than throw bodies at a problem - but actually because a long term partner to their clients.
This is the creation story of Digicode.
Sponsors
SpeakeasyQA WolfSnapTradeLinks
https://www.mydigicode.com/https://www.linkedin.com/in/elkhanshabanov/
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.