[object Object]

What It Is

A network of Salesforce-approved engineering partners supporting ISV agent development. Partners provide hands-on engineering help — architecture, Agentforce configuration, integration, evaluation, security review preparation — to ISVs building on the platform. Engagements range from a few-day architecture review to multi-month embedded teams. Partners are billed at published rate cards, with credits expensable against the AgentExchange Builders Initiative for qualifying ISVs.

Typical engagement shapes:
  Architecture Sprint     5-10 days   Topic/Action design, eval plan, scope
  Build Acceleration      4-12 weeks  Embedded engineer(s) co-building
  Security Review Prep    2-3 weeks   Pre-flight for AgentExchange certification
  Production Hardening    2-4 weeks   Observability, alerting, runbook
  Incident Response       on demand   Live triage on production agents

Why Salesforce Created It

Agent development has specialized skills (Atlas reasoning patterns, MCP integration, Trust Layer configuration, eval design, Data 360 retrieval tuning) that small ISVs lack in-house. The partner network provides on-demand expertise without forcing the ISV to hire and onboard. It also accelerates ecosystem velocity — Salesforce wins when more agents ship, even if the ISV builds them with help.

Who Qualifies

Salesforce vets partners for technical skill, Agentforce-specific certifications (Agentforce Specialist, Data Cloud Consultant, Platform Developer II at minimum), and demonstrated agent ship history. The current network is relatively small (~30 firms in April 2026) and biased toward boutique AI consultancies and specialist Salesforce firms with agent practice areas. Salesforce expands the roster on a rolling basis; partners apply through the Partner Community portal and undergo a technical interview plus a reference build review.

When to Engage

Starting a new agent product without prior Agentforce experience on the team. Hitting technical walls in an existing agent (eval scores plateaued, Atlas planner making suspect decisions, Action callout patterns hitting governor limits). Compliance or security architecture review before AgentExchange certification submission. Production incident response when on-call engineering doesn’t yet have agent expertise. Don’t engage for generic Salesforce work like LWC builds or Apex refactors — the network is agent-specialized and priced accordingly.

How to Pick a Partner

Ask three things: how many production agents you’ve shipped on Agentforce in the last 12 months, what your typical Topic/Action ratio looks like, and who your last reference customer was. Strong partners answer concretely. Weak ones pivot to slide decks. Match vertical fit — a partner who has shipped a Health Cloud agent will save you weeks on the FHIR data plumbing a horizontal partner will discover the hard way.

Cost Considerations

Partner rates land $250–$450 per hour depending on partner tier and engineer seniority. A typical Architecture Sprint costs $25k–$60k. A Build Acceleration engagement runs $80k–$300k. Builders Initiative credits cover up to 1,000 hours of partner engineering for grant recipients, materially de-risking the cost for early-stage ISVs.

Common Failure Modes

  • Hiring a partner before scoping the problem. The first deliverable should be a written scope from your team, not theirs.
  • Treating the partner as a black box. The fastest builds happen when ISV engineers pair with partner engineers daily, not when work is “thrown over the wall.”
  • Skipping the knowledge transfer. Partner-built agents often fail in month 9 because no one on the ISV team can debug them.

What to Do This Week

If you’re an ISV building an agent and your team has shipped fewer than three production agents on Agentforce, scope a 5-day Architecture Sprint engagement and brief two qualifying partners with the same problem statement.

[object Object]
Share