Imagine renewing Canva at a company where the sales team makes its decks in Claude. Marketing still wants Canva. It keeps the brand kit there and uses the editor every day. The sales director remembers typing a few sentences into Claude and getting back a finished presentation. She has a reasonable question about the proposal on her desk: why are all her reps on it?
That decision matters a little more after Anthropic’s IPO. The company priced 980 million shares at $83 each, giving it a fully diluted valuation of about $1.5 trillion. In its midday market report, the Associated Press put ANT at $98.56, up 18.7% from the offering price, after the shares briefly topped $115. About $79.4 billion of the $81.34 billion offering goes to Anthropic before fees. It already has a business that can sit down with a software vendor’s customers and build something for them. Ode with Anthropic helps midsize companies implement and maintain systems that use Claude.
For years, selling business software meant persuading a company to adopt your product and then selling more seats as more employees used it. Claude gives those two decisions room to come apart. A company might depend on Canva for every deck its reps send and still want to buy Canva only for the design team. We think some software businesses will end up selling a capability by the deck, the search or the transaction. Others will lose the account altogether once Claude or another supplier can do the same job. The difference is what the customer would have to give up to switch.
What Salesforce can give away
Under the Claudeforce agreement, Salesforce made Claude the default model for several products, including Slackbot. Salesforce brings account records, permissions and rules about who can change a deal. A manager asking why a deal slipped might prefer to ask Claude. She still needs the revised close date in Salesforce before Friday’s forecast. Her CRM subscription is fairly easy to defend. A proposal to buy her a second assistant will get a closer read.
Slack’s interest in the arrangement depends partly on where that manager asks her question. If she calls Claude into the account team’s thread, the rep who spoke to the customer can correct the answer where everyone will see it. That exchange gives the team a reason to spend more time in Slack. If the manager gets her answer privately in Claude, Slack may have supplied the crucial conversation and still missed the follow-up.
Where the work goes after Claude answers
Figma lets a developer bring a working interface from Claude Code into a design file as editable layers. A designer who used to receive a screenshot of a prototype can now move the checkout button herself and show the developer where it belongs. In that instance, using Claude creates work the team will do in Figma.
Canva’s connector lets the rep apply a Brand Kit inside Claude. For a designer building that kit, Canva is still a place to work. For the rep, it can already function as a plugin. Canva could do very well out of that arrangement if easier access means a company produces hundreds more Canva designs. The weaker position would be to depend on Anthropic to bring in each request while buyers come to regard any presentation tool that respects the house style as an acceptable substitute. At that point, the person choosing the software may be the administrator configuring Claude.
Which subscriptions would a buyer actually cancel?
A department head can use Atlassian’s connector to ask Claude about a release using information from Jira and Confluence. An engineer still has to record what blocked the release, and somebody has to document the decision to push it back. The department head might visit Jira less often while relying just as heavily on the people who keep it current.
On monday.com, Claude can create a board, change an item’s status or add an update, subject to the user’s permissions. An account director could move a launch date from inside a chat, and the production team would see the change on the board where it schedules the work. That board would be a nuisance to replace. A second board somebody maintains just to prepare the director’s weekly status report is a more plausible cut.
A law firm can use Claude inside Harvey or buy access from Anthropic. On a live acquisition, Harvey’s Vault lets lawyers compare contract terms, check findings against the original documents and control who sees each client’s files. Suppose an associate finds a change-of-control clause that requires written consent. Before the deal can close, the partner needs to know which other contracts contain one and whether anyone has checked them all. Access to the same model elsewhere does little to spare the firm that work.
We’d watch companies buying software for a new team. Existing customers have years of files to move and colleagues to retrain. A new team can start in Claude and add tools only when it runs into something Claude can’t handle. A partner running a deal has a reason to request Harvey by name. A manager who needs a Friday status report may be happy with whichever connector IT has already enabled. Software can survive either purchase. Only in the first does the software company have a customer who went looking for it.




