Our clients are small and medium size manufacturers (e.g. furniture). They need to distribute data to their salesforce - catalogs, pricelists, pictures, credit application forms, assembly instructions, etc. 50 years ago they used paper for everything, 15 years ago they switched some document distribution to FTP - the documents which you don't need to close the sale, but those that must follow after (credit applications, assembly instructions). Then Dropbox came along, and half of them jumped to replace FTP with that. FTP has its own problems, DB has its own. You're right in that it's a wrong tool for the job, but that's what they use for the (perceived) lack of better alternatives. My point is that Dropbox is often times used where it doesn't fit, so there is plenty of room for competition in the "file-sharing" space, which is counterintuitive - one would think that Dropbox owns the space by now.
Going back to my first paragraph... What is the minimally viable content management and distribution system (CM/DS) for such business? It's a Dropbox that doesn't let "subscriber" users delete files (and is otherwise friendly to low-tech "subscriber" users). The sales manager will load it with PDFs and JPGs and Excels, and the sales reps will then get the files and use them. That's MVP. What is the ideal system? Rather than distributing the product catalog as a pile of JPG and Excel files you would want to distribute a native catalog application where the list of clients is well-organized, history of the past orders is right there next to each client, all products are neatly categorized, and it's easy to build a new order with all the math done for you. In other words, rather that treating content as opaque files, this CM/DS is keenly aware of the inner structure of the data and about the workflow surrounding use of that data. This awareness begets usability and accuracy. That's the vertical-specific CM/DS I am talking about.
Yeah, I think it was the liberal use of "vertical" in your elevator pitch that made it confusing.
You're building a one-way file sharing app.
The other things you're talking about, is your goal to build a point-of-sale or sales management system? What's your goal for differentiating yours against a relatively broad market? A cheap, low-feature alternative to the biggers CRMs and Sales systems could certainly provide a service.
For example, how does your vision compare with the customer management, inventory, product development, etc. from Square: https://squareup.com/ ?
We're primarily wholesale, not retail, so it's not POS and not competing with Square on any level. Not yet, anyway.
A better comparison is SAP - the data management that we provide can be done in SAP for a few million dollars, but if you happen to be in the vertical we're targeting, like furniture, and have modest needs, you can go wih us for two orders of magnitude less, and it takes only hours to set up because it's tailored to the vertical. That is the differentiator - vertical tailoring makes it quick and cheap to install.
I've been in it so deep for so long, it's surprisingly difficult to explain...
Going back to my first paragraph... What is the minimally viable content management and distribution system (CM/DS) for such business? It's a Dropbox that doesn't let "subscriber" users delete files (and is otherwise friendly to low-tech "subscriber" users). The sales manager will load it with PDFs and JPGs and Excels, and the sales reps will then get the files and use them. That's MVP. What is the ideal system? Rather than distributing the product catalog as a pile of JPG and Excel files you would want to distribute a native catalog application where the list of clients is well-organized, history of the past orders is right there next to each client, all products are neatly categorized, and it's easy to build a new order with all the math done for you. In other words, rather that treating content as opaque files, this CM/DS is keenly aware of the inner structure of the data and about the workflow surrounding use of that data. This awareness begets usability and accuracy. That's the vertical-specific CM/DS I am talking about.
Does this make more sense now?