This misunderstanding is valid. Another example is why subscription/recurring billing software exists when payment gateways can solve this problem themselves.
The elephant in the room is the complexities involved down the funnel that need very specific focus/solutions.
A few that we experience as we’re building Trellis out:
1. Managing end-to-end workflows from integrating with data sources, automatically triggering new runs when there’s new data coming in, and keeping track of different business logic that’s involved (i.e. I want to classify the type of the
emails and based on that apply different extraction logic)
2. Most out-of-the-box solutions only get you 95% of the way there. The customers want the ability to pass in their own data to improve performance and specify their unique ontology.
3. Building a good UI and API support for both technical and non-technical users to use the product.
