Building a DocSend/Papermark alternative — curious how others decide which features to skip

Hey PH community 👋

I've been building PaperTrack (papertrack.io) — a secure document sharing and data room platform inspired by Papermark and DocSend. It's for teams sharing sensitive files (pitch decks, sales docs, contracts) who want visibility into who viewed what, how long they spent on each page, and so on.

One decision I keep coming back to: I deliberately left out general folder/document organization. The product is built around sharing and tracking individual document links rather than being a full file-management system, and I've been going back and forth on whether that's the right call long-term or whether it'll frustrate users as their document volume grows.

So here's my question for the community: when you're building a focused tool, how do you decide what NOT to build? Do you wait for users to actually complain about a missing feature, or do you try to anticipate it upfront? Would love to hear how others have drawn that line, especially in tools that could easily scope-creep into "do everything" platforms.

Would love to hear your take 🙌