Enterprise VC @Work_Bench | We Lead Seed Rounds with $2-4M Investments | Organizer @NYETM, @KauffmanFellows 19 | My better half is @MichaelaLehr | 305 Native
🚨 Big news: We’ve raised $160M for @Work_Bench Fund IV to back Seed-stage founders with massive enterprise ambitions.
Enterprise is in our DNA and with Fund IV, we’re quadrupling down.👇
Infectious energy is a description I've often used when describing @ProbyShandilya and it makes me so happy when others see it too!
NYC founders and operators, definitely hit him up
@ProbyShandilya has such calm + infectious energy — so much curiosity and a genuine love for thinking deeply about life
couldn’t think of a more fitting person to start a podcast called Thinking about Thinking
We've had hundreds of calls with execs (F500s, T20 PE Firms, etc), and I fed notes from the last 25 into Claude to answer the question: "What are companies struggling with, when it comes to AI Transformation?"
It gave a really good response:
[We fix all 10 of these at Varick. Work with us below.]
1. They're improving one step but not seeing end-to-end impact. The amount of hands-on cycle time in most processes is 1-5%, and that's the part that gets faster while people outside the process wait. The engineering org that writes twice as much code but isn't shipping faster. The equipment dealer that's had a vendor come in and work for months to automate one step of an 8 step order processing process. Most point solutions are 1/20th of the value people think they are.
2. They're treating workflows as if they're exceptions. >25% of invoices come in without a PO for this finance team, and as the head of the process said, "statistically they won't be exceptions. They will be the norm." Which is why anyone who's seen a process end-to-end immediately discounts demos people bring in, which are almost always the happy path only.
3. They're catching errors based on size, not based on good controls. I spoke with an Accounts Receivable team that bills a partner based on tickets with free text fields that, to put it politely, have been incorrect or required rework in 5 of the last 8 quarters. Why didn't they catch it? Well if the team credits the partner for $3M they'll catch it at close, but if they credit the partner for $20k they won't. As one person on the team said, "Humans. Humans catch it."
4. IT owns AI and part of their job is to say no. Spoke with a bank, a software company, and an insurance company in one day who said they've been blocked on everything by IT. One engineer told me he spent a month and $600 of his own money building a multi-agent system in Claude to help with a design process. And while he can spend $600 personally, he's only allowed to spend $150/mo on AI at work, and the company won't even let him buy a subscription.
5. They don't have accessible data. Sales can't connect to Salesforce until they "clean up the data." Their ERP doesn't have OAuth so they can only log in with a username and password. One engineering team's design data is a 648GB zip file that drops every 5-10 hours. Most prototypes get to demos because they're built on static data, and then can't move to production because real processes need real-time data.
6. They don't have good process docs, and even if they did they wouldn't be accurate. As one person told me, the SOPs for their processes are "on random SharePoints everywhere. A treasure hunt." Plus, when we mine the systems of record our process maps generally have ~20% more steps than what companies think is in the process.
7. Legal needs tracking, not contract drafting. I spoke with a legal team that had ~8,000 tickets last year, the vast majority administrative. Another legal team said they generally track contracts until the first draft is complete, and then the system no longer tracks them. As they told me, "the default is, it's legal. It's always our fault." And none of these teams can track how long things take, which is a problem when they need to ask for more headcount and the answer they get is, "okay prove it."
8. The last consulting engagement they had only provided numbers, not a path forward. In the words of one person I spoke with: "they gave us a lot of numbers. But the how is really the most complex thing." Even engineering teams are being asked by boards what they're measuring, and most can only provide metrics around merge requests.
9. Most companies don't have agent sprawl but they do have agent nothing. People are building agents for themselves but they're the spreadsheets of 2026: only the people that built them know how they work, and they'll keep running after those people move on. Meanwhile the companies that we're talking to that are backed by PEs and have real moats in their businesses told us that agent sprawl "would be a good problem if we had it."
10. They're betting on the team, not on the method. In the words of one person I spoke with, "everybody has a story. Pitch went great and then project went terrible. And the difference is the person that walked in the door."
If you want these problems solved for you and more, check us out below:
Episode 2 of Thinking About Thinking is live!
In 2018, I published a book titled Surrounding Factors. The essential premise was that how a basketball player performs is not just a function of their individual skillsets and talents - how they fit with the "surrounding factors" around them (the coaching style, the other players on their team and complementary skillsets, the strategy the team employs, the overall environment, etc) is a *very critical* determinant.
Whenever I talk about this with folks in the startup ecosystem, I joke that this is essentially "founder market fit for basketball players" - because it's true! The surrounding factors mental model applies universally, whether it's for players on a sports team, people within an organization, or even products within certain time periods (the "why now") and surrounding environments (early customers/ICPs, business models, GTM motions, etc).
Hope this is a fun listen!
Pumped to share that we’ve led a $5.7M round into @EarthlyTech
AI coding agents have 100x’d developer productivity, but as more code gets written by agents, it’s getting harder to ensure that the same standards are followed across the organization.
Earthly Lunar 🌖 helps teams enforce engineering standards across thousands of repos. Teams can define a rule once and check it as AI agents write code, when developers open PRs, and before anyone deploys.
Lunar’s enterprise footprint already spans more than 100,000+ repositories across some of the largest companies in financial services, communications, defense, and more.
Most importantly, Earthly is led by @VladAIonescu, a deeply technical founder who has turned himself into a true enterprise seller. Working with Vlad has been an absolute pleasure — he's exactly the kind of founder we love backing at @Work_Bench! Plenty of engineers can build great products, but fewer can walk into a Fortune 500 company and close a massive enterprise deal (time and time again). Vlad can do it all!
Here are a few ways Earthly’s already helping customers:
→ A large bank turned 65 pages of software delivery policy into 41 automated guardrails that run in its existing pipelines.
→ A global communications company immediately rolled out Lunar across 11,000+ repos and 2,000 engineers.
→ A large employment tech company brought engineering standards to 90,000+ repos that its golden-path templates couldn’t reach.
→ A defense tech company automated the compliance checks and software bills of materials that used to take weeks for every DoD delivery.
This is just the start for Earthly Lunar. Next stop, the moon! 🚀 🌖
Read more about their coverage with the links in the comments.
@AlexPallNY Since covid days we've paired each written QL with a webinar! Lets LPs get the voiceover with some more context + hear from our whole team each quarter. It's great
incredibly excited to be partnering with @OpenAI on embedded assessments!
we'll be embedding interpretability researchers who will use the @GoodfireAI platform to monitor and debug training runs to improve safety and alignment
our primary audience for our assessments are internal OpenAI researchers, but we'll publish our findings as the collaboration progresses
Last night, @fendien and I hosted an AMA Dinner with @jaykreps (founder/CEO of @confluentinc and creator of @apachekafka) and it was a blast.
Confluent has always been one of my favorite enterprise software companies to study. It all started when Jay, alongside Neha Narkhede and Jun Rao, created Kafka, an open source data streaming platform, within LinkedIn. They had deep conviction that continuous, real-time data was something that had to exist in the data infrastructure stack, and before long the market agreed with them…they experienced pull from outside customers and decided to start a company, Confluent, around it. They started the company in September 2014, launched the platform in Jan 2015, released their cloud product in 2017, and went public in 2021 en route to being bought by IBM earlier this year for $11B.
So many incredible learnings from Jay last night. Sharing a couple here:
- He shared a very elegant framework to think about GTM: think about how a customer buys your product and figure out how to engineer that as much as possible. Lessons from other companies and sales leaders are great, but what matters most is anchoring to your unique buying decision and trying to accelerate that as much as possible.
- “It’s not about what can we do, it’s about what must we do” - this was one of the core ideas that drove the cloud product in the early days of Confluent. There a lot of things that a company can do, but there’s one or two things that a company must do to get to their North Star / where they want to be in 3-5 years. Having that sense of focus and clarity is critical.
- A company should feel like a startup for as long as possible and you as the founder should be in the trenches for as much of the company’s life as possible, but at the same time, the CEO job starts from day one. Super important for founders to deeply identify with the CEO role as early as possible and learn the operational and management skills they need to in order to run the company effectively.
Left the dinner so energized - few things beat spending time with one of the greats in enterprise software, and many of the timeless principles around company creation / leadership / hiring / enterprise sales will stay timeless. Thank you Jay for spending your Thurs night with us and thank you to everyone for coming and bringing great energy and an insatiable curiosity!