This is the same reasoning people use to say SaaS is dead, but it makes no sense. Rolling things yourself is often 10x more costly and not worth it, even with agents you need to pay 5-10 guys 150k-250k a year to build and train your own agent, why not pay fin 250k flat and not deal with any of it? Same goes with basically all other software that has nothing to do with your core product.
I see absolutely zero value in something like Fin. There is no model training needed. It's all context. Anyone who is training a Qwen model for their customer support is doing it wrong. Paying Fin $250k flat does nothing since it isn't going to actually know how to solve problems. The real challenge is the knowledge and context engineering and Fin doesn't help there. The technical stuff is really easy to build.
"Paying Fin $250k flat does nothing since it isn't going to actually know how to solve problems. The real challenge is the knowledge and context engineering and Fin doesn't help there"
You misunderstand the model. Fin does not have flat fee. They charge exclusively for resolutions. That's the entire value prop.
Correct that knowledge and context engineering are the key. Fin DOES help here. They have an entire backend suite to help you build out areas where Fin is failing. It shows you questions it couldn't resolve, looks at the answers your human team gave, and suggests updates to help articles to
You're correct this could all be build by a skilled engineer, but that's not the point. It's built for non-techincal users to use and implement. A person who rose through the support ranks and shows some technical competency can learn the system without any software knowledge.
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.
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
In 2026, every time I've tried to build a custom tool to replace a SaaS, I've succeeded. The biggest problem with SaaS is that they build a one size fits all. When you build a custom tool, you control everything from data to UI and it works for your business.
Many, many people do not have the capacity to build and maintain custom solutions (whether in-house skills, or simply bandwidth) and therefore outsource to vendors.
It's an incredibly common aspect of business. Enterprise level contracts often include the sort of white glove service to help fill in these sort of gaps. On simpler plans, having the tooling provided frees up just enough capacity to handle the exceptions to keep the process running smoothly (since one doesn't have to build and run simultaneously).
Sometimes people want to minimize the hassle with stuff. It's why car washes and oil change places and coffee shops exist.
For the last 15 years, I'm that person in the company who always said "let's not build it ourselves".
In the last 6 months, I'm that person in the company who always said "let's just build it in a few days".
I agree with you 100%. Fin and products like this simply do NOT solve the hard part of providing support in 2026. Basically, the hard parts are (1) coming up with the tools for agents to use, like searching for data, making updates, etc. (2) reviewing the logs of actual usage and adjusting prompts, docs, tools based on the real feedback. (3) tuning human escalation procedures.
This process is an ongoing effort, with an upfront engineering commitment which depends entirely on the product, but can be months of work. But if you have your own backend, I would argue this hard works is made HARDER by implementing something like Salesforce/Fin, because you have to now pipe a bunch of data and structure over to them, which is a pain.
LLM models capable of doing this are a commodity, the UI for customers and support teams is pretty trivial, the database/backend is trivial.
Outside of some cases, if you have your own app, and you have a given support volume, build your own.
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
F500 is exactly the kind of scale where I fully expect support agents to be developed in house. They'll try Fin. Then one day, a single dev inside the company demos a custom agent that outperforms Fin and cost almost nothing.
tech forward f500 is possible (but.. even anthropic used fin)
most f500s are going to outsource. i think sierra is already at 40% of the f50? and each of those deals they have to compete against teams of inhouse engineers and convince execs to buy instead of build
the reality is agents at scale is a hard problem and most f500 engineers are not equipped to solve it
Rolling something yourself was a waste of time when SaaS was cheap and competitive.
Not they’re all getting incredibly expensive, even the last few startups I worked at were paying hundreds of thousands of euros for services that were total garbage.
Do I really need a crappy 20k/yr app to help me with my 1:1s? Do I really need a 100k/yr clicks counter that requires two devs to keep running and still heavily miscounts the clicks? Do I need another crappy app to manage my translation JSON files?
> I see absolutely zero value in something like Fin.
The value, of course, is that there is a website with a chatbox that some MBA can type in "never give any refunds anymore for any reason", and it just updates the AI support agent and sends an automated "I deserve a promotion and a raise" to their boss.
Yes. I agree. When I look at Fin's home page and marketing, I think to myself that this stuff can mostly just be text documentation given to an LLM. It's a tool built for MBAs but most of the work is done by a software engineer to give Fin that context in the first place.
So all Fin is is a UI on top of the context engineering done by a software engineer who integrated with Fin. It's extremely easy to duplicate Fin's UI and get rid of the $250k fee.
Well, it's a few weeks of work, systems integration, and you'll need an SRE too if you're hoping to run it on any scale. But yes, I agree.
You'll need an SRE for Fin too. How else can Fin get access to your customer's data?
It takes the same amount of time to build a custom agent as an agent on Fin. All Fin does is provide a fancy UI for non-technical people to create rules.
They can create the same rules in plain text. If they want a fancy UI like Fin to do it, just build one in a day.
They call it rules? Because of course one of the defining properties of LLMs is that they can decide to deviate, reinterpret, or ... rules. Which makes them more like guidelines, or so the meme goes.
And why would Fin's LLM solve hallucination/deviation over Claude/GPT?
A rule is just a line of text to an LLM.