I can confirm the “goes silent” part isn’t hypothetical. We ran ours as a sales-assist bot during launch week and the credits ran out mid-campaign. No warning email until after it was already down.

The point about AI needing appropriate permissions is crucial. One of the biggest mistakes companies make is giving an AI agent the ability to promise actions without a real-time API connection to the CRM. When the AI says it’s done something but hasn’t, you lose the customer’s trust instantly.

The hidden cost of scaling AI right now isn’t infrastructure but it is human oversight. Businesses often expect AI to operate autopilot, but in reality, scaling poorly calibrated AI just scales risk. Until AI confidence rates are near flawless, you are not replacing your human agents: you are just changing their jobs from answering tickets… Read more

I like the point that software is increasingly competing with workflows. There are many legacy SaaS companies that are just fussing a chatbot on their 10-year-old architecture and calling it an AI feature.

Well, 200 active deals isn’t an enterprise scale yet, but it is enough to expose the weaknesses of AI-generated code. The prototype phase is a trap because LLMs are great at the happy path but terrible at the unhappy path like network timeouts, duplicate records and OAuth refresh.

Most SaaS companies have spent the last few years focusing more on generating revenue than on actual innovation. When a product becomes too complex, it is usually a sign that the company is trying everything to everyone to capture more market share.

Technical reliability is not enough. It should come with service reliability. A platform with 99.9% uptime is still a failure, if during that 0.1% downtime, their support team is unreachable.

The best approach may be hybrid: AI handling repetitive tasks while human beings manage complex, sensitive, or high-stakes interactions.

$300/ month app looks cheap until the person who built it leaves, or it breaks at 2a.m with no vendor to call. There are implicit costs in owning your own stack (maintenance, onboarding documentation and security patches) that you skipped over.

Interesting opinion, but I think you are underselling the importance of UX. Internal tools that are built by SI often lack the intuitive design that help, keep employee burnout low. If a tool is clunky or requires a prompt-heavy interface to navigate. You may save $40k on a contract but lose $60k worth of employee productivity because the… Read more