DevRev

Think you can trust your AI? Keep thinking. Then ask us about Computer – proven more precise, efficient, and safer.

[DevRev @devrev]

We’re excited to share that DevRev is a launch partner in @OpenAI Marketplace.

Getting help at work shouldn’t mean repeating your story, digging through tabs, or figuring out who owns what.

DevRev helps customers and employees get unstuck – with the context needed to move things forward. And when the next step needs a person, the right context comes with it.

Now, OpenAI enterprise customers can find DevRev in the OpenAI Marketplace, see what it can do, and tell us they want to learn more.

Want to know how this will work? Adnan Bhutta, our CVP of Business and Alliances, shares more in his blog: https://t.co/9N3YCKyHN5

[Arth Gajjar @iarthstar]

new badge, same me.

i'm at @devrev, working on Computer, an AI teammate that actually remembers your company.

the goal is simple to say and hard to build: nobody at work should wait on a ticket, a coworker, or a search bar ever again.

gonna document the build in public. follow along.

[DevRev @devrev]

The issue says “fix it.” The repo has questions.

Tomorrow on DevRev Live, Ahmed Bashir, Piyush Malu, and Abhinav Manchanda show how we bring customer context into Computer’s coding workflow, from issue to reviewable code, and where a developer steps in.

Join us here on X!

[DevRev @devrev]

Episode 5 of The Computer Program, Season 2 is out!

One of the key features planned for Computer’s desktop launch, Multiplayer, had been taken out of scope.

It was meant to let teammates continue a Computer conversation where someone else left off, but a blocker and a tight deadline stood in the way.

Hours after agreeing on how the experience should work, the team ran into that very gap themselves.

They started tackling the blocker, got the go-ahead, and brought Multiplayer back into scope.

The deadline hadn’t moved. Could they pull it off?

Watch the full episode to know more: https://t.co/JENmsxggLH

[DevRev @devrev]

An escalation closes, but the work behind the resolution rarely makes it into the ticket.

It lives across old conversations, in the memory of someone who remembers the workaround, or in a product change from months ago that finally explains the customer’s issue.

Phil Verghis, Founder of the Verghis Group and Advisor at DevRev, calls this the “second job” – the work your best people do just to get their actual job done.

When problems cross vendors, that job often falls on the customer. It’s 2 AM, their systems are down, and every vendor’s dashboard is green.

AI can connect the old case, the Slack thread, and the engineering change. But the call nobody documented? The workaround only one colleague knows still holds?

So how do we make that knowledge available when it matters most?

Phil Verghis explores the challenge and what it takes to solve it in the full article: https://t.co/H06STZNB3V

[DevRev @devrev]

@burkov Amen! When someone says ‘I can’t get access,’ sending them three help articles usually doesn’t solve it. You really need to find out what changed and whether it’s something the system can safely fix 👍

[DevRev @devrev]

@asemota @googlefi @instinct Having your AI deal with their AI is funny, but you still need the original issue fixed. Did it get you an actual resolution?

[DevRev @devrev]

@aiDotEngineer Starting with real user questions makes so much sense. Did the benchmark check whether people got a usable answer, or just whether search found the right document...?

[DevRev @devrev]

@mardehaym A weekend demo is one thing. Letting an agent make changes to a customer record or send a message on your behalf is another. You need to know what it changed, who signed off on it, and whether you can reverse it.

[DevRev @devrev]

@jeffsheehan @cmswire A better voice helps... but interested to know what happened after the call? was the issue fixed, or did the customer have to call back and explain everything again?

[DevRev @devrev]

Your AI misses a customer affected by a bug. Would a better model catch it, or did the system never connect the bug to that customer’s account?

Our Co-founder and CEO @dheeraj shares what we learned testing that question in this CIO article: https://t.co/8I7KqorB0C

[DevRev @devrev]

Cards, charts, or plain text? Designing GenUI in Computer https://t.co/gP6ZiR52dR

[Arseniy Shishaev (YC P26) @arseniycodes]

things we shipped today to https://t.co/xxI2WI4TZV:

- triggers on @github pull requests opened or merged
- integration with @devrev
- using @vercel as a context in your automations

🚀 never stop shipping

[DevRev @devrev]

Need a status, comparison, or trend? You shouldn’t have to dig through a long AI answer.

Later today on DevRev Live, Technical Engineer Shivam Kumar and Product Designer Kavinas Sundaramurthy discuss how they’re designing GenUI in Computer.

See you here when Shivam and Kavinas go live.

[DevRev @devrev]

“Work softer.” Sounds good. But are we really going to say that?

Even inside DevRev, it took a little getting used to. What does it mean? Is it too soft? What happened to working hard?

In S2E4 of The Computer Program, the team shares those first reactions... and how a few days with the idea helped them see where it could go.

Catch the full story in S2E4: https://t.co/Lx5QAFLrqW

What was your first reaction to “Work softer”?

[DevRev @devrev]

“I’ve always been drawn to companies that challenge conventional thinking.”

We’re glad that brought you to DevRev, Chris.

@chriskaddaras is joining us as an advisor, bringing experience from Juniper Networks, @nutanix , and beyond.

We’re looking forward to his perspective on the decisions ahead: where to focus, how to grow, and how to turn our ambition into something that matters to customers.

[Yossi Garmazi @Yossigarmazi]

Exclusive: I sat down with @dheeraj (Dheeraj Pandey), Co-Founder and CEO of @devrev and Co-Founder and Fmr CEO of @nutanix, to discuss how AI is transforming enterprise software and the future of programming.

In 2016, he took Nutanix public in the largest U.S. venture-backed IPO of the year.

Now, he’s building again with DevRev, valued at $1.15B after a $100M Series A, backed by @vkhosla (@khoslaventures), @NavinChaddha (@MayfieldFund) and others.

“The iPhone moment for the enterprise is here. The LLM is the new compiler.”

@BoardroomClub1

Chapters:
00:00 iPhone Moment for the Enterprise
00:15 Intro
00:51 Advice for people in the AI era
03:30 From Oracle to Building Companies
06:41 Building Nutanix: Critical Bets
09:25 From Nutanix to Building DevRev
11:08 Lessons from Nutanix
14:28 DevRev Mission
19:25 The Relation between Dev and Rev
25:05 How to Decide Which Features to Build?
29:20 The Future of Developers and Computer Science
33:50 Other Verticals Dheeraj Follow: Biotech & Quantum
36:57 Mentorship
37:56 Favorite Book
38:09 Favorite Movie

[DevRev @devrev]

@lukaivicev Having the choice makes such a difference. It's always better to have the users operate from a "Let me get started on my own, then make it easy to reach someone when I’m stuck" .

That’s truly a much more comfortable way to try a product.

[DevRev @devrev]

@dhinchcliffe Clear boundaries make self-service much easier to trust. People should know what they can do themselves and what needs approval.

[DevRev @devrev]

@_nicolealonso The knowledge piece is so important. Even a simple “which leave policy applies to me?” can turn into three messages and a wait.

Curious whether you’re seeing these roles take on completing requests too, beyond answering questions.