One example that I can share, that would have also been a good Django candidate is our system for handling employee absence. When it launched it only let you report the two types of paid vacation we have, but being the public sector of Denmark, we actually have around 80 different types of legal absence, with various rules attached, and we knew we'd want to add more over time. We also knew every employee would need their own profile to keep track of their accounts, and we knew some managers would want to outsource the responsibility to secretaries and such. So that's what would be an obvious Django project to us, but it was build in .NET because that's what we were most comfortable with at the time.

It has a lot of extra stuff included in the framework that you might not need for a smaller app, but if you don't care about that extra overhead (or you need to use it) then Django is a great choice.

It also has a fantastic ecosystem of "apps" (what Django calls plugins or packages) that you can drop into your project which can save a substantial amount of time; which makes it great for consulting work.