I did not build Edventory on a sabbatical with a runway and a team. I built it, and I am still building it, while running technology for two districts full time. That is not a complaint, it is context, because the constraint shaped the product in ways I think are good.
When the only time you have to build is the time around an already full job, you become ruthless about what is worth building. You do not add features for a slide deck. You add the thing that is going to save you real hours next week, because next week is coming whether the feature exists or not. Every piece of Edventory had to earn its place against a very simple test. Does this make my actual job easier, starting now. If it did not, it did not get built, because I did not have the spare hours to build things that do not pay off.
It also means I am the first and harshest user of everything. I do not get to ship something half baked and move on, because I have to live in it the next morning, in the real job, with real tickets and a real budget. The dogfooding is not a strategy, it is just my life. The shortest possible feedback loop is one person who builds the thing and then has to use it under pressure the next day.
I think you can feel that in the product. It is focused, because the person building it had no time to waste. It is practical, because it was built by someone who needed it to work, not someone imagining what schools might want. The day job is not a limitation on Edventory. It is the reason it is honest.