Unofficial. A job application for OpenAI’s Applied AI Delivery Lead role, built from public pages. Not affiliated with OpenAI.

One delivery plan for one priority deployment.

OpenAI’s posting for Applied AI Delivery Lead asks for an “integrated delivery plan”: scope, milestones, accountable owners, dependencies, resource needs and success measures across customer, OpenAI and partner teams. This is one, for a made-up customer. I built it in one day from OpenAI’s public pages, with AI agents doing the reading.

The bottom lineOpenAI already publishes most of what a delivery plan needs. It sits on five sites, and no public page joins it up for one deployment.
So the plan isOne page per deployment. Every workstream has one owner, every dependency a date, every number a source.
Done meansThe customer’s people are using it, measured against a baseline set in week one, and the review can show why.

One deployment, three teams

The deployment is a claims assistant at Fernhill Mutual, a made-up insurer. An agent built on the API drafts claim summaries and next steps inside the adjusters’ claims system, and the claims organization gets ChatGPT Enterprise. A delivery partner does the integration.

Customer

Fernhill Mutual, a made-up insurer.

Outcome and measures
Owner: Chief Claims OfficerThe result to improve, the measure, and a signature.
Waits on nobody elseby week 2Nothing. It is first.
Baseline
Owner: Claims operations leadThe starting figure, from the claims system and a first survey.
Waits on nobody elseby week 2Its own claims reports.
Security, privacy and legal review
Owner: Security reviewerA sign-off, with any conditions written down.
Waits on another teamby week 8The partner’s data-flow diagram, and OpenAI’s Trust Portal documents.
Identity and access
Owner: Identity adminVerified domain, single sign-on and directory sync.
Waits on nobody elseby week 6Nothing outside the customer.
Claims system access
Owner: Claims platform ownerA test environment and a change window.
Waits on another teamby week 9The partner’s list of actions to approve.
Training and floor support
Owner: Change leadA trained pilot group, and someone to call.
Waits on another teamby week 10Training material from the partner.

OpenAI

Role names as they appear on OpenAI’s public pages.

The integrated plan and reviews
Owner: Delivery LeadOne plan, one board, and a review every two weeks.
Waits on another teamby week 1A named owner for every other workstream.
Agent build and evals
Owner: Forward Deployed Engineering leadThe agent, and evals with a pass mark agreed first.
Waits on another teamby week 8Example claims and a test environment from the customer.
Model and capacity
Owner: Account directorA model with its retirement date checked, and capacity ordered.
Waits on another teamby week 9A load estimate from the partner’s acceptance testing.
Workspace guidance
Owner: AI advisorSetup advice for the claims organization’s workspace.
Waits on another teamby week 6The customer’s identity work.
Measurement
Owner: Delivery LeadAdoption against the baseline, with a source on every number.
Waits on another teamby week 14The baseline, and analytics access from the customer’s admin.
Support path at launch
Owner: Support leadA named route for the first weeks.
Waits on another teamby week 10Named admins and an escalation contact from the customer.

Partner

A delivery partner from the Partner Network.

Integration with the claims system
Owner: Partner engagement leadThe agent reading from and writing to the claims system.
Waits on another teamby week 9API access from OpenAI, and the customer’s test environment.
Data-flow diagram and security answers
Owner: Partner architectThe diagram the customer’s reviewer needs.
Waits on nobody elseby week 5Its own design freeze.
Acceptance testing with adjusters
Owner: Partner test leadA test report, and the load estimate.
Waits on another teamby week 10Evals at the agreed mark from OpenAI, and a pilot group from the customer.
Rollout and training delivery
Owner: Partner change managerSessions run, attendance reported.
Waits on another teamby week 11The go decision, from the customer’s sponsor.
Handover
Owner: Partner engagement leadA run-book the customer’s platform owner accepts.
Waits on another teamby week 16Acceptance by the customer’s claims platform owner.
17workstreams17with exactly one owner3teams
13wait on another team4wait on nobody else

Fernhill Mutual and its people are made up. The role names in the OpenAI column are ones OpenAI’s public pages use. Which role owns which workstream is my proposal: I cannot see from outside how OpenAI assigns them. Sources are on the evidence page.

The sixteen weeks

Five phases that overlap. Sixteen weeks is my assumption, to make the plan concrete. Scoping sets the real length. OpenAI’s forward-deployed team has written of one first deployment that took two months.

Weeks 1 to 2

Scope, owners, baseline

OpenAI’s own sequence for managed deployments starts with outcomes and success criteria. So does this.

  • Interview every workstream lead before the plan is written.It is how I start a program. The answers become one script that all three teams plan from.CustomerOpenAIPartner
  • Agree the outcome and how it will be measured.With the sponsor and the account team: the result to improve, the measure, and who reports it.CustomerOpenAI
  • Set the baseline.From the customer’s own claims reports, and a first survey started by their admin. OpenAI’s scheduled surveys begin at day 120, which is too late to be a baseline.Customer
  • Name one owner for every workstream.Seventeen workstreams, each with one name beside it. A workstream with two owners has none.CustomerOpenAIPartner

How I will know. Every workstream has a named owner and a first milestone, and the sponsor has signed the measures.

Weeks 3 to 8

Build and review

The build and the reviews run side by side, because the review is often the longer of the two.

  • Security, privacy and legal review.The reviewer gets OpenAI’s Trust Portal documents and the partner’s data-flow diagram in week 3, not week 7.CustomerPartner
  • Identity before invitations.Domain, single sign-on and directory sync first. That is the order OpenAI’s quickstart gives.CustomerOpenAI
  • The agent, with evals written with adjusters.Forward Deployed Engineers build it. The pass mark is agreed before the first test run.OpenAICustomer
  • Integration with the claims system.The partner connects the agent. The customer supplies a test environment and a change window.PartnerCustomer

How I will know. The evals reach the agreed mark on real example claims, and the security review has no open blocker.

Weeks 7 to 10

Launch readiness

A go or no-go is only honest if every gate shows its evidence. A gate with nothing behind it shows a dash, never green.

  • Check the model against the launch date.OpenAI publishes retirement dates and gives generally available models at least six months’ notice. The plan records the date beside the launch date.OpenAI
  • Size capacity from testing, then order it.Reserved capacity is bought per model through sales. The load estimate comes from acceptance testing, not from a guess.OpenAIPartner
  • Acceptance testing with the pilot adjusters.On real claims, in the test environment, with the people who will use it.PartnerCustomer
  • Training, floor support and the support path.Who trains, who attends, and who a stuck adjuster calls in week one.CustomerPartnerOpenAI
  • The go or no-go review.Eight gates, each with its evidence, and each owner in the room.CustomerOpenAIPartner

How I will know. Every gate has evidence or a stated reason it does not, and the sponsor decides in one meeting.

Weeks 11 to 12

Launch

A staged rollout: a pilot group first, then the rest of claims. OpenAI describes the same staging for its managed deployments.

  • The pilot group goes live.With a daily check in the first week: errors, hand-offs to a person, and what adjusters rewrote.CustomerOpenAIPartner
  • The wider rollout.Only after the pilot’s first-week review.CustomerPartner
  • A launch report to both sponsors.What shipped, what did not, and what is still open.OpenAI

How I will know. Adjusters in the pilot use it on live claims, and no gate was waved through to get there.

Weeks 13 to 16

First adoption, and the playbook

Launch starts the measurement. It does not end the plan.

  • Adoption against the baseline.Usage from the analytics API, the outcome from the claims system, and what people report. Each number carries its source and its date. OpenAI says workspace analytics can lag by up to 48 hours, so the review says so too.OpenAICustomer
  • What the result means for usage.The account team hears whether the ramp is on its planned date, and why, at the review and not at quarter end.OpenAI
  • The playbook page.What I would reuse, what I would not, and feedback for product, written so the next delivery lead can start from it.OpenAI
  • Close-out with both sponsors, and handover.The partner hands the run-book to the customer’s platform owner.CustomerOpenAIPartner

How I will know. The sponsor can say what changed against the week-one baseline, and the next deployment starts from this one’s plan.

The delivery review I would run

Every two weeks with the customer, every week inside. One page, in the same order each time.

The posting asks for reviews that “drive decisions and action”. So decisions come first, while the people who can make them are in the room.

  • 1. Decisions needed today.Each with the options, the owner, and what waits on it.
  • 2. Gates, with their evidence.Passed, at risk, late, not due, or no data. Never green over a blank.
  • 3. Risks that moved.Only the ones that changed, each with one owner and a date.
  • 4. Launch confidence, and what it rests on.Derived from the gates by a stated rule, so anyone can see why.
  • 5. Adoption against the baseline.After launch. Before launch this part is empty, and says so.
  • 6. What a moved date means for usage.If launch slips, the ramp slips with it. The account team hears it here first.

What I would cut

  • A second use case.The posting says priority initiatives. One deployment taken to adoption, before a second starts.
  • A weekly status deck.The board is the status. A deck is a second copy that goes stale by Friday.
  • Reports built on dashboard exports.OpenAI’s own guide says not to build a lasting report on dashboard labels. The board reads the analytics API and the customer’s system.
  • Fine-tuning.OpenAI’s self-serve fine-tuning stops taking new jobs on January 6, 2027. Prompts, tools and evals first.

What would change this plan

  • If OpenAI already has a plan format,I use it. This one shows how I think, not what I would impose.
  • If the deployment is a managed voice or chat agent,it follows OpenAI’s published sequence for those, and the partner’s share changes.
  • If the customer already runs ChatGPT Enterprise,the identity and workspace work drops out and the plan is shorter.
  • If the account team’s forecast hangs on one date,that date becomes a gate with an owner.
  • If a workstream lead tells me something this page missed,it goes in. That is what the week-one interviews are for.

How I would measure it

Four measures, agreed in week one and reported at every review.

I can see no baseline for any of them from outside, and I have made none up. Setting them is week 1 work.

  • The outcome the sponsor chose.For this customer, time from first notice of a claim to first contact. From their system, not ours.
  • Share of the pilot group using it each week.Adoption, not seats handed out.
  • Gates passed on their planned date.The delivery measure. A launch that arrives by waving gates through has not arrived.
  • Days from launch to the first review with real numbers.How soon the customer can see value for themselves.