Weave (@WorkWeave) header
Weave (@WorkWeave) profile picture

Turn your software team into a software factory. Used by 1000+ organizations.

San Francisco, CA
Joined May 2024
Photo by Weave (@WorkWeave)Photo by Weave (@WorkWeave)Photo by Weave (@WorkWeave)Photo by Weave (@WorkWeave)Photo by Weave (@WorkWeave)Photo by Weave (@WorkWeave)Photo by Weave (@WorkWeave)Photo by Weave (@WorkWeave)Photo by Weave (@WorkWeave)Photo by Weave (@WorkWeave)
Weave retweeted
In March 2025, YC said a quarter of its Winter 2025 startups had AI writing 95% of their code. The internet did not take it well. @snowmaker, the YC partner who shared that number, remembers the reaction: "There was a lot of kerfuffle on Twitter about like, what? They're doing what?" "There was outrage on the internet of how dare the programmers have AI write the code for them?" One startup in that same batch had a harder sell. @WorkWeave measures how much engineering work actually gets done, by people and by AI. Back then @cursor_ai was what everyone used, and @claudeai's Claude Code had only just come out, in February 2025. Co-founders @adambcohen93 and @AndrewChurchiII were selling that in early 2025. One of them on how it went: "Every single call we got on was pure skepticism. I don't believe that you can actually do this. So we had to actually prove it to them with their data." "We would connect their data and show them, here's how it's actually working. Does this match your expectations?" What happened next: → July 2025: a $4.2M seed round, with YC among the investors → July 2026: a $13.5M Series A led by @Standard_Cap, the firm former YC partner @daltonc co-founded → Its pitch now: end "tokenmaxxing", spending on token volume instead of real output → It also sells Weave Router, which picks a model for each coding task From @ycombinator.
4
1
8
1,155
That’s our boys 🥹
Weave (W25) helps engineering teams understand whether their AI coding tools are actually making them more productive. Its models measure the work humans and agents produce and compare that output with AI spending. The company recently raised a $13.5M Series A led by Standard Capital and launched Weave Router, which selects models for different coding tasks. In this fireside, @WorkWeave co-founders @adambcohen93 and @AndrewChurchiII join YC's @snowmaker to share how the company evolved alongside the rapid rise of AI coding, from measuring the impact of tools like Cursor to helping teams build software factories that can work autonomously. They explain how the best engineering teams are learning to measure the real output of their agents, spread the habits of their strongest AI users, and optimize for a future where much more software is written without a human at the keyboard. 00:00 — Optimizing AI Coding With Weave 04:02 — Getting More From Your AI Budget 08:39 — Measuring Work Beyond Lines of Code 12:30 — From AI Adoption to Optimization 16:47 — Measuring AI ROI and Coaching Engineers 20:16 — Building Software Factories 25:38 — The Future of Model Routing
6
422
After A LOT of storyboarding and iterating, almost done editing the @WorkWeave x @Composio video for Season 3 of my "Agents at Work" Series:)
2
1
21
1,063
Get more from your Claude & Codex subscriptions with Weave Code Boost. Combine 10+ plans with top open-source models hosted by us, with automatic model routing in the coding tools you already use. $100/month includes $200 in monthly Boost credits.
3
5
2
16
838
AI adoption is easy to count. Engineering leaders need the impact view too. Weave brings complexity-weighted output, AI-tool spend, code quality, and delivery signals into one view. See the Q3 benchmarks: weaveos.com/blog/q3-2026-eng…
1
6
389
People are finally catching on 👀
How does a company allocate token budget to it's employees? One interesting analogy is to how multi-strat hedge funds allocate balance sheet amongst different pods. I think there are multiple startups to be built in this space. Let me know if you're building something here.
1
1
20
3,337
Something massive just happened in software engineering. For 8 straight months, every dollar spent on AI coding bought less code than the month before. January: $2.80 per expert hour of output August: $11.00 That's a 4x cost increase in 7 months. Teams kept buying more tokens. Code wasn't keeping up. And then we saw a huge shift in September... For the first time all year, output grew FASTER than AI spend. Cost per output hour: $11 → $9.39 (−15%) Code per dollar: 0.09 → 0.106 (+18%) The first wave of AI coding was brute force. Throw tokens at the problem, hope something ships. What we may be seeing now is the efficiency era. Engineers are learning which tasks to hand off, how to prompt, and when not to use AI at all. The engineers who figure this out first won't just be faster. They'll be dramatically cheaper. One month isn't a trend. But we'll see what happens this month.
4
3
20
789
Weave retweeted
Q3: average engineering output per employee on Weave rose 78% from June to September. Average AI spend per employee rose 2.5×. In September, output growth outpaced spend for the first time this quarter. Read the report: weaveos.com/research/q3-2026…
1
6
497
Q3: average engineering output per employee on Weave rose 78% from June to September. Average AI spend per employee rose 2.5×. In September, output growth outpaced spend for the first time this quarter. Read the report: weaveos.com/research/q3-2026…
1
6
497
Weave retweeted
On Saturday, I am co-hosting Paddles, Pints & Big Ideas alongside our friends at @WorkWeave, @rootlyhq, @tryreplicas, and @getcasco. We are taking over SPIN San Francisco for an evening of table tennis, drinks, and good conversation with founders, CTOs, engineering leaders, and startup operators building the next wave of tech. Channel your inner Marty Supreme on the table, grab a drink, and talk shop with other builders off the clock. The RSVP link is in the comments below.
9
6
40
3,272
Had an insane September. Shipped 40% more per engineer MoM. Few notes on it: 1. Agent parallelization: our engineers ran multiple agents in parallel on multiple tasks, and we've learned to multiplex. 2. We immediately incorporated new models into our workflow thanks to the router. 3. More Slack agents and coding agents. Our engineers are running more of both day to day. 4. We built an internal code quality check (more to come on that soon).
1
17
507
Who are we flying out next 👀
I got flown out to SF for tech week! I want to meet as many people as possible in the next 72 hours. Thank you to Weave for making this happen.
1
7
482
By Using Me! 👋
How does a company allocate token budget to it's employees? One interesting analogy is to how multi-strat hedge funds allocate balance sheet amongst different pods. I think there are multiple startups to be built in this space. Let me know if you're building something here.
10
455
we’ll literally fly you to SF tonight. DM me ✈️
SF Tech Week FOMO? We’re flying out creators + builders to SF TONIGHT. Flights + hotel covered. Build with us, explore Tech Week, & meet great people. First one out: @jackprice. Good at what you do? DM me or @adambcohen93
5
1
17
1,014
we’re revoking DoorDash permissions
pov: checking the bill after giving our agent the DoorDash CLI and telling it to “handle lunch”
1
7
723
Coziest office in San Francisco. Don’t take our word for it. Come see for yourself. luma.com/a5ouvlt8
3
2
12
769
We’re ready for you 🫡 Signups are filling fast, don’t wait. RSVP: luma.com/a5ouvlt8
I jumped out of a plane for our Series A announcement. For the celebration, we’re staying on the ground. Thursday: run with us. Friday: party at the new office. DM me, and I’ll add you to the list for Friday. Luma: luma.com/a5ouvlt8
1
2
12
1,249