Head of People & AI @_btcinc

Joined October 2018
158 Photos and videos
Pinned Tweet
Had fun building this. Originally inspired by @geoffreylitt 's tutorial connecting Claude to Notion. Later @pusongqi 's roro and @openai's Codex app. It's slowing morphing to an HRIS for agents experiment, with performance ratings and similar features.
1
1
6
2,868
🎯
THE TOKEN HANGOVER @matanSF (Matan Grinberg), CEO and co-founder of @FactoryAI , interviewed by @HarryStebbings (@20vcFund ) This is a special for me since I've been an investor in @FactoryAI since their seed round, and think Matan is a very very special founder. Summary: Grinberg argues the next 24 months in enterprise AI are a resource-allocation problem: tokens, dollars, and people. Most CIOs are now waking up to bills they cannot justify. The fix is to spend frontier tokens only on the 10-20% of work that requires planning intelligence, run the other 80-90% on open models, and rebuild teams around load-bearing polymaths who own business outcomes. The single-frontier-monopoly fear is fading: four roughly-equivalent labs is the emerging reality, which puts pricing power back in the application layer. 1. The Token Hangover. Enterprise AI adoption ran through three phases this year: boards yelling at CEOs about AI strategy, "token maxing" with AI usage written into perf reviews, and now the morning-after bill. One CIO Grinberg spoke to was spending hundreds of thousands of dollars a month on engineers asking Opus 4.8 things like "how's it going" and "what are my macros from lunch." The frontier model became the default surface for every question, no matter how trivial. Phase 3 is the moment routing matters: every call to a frontier model needs to earn its price. 2. Resource Allocation Is the Job. For the next 24 months every C-suite is solving the same problem: how to allocate dollars, tokens, and headcount against business outcomes. Engineering teams used to be judged by features shipped per quarter, a metric with no link to revenue, market share, or retention. A logistics company adding more engineers to ship more features was always solving the wrong problem; AI made the misallocation visible. Tie every person's work to the metric that actually moves the business, then re-allocate. 3. Load-Bearing Individuals. The "10x engineer" frame measures lines of code, the wrong unit. Grinberg's unit is the load-bearing individual: the person whose absence breaks something. With AI the load-bearing few compound roughly 10,000%; the others get close to nothing, so any org enforcing one token-spend-per-engineer number is painting with too wide a brush. Average token spend per engineer will land on the same order of magnitude as their salary within three years, with a wildly bimodal distribution. 4. Frontier for Decisions Only. 80-90% of software development tasks can run on open models; the remaining 10-20% is planning, where the frontier still wins. This mirrors how human orgs work: leadership is a tiny share of total hours but decides the company's fate. The ego trap is engineers assuming their work is too important for an open model. The router decides better than the engineer, and the cost curve falls only if you wire the routing. 5. The Kirkland Mistake. Kirkland & Ellis announced a $500M, five-year internal AI build, which Grinberg reads as validation for Harvey rather than a threat. Building AI is not a law firm's core competency, and Kirkland's spend will teach them how hard it is. The general rule: just because you can build it does not mean you should, and the discipline is naming the few things you and your team own end-to-end. Outsource everything else, even when you technically know how to do it yourself. 6. Model-App Separation. When the model provider also sells the app, the incentives split: an API business wants you to spend more tokens. A healthy market keeps the application layer independent, so model providers compete on price, speed, and quality every week. Enterprises do not want to vendor-lock again; every CIO carries scars from the cloud era's three-year discount-then-jack-the-price trap. The application layer survives precisely because it forces that competition. 7. Sales as Product. Name a legendary company with a weak sales or marketing team. You can't. The Silicon Valley fallacy that research sits at the top and sales is "dirty work" produces companies that win the gold rush and then collapse when gravity returns. At Factory, engineers and salespeople sit intermixed; when sales closes, engineering says "we closed"; when engineering ships, sales says "we shipped." Atrophied sales muscles will not regrow once enterprise buyers stop saying yes to everything. 8. Polymath Era. Da Vinci, Newton, Euler could be polymaths because their fields were shallow. By the 2010s a theoretical physicist needed 50 years to reach the frontier before contributing anything new. AI collapses that catch-up time, so one person can push forward developer marketing, token-caching infrastructure, and solution engineering at once. The engineer of the future is a GM who owns marketing copy, product metrics, and sales enablement. 9. Build the Factory. Factory's name is literal: engineers in the next era design the assembly line that produces software. The DevX investments that used to scale linearly with headcount (good docs, CI/CD, linters, pre-commit hooks) now scale with the number of agents you run, which is 10x or 100x larger. Every dollar spent making agents production-ready compounds against thousands of PRs a week. Humans move up the stack, from writing code to designing the system that writes code. 10. Seal Team Six. Mandating beds in the office is a hiring failure dressed up as commitment. Grinberg's image: a basketball game judged by who sweat the most, when the scoreboard is what counts. Factory bought eight sleeps for all 30 team members at the time, because recovery is where the gains come from when work requires every ounce of brain power. If your load-bearing engineer can do their best work on two hours of sleep, they were not doing load-bearing work in the first place. 11. Four Frontier Labs. Grinberg's biggest mind-change this year: a single dominant model is unlikely, and four roughly-equivalent frontier providers is the more probable steady state. That outcome is the win for humanity. A one-lab monopoly was the dangerous scenario, and four equivalent labs is also the structural bull case for the application layer because it forces real ongoing price competition. Every CIO Grinberg meets has already decided not to throw their lot in with a single provider. 12. Dario's Self-Serving Doom. "AI will take your jobs" was the pitch that helped raise hundreds of billions, and Grinberg thinks it damaged public psychology and fed the slow-AI lobby. Watch the rhetoric flip at IPO: humans will suddenly become important again, because humans are the ones buying the stock. Founders who never needed to raise that money, like Zuckerberg and Hassabis, never made that argument. Incentives drive the labor-displacement rhetoric more than philosophy does.
1
51
Nick Beaird • retweeted
Introducing the Fusion API, the smartest compound model in the market. Fusion achieves Fable-level intelligence at half the price. How it works 👇
371
959
8,592
2,057,061
Nick Beaird • retweeted
Agent x Loop It should have been obvious 3 years ago to that putting an LLm in a loop was the endgame. I’m surprised y’all weren’t already thinking about ai coding like this Your job is not to guide a coding agent It’s to surf on the back of a bucking bronco demon alien that’s smarter than you and can work in 1000x parallel That’s an entirely different task from writing clear linear tickets or product descriptions for small features You don’t tell an agent to pick up a hammer and assemble a chair with a detailed design spec. It already knows to do that. Your new job is building onboarding documents, design direction & high level cultural values (aka decision frameworks) for a furniture factory, distribution center & business Then you simply hire Ai workers on loop to do the thing It’s very similar to the way fast food restaurants have standardized and documented practices to teach dumb unmotivated and non-sober high schoolers how to run a fully working restaurant, at the scale of millions Except instead of producing burgers or chairs you produce code & outcomes via software
Here’s your monthly reminder that you shouldn’t be prompting coding agents anymore. You should be designing loops that prompt your agents.
42
6
149
18,891
Nick Beaird • retweeted

309
1,112
7,238
1,813,147
Nick Beaird • retweeted
good morning, stay humble and stack sats 🫡
35
48
755
14,990
Nick Beaird • retweeted
Today, Ramp raised $750M at a $44B valuation. Last time we grew this fast, we were 1/20th the size. For 2000 years, business was built on two pillars. Today, a third: intelligence. It’s your least governed cost. It’s also your single greatest opportunity.
139
201
2,600
1,053,575
RT @herdrdev: new herdr.dev is live. also, the site is terminal-native now too. it has an interactive theme switcher that r…
6
Nick Beaird • retweeted
We’ve automated every single thing we can @every with AI agents. And yet there’s way more human work to do than ever. We’ve gone from 4 -> 30 human employees since GPT-3. I wrote a report on the structural reasons: how AI makes expert competence cheap, why that drives up demand for experts, and why the dynamic only intensifies as we approach AGI. After Automation: every.to/p/after-automation
184
301
2,411
1,443,166
Nick Beaird • retweeted
Introducing Zero The programming language for agents. I wanted a systems language that was faster, smaller, and easier for agents to use and repair. Explicit capabilities. JSON diagnostics. Typed safe fixes. Made for agents on day zero.
393
211
2,714
1,704,149
Nick Beaird • retweeted
20 Dec 2020
Bitcoin is my safe word
6,274
19,338
215,120
Nick Beaird • retweeted
You don't understand That 40b val is because Ramp is not an expense management company. They're the AI lab for finance
We partnered with @PrimeIntellect to build Fast Ask, a small RL-trained subagent that helps our Sheets agent find answers in spreadsheets. It scores 4% over Opus on exact match accuracy at Haiku latency.
7
7
210
33,029
Nick Beaird • retweeted

17
36
221
25,459
Nick Beaird • retweeted
Anthropic made its first dollar three years ago. last month it crossed $30B in revenue. that money is coming from somewhere, and your CFO probably can't tell you where. the problem isn't the spending. the companies on Ramp investing the most in AI have more than doubled their revenue since 2023. the problem is that no one can see where it's going: which team drove the spike, whether it's COGS, Opex or R&D, if commitments are actually being used. your AI providers aren't going to help you spend less. they're not going to tell you a competitor's model does the same job for a fraction of the cost. or that an open-source alternative works just as well. so we built something. Ramp pulls token-level usage data directly from Anthropic, OpenAI, and OpenRouter into the platform where you already manage cards, bill pay, and procurement. connect an API key — five minutes, no engineering — and finance can see every dollar by provider, model, team, and project. free for all Ramp customers. if you want it too, Veeral shows how to set it up in minutes. the companies building financial discipline around AI now will know where to double down and where to cut. everyone else will be explaining to their board why their fastest-growing cost is also their least well understood.
24
41
709
170,575
Nick Beaird • retweeted
You can use AI to cut costs. You can also use AI to raise your ambition. Too many people focus on the first. More people should be thinking about the second.
89
121
1,048
53,683
Nick Beaird • retweeted
Apr 9
Bitcoin's quantum defense just got its first working prototype. Olaoluwa @roasbeef Osuntokun, CTO of Lightning Labs, published a functional tool to the Bitcoin developer mailing list that solves one of the hardest problems in Bitcoin's long-term security, how to protect the network from quantum attacks without locking millions of users out of their own wallets. The problem is a painful paradox. Bitcoin's leading quantum defense proposal (BIP-360) would disable the current signature system network-wide if a quantum threat emerged. That protects the network, but every wallet that hasn't migrated to the new quantum-resistant format gets frozen permanently. The coins are still there. The rightful owner just can't access them. Osuntokun's prototype is the escape hatch. Instead of proving ownership with a digital signature, the system lets users mathematically prove they created the wallet using its original seed phrase, without ever revealing the seed itself. Recovering one wallet doesn't compromise any others derived from the same seed. It replaces "I can sign this transaction" with "I can prove this wallet came from me." It already runs on a consumer MacBook. Generating the proof takes about 55 seconds. Verification takes under two seconds. The proof file is roughly 1.7 MB. There's no formal proposal to integrate this into Bitcoin yet and no deployment timeline. But the prototype closes a gap that had only existed in theory until now, a credible path to quantum resilience without the collateral damage of stranding user funds.
36
126
818
42,634
Goose is great. I hadn't updated since January, but the latest version is a much better experience.
Apr 3
people are sleeping on how excellent goose has become under the hood (interface needs some work but team is pushing). it's a superpower. github.com/block/goose
109
Nick Beaird • retweeted

19
32
462
239,839
The team you build is the company you build
115
Nick Beaird • retweeted
How I actually run OpenClaw in practice. SimpleX, proton mail and drive. Everything stays as local as possible while still being useful, although main inference is cloud. Tts and stt, embeddings, etc is local. No Mac mini required. juraj.bednar.io/en/blog-en/2…
18
26
244
22,184
Nick Beaird • retweeted
Mar 18

262
609
4,253
1,391,759