Insight

Claudeforce

The product used to be the place you signed into: the screen, the nav, the logo in the corner. Now the biggest CRM ships itself as a set of skills inside somebody else's interface. The product isn't the screen anymore. It's what the screen can be asked to do.

The old shape: one product, one front door

A box labeled "the app", with a login, a nav bar, and every workflow living inside it. Users come to the product; the product owns the whole visit.

The new shape: one product, many mouths

The same box, but the screen is gone from the middle. Around it: Slack, a chat assistant, Teams, SMS, another agent — all calling the same governed skills. The product is the capability, not the container.

What actually stays yours

Peel the layers: the UI is now replaceable. The data model, the permissions, the audit trail and the skill definitions are the moat. The design work moved one layer down.

Every account manager I've watched lives in email and Slack. The agency management system is the tab they open when they have to, and close as soon as they can. Most of what we call an adoption problem in this category is really a "please come to my screen" problem.

Then I read about Salesforce shipping as a plugin inside Claude, with 37 prebuilt sales skills, and one of their execs saying it out loud: the Salesforce user interface might not be the future of their business. The same week, Workato launched agents you can reach from Slack, web or SMS. A CRM admitting its interface isn't the product. The skills are.

Each skill is a named, governed action. Draft the proposal, check the pipeline, update the record. Callable from wherever the person already is. The screen becomes one client among several, and probably not the most used one. Read that back with agency verbs and it's the same list: draft the remarketing note, pull the loss runs, update the record.

The first thing I wanted to say was "then let's build our own chatbot too." That's the wrong layer. The work is the skill catalogue: what each skill is called, what it needs, what it returns, what it's allowed to touch. Get that right and any surface, a person or an agent, gets the same behaviour. I haven't written that list for anything I work on yet, but I think about it every time someone asks for a new screen.

I still design screens most days. I'm just less sure they're the product.

Claudeforce

The old shape: one product, one front door

The new shape: one product, many mouths

What actually stays yours

References