Embedded AI Team, Project or Hire: What an AI Retainer Includes

Q: How do you decide between a retainer, a project and a hire?

Ask five questions, in this order. 1. Can the outcome be written as one deliverable with an end date? If yes, buy a fixed project. 2. Is there a continuing queue of AI work whose priorities will change as you learn? If yes, a retainer fits. If not, you would pay for idle capacity. 3. Is AI core to what you sell, with steady work and a realistic path to hiring and keeping senior people? If yes, plan to hire, perhaps after a project or a retainer has taken the first system into production. 4. Can you name a product owner and a sponsor with time for sprint decisions, and give the team access to data and systems? If not, a retainer will wait on you whatever the contract says. 5. Can you leave? Ask for the exit terms in writing: who owns the repositories, what only the vendor can operate, and what leaving costs. None of the three fits if the best candidate does not need AI. A rule, a report or a process change sometimes does the job, and a team that only ever answers "build it" is not advising you. If you are unsure where you stand, start with which AI engagement you need or how to choose an AI partner.

Last updated: October 2026. External figures are attributed and dated in the text.

In short: An embedded AI team, or AI team as a service, is a small senior group that works inside your tools and meetings on a monthly fee and carries AI work from strategy to production and operation. "Fractional AI team" is used both for this and for part-time senior advice, so ask which you are buying. A fixed project buys one deliverable, a hire buys one person, and a retainer fits continuous work whose priorities will move. NewGenApps' Your AI Team starts from $10,000 per month for the smallest pod and runs month to month after an initial term of typically three months. Someone other than the builder verifies work before it is promoted; the exit is included in the fee.

What is an embedded AI team?

An embedded AI team is a small group of senior AI practitioners that works inside your organization's tools, stand-ups and working hours, on a recurring monthly fee, and carries AI work from strategy through build, deployment and operation. The market also says "AI team as a service" and "fractional AI team" for this idea, and not consistently: "fractional" is often used for a part-time senior adviser, which is a different product. In this article an embedded team does the hands-on work and is accountable for what runs in production.

It also differs from staff augmentation, where you direct individual contractors to fill seats. In a retainer you decide what is built next, the team decides how, and someone other than the builder shows that it works.

Retainer, project and hire compared

This is our working comparison, a judgment rather than a measurement. We looked for an independent study comparing outcomes of retainers, fixed projects and in-house hires and did not find one; the comparisons we found were published by firms that sell one of the three. The nearest evidence compares building with partnering in general: see build vs buy for an AI team.

	Fixed project	Embedded retainer	In-house hire
What you buy	A written deliverable at a set scope and price	A standing team's capacity on a monthly fee	One person's time and judgment, on an open-ended basis
Who sets priorities	Fixed at signing; changes go through change control	You, through a backlog re-planned every sprint	You
Who carries the risk	The vendor carries overrun for the written scope	Shared: you pay for capacity, the vendor answers for how it is used	You: recruiting, ramp-up and key-person risk
Best for	A decision or build whose scope is knowable up front	Continuous AI work whose priorities will move	AI that is core to the product, with steady work
Watch for	Improvement after handover needs a new scope	A vague backlog, or no named owner on your side	Time to fill senior roles; knowledge leaves with the person
How it ends	Delivery and handover	Notice, then a structured hand-over	Notice under the employment contract

What does an AI retainer include?

Your AI Team, the NewGenApps retainer, includes the following (headline terms published on the engagements page on 2026-09-29; detail from the engagement charter):

A small senior pod working in your tools, stand-ups and overlapping hours, led by an Engagement Lead, with an architect, builders and verification sized to the tier.
A rolling backlog, re-planned every sprint.
A monthly strategic review that reads the roadmap alongside outcome metrics.
Independent verification: work is checked by someone other than the person who built it before it is promoted.
Responsiveness tiers for incidents, set by severity and applied within the pod's working hours.
Continuous knowledge transfer and a structured, no-lock-in exit at no extra charge.

Not included, unless added through change control: general application development unrelated to AI; round-the-clock on-call beyond those tiers; standalone data-platform builds or large migrations; regulatory certification or legal sign-off; staff backfill. Third-party model, license and cloud costs are billed at cost or paid by you directly. Terms are confirmed in the engagement order.

How do the pod tiers differ?

Pods come in indicative tiers, sized to how much AI work is running at once. Every tier has an Engagement Lead accountable for outcomes and works to the same verification discipline; the tiers differ in team size and in how much of the lead's, architect's and verifier's time the pod carries. The tier is confirmed at scoping and can be adjusted at the monthly review.

Pod tiers at a glance

Indicative shapes from the engagement charter, not a quote.

Pod shape	Indicative composition	Best for
Focused pod	Part-time Engagement Lead and senior builder capacity, with architect and verification on call	A capability in steady production: maintenance plus measured improvement
Balanced pod	Part-time Lead, architect, builders and verification	Live capabilities being built and operated at the same time
Multi-stream pod	Dedicated Lead, architect, several builders and dedicated verification	A portfolio of AI capabilities across teams, with parallel build and operate streams

Who decides what, and how is work proven before it ships?

You decide what is built next, the Engagement Lead decides how, and a verifier who did not build a change decides whether it is done. The routine is a daily stand-up in your tools, sprint planning, a sprint demo of working software against the live system, a retrospective, and a monthly strategic review.

"Independent" has one specific meaning here: the person who verifies a change is not the person who built it, and judges it against acceptance criteria agreed in advance. It does not mean an outside audit. The verifier sits in the same pod and is paid from the same monthly fee. Formal independent verification and validation of software is a stricter standard. NASA's program, citing IEEE, describes independence in three parts: technical, managerial and financial (NASA, IV&V Overview, page updated 2024-07-23). If a regulator or your board needs that standard, commission a separate reviewer alongside the retainer.

The monthly review is where the Engagement Lead and your senior stakeholders step back from the sprint and read outcome metrics next to the roadmap: capabilities running in production, the business metric each exists to move against its baseline, and how much of what runs your own team can operate. Baselines are agreed early in the engagement. For how deployments are verified, see deploy and verify AI; for why outcomes rather than uptime are monitored, see liveness versus outcome.

Decision rights at a glance

Decision	Held by
What to build next	Your product owner, advised by the Engagement Lead
How it is built: architecture, tooling, model choice	The Engagement Lead, consulting your architects
Whether a change is done and ready to promote	The verifier, against criteria agreed in advance, never the builder
Whether to promote from pilot to limited to full rollout	Your product owner, on the verifier's evidence
A change of scope or price	Your sponsor and the Engagement Lead, through change control

Can you leave, and what do you keep?

Yes, on notice. There is an initial term of typically three months, after which Your AI Team runs month to month, and a structured exit is included in the fee. The work lives in your repositories, documentation and chat from the first day; there is no NewGenApps-only environment holding it and no tooling that only we can operate. Knowledge transfer is continuous, not an exit event. On notice, a structured hand-over covers a final knowledge-transfer pass, runbook walkthroughs, access transition and a documented sign-off that your team can operate the system. It is not charged as an extra.

The test applies to any vendor: at any point, could your team operate what is in production with the documentation and access it already has? Ask who owns the repositories, what only the vendor can operate, and what leaving costs.

When is a fixed project the better choice?

When the outcome can be written down: one use case, a clear bar, a known end date. A fixed-scope project puts overrun risk on the vendor for the scope written down, and it ends with a handover. A retainer is the wrong way to buy a single deliverable, because you pay for standing capacity you may not use.

A project is often the right first step. A proof of concept shows whether an unvalidated use case is worth building on your data, an AI production build takes a validated one into production, and AI Rescue triages a stalled pilot with a real off-ramp after week one. A retainer assumes a continuing queue of AI work worth running; in our view that queue is usually visible only once a first system is live.

When is a hire the better choice?

When AI is core to what you sell, the workload is steady, and you can hire and keep senior people. A permanent hire tends to hold your context and shape your culture in a way a vendor pod cannot. The economics, and the evidence on building versus partnering, are on build vs buy for an AI team; this page does not repeat them.

Hiring is also constrained by the labor market. The World Economic Forum's Future of Jobs Report 2025 (January 2025) surveyed over 1,000 employers representing more than 14 million workers across 55 economies. In it, AI and big data top the list of fastest-growing skills for 2025-2030, and 63% of employers named skill gaps in the labor market as a major barrier to business transformation. In the same survey chart, 27% listed inability to attract talent to their own firm. These are employer expectations across all skills, not measurements of AI hiring time. Read them as context, not as a reason to avoid hiring.

The routes are not exclusive: a pod's continuous knowledge transfer lets a later in-house team take over what is running, the partner, transfer, then build sequence described on the build-vs-buy page.

How do you decide between a retainer, a project and a hire?

Ask five questions, in this order.

Can the outcome be written as one deliverable with an end date? If yes, buy a fixed project.
Is there a continuing queue of AI work whose priorities will change as you learn? If yes, a retainer fits. If not, you would pay for idle capacity.
Is AI core to what you sell, with steady work and a realistic path to hiring and keeping senior people? If yes, plan to hire, perhaps after a project or a retainer has taken the first system into production.
Can you name a product owner and a sponsor with time for sprint decisions, and give the team access to data and systems? If not, a retainer will wait on you whatever the contract says.
Can you leave? Ask for the exit terms in writing: who owns the repositories, what only the vendor can operate, and what leaving costs.

None of the three fits if the best candidate does not need AI. A rule, a report or a process change sometimes does the job, and a team that only ever answers "build it" is not advising you. If you are unsure where you stand, start with which AI engagement you need or how to choose an AI partner.

What does an AI retainer cost?

Your AI Team starts from $10,000 per month for the smallest pod. Larger pods cost more, and the tier is confirmed at scoping. The price, in US dollars, was published on the engagements page on 2026-09-29. The fee is, indicatively, a fixed monthly amount per pod tier, covering the pod's capacity and the governance described above, with no per-ticket or hourly billing. Model usage, licenses and cloud infrastructure are separate: billed at cost or paid by you directly. To compare quotes, see how much AI consulting costs.