Avo beyond admin panels

I've been marketing Avo as an admin panel framework for years. And it's a very good one, but I think it's time to make the distinction between a "thrown-together" admin panel that nobody really uses (because they're afraid of touching the data or they don't have test coverage) and robust, optimized, well-tested, and documented operational software.

I never bashed other solutions. I tried to learn from them. They were built in different times with different technology and probably different goals in mind.

Avo isn't this "glorified database browser" that only does basic CRUD. One thing our users and I noticed right away was that these labels—admin panel, internal tool, content management system, CRM—they all blend into this fully customizable digital brain of your product.

And that's what we're all about: providing the tools you need to build the infrastructure to run your company.

Tools that evolve with you from one person to a few hundred people, like some of our customers have. Tools that are battle-tested by multiple organizations at once. Tools that have the features you need before you need them. Tools that put your mind at ease and enable you to ship the more unique aspects of your app instead of boilerplate.

So I'm curious: where do you draw the line between "admin panel" and "operational software"? What are your pain points with internal tooling right now?