renée berry 🌿 (@rfberry) header
renée berry 🌿 (@rfberry) profile picture

AI GTM @ AWS. Love systems design & constant learning. 📷🎨 Palliative care advocate & #hapc chat cofounder. Tweets my own. Show up for women.

San Francisco Bay Area
Joined March 2010
Photo by renée berry 🌿 (@rfberry)Photo by renée berry 🌿 (@rfberry)Photo by renée berry 🌿 (@rfberry)Photo by renée berry 🌿 (@rfberry)Photo by renée berry 🌿 (@rfberry)Photo by renée berry 🌿 (@rfberry)Photo by renée berry 🌿 (@rfberry)Photo by renée berry 🌿 (@rfberry)Photo by renée berry 🌿 (@rfberry)
The courage celebrated of entrepreneurs is actually way more common than recognized or written about & exists in neighborhoods around the world, in organizations of every size, in public service, companies, startups, you name it. 🔥Creators, keep persevering. The world needs you.
4
3
20
EVERYONE WATCHES WOMEN’S SPORTS 🏀 #Valkyries #WNBA #NBA #BayArea
32
If you’re a SF Bay Area sports fan, there is a correct color to be sporting today. #govalks #valkyries
106
Good post on how to think about process redesign in an enterprise with AI Agents. Unfortunately for most workflows, there’s no “easy” button. The best way to get real efficiency gains is you have to actually reengineer the process to take advantage of what agents are actually good at and can do differently and faster than people. One of the challenges of course is that the most important workflows actually space many functions at once, so someone needs to be able to go in and retool how work happens. “Nobody in that chain is empowered to walk into finance, for example, and say that their 14 step process should actually only be 5 steps. So nobody does it. Instead, you 'apply AI' on what you currently have, and you end up with faster sh*t.” This is the road ahead for AI diffusion in enterprises. This also presents the clear opportunity for companies - both at the applied AI layer (regardless of the article’s title) and teams or companies that can go and implement transformation into the enterprises. And all roads lead to FDEs one way or another.
9
320
🙌
Grok 4.6 is now available on Amazon Bedrock
310
renée berry 🌿 retweeted
Grok on Bedrock. Fire it up.
Grok 4.6 now on Bedrock
1
12
926
Important for engineering teams wanting to make sure they’re being thoughtful about #AI cost and value as they build! ⬇️ #Grok 4.6 👏🔥
Grok 4.6 has the lowest cost-per-task of any frontier model.
1
409
renée berry 🌿 retweeted
I’ve finally had the chance to play with Grok 4.6 today after exhausting all of my Codex usage. Grok Build + 4.6 has been the best experience I’ve had in a while. TLDR; It’s super fast and it just works. Full thoughts: It’s still extremely fast like 4.5 was but I can feel how much smarter it is. Because of the speed I find myself more involved in what’s going on because I don’t have to wait forever between responses, which means I’m context switching a lot less and actually getting things done end to end. I haven’t had the chance to use it on really complex projects yet but we’ll see how that goes. I’ve been rocking the $100 Codex plan for a while but i think I’d actually be willing to get Supergrok Heavy, I’ve never considered getting the $200 GPT plan.
73
86
4
967
321,307
Awesome seeing so much energy around @bot. I think this is an early look at how useful agents can be in our daily lives. Significantly different than chat agents. #SpaceXAI
This is one of the coolest projects that I’ve worked on. Grok Bot had insane PMF internally, almost instantly. For much of the company, Bots have become the interface for all of their work. Really excited to see what your Bots do!!
1
387
renée berry 🌿 retweeted
Grok 4.6 has the lowest cost-per-task of any frontier model.
SpaceXAI's Grok 4.6 scores 61 on the Artificial Analysis Intelligence Index, joining the frontier in line with GPT-5.6 Sol, with standout agentic performance at lower cost Grok 4.6 gains 5 points over Grok 4.5 on the Intelligence Index just over one month after its release, or +23 points compared to Grok 4.3. This brings SpaceXAI back to the intelligence frontier alongside OpenAI, behind only Anthropic. Key takeaways: ➤ Grok 4.6 joins the frontier of the Artificial Analysis Intelligence Index: It scores 61, in line with GPT-5.6 Sol (max), behind Claude Opus 5 (max, 63) and Claude Fable 5 (max with fallback, 62), and just ahead of Kimi K3 ➤ Strong agentic performance: Grok 4.6 achieves a GDPval-AA v2 Elo of 1753, behind only Claude Opus 5 and with overlapping confidence intervals with Claude Fable 5 and Qwen3.8 Max. It scores 50.7% on 𝜏³-Banking, among the top two scores alongside Qwen3.8 Max (51.3%), and 88.4% on Terminal-Bench v2.1, in line with the leading models ➤ Frontier-level intelligence at lower cost: Headline pricing is unchanged from Grok 4.5 at $2/$6 per 1M input/output tokens, 60%+ below Claude Opus 5 ($5/$25) and GPT-5.6 Sol ($5/$30). It cost $0.84 per task, the same as Kimi K3 with slightly higher intelligence, placing it on the Intelligence vs. Cost per Task Pareto frontier ➤ Grok 4.6 sits at Fable 5-tier on AA-Briefcase, our private benchmark of long-horizon agentic knowledge work tasks, with an Elo of 1577 - behind the Claude Opus 5 family. It is notably turn-efficient, completing tasks in ~53 turns and ~0.5B input tokens on average vs. ~103 turns and ~2.0B input tokens for Claude Opus 5 (max) Other model details: ➤ Context window of 500k tokens (unchanged from Grok 4.5) ➤ Pricing of $2/$6 per 1M tokens of input/output; cache hits discounted to $0.5 per 1M tokens, an increase over Grok 4.5’s $0.3 per 1M tokens for cache hits Congratulations to @spacexai and @elonmusk on the release!
16
23
10
312
22,726
renée berry 🌿 retweeted
Just getting going with Grokbot. Initial impressions: it's awesome.
5
2
72
4,089
renée berry 🌿 retweeted
Amazing outcome. Cursor executed the applied AI strategy flawlessly. Most people completely underestimated the market size in AI coding. The biggest developer tool exits in history were on the order of low billions of dollars. And it was already assumed to be a heavily competitive and somewhat saturated space when they really got going. Multiple mental models shattered near instantly. The market sizes for agentic coding was far larger than most realized. There was actually tons and tons of room to innovate between the user and the underlying model, and even on the model itself. Cursor provided out the applied AI playbook by figuring out the right product shape for agentic coding work, acting as a neutral layer between models and the workflows, post training models for the areas that make most sense to drive down costs or improve performance, building out the right infra stack for the relevant workflows, building out a strong category-aligned GTM motion, and more. Great set of lessons for anyone doing applied AI right now. We’re going to see a lot more of these.
Cursor has officially joined SpaceX. We’re grateful to become part of such a special company, and it has been a privilege working with the SpaceXAI team. Lots ahead.
54
43
7
654
129,748
renée berry 🌿 retweeted
My new blog post is Getting It Wrong: Rethinking a Life in Scholarship. The core insight is that research trajectories are not things you can carefully map out in advance.  They just happen.  You learn as you go.  And the most effective means of learning from your own work — at least from my experience — arises from getting it wrong, time and time again.  If you’re not getting things wrong, you may not be learning much at all, since you may just be continually finding what you’re looking for.  It may well be that what you need to find are the things you’re not looking for and that you really don’t want to confront.  The things that challenge your own world view, that take you in a direction you’d rather not go, forcing you to give up ideas you really want to keep. davidlabaree.com
1
2
88
renée berry 🌿 retweeted
80+ open roles at Cursor:
54
20
12
544
63,132
renée berry 🌿 retweeted
Had meetings and a dinner with 20+ enterprise AI and IT leaders today. Lots of interesting conversations around the state of AI in large enterprises, especially regulated businesses. Here are some of general trends: * Agents are clearly the big thing. Enterprises moving from talking about chatbots to agents, though we’re still very early. Coding is still the dominant agentic use-case being adopted thus far, with other categories of across knowledge work starting to emerge. Lots of agentic work moving from pilots and PoCs into production, and some enterprises had lots of active live use-cases. * Agentic use-cases span every part of a business, from back office operations to client facing experiences from sales to customer onboarding workflows. General feeling is that agentic workflows will hit every part of an organization, often with biggest focus on delivering better for customers, getting better insights and intelligence from data and documents, speeding up high ROI workflows with agents, and so on. Very limited discussion on pure cost cutting. * Data and AI governance still remain core challenges. Getting data and content into a spot that agents can securely and easily operate on remains a huge task for more organizations. Years of data management fragmentation that wasn’t a problem now is an issue for enterprises looking to adopt agents. And governing what agents can do with data in a workflow still a major topic. * Identity emerging as a big topic. Can the agent have access to everything you have? In a world of dozens of agents working on behalf, potentially too much data exposure and scope for the agents. How do we manage agents with partitioned level of access to your information? * Lots of emerging questions on how we will budget for tokens across use-cases and teams. Companies don’t want to constrain use-cases, but equally need to be mindful of ultimate token budgets. This is going to become a bigger part of OpEx over time, and probably won’t make sense to be considered an IT budget anymore. Likely needs to be factored into the rest of operating expenses. * Interoperability is key. Every enterprise is deploying multiple AI systems right now, and it’s unlikely that there’s going to be a single platform to rule them all. Customers are getting savvier on how to handle agent interoperability, and this will be one of the biggest drivers of an AI stack going forward. Lots more takeaways than just this, but needless to say the momentum is building but equally enterprises are acutely aware of the change management and work ahead. Lots of opportunity right now.
136
102
29
903
149,106
Shipping everyday. Not focused on vanity metrics. Solid.
2021: 2.5k GitHub stars, Discord community, zero revenue focus. 2026: Series A, 30% of recent YC batches on Porter, hundreds of customers deploying daily. How did we build Porter from "fresh out of YC" to where we are today? 1) We stopped optimizing for surface-level adoption Early on, we had hundreds of Discord members, GitHub stars were climbing, and developers were talking about us everywhere. We thought social proof meant we were winning. The reality? None of it translated to real usage. Not all social proof is created equal, as Discord community size doesn't mean you have something real. One customer deeply integrated with Porter beats a hundred people who think it's "cool" but never deploy. 2) We pivoted from enterprise-first to following the usage Initially, we focused solely on white-glove migration, mostly Heroku Enterprise users that wanted to be on AWS with the developer experience of a PaaS. Bigger contracts, multi-month sales cycles. We thought this was the path to revenue. Then we noticed something: self-serve startups signing up were exploding past enterprise accounts we'd spent months chasing. Some self-serve customers ended up generating more usage than enterprise contracts that took half a year to close. 3) We went all-in on the self-serve startup motion For the last 2.5 years, we've focused entirely on self-serve adoption from early-stage companies. We were initially ignoring startups because we didn't think they were worth the effort. Then we saw some of them explode and grow to be massive. The startups knocking on our door were going to become our best customers, we just had to let them in. 4) We built for developers, not just decision-makers We stopped pitching executives and started shipping for the people actually deploying infrastructure. If we could build better docs with faster onboarding, the result would be a better developer experience all around. The bottoms-up motion only works if your product sells itself to the person using it. 5) We measured what actually matters We stopped tracking GitHub stars and Discord members. We started tracking resources managed, customer growth, and revenue. The companies that matter aren't the ones talking about infrastructure on Twitter, they're the ones shipping on it every day. – The shift from 2021 to 2026 wasn't a product pivot. It was understanding which signals meant real traction and ruthlessly focusing on those. Vanity metrics will lie to you. Deep usage from companies that are actually growing won't.
1
228