AI tools for Forward Deployed Engineering — Vasuman Moza, Varick Agents

Allright, first and foremost, thanks so much for being here. It's been a great experience, you know, obviously chatting amongst other industry giants like Cursor and Factory and Anthropic, and I'm sure you guys are mostly here for them, but thanks for sticking around for this talk.

My name is Voss, I'm the CEO of Varick Agents. We work with some of the largest companies on the planet, transforming them from the inside out with AI and agents. And because of the nature of our work, which is highly bespoke, we go very deep into our clients.

It requires a lot of forward deployed engineering, and this conversation is around why that's so important, how we approach it at Varick, and some of the internal tooling that we've created internally to allow us to scale that forward deployed motion without, you know, increasing headcount exponentially.

And it's settled the next bottleneck because I fundamentally believe the next bottleneck is: how deep can you go into a customer without scaling headcount exponentially? How can AI do that job for you? So, as stated previously, AI is solving the execution of work.

If you were to look back a couple of years ago before, you know, thinking agents and reasoning agents were a widespread phenomenon, and I had asked you, "How many of you have used AI to solve an end-to-end task?"

the answer would be slim to none. But if I asked that same question to everyone today, saying, "Has AI solved an end-to-end task for you today?" I'm sure every single one of you would raise your hands. So clearly, execution is no longer the core bottleneck.

The models are improving to the point where intelligence is no longer the constraint, and harnesses are being built in a way that allow us to use whether it's browser-use tooling or API tooling with very robust MCPs that allow us to execute work with near perfection.

The difference and the bottleneck that is still here is: how much can you understand the business? Because every business, every consumer is different. One sales department for a healthcare company, for example, operates completely differently than the sales department for a SaaS company, and this is something that we see with our work today at Varick Agents.

And if there are any business operators in the room, you know exactly how hard it is to wrangle the latest models to solve for your specific use cases. It's very difficult to extract that context from your, you know, employees and from your team, and it's very difficult to feed that into an API call or a simple model call that doesn't break down very quickly.

So the bottleneck is: how much can you process or re-engineer, how much can you process, understand? And that's the job that we do here at Varick. Soright now, operations are fundamentally centered around the human. Right now, the work that you do today is done by humans, whether it's on top of software or completely agnostic to software.

But in the future, operations will be centered around AI. And this means not only, you know, providing companies with AI tooling like a Cursor, Claude Code, Codex, like a Factory, like any of the other brilliant AI tools that you're sure you're experiencing here today, but also changing the operations and the processes themselves.

And fundamentally, that is the role of a forward deployed engineer. It's going into the company, understanding how things run today, and re-envisioning what it could look like tomorrow. And we believe that is our job at Varick and why forward deployed engineering is such a core part of what we do.

So a forward deployed agent, what does that really mean? So why do we need FDEs? As stated previously, I'm not going to, you know, go into this too much. I'm sure you've been hearing a lot of this today.

FDEs are responsible for a few different things. One is they map the way that humans are doing their work today. So how we do that at Varick is: several forward deployed engineers will be embedded directly with the customer.

You can imagine it's an enterprise company with thousands of employees, but we'll scope it down to a single department. In a finance department, for example, we'll have them sit down with the process leads for APAR, card reconciliation, banking, billing, FP&A, etc.

So interviewing every single one of these process leads to understand not only how are things running today, but more importantly, when things go wrong, what happens. You know, a lot of the documentation that you have in companies about the golden path and maybe an edge case or two, but this is still fundamentally not the reality.

Where when we talk to customers, it's a lot of, you know, "Sarah in AP handles the workflow today in this way, but when things go wrong, she actually sends it over to Chris, who then takes four days of cycle time to handle reconciliations between a purchase order and an invoice."

Those are the realities that are, one, unique to every single company. The way that they handle things is different from one company to the next. And two, the real bottleneck for why AI can't just run amok and handle end-to-end processes without the handholding that you see today in the enterprise.

So this is the first section, which is mapping how humans do the work. The second is really re-engineering the process around AI. So what does this mean? You know, there's a lot of talk being given today in terms of slapping AI onto broken processes, and that's fundamentally why you don't see the ROI across the industry today.

There's a lot of, you know, semi-outdated but still very relevant statistics, like the MIT review saying that 95% of generative AI pilots fail to reach production, or the other statistic, which is 87%, very similar thing, that most AI pilots don't produce measurable ROI or they don't ship to production, period.

And the reason for that is, a lot of the time, AI is being slapped on top of broken processes in a way that the AI doesn't actually understand how to do things. You see this at the simplest level with coding, where as an engineer, it's very difficult, even with GOL loops and the latest technology there, to just say, "Go and solve this for me," and have it run off and refactor entire codebases without some degree of human input.

Now, if you extrapolate that to a business context, these are very non-technical operators in finance, sales, marketing, procurement, logistics, etc. So giving them this AI tooling will not allow them to receive the same ROI that a software engineer might be able to produce or create.

So what this means is you need forward deployed engineers to help them re-engineer their current process around AI. It needs to be not too different to where they don't understand, you know, how to operate the system. For example, if they're used to an 11-step workflow and you come in and change that with a one-step, they might be taken aback, the adoption rates might suffer, etc., as was alluded to in previous presentations.

But at the same time, it needs to be different enough to where you're actually capturing the ROI. Meaning, you do say, "Allright, four out of these eight steps will be handled completely autonomously. The other three will be handled with some human-in-the-loop intervention, and one step of that process will be handled by a human, period," either because the risk is too high or because, you know, it's not unique enough for an agent to produce measurable value in that specific step of the process.

So that's the second major step of a forward deployed engineer. That's why we need them. And third and finally, and this is what I want to bring one of my heads of engineering to discuss in just a moment, is actually deploying these agents on top of existing systems.

So fundamentally, at Varick, we believe that the AI wave left a lot of enterprises behind. A lot of enterprises marry to their systems of record. Not everybody, but most of them are. They've migrated to NetSuite, they've migrated to Dynamics, they've migrated to SAP and Salesforce.

And when you pitch them AI solutions that live completely disparate from these systems, you're ignoring the reality of enterprise. One of the quotes from our clients said that they spent $5 million and five years migrating to NetSuite. That's a real quote.

So if you're telling them, "Hey, I have this fancy AI tooling, but by the way, you have to migrate off of NetSuite," they're going to tell you to get out. They don't have any appetite for that. So what we believe in Varick, believe in at Varick, is we'll build the agents on top of your systems of record.

And the way that we do that is quite unique. We have our own Varick OS platform that allows us to spin up agents, monitor them, etc., with the full governance and eval suite baked in. But at the same time, it lives on top of your systems of record.

So if you are on a Salesforce or a NetSuite or a Dynamics or an SAP, we will not ask you to migrate off of that. And that is where enterprise needs AI the most, because they're too large to move off.

So why build the FDE agent in the first place? As mentioned previously, I think everyone is saying that 2026 and onwards is the year of the forward deployed engineer. And to some extent, we believe that's completely correct. There has never been more of a need to go deep into customers and understand their business use cases and help them adopt the latest in AI tooling.

But at the same time, we realize that it's actually very difficult to find forward deployed engineers who are both the technical, like, top 1% who are really able to understand and speak AI 10,000 times better than the average, you know, enterprise customer, but also have the communication and human skills needed to be, you know, as alluded to previously, very high IQ, high EQ, extracting the information from the customer and meeting them where they are in real time.

You know, typically you'll have consultants that you then train on the technical side or engineers that you then kind of train on the soft skill side, but it's very hard to find people who are, you know, the best of both.

So the FDE agent is our effort to bolster the existing forward deployed engineers that we do have. So, for example, allowing one forward deployed engineer or forward deployed strategist to manage and maintain several client communications. I know that most of the folks in the room are technical, but it's very easy to misunderstand how deeply involved you have to be with the client.

They're emailing you 24/7, they're sending you hundreds of pages of documentation, and every single process lead will pull you in a different direction. AP relies on AR, relies on reconciliation, relies on FP&A, and they each have their own version of what they think is the most important.

So being able to manage that context and being able to serve them all equally while also not hiring 50 people to do so is fundamentally very important, and it's how we at Varick avoid being, you know, a traditional consultancy while also offering that hand-holding and, like, very human experience, human-centered approach of consulting that we do think is very valuable.

So in the past, in 2024 and around that time, execution work was still the bottleneck. This was before the models gained the intelligence and the harnesses gained the integration abilities that allowed them to move past the execution bottleneck.

Now the AI models are trained to solve the execution of knowledge work. I will go as so far as to say that knowledge work is almost entirely solved. The difference is, and what we're realizing now, is that designing how work gets completed around AI is the next bottleneck.

It's the ability to go deep within the customer, redesign their workflows, deciding what should be automated versus shouldn't, and building this in a robust and scalable way on a platform that moves the needle for our clients. You know, as opposed to doing a point solution, which promises to transform just one part of your sales process, for example, maybe it's prospecting, that ROI might deliver 5 to 10% ROI for you as a sales function.

Same thing on finance. If you're just doing AP and no other part of your department, you might have a 5, 10% ROI. But at Varick, we deliver department-wide transformations, holistically transforming the entire department at a time. And that's how we get the ROI that we see for our clients, which is 25%, 50%, 75%, truly giving them back, you know, the three things, which is revenue uplift, cost savings, and risk mitigation, as was so eloquently stated previously.

And an AI FDE is trained to re-engineer these necessary tasks around AI. So I want to invite my head of engineering, JD Pruitt, to come up and share some more of the deep technical stuff on our FDE agent, because I haven't written a line of production code in a while.

So here's JD.

Okay. Thanks, Voss.

And maybe if we can get his mic going.

Great. Thank you. Thanks, Voss. So this project to give tools to our FDEs basically started with me. I lead the platform team, and we're over on one side of the office. We're hanging out, we're chilling, having a great time.

Codex, Claude, we're all hanging out. And then I look over at the FDE side of the room. They look stressed. They are sleep deprived. They're extremely miserable. They've got clients emailing them 24/7. I'm like, "My God, you guys haven't slept at all."

So I go and I start talking to them, and I'm like, "Okay, what is your guys' process likeright now? How are you actually engaging with these clients?" And like, "Well, we, you know, upload about 150 pages of documentation to Claude, and then we prompt Claude, and then we wait like two minutes, and then we get analysis, and then it's verbose and incorrect, and it kind of sucks."

And I was like, "Allright, we got to fix this." So we have been working on an FDE agent, which is the Codex for our FDEs, basically. And there's three stages of it, the last of which is certainly still in development.

The first is what we call the engagement. The first function is the engagement agent. And essentially, this is a better version of Claude built just for our FDEs. It's their assistant. They have it pulls in their granola notes.

It synthesizes documentation. It reads PowerPoint slides. It allows them to query and say, "Who is responsible for this process? I got an email that mentioned Sarah spelled, you know, this way, and I have a, you know, a Slack message with a different way.

Are these the same people?" Because these are the questions that our FDEs are asking all day, every day, and they waste a ton of time just waiting on Claude to respond. So the engagement agent is their way of it's their assistant to build the workflow.

Then there's the workflow agent. And what we did is we took our engagement agent and we embedded it inside of our platform so that when our FDEs go and they actually build the workflow, the FDE agent isright there saying, "Oh, you forgot about this edge case.

You should probably ask me, you know, who owns this process so I make sure the email goes to theright place." And it lives. It's basically a I can talk about more of the details on the next slide, but.

Whoops.

It lives on side of our inside of our platform. It works next to Claude or Codex, whatever model you're using, and makes sure that the workflow that the FDE is constructing is actually

it correctly shadows the process that we want to engineer. And then there's the final stage, which we're not at yet, which is an autonomous assistant for FDEs where it's receiving emails from clients who say, "Actually, I want to change, you know, where my QC report goes to.

I want to, you know, change it to a different email," etc. And our agent is able to process that information, query the understanding of the company that we currently have, ship an autonomous change to the workflow on top of our platform, and then our FDE never has to get involved, saving their time for the much more high-value work of sitting down, interviewing with the clients, really understanding what their process is, and not dealing with all of the small little minutia that anyone who has been an FDE can tell you takes up a lot of their time.

So how do we build this? The first thing is we need some single source of truth, some representation of a company's functioning. There's a lot of different ways to do this. If you were at the booths downstairs this morning, there was, you know, five companies trying to sell you a GraphDB, and you can just use Postgres, whatever it is.

Yes, I'm looking at you. It doesn't really matter what you use, but the point is we use a dependency graph. Most of these workflows inside of enterprise are remarkably linear. They just have a lot of cycles in them.

But at the end of the day, the process owners want things to be as dependency-driven as possible. They don't want person C in the process to have to deal with something before A and B have approved it. So a dependency graph is a very nice representation of this.

Then we do our own model training. And there's really two parts to this problem that we're trying to solve. The first is, given extracted context for the FDE, do we get a good, high-quality output? And the answer is, with Claude, honestly, no, which is kind of surprising.

But the really I'm sure you guys have experienced this. When you are trying to do a long analysis, frontier models are extremely verbose, and they lack the, you know, I would say the

I only started believing in consultants once we started hiring them at Varick. And the reason is they're so good at figuring out what is the part of the detail the client actually cares about and what is the part that can get glossed over.

And frontier models have absolutely no concept of this. So we started post-training our own models on top of open source models. We're a fan of Kimi K26, but a lot of these would do a lot of these would do fine to really get that nice balance between detailed and clarity that the frontier models often lack.

So that's a bit about writing a good normalized process flow from extracted context. But there's the second half of the challenge, which is getting good at traversing at extracting theright context. So we might have this huge knowledge graph, but it's remarkably difficult to traverse this knowledge graph in a reliable way that finds us theright context.

So once we have our post-trained model, we create an RL environment where we have exposed our own custom tools specifically designed to traverse our knowledge graph. These tools are things like, "Make sure person A and person B are actually the same person," because a lot of, you know, there's a lot of mics in every company we work with, and Claude gets very confused by this.

A second thing might be something like

identifying redundancy cycles or, like, violations of your DAG inside of your knowledge graph. And so in our RL environment, we train really good tools to do a good job of traversing this graph to extract theright context. So that's how we solve the two problems: writing good analysis from the context and extracting the correct context in the first place.

And then the third part, which we are still building towards, is an agent that operates autonomously to do the kind of workflow management on the small things that the FDE doesn't have to waste their time on. I think that's all I've got.

I'll hand it back over to Voss.

Thanks, JD. So where does that leave us? And I want to share a little bit more about Varick because obviously we're not the Cursor or Anthropic or OpenAI of the world. When we started this company, we fundamentally believed that the way the puck was moving, you had to get ahead of it, and you had to start learning how a business runs and building with that in mind.

I think a lot of Silicon Valley starts to go product, product, product, but what we're building for cannot be solved for with just a product. We start off every single engagement with an audit where we actually send our forward deployed engineers, strategists into a company to learn how it works from the inside out.

That is what I believe is the biggest bottleneck. And after that, we go into implementation. We build agents on top of our platform. And yes, you do still need all the bells and whistles and the fancy technology that allows us to, you know, really automate work in the future.

But again, the bottleneck is the forward deployed motion, which is why we are so bullish here at Varick on our AI FDE. And if you're interested in learning more about it, or if you're interested in joining one of the fastest-growing startups in Silicon Valley, working with some of the largest clients on the planet, come find us after and we'll have a chat because we are aggressively hiring.

And if you are a company looking to understand how AI can really move the needle for you internally instead of just slapping a frontier model on top of everything and watching it break in production, come find me after as well.

Thank you all so much for the time. I really appreciate it. And cheers.