We doomscroll, you upskill.
Finding signal on X is harder than ever. We curate high-value insights on AI, Startups, and Product so you can focus on what matters.
94 tweets
This doesn't work because a "product launch" isn't what it was 10 years ago anymore Back then you'd launch on Product Hunt and you'd get thousands or tens of thousands of users overnight and journalists would pick it up after A lot has changed since then Firstly, nobody cares anymore, there's too many products and things launching and unless your product is completely groundbreaking and new, a launch won't get much attention anymore Secondly, these days you essentially should be launching every day non-stop: you try get attention from potential new users, posting new features you build based on user requests, tapping into trends you see and then jumping on them You even see it with AI companies now, they just add the new version like Grok 4.1 or ChatGPT 5.1 without a big presentation. Just roll it out and improve the product for users So yes launching is dead I think
Good Products are Opinionated. “Every great founder I’ve seen up close, or even from afar, is highly opinionated and they’re almost dictatorial in how they run things. Also, early-stage teams are opinionated. And the products they build are opinionated. Opinionated means they have a strong vision for what it should and should not do. If you don’t have a strong vision of what it should and should not do, then you end up with a giant mess of competing features. @Jack Dorsey has a great phrase: “Limit the number of details and make every detail perfect.” And that’s especially important in consumer products. You have to be extremely opinionated. All the best products in consumer-land get there through simplicity. You could argue the recent success of ChatGPT and similar AI chatbots is because they’re even simpler than Google. Google looked like the simplest product you could possibly build. It was just a box. But even that box had limitations in what you could do. You were trained not to talk to it conversationally. You would enter keywords and you had to be careful with those keywords. You couldn’t just ask a question outright and get a sensible answer. It wouldn’t do proper synonym matching, and then it would spit you back a whole bunch of results. That was complicated. You’d have to sift through and figure out which ones were ads, which ones were real, were they sorted correctly, and then you’d have to click through and read it. ChatGPT and the chatbot simplified that even further. You just talk to it like a human—use your voice or you type and it gives you back a straight answer. It might not always be right, but it’s good enough, and it gives you back a straight answer in text or voice or images or whatever you prefer. So it simplifies what we looked at as the simplest product on the Internet, which was formerly Google, and makes it even simpler. And you just cannot make a product that’s simple enough. To be simple, you have to be extremely opinionated. You have to remove everything that doesn’t match your opinion of what the product should be doing. You have to meticulously remove every single click, every single extra button, every single setting. In fact, things in the settings menu are an indication that you’ve abdicated your responsibility to the user. Choices for the user are an abdication of your responsibility. Maybe for legal or important reasons, you can have a few of these, but you should struggle and resist against every single choice the user has to make. In the age of TikTok and ChatGPT, that’s more obvious than ever. People don’t want to make choices. They don’t want the cognitive load. They want you to figure out what the right defaults are and what they should be doing and looking at, and they want you to present it to them.”
I really think Opus 4.5 was a tipping point. I was at a 2 hour build with @cursor_ai event this evening and the scale, diversity and quality of work that people did in 2 hours was like nothing I’ve seen before. Every project that demoed would have been a strong contender for any 48 hours hackathon in 2023. Map that 24x speedup forward into businesses. Months long projects take days now and the benefits compound. What a time to be alive. Thanks @zeror404 for organizing and @ericzakariasson for MCing
Congrats to Channel3 on their $6M seed! Channel3 is building the connected database of every product on the internet. They provide developers and merchants with a real-time, universal product graph, enabling new AI-driven shopping experiences across the web. https://trychannel3.com/blog/channel3-raises-6m…
We just raised $3M to build the world's first AI Chief of Staff, and we want to build with exceptional people. http://bondapp.io
We're releasing a visual agent & workflow builder Fully open source Built on http://useworkflow.dev Outputs "𝚞𝚜𝚎 𝚠𝚘𝚛𝚔𝚏𝚕𝚘𝚠" code Supports AI "text to workflow" Powered by @aisdk & AI Elements Sample integrations (@resend, @linear, @slack) Clone & ship your own product, or embed AI workflow building capabilities into existing ones. Demo: http://workflow-builder.dev Deploy: http://vercel.com/templates/ai/workflow-builder…
startups: here's a mental model for pricing the land ... Small Business: ACV: < $10K size: 1-100 employees Upper-End Small Business: ACV: $10K - $50K size: 100 - 1000 employees Lower-End Enterprise: ACV: $50K - $100K size: 1,000 - 5,000 employees Enterprise: $100K+ ACV size: 5,000+ employees note: if selling to startups Seed (SMB), Series A - B (upper-end SMB), Series C+ (lower-end enterprise +)
Stripe offered to acquire us for $1.2 billion when we had $2M in revenue. Today, we've raised $330M at an $8B valuation and reached $1B ARR. We could've died three times during this journey. This is the story I've never told anyone before:
Anthropic is acquiring @bunjavascript to further accelerate Claude Code’s growth. We're delighted that Bun—which has dramatically improved the JavaScript and TypeScript developer experience—is joining us to make Claude Code even better. Read more:
Anthropic acquires Bun as Claude Code reaches $1B milestone
turns out, senior engineers accept more agent output than juniors. this is because: - they write higher-signal prompts with tighter spec and minimal ambiguity - they decompose work into agent-compatible units - they have stronger priors for correctness, making review faster and more accurate - juniors generate plenty but lack the verification heuristics to confidently greenlight output shows that coding agents amplify existing engineering skill, not replace it
We are excited to announce a strategic partnership between OpenAI and Thrive Holdings. Through our partnership, OpenAI will become an equity owner in Holdings, and collectively we will set out to deliver frontier technology for our customers. For decades, technology has transformed the world’s largest industries from the outside-in. We believe the AI paradigm will be different in that some of the most profound transformations will now occur from the inside-out. We view the businesses that we own and operate as the right reward system to build, test, and improve industry-specific products and models. The partnership will bring together a unique, cross-functional team, comprising OpenAI’s leading research and applied AI teams working alongside engineers, operators, and industry experts at Holdings to deeply integrate AI into the businesses that we own and operate. Our long-term orientation to transforming companies is possible because our time horizon at Holdings is forever. By training the most advanced models for specific tasks within our businesses, guided by both company-specific data and expert feedback, we believe we can continuously improve model capabilities and ultimately establish AI as an integral driver of long-term enterprise value. //
Thrive Holdings
"Why should companies pay for SaaS (HR/CRM/ERP/etc.) when they could just vibe code them?" I get variations of this question or comment with some regularity (granted, it's sometimes just me talking to myself). Here are some biased (but hopefully, well-considered) thoughts: 1) I am a big proponent and user of vibe coding (what I call "agentic coding"). I do it every day, 7 days a week, including Sundays. It's amazing. 2) My company, HubSpot is a software company. We have hundreds of professional engineers -- just about all of them use AI for product development too. They are brilliant and know how to build production-grade products. 3) Even with this powerful army of talent, the number of internal, core SaaS applications that we have replaced with a vibe-coded variant is exactly ZERO. The number of applications we plan to replace is also exactly ZERO. 4) It's not the absence of talent that keeps us from rolling our own SaaS apps, it's the presence of focus. It would be silly to try and replace our HR, team collaboration, expense tracking and 100+ other SaaS apps we use when we can just buy them. Just doesn't make sense. 5) That's us -- as a software company at some scale. If you're a non-software company it makes even less sense for you. Doesn't matter how good the AI coding tools get. Let's say you *could* vibe code a replacement for that SaaS app you're using, who's going to maintain it? Who's going to keep up with industry trends? What are you going to do when the 20-something genius that vibe coded it over a weekend leaves the company? Who do you call when there's a major bug? 6) If you're a Fortune 500 company at some scale, perhaps you could pull this off for some discrete use cases and the tradeoffs are worth it. You have an IT/Engineering department that is larger than the population of some countries. You can take on the pain in return for the positives. For the millions of others, my advice is: Spend every calorie possible on creating value for your customers.
vertical AI is having a moment. Harvey, Abridge, OpenEvidence all crossed billion dollar valuations by embedding deeply into workflows that horizontal software never cracked. The playbook: own the workflow, build proprietary data moats, price on outcomes not seats. The graveyard: wrappers and "AI-powered" features that get shipped by OpenAI/Anthropic six months later. meanwhile VCs are betting big on AI-enabled rollups—buy legacy service businesses, bolt on AI, expand margins. Thesis makes sense. Execution is brutal. Most rollups destroy value historically. Shoutout to @Trace_Cohen for tracking 150+ vertical AI startups across sectors:
New job! I’m hiring folks interested in building and researching the next generation of evals and eval infa. DMs are open :)
I've scaled 4 products past $100k MRR everyone asks for the strategy here's what actually worked: 1. week 1: build something, anything, ship it 2. find 5-10 people, get them to try it 3. become annoying - DM, email, call 4. watch them use it (most won't) 5. ask why, fix it, ship again 6. daily check-ins, daily updates 7. solve their actual problem, not what you think it is 8. keep shipping until they beg you not to change anything 9. that's your signal - now go loud 10. content everywhere, SEO grind, paid ads 11. double down on channels that work 12. cut everything else the gap between $0 and $100k? steps 3-8 most people never leave their code editor you can't build a business without talking to humans
Supabase launched all of the following last week Vector Buckets Supabase ETL Supabase Power for Kiro 7 new email templates for Auth Sign in with "Your App" Async streaming for foreign data wrappers Realtime Replay Supabase for Platforms
Slack CEO Denise Dresser to join OpenAI as chief revenue officer
Slack CEO Denise Dresser to join OpenAI as chief revenue officer | TechCrunch
Ben Evans released 90 slides on "AI eats the world" Here are the 14 most important ones: