The expensive part of an AI deployment is rarely the model call. In Greg Isenberg's conversation with Varick Agents CEO Vas Moza, the forward-deployed engineer (FDE) earns their place by finding out how work actually moves through a company. Only then do they decide whether a step should disappear, become plain software, use an agent, or stay with a person.
Map the real process before building. Interview the operators, inspect permitted system events, document exceptions and waiting time, remove unnecessary steps, and establish a baseline. Build inside the client's existing systems, with tests and human approval for consequential decisions. Measure cost, cycle time, quality, and risk after deployment. The episode's large savings examples are attributed client reports, not a promise of similar results.
Watch the FDE Masterclass
Credit: Greg Isenberg's Startup Ideas Podcast with Vas Moza of Varick Agents, published 1 October 2026. This article uses the video and the transcript supplied for this review; the discussion uses anonymized client examples. The opening Google audio segment is sponsored, and its links appear separately from the FDE evidence. See also Moza's own process-reengineering article.
What the $1M-a-Year Headline Does and Does Not Mean
The title describes a potential value-based arrangement, not a typical FDE salary. At 42:25, the speakers discuss sharing in the value of a successful transformation. The example of earning $1 million from $10 million in value is hypothetical. It depends on proving that value, agreeing commercial terms, and sustaining the result. It should not be read as an observed pay distribution or a career guarantee.
The practical lesson is to sell a measurable outcome, not a bundle of agents. That means defining the buyer's baseline and the unit of improvement before quoting an ROI. A CFO may care about cost per invoice and close time; a sales leader may care about quote-cycle time and conversion; a people leader may care about onboarding quality. The same technical work can matter for different reasons.
First, Map the Process People Actually Use
At 09:55, Moza walks through discovery. Start with the documented path, then compare it against interviews and timestamps from the systems of record. Documents tell you what should happen; operators tell you what happens when an invoice is incomplete, a quote comes back from legal, or two systems disagree. Event histories show how often those exceptions occur and how long each handoff waits.
A useful process map records the trigger, owner, input, system, decision, exception route, output, touch time, and elapsed time for each step. Ask which system wins when records conflict. Mark loops, not just the happy path. Moza's written method explicitly calls for interviews plus process mining; either alone leaves a partial picture.
In the anonymized $5 billion software-company example, Moza says a neat quote-to-signature diagram concealed roughly 20 steps and seven loops. He reports that 61% of requests returned through one loop. Those figures come from his description of a private engagement and cannot be independently checked from the public video. Their value here is diagnostic: if you optimize only the published diagram, you may speed up a step that is not the source of the delay.
Sort Each Step Into Four Buckets
The episode's four-way sort is a design decision for every step, including steps that should no longer exist:
- Delete. Remove duplicate approvals, re-keying, and handoffs that do not add necessary control. Do this before automating them.
- Plain code. Use deterministic rules or APIs where the input and outcome are stable and auditable. An LLM adds cost and uncertainty to a simple if/then rule.
- Agent. Use bounded model judgment where inputs vary, past examples exist, outputs can be evaluated, and failures can be caught. Keep a clear fallback.
- Human decision. Preserve review for high-risk, ambiguous, contractual, financial, or poorly evidenced actions. Give the reviewer the relevant evidence rather than a bare recommendation.
Moza's written article calls the surviving execution paths three buckets: deterministic, agentic, and human-in-the-loop. That is consistent with the video's four-way sort once the delete decision has been made. Neither framing means that every surviving step needs AI.
What the Reported Case Studies Show
The most concrete before-and-after example comes from accounts payable. Moza reports that an anonymized client's workflow moved from 17 steps to seven, cycle time from 24 days to six, straight-through invoice processing from 18% to 87%, and cost per invoice from $31 to $6. The last change is about an 81% reduction. He explicitly attributes part of the improvement to process redesign, not merely to an agent.
These are Varick-reported results from a client whose identity, data, measurement window, and cost allocation are not public. They illustrate what to measure, but they are not an independently audited benchmark. A reader should baseline their own fully loaded cost, exception rate, accuracy, cycle time, and control failures before estimating savings.
The five-NetSuite-company example adds another point: shared software does not mean shared process. Moza describes different step counts and regional variants. A reusable deployment needs a common process specification with explicit local exceptions, not a single agent copied blindly across every business.
Deploy Where Work Already Happens
Moza recommends building on top of existing systems of record such as Salesforce or NetSuite, with approvals surfaced in the tools staff already use, such as Slack. The aim is to avoid forcing a CRM or ERP migration just to run an agent. That is a sensible deployment preference, not permission to give an agent broad production access. Start with least-privilege, read-only discovery; define who may approve writes; log inputs, outputs, and overrides; and test failures before any production action.
At 40:29, the FDE skill set spans three disciplines: understanding the domain and its systems, shipping reliable integrations, and evaluating what models can safely do. Communication matters throughout because operators must trust the new process, and executives need a legible before-and-after scorecard. A polished demo without adoption and measurable improvement is not a deployment.
A Five-Day Starter Plan, Kept Small
The episode's five-day exercise begins with your own work before approaching a client. Here is a cautious version you can run without privileged access:
- Monday: List the applications that hold one recurring task and identify which record is authoritative.
- Tuesday: List 20 actions you took last week. Select one repeated, low-risk workflow with a visible outcome.
- Wednesday: Map that workflow end to end, including the ugly exceptions and waiting periods.
- Thursday: Assign each step to delete, code, agent, or human. Record a baseline and one failure mode.
- Friday: Ask a reachable business whether the same problem recurs for them. Offer a diagnostic, not a guaranteed savings figure. Get approval before accessing their systems or data.
For a first engagement, the sellable deliverable may be a process map, exception inventory, baseline, and prototype plan. That is smaller and more defensible than promising a fully autonomous department in a week.
Build a Business Idea From This Method
Use the four-bucket method on a process you understand. The prompt below asks for several buyer-specific opportunities, then turns one into a measurable, human-reviewed validation sprint. It works in a general AI assistant and does not require an enterprise agent platform.
Find a process worth redesigning
Three opportunities, one measured pilot.
Video Chapters
Jump to the part of the interview that matches your question:
- 03:58 FDE overview and process reengineering
- 09:55 How to map a company's actual process
- 14:11 The $5 billion software-company example
- 18:11 Four buckets for every step
- 19:04 Building in systems of record
- 21:36 Private-equity portfolio rollout
- 23:43 Selling to the C-suite
- 27:07 Mapping five NetSuite companies
- 28:39 Accounts-payable process and reported results
- 34:51 Code, agents, and human decisions
- 38:16 Sidekicks versus background agents
- 40:29 Skills of a strong FDE
- 42:25 Compensation and value discussion
- 45:26 Five-day starter plan
- 50:20 Full playbook recap
Sources and Useful Links
- Primary video: Greg Isenberg interviews Vas Moza. The supplied transcript and video chapters support the attributed examples above.
- Guest's written method: Vas Moza, "Don't Apply AI", and Varick Agents. These are company sources, not independent verification of client outcomes.
- Creator resources: FDE slides and Vas's article shortlink, as listed in the video description.
- Sponsored segment: Google audio-model links from the description: Gemini 3.8 Live, Gemini 3.5 Transcribe, and Gemini 3.5 Live Translate. This promotion is separate from the FDE analysis.