Luca Candela

This is a great counterpoint to AI's Bitter Lesson. Brute-force computation outperforms elegant design *where high-quality data* is available. Chess, go, and even grammar have objectively correct success conditions. Not everything does, and the Bitter Lesson may break down there. https://lnkd.in/eSMh-cmy

1

1 Comment

This might well become the UX debate of the year. Personally not convinced by Eric Schmidt's point. Natural language is powerful — but often not the most efficient way to consume or input information. I’d bet on a hybrid: co-pilot-style paradigms or structured UI components interleaved with natural language, depending on the context. The future UX isn’t NL everywhere — it’s NL where it makes sense.

29

6 Comments

Enterprise workflows often receive files dynamically (invoices, resumes, forms, attachments). The Runtime File Processor Tool in AI Agent Studio enables AI agents to read and process these files during execution, extracting usable content and feeding it into downstream automation steps. By interpreting runtime attachments - not just predefined inputs- agents can support document-driven workflows, richer interactions, and smarter end-to-end automation. I enjoyed reading this article from Gautam Rajgarhia .. https://lnkd.in/guRfsTic ... and in about two weeks, the 26B release will also introduce a dedicated workflow node type to manage runtime file uploads from end users, making it easier to capture, process, and route uploaded documents within agent-driven workflows.

164

2 Comments

Avoiding Claude Code because the terminal feels intimidating? Cowork changes that. Same power, zero command line. Anthropic released Cowork today and I've been testing it. Here's what makes it different: Cowork lets Claude interact with your computer through a visual interface. No typing commands. No scary black screens. What you can actually do with it: - Organize messy file folders automatically - Turn a pile of receipts into a clean spreadsheet - Draft reports by pulling data from multiple documents - Rename hundreds of files based on patterns - Create presentations from raw research notes This is Claude Code's capability through a visual interface. The same parallel processing that developers use, but accessible to non-technical users through Claude desktop. Worth exploring if you spend hours on repetitive computer work.

3

I don't think AI has killed SaaS (yet) but I do wonder if it's killed "value-based pricing" I've been doing a lot of software shopping the last month, particularly in the conversational AI space, where there's a Cambrian explosion of vendors figuring out business models in real time. You can find it all: conversation-based, outcome-based, platform + usage-based, and tier-based tied to some specific platform feature. Overall, "value-based" is the framing I'm most allergic to these days. Time was, a vendor could win with a high sticker price by anchoring to the outcome or business impact the solution would drive. This is generally a sales best practice. But at a time where the line between build and buy grows ever thinner, when customers have built their own agents, understand inference costs, and have seen how thin some product wrappers actually are -- value-based feels untethered. The age of AI doesn't mean I'm going to build every tool in Claude Code. But higher buyer literacy DOES mean that the relationship between your sticker price and your underlying cost-of-goods-sold is going to get more scrutiny. I'm happy to rent your application layer (and the expertise it encodes) and pay a reasonable cost for maintenance and support. But charging a disproportionate premium that's not moored in variable costs like inference and compute seems increasingly hard to justify. If your pricing can't survive a conversation with a buyer who's been tinkering in Claude Code for six months, you have a problem.

59

17 Comments

Seat-based SaaS pricing made sense when software value scaled with headcount. AI flips that model. The better your AI gets, the fewer humans you need to operate the workflow - so seat-based pricing can actually punish adoption and cap vendor upside. Meanwhile, usage (transactions/volume) keeps climbing because AI enables teams to do 5–10x more work with fewer people. In the AI era, pricing should track throughput, not logins. Read the full take here: https://lnkd.in/gAKnSv6c #LegittAI #ContractManagement #Contracts

21

2 Comments