Thanks for the feedback.
>I am looking at this and thinking, how many times would a typical user need this?
I am trying to keep the product easy-to-use and the price low to reduce this barrier. But I guess a lot of people would rather spend several hours tweaking their data in Excel, rather than pay $99 and learn a new tool.
>Is this meant to support ETL workflows?
No. I imagine my target user as a marketing guy, scientist or business analyst who has a bunch of CSV and Excel files they need to munge together and clean-up to get some useful data. Maybe they build a process that they repeat once a month or with several different datasets. But they aren't data science people building an ETL pipeline. In fact they have probably never heard of 'ETL'. Data science people seem fairly wedded to R, Python+Pandas and expensive corporate ETL tools.
>Is it possible to create transform recipe packs as part of the product offering?
I think everyone is going to have different data sets and different use cases. I'm not sure that is possible to generalize the process beyond the individual transforms.
>Is this something you can package as a component that other ETL products could plug into?
Probably not.