I can absolutely see your point about *not* describing what's built. It doesn't describe the business logic at all. But that's OK by me. The business logic can be adapted as long as the structure is sound underneath.
And to your point, that's why having an ER Diagram for the calendar or gantt chart portions is unneeded for me. I know it's business logic magic and I don't really even want to know *how* that works, lol. I just trust you on that stuff.
But when bolting on the Contacts, Projects, and Invoices, I'd like to see a quick overview of what it is we have and how it will address my data handling needs. Like you said, it's a big part of the sketch. Then I'd know right off the bat "oh, I'll need a payments table, I'll need an inventory table, I'll need a PO solution, but I won't need a lineitems table, mailings table, or a user table, cool."
By the way, the fact that you have an inferred "Company" table is awesome! I made that exact same choice 8 years ago with Indie Band Manager and have never regretted it.
Thanks again for all your hard work on this John, the more I use it the more I like it. It's an elegant piece of work and I hope you feel you're getting the kudos you deserve. I'm really grateful for what you've made.