[davidpolberger]

The flowchart you link to looks a lot like the workflow editors offered by no-code and low-code app designers:

https://docs.bettyblocks.com/en/articles/998093-what-are-act... https://www.zoho.com/creator/newhelp/new-workflows/understan...

I can imagine that what your engineering team built is tightly coupled to a product, allowing its logic to be customized easily with no involvement from engineering. In order to productize the solution, I'm assuming that you'd need to create hooks allowing a different engineering team to integrate it with their particular product, before non-technical people could use it?

We're on a mission to do something similar, but using Excel-like formulas instead of flowcharts: https://news.ycombinator.com/item?id=25389963

These formulas are currently used by our app builder, but we will make the formula engine available separately sometime this year. The idea is that other engineering teams will be able to integrate our formula engine with their products, allowing non-technical people to customize products through the use of formulas.

[white]

Interesting you bring this up. Actually, our implementation was intentionally de-coupled from the product and it's based on auth API endpoints. (So yes, for something beyond basic conditional logic, this needs to be enabled first.)

Before a call, this diagram comes with manifest of what data has to be supplied into it. So once it's called, all prep data is there. Whatever happens inside is data manipulation and some basic operations. The output of it is also described in the contract.

Very similar to how customized pricing/rating engine might work (as, in fact, I was PM for one of such).

Your project seems fun, too. I'm pretty sure you are going after some specific use cases.