If you're going to do this I recommend you at least take these things at heart: Why do developers slow down > https://youtu.be/7EmboKQH8lM?t=1476 https://yout

If you're going to do this I recommend you at least take these things at heart: Why do developers slow down > https://youtu.be/7EmboKQH8lM?t=1476 https://youtu.be/7EmboKQH8lM?t=1476 80% of developers are unhappy. The problem is not AI, nor is coding > https://shiftmag.dev/unhappy-developers-stack-overflow-survey-3896/ https://shiftmag.dev/unhappy-developers-stack-overflow-surve... What you're looking at is starting greenfield development. This always starts in the same way: 'we need to deliver functionality quickly because management wants results'. This always leads to the same issue, where code quality is ignored for sake of delivering functionality, which then leads to development slowing down and both management and devs becoming unhappy. If you want to build something for the long term, I'd recommend starting slow. Get some experienced freelance devs where you do thorough reference checks. Get them to set up a stable core and help in hiring some medior level devs to train. The medior level devs can grow to become the coaches of junior devs and then you can start scaling down the freelance devs. Whatever you do, don't plan to release something within the first year. Don't ask the team to estimate a delivery date within the first six months. After six months you should have a baseline that development can be continued with and then you probably have a team that can start estimating work and has a grasp of what they need to do to deliver something useful. Also, get a good product person, someone who can talk to business, draw out the different parts of the application and explain them to the developers. All of these things are hard, so you really need to commit, or else you're setting up to fail.