Skip to main content

FDEs for SAP

Forward deployed engineers for SAP

Our forward deployed engineers (FDEs) are a small Mindset team that works inside your business until the agents they build are in daily use. They know SAP, and they start from agents we have already built.

A Mindset working session on SAP BTP and Business Data Cloud, with people around a conference table and laptops open
A BTP and Business Data Cloud working session, March 2025

We started out forward deployed.

Mindset began in 2010 as Target’s SAP R&D lab, a few people working inside one customer’s business. We have built on SAP for the people who use it ever since. Our FDE teams work the same way, with AI agents.

“My theory then, and now, was simple: pull the good parts out of SAP, combine them with great design and more modern technology, and actually make SAP work for people.”
Gavin Quinn, founder and CEO, in his note on Who We Are

How it works

A builder and a designer

Every team pairs an engineer who builds on SAP with a designer from our AppHaus practice. The designer spends the project with the people who will use the agent, like the customer service reps clearing blocked orders, and what they learn shapes each build. We have run the Minneapolis AppHaus since 2018, the first partner-run AppHaus in the US.

Start from what already works

MIND is our library of Joule agents and SAP accelerators, built from sixteen years of projects. SAP’s AI architects validated 20 of the agents before Sapphire 2026. We fit those to your processes and data first, and write new code only where there is a gap.

Stay after go-live

When the pilot ends, we keep the agents running for a monthly fee, fix what users report, and help pick the next process. Each project adds to MIND, so later agents take less time to build. Your data stays with you. When a pattern is worth reusing, we rebuild it in our own SAP systems with test data.

Work inside your AI rules

Some clients let our AI tools into their code repositories. Others run on government cloud and allow no generative AI near their data. We agree on the rules in writing before kickoff, and on restricted projects we use only tools your security team has approved.

The first six weeks

  1. Day one

    A working session with your users picks one process and writes down the number it should move, like orders stuck in credit block.

  2. Weeks one to five

    Short build rounds. The pilot group sees each one, and their feedback decides what changes next.

  3. Week six

    Two or three agents go live for the pilot group. We measure them against the day-one number.

  4. After that

    We run the agents for a monthly fee and start on the next process.

Fixed price, agreed before we start.

“That is a gamechanger. This thing will save me so much time.”
Kent Fischer, Operations Special Projects Manager at Border States, on the Gen AI sales assistant we built on SAP BTP
Jon Bragg and Lionel Susini leading a working session at the Minneapolis AppHaus
A working session at the Minneapolis AppHaus, 2024
Mohan Babu Perumalla leading an Integration Suite coding dojo for the team in Hyderabad
An Integration Suite coding dojo in our Hyderabad office, September 2025
Mindset team members on stage at SAP Sapphire for the Joule agents launch
On stage at SAP Sapphire 2026 for the Joule agents launch

Start with one process.

Tell us which process takes up most of your team’s time. We will give you a fixed price for the first six weeks before you commit. SAP’s Business AI incentive reimburses partner SOWs for a customer’s first wins, so ask whether you qualify.