Client Delivery Lead

AJAIA•New York, NY

6d•Onsite

About The Position

Ajaia is hiring a Client Delivery Lead to own delivery operations across every active client account at once: the calendar, the resourcing, the quality of what goes out the door, and adoption after go-live. You run the weekly delivery review, and you are the person who notices a deliverable is not good enough before the client does. This is an operating seat with real stakes on both sides. You are not building the client relationship, and you are not writing the technical spec for a single engagement. You are the layer that makes sure everything Ajaia is delivering, across every account you carry, is staffed correctly, meets the bar, and actually gets used once it ships. You will carry a portfolio, not one build, and you will be the reason a client's second engagement with Ajaia is smoother and cheaper than their first.

Requirements

Highly organized across many moving projects at once.
A sharp eye for quality: you notice what is wrong with a deliverable, not just that something is off.
Calm, clear, honest client communication, especially when the news is bad.
AI fluent: you use AI daily to triage, draft, and check work, and you can tell good output from slop.
Comfortable making priority calls and owning them.
2 or more years in delivery, implementation, or operations.
On-site in New York, with client-site travel as engagements require.

Nice To Haves

Experience delivering AI, data, or software implementations.
Exposure to a regulated industry such as healthcare, financial services, insurance, or education.
Familiarity with delivery or project tooling such as Jira, Asana, Monday, or Linear.

Responsibilities

Own delivery operations across every active account: the calendar, who is staffed where, and what ships when.
Run the weekly delivery review across the portfolio, and walk in already knowing which account needs the conversation before anyone raises it.
Decide, account by account, what ships, what gets fixed first, and what gets delayed. Own that call.
Read a deliverable before the client does. Catch what is wrong, not only what is late.
Build the resourcing plan across engagements, and say no to a request that would starve one account to feed another.
Own adoption after go-live. A tool nobody uses is not a finished engagement, whatever the contract says.
Build the playbooks, templates, and checklists that make the second engagement of a given build type cheaper and faster than the first.
Escalate early when an account is at risk, with a specific ask attached, not a status update dressed up as one.
Partner with the account lead on the relationship and with the project lead on each build.
Report the state of the portfolio honestly, including the account that is not going well.