I think spam is just a nuisance, not a big problem. What is a big problem when hosting providers or your email server are blocking or marking as spam legitimate business communication.
It has happened several times to me that I have not seen a customer's email because it was marked as spam and likewise customers have not seen my email as it was sorted in their spam folder. This is a breakdown of communication that is far worse than spam.
A classic use case that is more likely to be flagged as spam is when a customer submits a request via a web form or on social media and you try to follow up by email. From the receiving email server point of view this is a cold email and in danger of being flagged as spam.
This is an increasing problem and I too think that larger providers try to get control over mail infrastructure.
GMail isn't really a solution for professional correspondence in my opinion. I am surprised so many are oblivious to that. Other private mail providers didn't keep up with SPIF, DMAC rules/configuration and large providers like Microsoft and Google might blacklist them outright.
Leaving mail infrastructure for shitty tech companies is a larger problem than some spam in my opinion as there are powerful solutions available already.
Then make it a one-time purchase valid for 3 or 5 years and after that customers need to pay again. Kind of in the middle between strict one-time only and classic SaaS that auto-renews.
Or: before SaaS we used to have the model of one-time purchase + annual maintenance fee (which was a small percentage of purchase, like 5-10%). The benefits of the "maintenance fee" to be defined by you. But it used to include updates of software and in enterprise context often support.
If I understand this correctly, you are proposing to deconstruct (a priori unstructured) documents into structured data, no?
I think you need to have a demo use case in your app so people can better understand what this is about.
I tried to make an invoice document type. So far I got simple header data and line items and I created a method to add up line items to a total. It would be nice if methods could be triggered to run automatically. I can place buttons to run methods, but can I run a method at document update or field update?
Also I to speed up creation of methods you should have simple aggregation function like summing all items of a list (given a field name to sum over).
Well I'm proposing to have a workspace with everything structured indeed, where all the documents would be "programmable" and "queryable" and where unstructured data would simply be attachments of structured data.
At some point when uploading a new "file", I think the framework should systematically call a multimodal LLM to extract structured data from it, so that it can be queried from anywhere in the workspace. My main concern on this is that the LLM should stay local...
Yes you are right this is lacking a good and simple demo usecase, I'm working on it.
Yes, as you've seen, some field types have a limited set of "builtin methods" that I've added just for the demo, and List is clearly the one that should have much more ! (map, reduce, filter, sort, sum...).
And indeed, being able to call methods dynamically in "formulas" like Excel does, and not just when clicking on buttons (what excel calls "macros") is a must-have as well !
It has happened several times to me that I have not seen a customer's email because it was marked as spam and likewise customers have not seen my email as it was sorted in their spam folder. This is a breakdown of communication that is far worse than spam.
A classic use case that is more likely to be flagged as spam is when a customer submits a request via a web form or on social media and you try to follow up by email. From the receiving email server point of view this is a cold email and in danger of being flagged as spam.