登録して招待リンクを共有すると、動画再生報酬と紹介報酬を獲得できます。

Romain Lapeyre
@Romain_Lapeyre
Co-founder & CEO @gorgiasio. Building Conversational Commerce, starting with Support and Shopping Assistant.
参加 March 2010
735 フォロー中    1.6K ファン
It's been one month we've moved to usage based pricing on Claude, which in my case costs 6x more than the previous subscription cost, so I wanted to share some of the learnings I had through this period. BEFORE AUGUST (everything on Claude world) - We had packaged our company skills and MCPs on github with the whole company contributing to these - I would use max out claude weekly limits each week and use opus as my daily driver - I would hit limits and had the need to connect user mcps to run certain tasks, for instance truly doing email (vs just creating drafts), doing slack from claude on shared channel, properly doing google slides, etc.. Some of these MCPs could only run on my laptop NOW - Our internal AI team has done a wonderful job building an internal platform that is connected to all the skills, MCPs we need. It loads all our skills, all the necessary MCPs - We are able to tweaks MCPs the way we want and host them in the cloud. It outperforms Claude when we tag it on Notion comments or mention it on slack for my use case - We are able to plug routines with the exact context we want via slack apps - Everything is multiplayer and cloud first, which is better for collaboration + work on the go - We can easily experiment building agents that are customer facing in a multiplayer way too - Cost remains in control, you choose the model, it's a mix of Kimi 2.7 for basic tasks and frontier models for more complex ones - Where there's something I want to change, I can PR into it and get the change live within hours Net net, I'll miss what felt having unlimited opus access, but the ease of use of having your own internal platform really well connected to our own tools is a game changer. More on this here:
もっと見る