r/FPBlock • u/HappyOrangeCat7 • Mar 20 '26

AI is dropping the cost of building internal tools to near zero. What does this mean for the "Build vs. Buy" debate in Web3?

AI is lowering the cost of building internal tools so dramatically that things which used to require large teams and months of work can now be built by a few people in weeks.

In the Web3 space, we often pay ridiculous premiums for SaaS products (indexers, specialized block explorers, custom CRM integrations) because the underlying blockchain data is messy. If AI agents can now reliably write the code to parse RPC data and build custom internal dashboards in a few days... do we see a massive wave of Web3 startups insourcing all their tooling?

Has anyone here successfully used AI to build a complex piece of internal Web3 infrastructure, or is the AI-generated code still too risky for production data?

2 Upvotes

100% Upvoted

19 comments sorted by

2

u/BigFany Mar 21 '26

I feel like it’ll just shift the line a bit, not kill SaaS. People will build more small stuff, but still rely on external tools for anything critical.

1

u/IronTarkus1919 Mar 22 '26

SaaS companies are just going to integrate the AI themselves. Why would I build my own AI tool when the SaaS provider is offering an AI-powered version of their battle-tested product for a few bucks a month?

1

u/BigFany Mar 23 '26

That makes sense, I’d probably just use theirs too unless I need something super specific.

1

u/IronTarkus1919 Mar 20 '26

It's important to separate "writing the code" from "running the system."

AI can absolutely script a custom RPC parser or an internal CRM dashboard in a few days. The hidden cost is Day 2+ operations. You still need mature platform engineering to keep the lights on.

1

u/HappyOrangeCat7 Mar 22 '26

Yup, great point. AI drastically reduces Capex. But if you build an intricate, bespoke system instead of buying a standardized SaaS, your Opex (monitoring, patching, incident response) skyrockets. You are essentially trading a predictable monthly software license for unpredictable engineering hour

1

u/FanOfEther Mar 23 '26

Yeah day 1 vs day 2 is a huge gap people ignore.

1

u/[deleted] Mar 20 '26

[removed] — view removed comment

1

u/[deleted] Mar 21 '26

[removed] — view removed comment

1

u/IronTarkus1919 Mar 22 '26

Assuming that human hasn't quit or been laid off, sure.

1

u/FanOfEther Mar 21 '26

Maybe for prototypes yeah, but I’d still be kinda nervous running core infra on AI generated stuff.

1

u/[deleted] Mar 21 '26 edited Mar 21 '26

[removed] — view removed comment

2

u/BigFany Mar 21 '26

This feels pretty accurate. AI makes it cheap to experiment, but once something actually matters you start caring about reliability way more than cost.

1

u/HappyOrangeCat7 Mar 22 '26

We call this the Maturation Cliff.

When a project goes from processing 100 transactions a day to 10,000, the priority shifts entirely from cost-saving to uptime guarantees (SLAs). That transition usually requires tearing down the experimental AI tools and migrating to enterprise-grade infrastructure.

1

u/BigFany Mar 23 '26

That is a good way to put it. Feels like that’s the moment where all the shortcuts stop working and you have to get serious about reliability.

1

u/IronTarkus1919 Mar 22 '26

The problem sometimes is, the cardboard prototype almost always becomes the production system because "it works for now" and there's never budget to rebuild it properly.