Remember the goal here is not "make a demo for a site that looks like Fandango" but would be "make something that's truly better in terms of fit and finish and details and that can be proven better in terms of customer success and engagement metrics". AI might help with that, but it's not going to be something an intern can do in two weeks.
Now I wanted to say "it makes it hard that they have to integrate with external systems such as the partner theaters" but actually I think the API economy has offered a way out of enterprise software complexity, see
https://en.wikipedia.org/wiki/Strangler_fig_pattern
but I think most people don't see it that way. Like my belief is that the main difficulty in the API economy is that 20% of API vendors just don't care how hard the client auth experience is, in fact they have an ideology that the best possible life is
https://www.youtube.com/watch?v=o2ObCoCm61s
but boy have vendors like Zapier really intimidated management into giving up 20 lines of simple Python for a "can't get here from there" nightmare.
I agree that Fandango is much more complicated than the customer experience, but an entire rewrite is definitely doable within a $2m scope (I would forecast closer to $500k).
Wouldn't you spend $2m today to make $10m more in 6-12 months, and spend $5m less on operations (fewer devs, fewer servers)?
This is pretty optimistic. In reality, when money or critical systems are involved they'd want to thoroughly vet the new work and that'll take a lot more than two months.
You're the one making the claim, demonstrate that it's not overly optimistic like the rest of us seem to think.
What's your opinion? do you think it would be significantly more expensive?
I can only speak from my past experiences with B2B. We had many B2B customers running ancient applications that would connect to us and transfer incredibly sensitive data. Getting them to update even a single application was not an option. The application may have been running for decades. The people that wrote it may be deceased or retired. Nobody knows what to do if it breaks so they dare not touch it, stare at it, taunt it or talk about it. It just works and nobody wants to create the crap-storm of creating something new that does not cover all the edge cases as a day of down-time could be millions or billions of dollars lost. Nobody want to be the one that caused that history making moment. Adding to this the application may be reaching out to dozens or hundreds of companies, government agencies, etc... and each organization expects it to work a specific way, yet there is no detailed architectural documents that would allow someone to flawlessly make a new application. Flawless is the key word. If a new thing is not flawless it will be immediately backed out and never spoken of again.
I know the migration cost isn't zero, but neither are the operations costs of the legacy software, or the losses from bugs and lossy software. and now the migration costs are very low
But many of these apps have loads of money on the table. Reduced operations & labor costs, increased revenue opportunity.
I'm more curious about the latter.
Care to elaborate? How much money? I'm intrigued.
Every click is a lost customer. I could find them $10m in added revenue in 30 minutes.
I could find $1m of lost revenue on their site in 30 minutes
Because they are not software businesses, so they treat it like furniture. If it looks like a furniture and it's right there, then what are you even asking, it's right there I can even see it