Yep. You’re on the money. Look at it this way. The product I worked on got acquired, and we went from a 5 person bootstrapped company that knew the product inti

Yep. You’re on the money. Look at it this way. The product I worked on got acquired, and we went from a 5 person bootstrapped company that knew the product intimately, to all sorts of far less familiar customer support, sales, etc people needing to do various sorts of “admin” actions. I flat-out refused to subject these newbies to Django admin, and prioritised building proper administrative tooling. That decision has paid dividends. Django admin by its nature is always going to expose idiosyncrasies of your data model and by its own admission doesn’t give you infinite opportunity to insert your business logic layer. Cue someone used to working in “scale until you die” startups telling me that any time not spend on juicing MAU is time wasted. I like working in sustainable businesses. I’ve worked with Django for a decade. I’ve done ungodly things with Django admin. Things most people wouldn’t dream of. I am completely over doing any of that. This isn’t a fault of Django admin. It’s very good at doing what it’s intended to do. It’s just a very common beginner’s trap to try to push it further than it wants to go. There’s plenty to critique Django admin for. I fought with it just last week. At the same time, most complaints I see about it tend to be people (IMO) misusing it. It’s the service panel. And yes, people other than the engineers that built the thing have reason to pop open the service panel. These are your mechanics. But, and especially for SaaS products, don’t conflate “user” with “customer”, and not think about your other audiences.