Recipes as Standalone Product
Wordware
Recipes point to a second business inside Sauna, because once an assistant learns how a person repeatedly handles work, that know how can be packaged and distributed far beyond the original user. Wordware already describes Recipes as reusable automations derived from repeated tasks, and Sauna is built around shared spaces, persistent context, and background execution, which makes role specific recipe packs a natural product for recruiting, executive ops, sales ops, and legal admin.
-
This is different from classic automation templates. Wordware v1 asked users to build flows up front, while Sauna watches real work, learns the pattern, and then turns it into a repeatable recipe. That makes the template more like captured judgment than a static if this then that rule.
-
There is a proven market shape for template distribution. Zapier runs a large public template library, and n8n has an official workflow template system, showing that packaged automations help users start faster and create ecosystem pull. Sauna could apply that model to higher judgment desk work instead of simple app to app handoffs.
-
The team product is the bridge to standalone value. Wordware already frames shared recipes and org level permissions as the path from individual adoption to larger contracts, so a recipes catalog could become both a product led acquisition channel and an upsell layer inside team workspaces.
The next step is a shift from personal automation to network effects. As more users let Sauna observe hiring loops, inbox triage, meeting prep, and reporting work, the best recipes can become a library of role specific playbooks, which would give Wordware a distribution surface that compounds alongside the assistant itself.