Qualified implementation cost: Piper plans, quotes and the Salesforce work behind them

Qualified is the newest sales-side acquisition in this set. Salesforce's newsroom confirms: "Salesforce completed its acquisition of Qualified on April 1, 2026." The product most buyers mean when they say Qualified is Piper, an AI agent that works inbound visitors on your website and in email, qualifies them and books meetings. Salesforce's announcement said Qualified would strengthen its Agentforce Sales and Agentforce Marketing products. As at October 2026, Qualified still sells Piper from its own site, on its own plans, and that is what this guide prices.

An AI SDR looks like a simple purchase: add a script to the website, switch the agent on, watch meetings arrive. In practice the agent is only as good as the routing, data and rules behind it, and almost all of those live in Salesforce. That is where the implementation cost sits.

#What you pay Qualified

There are no public prices. As at October 2026, the Qualified pricing page opens with "Hire Piper the AI SDR Agent to scale inbound pipeline generation." and then lists three plans, each with a "Contact us" button. So Qualified is quote-only, and the useful work is understanding what the quote is sized on.

All plans include the AI SDR Agent Studio, account segmentation with enrichment, integrations with Salesforce CRM and more than 20 other go-to-market systems, reporting inside both Qualified and Salesforce, and routing for conversations, emails and meetings.

Read that table as a list of pricing inputs. The first is monthly web sessions, which means your website traffic. The second is monthly active email contacts, the number of people Piper is working by email in a month. The third is the number of agent profiles, which matters if different brands, regions or product lines need different agents. Bring real numbers for each. Your web analytics will give you sessions by month, including the seasonal peaks that might push you over a plan limit. Your marketing automation platform will tell you how many inbound leads you would want Piper to follow up.

If Salesforce rather than Qualified presents the offer, perhaps alongside Agentforce or Marketing Cloud Next, ask how the Salesforce line maps to the Qualified plans and limits above. A bundle is only comparable if you can see the session and contact allowances it includes.

#Where Enterprise matters for the implementation

One detail on the pricing page affects the implementation as much as the licence. A Salesforce sandbox, agent hand-off, and MCP and API access are listed as Enterprise features. On Premier, then, you should ask Qualified directly how you test changes to routing and qualification before they reach production, because the sandbox connection is not listed at that tier. You should also ask how a live conversation passes to a human seller when hand-off is not listed.

This is worth settling before you choose a plan. A Premier quote may look attractive until you realise that every change to routing has to be tested in production, with real visitors, or that a hot prospect cannot be passed to a person mid-conversation. Sometimes Premier is the right answer for a pilot. Make that a decision, not a surprise.

API and MCP access, also listed from Enterprise, matter for a different reason. If you want Piper's conversations, qualification results or meetings to flow into systems beyond the standard Salesforce CRM integration, such as a data warehouse, a product analytics tool or your own agents, that access is how it happens. If your plan does not include it, any custom integration a partner proposes may not be possible as described. Ask the partner to name, for each integration in their quote, which Qualified feature it relies on and which plan includes that feature. It is a five-minute check that prevents an expensive change of plan halfway through the build.

#What a Qualified implementation is made of

The Salesforce connection and routing packages are where most of the effort goes. Piper has to decide, in seconds, whether a visitor belongs to an existing account, who owns that account, and whether the right next step is a meeting with that owner, a meeting with an SDR, or nothing. If your org has duplicate Accounts, unclear ownership rules or a lead assignment process with layers of exceptions, the agent will reproduce those problems at speed. Fixing them is often the most valuable part of the project, and it is Salesforce work, not Qualified configuration.

Qualification design is the other hard part, and it is mostly a conversation between people. Marketing wants every engaged visitor to count. Sales wants only the ones ready to talk. Piper needs a written answer: which company sizes, industries, regions and stated needs justify a meeting, which justify a follow-up email, and which should be politely sent to self-service content. Without that answer, the agent books meetings your reps will not take, and the project is judged a failure for reasons that have nothing to do with the software.

#A scoping example

Take a hypothetical B2B software company selling in Australia and New Zealand, with one marketing website, about 120,000 sessions in a normal month and peaks near 200,000 during campaigns. It has six SDRs and fifteen account executives, named accounts for its top 300 customers, and round-robin assignment for everyone else. Inbound demo requests go to Salesforce as Leads through a web form, and an SDR calls them back, usually the next day.

On capacity alone, that traffic sits inside the Premier session limit even at its peaks. But the company wants Piper to pass hot conversations to an SDR during business hours and to test routing changes before they go live, and both of those are listed as Enterprise features. So the plan question is not really about traffic. It is about how the company wants to work.

The implementation scope follows from the routing. Named accounts must match reliably, which means de-duplicating Accounts and agreeing a matching rule on company domain. Round-robin has to move from the web form process to Piper's meeting booking, with calendars connected for six SDRs and fifteen executives. Qualification rules need sign-off from the head of sales and the head of marketing. And the existing next-day callback becomes the fallback for visitors who leave without booking. None of that is unusual, but every piece is specific to this company, and it is where the services quote should spend its time.

#Measuring whether it paid for itself

Because Qualified is quote-only, the business case has to come from your own numbers. Before go-live, record the baseline: inbound demo requests per month, the time from request to first contact, the share of requests that become a meeting, and the share of meetings that become qualified pipeline in Salesforce. Write the counts down as numbers, not impressions.

After go-live, measure the same things in the same way, using Salesforce campaign and opportunity data rather than the agent's own dashboard alone. Piper's reporting is useful for conversation quality, but the pipeline that sales accepts is what pays for the licence. If meetings rise and accepted pipeline does not, the qualification rules need work, not the software. If both rise, you have the evidence you need at renewal, when the session and contact limits will be renegotiated.

#What pushes the effort up or down

Effort rises with the number of websites and brands, because each needs deployment, targeting and often its own agent behaviour, which can push you to Ultimate for multiple agent profiles. It rises with territory complexity, named-account models and partner channels, because routing logic multiplies. It rises if you sell in regulated industries where the agent must not discuss certain topics, because those boundaries need writing and testing. Multiple languages are supported, but each language still needs its answers reviewed by someone who speaks it.

Effort falls when the Salesforce org already has clean Accounts, clear ownership and a lead process people trust, when one person can sign off the qualification rules, and when the SDR team is ready to work alongside the agent rather than compete with it.

#Getting quotes you can compare

For the licence, give Qualified your monthly web sessions for the last twelve months, the number of inbound contacts you would want worked by email each month, the number of brands or regions that need a distinct agent, and the features you need, particularly hand-off, API access and the sandbox. Ask for the plan, the annual price, what happens if traffic exceeds the plan limit, and the contract length.

For the services, give each partner the same description of your routing rules, your territories, your calendar platform and your website stack. Ask each quote to list the routing scenarios it will build and test, the qualification rules it assumes, who writes the agent's knowledge and guardrails, and how the hand-off to sellers will work on the plan you are buying. Ask whether Salesforce data clean-up is included or assumed done. A quote that assumes clean data in an org that does not have it is not cheaper; it simply moves the cost to week four.

#Costs that sit outside the first quote

1. Salesforce clean-up. Duplicate Accounts and unclear ownership must be fixed for routing to work. That is often the largest hidden item.
2. A higher plan than expected. Traffic peaks, a new website or a second brand can push you past session or profile limits.
3. Testing without a sandbox. If you choose Premier, factor in the time and care needed to test routing changes safely.
4. Email set-up. Sending domain authentication, warm-up and monitoring take time, and poor email reputation affects every channel.
5. Content for the agent. Someone must write and maintain the answers Piper gives about products, pricing and next steps.
6. SDR and seller time. People must review conversations, take hand-offs and give feedback on meeting quality, especially in the first months.
7. Privacy and consent. Chat transcripts and enrichment data are personal information. Check your privacy notice and consent handling under the Privacy Act, and confirm where conversation data is stored.
8. Overlap with existing tools. If Piper replaces a chat tool, a scheduling tool or a sales engagement platform, budget for the overlap until cutover.

#Where to go next

For the product picture, read Qualified and agentic marketing and what happened to Qualified. The licence detail is in Qualified licence cost. The data and routing connections are covered in integrating Qualified with Salesforce, and if you are weighing whether to move from another tool or away from Qualified, should I migrate from Qualified sets out the trade-offs. When you are ready to compare partners, hiring a Qualified Salesforce partner lists the questions to ask. If Piper will sit alongside your marketing automation, our Marketing Cloud Next team can help line up the two.

The practical summary: the quote is sized on traffic and contacts, so bring real numbers. The implementation is sized on your Salesforce routing and your qualification rules, so fix and write those down before the agent goes live.