Deployment Strategist, Enterprise

// About the role

// What success looks like

• –The executive sponsor trusts Zingage as an operating partner, not just a vendor running an implementation.
• –The rollout expands branch by branch or workflow by workflow because the first motion proved value.
• –Frontline coordinators and managers actually use the workflows after the launch team leaves.
• –QBRs create executive alignment, expansion decisions, and product clarity instead of just reporting activity.
• –The messy details you uncover in one enterprise account become product direction and deployment standards for the next ten.

// What you'll do

• –Run structured operating discovery across departments and branches: shadow coordinators, interview branch managers, map escalation paths, and learn how work actually flows.
• –Build the stakeholder map and rollout sequence: who needs to trust the workflow, which branches go first, what can break, and how the customer will know it is working.
• –Own the executive working group: set the agenda, drive decisions, track action items, and hold internal and customer stakeholders accountable.
• –Stay close after go-live as first contact for the agency, own the issue queue, and triage before anything reaches the FDE.
• –Deliver the QBR: own the numbers, narrative, executive sponsor conversation, and expansion recommendation.
• –Run training and change management so the workflow sticks after you step back.
• –Build the playbook and feed the product by translating recurring enterprise friction into prioritized feedback.

// What we're looking for

• –Enterprise deployment ownership. You've run complex engagements end-to-end, not just to go-live but to adoption, executive trust, and expansion.
• –Operational intelligence. You can walk into an agency and figure out how it actually works, not how the org chart says it works.
• –Executive range. You can run a QBR with a COO, pressure-test rollout risk with a VP of Operations, and train a frontline coordinator in the same week.
• –Product translation. When you see the same friction three times, you turn it into a clean field brief and follow through until Product can act on it.
• –Also: 3-5 years in implementation, deployment, customer success, TAM, engagement management, or consulting. Strong writing. Comfortable in technical conversations without being the engineer. NYC-based; travel as needed.

// Interview process

• –Intro call: 30 minutes with Deployment/Product Lead. First filter: enterprise judgment, customer presence, and role clarity.
• –Live case: a complex enterprise deployment scenario using real customer context. No take-home; we move fast.
• –On-site: present your case findings as if running an executive deployment review. Founders chat follows. Strong candidates receive an offer the same day.

// What we offer

• –Competitive base and meaningful equity. If this works, it should work for you.
• –Equipment stipend: whatever setup makes you fast.
• –Luxury gym membership in NYC. We work in health care — yours counts too.
• –Daily lunch, and dinner when work runs past dark — big fan of late-night jams!
• –Time off as needed. We measure output, not hours at a desk.
• –Happy hours, poker nights, and builder events in our Soho office.
• –Snacks in office, including team favorites like Gruns gummies, sardines, protein bars, and midday froyo runs.

// Apply