Deployment Strategist

Role Overview

The Deployment Strategist (DS) is the business counterpart to the Forward Deployed Engineer during onboarding. While the FDE owns the technical build, the DS owns the “why” and the “what” — understanding how the client’s operation actually runs, deciding which use cases go live first, and making sure every deployment translates into measurable impact on fill rates, inventory levels, and cash-to-cash cycle time.

This is not an engineering role. The DS reports to the Head of FDE & Research and works side by side with the FDE from signature through go-live, owning the client’s business stakeholders and success criteria. Once a client goes live, the account transfers to Customer Success with a clear value story and a map of what comes next — and the DS moves on to the next onboarding.

Key Responsibilities

• Lead business discovery after signature — map the client’s supply chain workflows, decision-makers, pain points, and the metrics that define success for them

• Define and prioritize the use cases for each onboarding, sequencing them so each deployment compounds the next, and translate them into clear, scoped requirements for the FDE

• Own the client’s business stakeholders through onboarding — run steering meetings, manage expectations and scope, and keep the timeline on track from signature to go-live

• Translate between the client’s operation and Nauta’s AI — explain what the agents can and can’t do in language that operators and executives can act on, and bring client insights back to the FDE and Research team

• Build the value case for every client: baseline metrics before go-live, impact tracking after, and the business narrative that supports renewal and expansion

• Co-own the handback with the FDE — success criteria met, value documented, and expansion opportunities (new use cases, sites, or teams) handed to Customer Success and Sales with full context

Profile We’re Looking For

• You solve business problems: 3–5 years in strategy or management consulting, solutions consulting, customer-facing product roles, or operations at a tech startup

• You operate in ambiguity: comfortable walking into a client’s operation without a complete brief, asking the right questions, and turning a messy reality into a clear, prioritized plan

• You’re fluent with data: you can read a dashboard, build an analysis in spreadsheets or basic SQL, and turn it into a recommendation a client will act on

• You’re technical enough to be credible: you understand how APIs, integrations, and AI agents fit into enterprise workflows — and can partner with engineers without being the one who builds

• You communicate with executive clarity: structured and concise, able to run a meeting with a VP of Operations and an analyst at the same time — in both Spanish and English