Forward Deployed Engineer, SAP

You'll take Causa Prima from a signed customer to agents running live inside that customer's SAP system. You're the person the customer trusts to get it done. You understand how their finance team works, you can earn the respect of their IT and SAP teams, and you get the deployment over the line and keep it delivering afterwards.

Our agents run accounts payable, accounts receivable and working capital for the CFO office. They only create value once they're live in the ERP the customer actually runs, and for most enterprise customers that's SAP. You sit between the customer and our product and engineering team. You turn how a finance team really works into what we build, and you make sure what we build actually goes live.

If you have experience deploying AI or software tools for sophisticated clients and know your way around SAP, this is the role for you.

• Work hand in hand with GTM and product engineering. You're involved before the deal is signed: you join prospect calls, scope what the deployment will really take, and help close the sale. Once it's signed, you work day to day with our product and engineering team, so what we sold is what we build and ship.

• Own the customer relationship through deployment. You're the customer's main point of contact from kickoff to go-live and beyond. You run the workshops, the weekly updates, and the hard conversations.

• Map the real process, not the documented one. Sit with AP clerks, controllers and shared service teams to understand how purchase orders, goods receipts, invoices and payments actually flow, including the exceptions nobody wrote down. Turn that into clear requirements our engineers can build from.

• Be credible with IT. Work with the customer's SAP admins, Basis team, security and architects to agree how we connect: which system, which interfaces, which authorizations, which approvals. You own the open-questions list until it's empty.

• Scope the integration for each customer. Understand their SAP landscape, including company codes, document types, approval rules, and ECC versus S/4HANA. Work out what that means for our product, and agree the setup with our engineers before anything is built.

• Find the way when the obvious path is blocked. A third-party tool with no API, a vendor who doesn't answer, an IT team that won't open access this quarter. On one deployment the customer's invoice tool had no API, so we built our own extension and went live anyway. You find the plan B, get the customer and the team behind it, and ship.

• Own the plan with the customer. Keep one shared roadmap of what's promised, by when and by whom. Set release dates with our Head of Product, protect a customer testing window before every go-live, and hold everyone to one definition of "live": running in production, not demoed.

• Prove the value. Agree with the customer what success looks like, such as invoices processed without a human, hours saved, or discounts captured. Then track it and report it.

• Feed the product. Every deployment teaches us something. You bring the patterns back so the next customer is a configuration, not a project.

We're building autonomous finance operations for the CFO office, founded by the team behind Taulia. SAP is where the money actually moves, so this role sits where our product meets reality. You'll own customer deployments from day one, work directly with the founders and the product team, and see the results in live customer systems.