ibl.ai Agentic AI Blog

Insights on building and deploying agentic AI systems. Our blog covers AI agent architectures, LLM infrastructure, MCP servers, enterprise deployment strategies, and real-world implementation guides. Whether you are a developer building AI agents, a CTO evaluating agentic platforms, or a technical leader driving AI adoption, you will find practical guidance here.

Topics We Cover

Featured Research and Reports

We analyze key research from leading institutions and labs including Google DeepMind, Anthropic, OpenAI, Meta AI, McKinsey, and the World Economic Forum. Our content includes detailed analysis of reports on AI agents, foundation models, and enterprise AI strategy.

For Technical Leaders

CTOs, engineering leads, and AI architects turn to our blog for guidance on agent orchestration, model evaluation, infrastructure planning, and building production-ready AI systems. We provide frameworks for responsible AI deployment that balance capability with safety and reliability.

Back to Blog

105 Forward-Deployed Roles, 5 Sales Roles: AI's Last Mile

Mikel AmigotSeptember 21, 2026
Premium

On September 21, 2026 the job boards of OpenAI, Anthropic and Palantir list 105 forward-deployed engineering roles against 5 in sales development β€” Palantir posts 77 while carrying about 70 salespeople.

The Short Answer

Palantir's Alex Karp told CNBC's Squawk Box on July 1, 2026 that "something has gone completely wrong" with how AI is sold β€” not that something terrible happened to AI sales. The hiring data agrees: on September 21, 2026 OpenAI, Anthropic and Palantir together list 105 forward-deployed engineering roles against 5 sales-development roles. With ibl.ai you own all the code and the data, and engineers deploy it inside your perimeter.

The quote is real. The framing that usually travels with it is not quite what he said, and the correction changes what the data point is evidence of.

What did Palantir's Alex Karp actually say about how AI is sold, and when?

He said it on CNBC's Squawk Box on Wednesday, July 1, 2026 β€” roughly twelve weeks before this post, not this week β€” and the sentence was "something has gone completely wrong" with how AI is sold.

His objection was to the commercial model, not to sales headcount. Reporting on the appearance quotes him voicing the enterprise buyer's fear directly: "I'm going to chillax and waste my time with tokens, I'm going to get no value, and they're going to get my IP."

The argument underneath it is that durable profit sits at the compute layer and the application layer, and that renting cognition by the token in between leaves the customer paying to expose its own advantage.

Karp is not a neutral witness here. He runs a company that sells the application layer, and the claim is convenient for him.

That is a reason to check the argument against evidence he does not control, which is what the hiring boards provide.

How many forward-deployed engineers are OpenAI, Anthropic and Palantir hiring compared with salespeople?

On September 21, 2026, reading the three companies' own public job boards on the same day, the ratio is 105 to 5.

Company (board read 21 Sep 2026) Open roles Forward-deployed Sales development
OpenAI 815 21 3
Anthropic 616 7 2
Palantir 312 77 0

Palantir's board is the extreme case. Of 312 open roles, 77 carry "forward deployed" in the title, and exactly one posting has the word "Sales" in its title at all.

OpenAI's board lists forward-deployed engineers for Tokyo, Sydney, Singapore, Seoul, Madrid and Washington, DC, and separately for healthcare, legal, financial services and government.

Anthropic's board lists forward-deployed engineers in Munich, London, Paris and the US, two engineering-manager roles for the function, and a pre-sales program lead attached to it. Its sales-development count of 2 above comes from counting SDR and BDR titles.

One correction: the $350,000 figure traces to a real OpenAI posting, Head of North America Sales Development, San Francisco, advertised at $335K–$350K on 28 March 2026 and since closed. It is a closed requisition, not a disclosed hire, so it is not counted in the table above.

Why does Palantir sell more with 70 salespeople than most companies do with 7,000?

Because the deployment work is the sale, and Palantir has said so in plain terms on an earnings call.

On the Q1 2026 call, Karp described the sales organisation this way: "They buy our product despite the fact we have 70 salespeople. A normal company of our size would have 7,000. Only seven of our salespeople actually even really sell."

The revenue those seventy people sit behind is not small. Palantir's Q2 2026 results were $1.94 billion, up 93% year over year, with US commercial revenue up 149% and full-year guidance of $8.15–8.16 billion.

Divide the low end of that guidance by seventy and you get roughly $116 million of annual revenue per salesperson. That arithmetic is ours, from those two published figures, and it is a ratio no conventional enterprise sales motion produces.

What it describes is not sales efficiency. It is a company where the engineers in the customer's building are the go-to-market, and the sales team exists to paper what they have already proven.

Is forward-deployed engineering a real hiring category or a job-title fashion?

It is a real category, and the growth rate is the evidence.

Lightcast data shared with Fortune on September 3, 2026 by Dice president Paul Farnsworth put postings for forward-deployed engineers up more than 1,000% between January and August 2026 against the same period in 2025, and more than 4,600% against 2023.

The comparison that matters is the base rate. Tech hiring overall grew 13% year over year in the same window.

The pay follows. Median advertised salary for the role is above $188,000, against roughly $145,000 for a software engineer, and some Anthropic forward-deployed roles reach $400,000. OpenAI's San Francisco posting for the role lists a base range of $185,000 to $325,000.

Companies do not pay a 30% premium over a software engineer for a title. They pay it because the model does not become revenue until someone gets it working against real systems, real identity and real data policy.

What does a forward-deployed engagement have to deliver that an API key cannot?

Access to a model, and the work that turns access into a system your organisation can run.

An API key gives you inference. It does not connect your HRIS, LMS, CRM, ERP, identity provider and document stores, map which fields a given role may see, or leave an audit trail an examiner will accept.

It also does not tell you what happens when the vendor changes terms. This is the same distinction that separates sovereign deployment from sovereign ownership: running inside your jurisdiction on someone else's platform is not the same as holding the stack.

And it is why pilots stall. Campuses and enterprises get stuck in endless proof-of-concept cycles precisely when the demo works and the integration never ships.

The last mile is where the ownership question gets decided, because whoever writes the integration decides who holds it afterwards.

How does ibl.ai ship forward-deployed engineering rather than API access?

By sending engineers into your environment and leaving the code behind when they go.

With ibl.ai you own all the code and the data.

You self-host the entire platform with full source code, run it model-agnostic across any LLM and switch whenever a better or cheaper one appears, pay by usage with no per-seat pricing, and deploy anywhere β€” your own cloud, on-premise, GovCloud, or a fully air-gapped network.

Forward-Deployed Engineering is a named service, not a bundled extra. ibl.ai engineers embed with your team and build Model Context Protocol servers for each system in your stack β€” HRIS, LMS, CRM, ERP, identity, storage β€” with field-level permissions, PII masking and audit logging enforced beneath the model.

The deliverables list is the point: MCP server source code, Terraform and Kubernetes manifests, policy configs, contract tests and evaluation harnesses, all yours to run and extend.

AI Transformation engagements work the same way β€” workflows analysed, knowledge bases built, agents deployed on your infrastructure, your team operating everything independently at handover.

The commercial shape matches. Engagements are one-time rather than subscriptions, engineering hours scale with scope rather than with headcount, and full codebase ownership is quoted to your requirements.

More than 1.6 million users across 400+ organizations run the platform this way, including NVIDIA, MIT and Syracuse University.

ibl.ai is family-owned and operated from New York, NY.

Related reading: Palantir and Nebius: sovereign deployment vs ownership β€” the same ownership test applied to infrastructure rather than to the go-to-market.

Sources: the July 1, 2026 Squawk Box remarks and the "tokens… my IP" quote from Yahoo Finance and its companion report, with CNBC's own video page fixing the date; the "70 salespeople" quote from Palantir's Q1 2026 earnings call as reported by Yahoo Finance; the Q2 2026 revenue, growth and guidance figures from Yahoo Finance's earnings report; the Lightcast posting-growth and salary figures from Fortune, September 3, 2026; the role counts and the $185,000–$325,000 range read on September 21, 2026 from OpenAI's job board, Anthropic's job board and Palantir's job board; the closed Head of North America Sales Development posting and its $335K–$350K range from its listing.

Why does owning the AI stack matter?

ibl.ai is the agentic AI platform where you own all the code and the data. You self-host the entire stack inside your own perimeter, run it model-agnostic across any LLM and switch anytime, and pay by usage with no per-seat pricing β€” so you can deploy anywhere: your cloud, on-premise, GovCloud, or fully air-gapped.

  • You own all the code and the data

    Full source code under a perpetual license, running on your infrastructure. Not API access to someone else's platform β€” the stack itself is yours.

  • Model-agnostic

    Run any LLM β€” Claude, GPT, Gemini, Llama, Command, or your own fine-tune β€” and switch providers without rewriting the platform.

  • No per-seat pricing

    Usage-based billing against a budget cap you set. Cost tracks what your organization actually uses, not how many people you employ.

  • Deploy anywhere

    Your cloud, your VPC, on-premise, GovCloud, or a fully air-gapped network with no outbound connectivity.

1.6M+ users across 400+ organizations run the platform this way, including NVIDIA, MIT, and Syracuse University.

ibl.ai is family-owned and operated from New York, NY β€” a U.S.-headquartered, domestically-owned long-term partner, not a vendor that sells licenses and moves on.

See the ibl.ai AI Operating System in Action

Discover how leading universities and organizations are transforming education with the ibl.ai AI Operating System. Explore real-world implementations from Harvard, MIT, Stanford, and users from 400+ institutions worldwide.

View Case Studies
Work with our team

Pilots, deployment, and full ownership

Most enterprise engagements are one-time, not subscriptions. You integrate ibl.ai with your own data, deploy it on your own infrastructure, and the engineering hours scale with the work β€” so the price tracks the scope, not your headcount.

Start here

Pilot

from $15K

fixed scope Β· fixed timeline

A time-boxed proof of value on your real data β€” not a slide deck.

Best for: Teams that want to see ibl.ai working before committing.

  • Deployed on your infrastructure or our cloud
  • 1–2 production agents wired to a slice of your data
  • One integration (LMS / SIS / SSO / data source)
  • Weekly working sessions with our engineers
  • Pilot fee credits toward a full engagement
Scope a pilot
Most common

Integration & Deployment

$25K – $80K

one-time Β· not a subscription

Full deployment integrated with your data and systems. Engineering hours scale with scope.

Best for: Organizations rolling ibl.ai out across a department, campus, or business unit.

  • Platform deployed in your VPC, on-prem, or air-gapped
  • Integrated with your data + identity (SSO / SAML)
  • Multiple custom agents built to your workflows
  • Engineering hours proportional to scope
  • You own the data Β· run any LLM you choose
Plan a deployment
Full ownership

Codebase Transfer + Custom AI Engineering

Custom quote

perpetual license Β· you own the stack

We transfer the full source code. You own and self-host the entire platform β€” outright.

Best for: Organizations and enterprises that benefit from perpetual ownership and sovereignty.

  • Complete source-code transfer + perpetual license
  • Dedicated AI engineering team on your roadmap
  • Custom agents, models, and integrations to spec
  • Air-gapped capable Β· zero vendor lock-in
  • Family-owned, New York–based long-term partner
Talk about ownership
You own the code and data Run any LLM β€” Claude, GPT, Gemini, Llama Family-owned & operated from New York, NY