This role is the operational and technical backbone of Maven's most complex, highest-stakes customer pilots. It exists because the work requires someone who is simultaneously a builder, a tracker, and a communicator who won't let things fall through the cracks.

What this person does:

• Owns execution end-to-end on strategic pilots. Not coordination, ownership. They track every open item across customer-facing trackers and internal tools (Linear, ClickUp, Notion), know what's blocked, know who needs to be chased down, and drive things to resolution without being asked. Tickets are clean, unambiguous, and mapped correctly. They don't wait for someone to flag a gap, they catch it first.

• Understands the platform deeply enough to be useful, not just present. They know Maven's platform and how it interacts with external systems. They can debug a broken integration, read an API error and know where the problem lives, recognize when an intelligent field evaluation is causing a downstream cascade, and describe what's wrong clearly enough that an engineer can fix it immediately. They won't need hand-holding on the technical environment.

• Translates between customer and engineering. They join working sessions with customers and come out with crisp, actionable documentation. They write the kind of meeting notes and tickets that engineers actually want to work from. They understand what customers are trying to accomplish, can spot when a request is misframed, and know when to push back internally versus when to escalate.

• Tests relentlessly before go-live. They run test suites, document what broke and why, validate fixes, and track edge cases with rigor. They're comfortable doing this at 11pm the Sunday before a launch because they understand what's at stake.

• Runs the operational rhythm. Daily standups, go-live checklists, readiness reviews, metrics readouts — they own the structure that keeps a complex multi-team pilot from going sideways. They're the person who notices when the ClickUp tracker hasn't been updated and fixes it before the Monday client session, not after.

Who this person is:

• Organized to the point of being vocal about it.

• Technically credible without being an engineer.

• Comfortable sitting in rooms with enterprise stakeholders and with product engineers on the same day.

• Does not need external motivation to chase someone down when something is stuck.

• Gets things done.