But this is not really a question as The-Data-Box is not addressing the same needs.
On one side, we have the "big products" that are file-oriented, and they are very good at it.
On the other side, we have The-Data-Box, which is data-oriented.
With The-Data-Box, you don't handle files, but you handle "data".
Data "can" be files if required, but it's mostly a structure of informations.
From the beginning, I wanted to have a flexible data structure in order to address the simplests needs for small to medium business companies. This particuliar flexibility of The-Data-Box allows the users to imagine their own solution, depending on the data they need to store and process.
Do they need a specifc structure to store their bills ?
Is it only for future searching ?
Is it to validate it through a workflow ?
Is it to share it with other people ?
Is it to make stats about the bills, consolidated by year and by month ?
...
With The-Data-Box, the response to this kind of questions will define the "Box" used to store the bills. In this case, a "bill container".
In short, they just have to decide the structure of the Box (more or less, form fields), and which standard features they want to activate for this box : workflow, versionning, sharing, linking, discussion...
In the end, the right word for a Box is versatile.
On top of this, The-Data-Box allows the users to handle their data in very soft and friendly manner, with no technical skills required because everything is setup with detailed and easy wizards, and no code at all.
From the start, I've really wanted that the work left to the users is as small as possible, and I've brought the wizards at the heart of the product... The-Data-Box is a "w w w product" :
Wizard, Wizard, Wizard !
Honestly, I think I'm now close to the goal... Ok, I still have to enhance some details, but, hey, it's still in beta...
Below, the Box versatility illustrated :
