Bluebirds implementation cost: Sales Cloud editions and prospecting agents

Bluebirds was a prospecting platform: it found accounts and people worth approaching, enriched them with context and drafted the first message. Salesforce completed the purchase on 13 August 2025, and the announcement was direct about where it was going: "Upon close, Salesforce plans to bring these capabilities into Sales Cloud and Agentforce, giving customers new ways to automate pre-sales work and drive productivity."

That sentence is the budget. You are not implementing Bluebirds the product. You are implementing prospecting inside Sales Cloud, with Agentforce doing the work a sales development team does at the top of the funnel. The cost is a Sales Cloud edition, an Agentforce entitlement and a services project whose hardest question is not technical: when should a machine be allowed to put a new person into your CRM?

#What you pay Salesforce for prospecting today

The Sales Cloud pricing page lists these editions as at October 2026, per user per month, in US dollars with the Australian dollar figure shown on the same page:

The page carries a short line that defines the decision: "AI can be added to Core and above." Below Core, you are buying a CRM and will need a separate tool for agent-led prospecting. At Core or Advanced, you add Agentforce for Sales, which the same page lists "From $125 USD/user/month". At Max, it is included.

In the edition comparison, Salesforce lists "Agentforce: Prospecting", "Agentforce: Lead Nurture" and "Agentforce: Account Research" as separate capabilities, several marked "Available for purchase". We could not find a Salesforce page that says, in so many words, that Agentforce: Prospecting is Bluebirds under a new name, so this guide does not claim it. What is clear is that prospecting by agent is now sold as part of Sales Cloud and Agentforce, which is exactly where the announcement said Bluebirds would go. Ask your account executive which SKU on your order form carries it.

If you choose consumption rather than per-user add-ons, the Agentforce pricing page lists Flex Credits at US$500 per 100,000 credits (AU$700) and states: "Agentforce actions are 20 Flex Credits, while Agentforce Voice actions are 30 Flex Credits." At 20 credits an action, 100,000 credits covers 5,000 standard agent actions. A prospecting agent that researches an account, checks for duplicates, drafts an email and logs a task may use four or five actions per prospect, so model your expected weekly prospect volume before choosing between per-user and consumption pricing.

Contact data is the cost that does not appear on either page. Bluebirds enriched leads from external sources. Whatever data provider your prospecting agent relies on, whether bought through AgentExchange, through a data vendor directly or already under contract, is a separate licence with its own terms on storage, re-use and refresh.

#What a prospecting implementation is made of

The work packages here are different from a normal Sales Cloud rollout because the system, not a person, is creating records.

1. Ideal customer profile and target rules. Write down which industries, sizes, regions and roles count. An agent cannot prospect against "good fit". Each rule needs a field to check it against, which often exposes Account fields that were never filled consistently.

2. Matching and duplicate rules. This is the heaviest package. Before an agent creates a Lead, it must check whether the person is already a Contact, already a Lead owned by someone else, or belongs to an Account in an active opportunity. Salesforce duplicate and matching rules handle part of this. The rest is policy: does a new contact at a customer account become a Lead, a Contact, or a task for the account owner? Every answer is a design decision and a test case.

3. Data source and enrichment. Decide what the agent may read: your own CRM, web research, a licensed data provider. Each source needs credentials, a refresh rule and a decision about which fields it may overwrite.

4. Agent design in Agentforce. Configure the prospecting agent with its Agentforce subagents and actions: research an account, find contacts, draft outreach, log activity. Each action needs an owner field and a stop condition. Instructions that say "find good leads" are not a design.

5. Email and channel setup. Outreach needs a connected sending identity, a Gmail or Outlook integration, and deliverability settings. A sending domain that suddenly emits hundreds of agent-drafted messages can damage the reputation of the domain your account executives also use.

6. Consent and compliance. In Australia the Spam Act 2003 requires consent, sender identification and a working unsubscribe for commercial electronic messages. Your design needs a consent field, a suppression list the agent checks, and an unsubscribe path that writes back to Salesforce. Other jurisdictions add their own rules.

7. Routing, review and measurement. Decide whether a person approves each draft before it is sent, at least for the first weeks. Build the reports that show prospects created, messages sent, replies and meetings, so the business can see whether the agent earns its credits.

8. Training and change. Sales development representatives move from writing first emails to reviewing them and working replies. That is a role change and needs to be treated as one.

#What drives the effort up or down

The state of your Account and Contact data. Clean, deduplicated accounts with consistent industry and size fields make targeting quick. A CRM with three versions of every major customer makes matching slow and risky, and a data clean-up has to come first.

How many teams prospect. One sales development team with one territory model is simple. Several regions, partner channels or product lines that each claim the same accounts need ownership rules before an agent can act.

Whether a person reviews every draft. Review keeps risk low and makes the first phase cheaper to approve, but it limits throughput. Moving to unattended sending later is a second, smaller project with its own testing.

Data provider integration. A provider with a native Salesforce app is configuration. A provider that only offers a file or an API means integration work and storage decisions.

Edition upgrade. Moving from Pro Suite to Core is a licence change with its own migration effort, because features, limits and security settings differ. If the prospecting project triggers the upgrade, the upgrade belongs in the quote.

#Working the licence maths before the quote arrives

You can do most of the licence arithmetic yourself from the public pages, and it is worth doing before any partner meeting, because it tells you which pricing model to ask about.

Take a team of ten sales development representatives on Core. The edition is US$195 per user per month billed annually. Adding Agentforce for Sales per user starts at US$125 per user per month, so the list starting point for that team is US$320 per user per month before any discount, or the Max edition at US$550 if the wider features in Max are wanted anyway. Those are list figures and starting points. Your order form will differ, and the "From" on the add-on means the final figure depends on what is bundled.

Now take the consumption route for the same team. If the agent works 2,000 prospects a month and uses five actions per prospect, that is 10,000 actions, or 200,000 Flex Credits at 20 credits an action, which is US$1,000 a month at the published rate of US$500 per 100,000. The comparison is not exact, because per-user Agentforce for Sales brings unmetered employee use and other features, while consumption pricing pays only for what the agent does. The point is to arrive at the conversation knowing roughly where the line falls for your volume, rather than accepting the first model you are offered.

Two caveats keep this honest. The action count per prospect is a design choice, so ask the partner for theirs in writing. And prospecting volume is rarely flat: a campaign month may be several times a quiet month, which matters more under consumption pricing than under per-user licences.

#Risks that are particular to agent prospecting

Most Sales Cloud risks are about adoption. Prospecting by agent adds three of its own. The first is reputational: a poorly instructed agent can send a confident, wrong message to a senior buyer at a target account, and that message carries your brand. The second is ownership: an agent that does not respect account ownership will create friction with account executives within days. The third is regulatory, covered above, and it is the one that can cost money directly. Each of these should appear in the partner's risk register with a named control, not a general promise of care.

#Getting quotes you can compare

Give every bidder the same facts: your current edition, user counts by role, how many prospects you want approached per month, the regions you sell into, your data provider, and whether a person must approve each message.

Then ask three questions that separate prepared partners from the rest. First, show us the matching rule: what happens when the agent finds someone who is already a Contact at an open opportunity? Second, show us the consent check: which field, which suppression list, which unsubscribe path? Third, how many agent actions per prospect does your design use, and what does that cost at the published Flex Credit rate?

Ask for the licence quote from Salesforce separately. Ask whether per-user Agentforce for Sales or Flex Credits is cheaper for your volume, and get both priced. Ask the partner for testing evidence on duplicate handling, not just a demonstration of a well-written email.

#Costs that are commonly left out

• Edition uplift. Agentforce for Sales needs Core or above. If you are on Pro Suite, the upgrade is part of the cost.
• Licence ramp overlap. If you are replacing a separate prospecting tool, you may pay for both during a parallel run.
• Contact data licences and their renewal, plus any storage growth from new Leads. Sales Cloud editions include set data storage, and a busy prospecting agent fills it.
• Flex Credits beyond the included pool. Max includes 2.75M Flex Credits per org per year. Other editions consume purchased credits for metered use.
• Email deliverability work, including domain warm-up and monitoring.
• Legal review of outreach templates and consent handling.
• Sales manager time to review drafts in the first weeks and tune the instructions.
• Sandbox testing with realistic data so duplicate rules can be proven before the agent touches production.

#Where the other Bluebirds questions live

The licence question on its own is covered on Bluebirds licence cost. How prospecting should sit in Sales Cloud, including sources and the rule for creating records, is on Bluebirds prospecting. The acquisition and its timeline are on what happened to Bluebirds, and the connector and field detail is on integrating Bluebirds with Salesforce.

If you were a Bluebirds customer before the acquisition, should I migrate from Bluebirds covers the choices. When you are ready to brief a delivery team, hire a Bluebirds Salesforce partner lists what to test them on.

For a budget holder, the summary is short. Confirm your edition is Core or above, price Agentforce for Sales both per user and as Flex Credits, add the data provider and deliverability lines, and pay properly for the matching rules. A prospecting agent that creates duplicates is more expensive than no agent at all, because every duplicate costs a salesperson time and costs the customer some patience.