The bulk of the work is context engineering which is done outside of Fin. Once you do the context engineering, it's very easy to duplicate Fin's features. Seriously. Just try it.
You don't need a fancy editor for "if this then do this". A simple text document is all you need. And if you do need a fancy editor, it's extremely easy to build it in 2026. Maybe 1-2 days.
I'm not a SaaS believer anymore.
the bulk of the context engineering for users of these ai support platforms is done in the platform
and the amount of context needed to automate f500 is non trivial, plus you usually cant use reasoning because latency would blow up and you get escalated on
if this was so easy as you claim theres many millions for you to be made selling it to enterprises, but you wont
Have fun sinking 100s of hours into improving and maintaing that. Someone who sells software for real estate probably doesnt want to get into building software for customer service agents. This makes no sense. There should be urgency to make the product your selling better, not wasting time building support tools. Just pay for it.
Maybe you've done this yourself. I'm honestly jealous if solving customer support was as easy as your describe.
In my case, I've spent the past 12 months running implementations at multiple companies. I've engaged directly with smart engineering teams to assist. It was not that easy.
What you outlined might work for a simple ecom business. It probably does 95% of the job for a simple case where you're delivering information. But it will fail the second it needs to take action or deliver personalized information based on client's account data.
That leads to the exact issue people here complain about... an LLM that doesn't actually answer the question, can't solve the problem, and is worse than talking to a human