正在加载视频...

视频加载失败

Fun old lore fact. What they’re talking about here, the “second in command” for a space marine squad has technically already got a name “squad leader”, they even used to have their own backbanners. Nick Bayton, chief ultramarine fan at GW, came up with a non-official way of denoting...

20,172 次观看 • 3 个月前 •via X (Twitter)

0 条评论

暂无评论

原始帖子的评论将显示在这里

相关视频

Stripe’s strategy is to “win all the startups and then win them again.” I had a great time talking with Will Gaybrick. Will has held a broad seat at Stripe for more than a decade, joining as CFO in 2015, and today leading Technology and Business. This makes him the right person to explain how Stripe went from a simple payments API to a platform with ~25-30 banner products and 288 launches at its most recent Sessions event. Here’s what their strategy looks like: -Companies like DoorDash and Instacart started on Stripe when they were tiny and pulled the company upmarket as they expanded. -The fastest startups act as canaries for new product opportunities. Cursor surfaced a burgeoning problem of AI free-trial and token abuse; so Stripe built a token detection pipeline with the team in a weekend, and the resulting network now helps companies on Stripe’s platform block thousands of fraudulent trials daily. -Stripe keeps expanding the number of needs it serves inside each company, from Billing, Radar, and Tax to Managed Payments, Treasury, and stablecoin infrastructure. There is a large and timely lesson from Stripe which I strongly agree with: using AI solely to reduce cost is essentially going short your own company. Instead, companies should be using AI (and the tailwinds it creates) to ship more, serve users better, and create their next product line. And as Stripe continues to invest in agentic commerce, the company can move from processing a transaction to orchestrating the entire economic loop around it. The line between tokens and dollars is already blurring, and Stripe’s next mandate is to make moving between them as seamless and safe as moving between dollars and euros. A fun conversation about what it takes to build the next Stripe inside Stripe. a16z

David George

68,998 次观看 • 1 个月前

Stripe CEO Patrick Collison shares the tactics he used for finding product/market fit “We tried very hard to understand in granular detail what exactly it was that people were doing, where they were tripping up and so on.” Patrick gives some examples of specific tactics: • A public chat room to provide support to people integrating Stripe • For the first 10 users of Stripe, every API request sent an email to the founders so they could better understand how users were using their product and see if users were doing anything weird • All errors generated a high-priority email to the founders. This created a pleasant user experience where 15 minutes after hitting an error, Patrick could reach out to them and let them know the issue was fixed “These are all kind of examples of a general pattern of trying to be hyper-attentive to all the micro details of what people were doing in the product and iterating rapidly in response to it. Generally speaking, I think pre-product/market fit metrics are actually relatively unhelpful because probably not that many people are using your product. If it’s 20 users, you can in some sense afford to just look at everything they’re doing to understand what’s working and what isn’t.” Another example of this Patrick gives is embedding a text input on each of their web pages with placeholder text prompting users to give them useful feedback(e.g. “The worst thing about Stripe is…”, “The worst thing about this page is…”, or “I really hate the way Stripe does…”). As Patrick explains: “At that stage, you have to be kind of masochistic. We’d always be waking up to all these emails telling us all the terrible things about Stripe. But that was a helpful to-do list for the day ahead. Video source: Y Combinator (2018)

Startup Archive

45,833 次观看 • 8 个月前

Stripe CEO Patrick Collison shares the tactics he used for finding product/market fit “We tried very hard to understand in granular detail what exactly it was that people were doing, where they were tripping up and so on.” Patrick gives some examples of specific tactics: - A public chat room to provide support to people integrating Stripe - For the first 10 users of Stripe, every API request sent an email to the founders so they could better understand how users were using their product and see if users were doing anything weird - All errors generated a high-priority email to the founders. This created a pleasant user experience where 15 minutes after hitting an error, Patrick could reach out to them and let them know the issue was fixed “These are all kind of examples of a general pattern of trying to be hyper-attentive to all the micro details of what people were doing in the product and iterating rapidly in response to it. Generally speaking, I think pre-product/market fit metrics are actually relatively unhelpful because probably not that many people are using your product. If it’s 20 users, you can in some sense afford to just look at everything they’re doing to understand what’s working and what isn’t.” Another example of this Patrick gives is embedding a text input on each of their web pages with placeholder text prompting users to give them useful feedback(e.g. “The worst thing about Stripe is…”, “The worst thing about this page is…”, or “I really hate the way Stripe does…”). As Patrick explains: “At that stage, you have to be kind of masochistic. We’d always be waking up to all these emails telling us all the terrible things about Stripe. But that was a helpful to-do list for the day ahead." Source: Y Combinator (Oct 2018)

Startup Archive

32,192 次观看 • 1 个月前