[yellow_lead]

Although this may attract developers initially which is the original question, this seems like an ineffective strategy for a business. In The Mythical Man Month, the author argues that one of the most important things in software architecture is conceptual integrity. Having many different architects cycle through seems like a great way to end up with too many different ideas in your systems and a poor conceptual integrity.

Maybe this could work for a short time at a startup, but I'd be curious to know your thoughts in response.

[pizzaparty2]

That's a good point. I left out a concept of constraints. For example, it has to be written in the same language as our other applications. But if it's not different enough from an existing application just copy the existing application and don't call it a greenfield.

Or let someone burn their turn by copying the existing application but making minor tweaks and changes. That could work just as well.