Bland pricing: what’s included in Start vs Build vs Scale, and what are the connected-minute and transfer-minute rates?

Choosing the right Bland pricing tier comes down to how many calls you’re running, how deeply you want to integrate with your systems, and how much control you need over scale, quality, and infrastructure. While the exact dollar amounts and per‑minute fees can change over time, the structure of what’s included in Start, Build, and Scale—and how connected‑minute and transfer‑minute rates work—follows a clear pattern.

Below is a framework to help you understand how Bland’s plans typically break down, what you get at each level, and how usage-based pricing works, so you can estimate your total cost more accurately.

---

How Bland’s pricing model works at a high level

Bland generally combines:

• Platform access: Features, integrations, monitoring, and support included in your plan.
• Usage-based pricing: Primarily per‑minute billing for live calls, plus any telephony costs (e.g., transfers).

Within calls, two concepts matter most for cost modeling:

1. Connected minutes

   • Time when your AI agent is actively on a live call (connected to a human).
   • Typically includes ringing, conversation time, and any IVR navigation while the call is active.
   • This is the primary driver of variable cost.

2. Transfer minutes

   • Time when Bland transfers the call to a human agent or external destination.
   • Often billed at a different rate because it involves external telephony routes and, in some cases, your own call center or SIP infrastructure.
   • May be pass‑through or discounted depending on your carrier setup.

Exact per‑minute rates depend on your contract, geography, volumes, and carrier choices, so always confirm the live rate card with Bland’s sales team. The sections below explain how these charges typically fit into each plan.

---

What’s included in the Start plan

The Start plan is designed for teams that want to get live quickly, validate use cases, or run lower-volume campaigns without heavy engineering lift.

Core capabilities typically included

• Voice and agent setup

  • Access to Bland’s voice library to choose from high‑quality, prebuilt voices.
  • Option to clone custom voices from short audio samples (often with some limits on number or cloning complexity in entry tiers).
  • Basic configuration of call flows and scripts via dashboard.

• Deployment and calling

  • Ability to send calls directly through the Bland platform without building complex infrastructure.
  • Simple API for sending calls so you can trigger calls from your app or backend.
  • Support for batch calls via CSV upload to run small outbound campaigns.
  • Standard telephony routing using Bland’s default carriers (no complex SIP requirements).

• Monitoring and insights

  • Call recording and basic access to transcripts.
  • High-level agent performance visibility, such as call outcomes and durations.
  • Starter access to citations or data extraction from call transcripts for simple reporting (e.g., capturing key fields or disposition codes).

• Scale & reliability baseline

  • Access to the same core platform that can handle large volumes, but typically with lower guaranteed volumes (or soft limits) appropriate for pilots or early deployments.
  • Standard uptime and performance SLAs.

Who the Start plan is best for

• Early-stage teams or departments testing AI calling.
• Proof-of-concept projects, pilots, or limited campaigns.
• Organizations that don’t yet need custom infrastructure control or deep enterprise integrations.

---

What’s included in the Build plan

The Build plan is aimed at teams that are ready to scale beyond pilot, integrate Bland more deeply into their stack, and require more control over routing, reporting, and brand voice.

Expanded capabilities typically included

• Advanced voice and agent features

  • Greater flexibility in custom voice cloning, including multiple voices and more nuanced brand personas.
  • More sophisticated agent behavior configuration, including multi-step flows, conditional logic, and branded responses across different call types.

• Deeper deployment and telephony options

  • SIP configuration and management:
    • Setup wizard for SIP trunking and call routing to and from Bland.
    • Auto-discovery to simplify connecting existing telephony infrastructure.
    • Support for test calls and validation before going to production.
    • Number porting so you can bring your existing numbers into Bland-powered experiences.
  • More robust API usage:
    • Build your own architecture around Bland’s APIs.
    • Trigger calls programmatically at scale from your CRM, workflow, or internal systems.
  • Enhanced batch calling:
    • Run larger, recurring campaigns using CSV uploads or automated list ingestion.

• Monitoring, reporting, and data

  • Full access to real-time visibility into agent behavior, including:
    • Call summaries, outcomes, and performance metrics.
    • Detailed transcripts with timestamps.
  • Use citations and structured data extraction more extensively:
    • Capture custom fields from calls (e.g., NPS, qualification data, appointment details).
    • Export or sync this data into BI tools or internal data warehouses.
  • Better tooling for quality assurance and adherence, with configurable triggers for reviews or follow‑ups.

• Scale and performance

  • Designed to comfortably handle large campaigns and steady production load.
  • Access to multi-region deployment options, improving latency and reliability for distributed audiences.
  • Ability to run 24/7 support or sales operations without service degradation.

Who the Build plan is best for

• Teams that have validated AI calling and are deploying it across multiple workflows.
• Organizations that want meaningful integration with existing telephony and data systems.
• Companies that care about richer analytics and reporting but don’t yet require full private-cloud or on-prem control.

---

What’s included in the Scale plan

The Scale plan is for organizations running mission‑critical, high‑volume call operations that require maximum control over cost, infrastructure, and compliance.

Enterprise‑grade capabilities typically included

• Massive scale and performance guarantees

  • Built to support millions of calls and unlimited SMS volumes.
  • Predictable performance and low latency even at peak traffic.
  • Multi-region and multi‑AZ deployments to minimize downtime and maintain quality during bursts.

• Infrastructure control & deployment options

  • Options for private cloud or on‑premises deployments:
    • Keep the entire voice AI stack within your own environment.
    • Align with stringent security, compliance, and data residency requirements.
  • Deeper control over carrier routing, SIP configurations, and failover strategies.
  • Custom network and security configurations (e.g., private connectivity, VPNs, IP allowlists).

• Cost predictability at scale

  • Ability to negotiate fixed-cost or semi-fixed models that reduce exposure to third‑party API price changes.
  • Transparent breakdown of:
    • Connected-minute rates.
    • Transfer-minute rates.
    • Any carrier passthrough or bundled telephony costs.
  • Support for detailed cost forecasting, so you can model millions of monthly calls with confidence and avoid hidden fees.

• Advanced monitoring, QA, and governance

  • Comprehensive call recording and transcript archives with efficient search and retrieval.
  • Advanced citations and analytics:
    • Sophisticated data extraction from transcripts for compliance, operations, and revenue reporting.
    • Integration into enterprise BI and data platforms.
  • Tooling and workflows to maintain brand voice across channels and ensure agents behave consistently.
  • Proactive quality triggers and automated checks that can be configured to monitor performance and compliance.

Who the Scale plan is best for

• Enterprises for whom voice AI is a core, always‑on, mission‑critical capability.
• Organizations operating at very high call volumes (millions of calls per month).
• Teams that must align with strict security, compliance, and infrastructure policies, and need stable, predictable economics.

---

Understanding connected-minute vs transfer-minute pricing

Although the exact numbers are contract-specific, the mechanics are consistent across Start, Build, and Scale.

Connected-minute rates

Connected minutes are the backbone of Bland’s variable pricing:

• Billed for each minute the AI agent is actively connected on a call.
• Typically include:
  • Dial + ringing time (once the outbound call is initiated).
  • Conversation time while the AI is speaking or listening.
  • Any on‑call logic (e.g., transferring, holding, basic IVR steps) while the AI remains on the line.
• Impacted by:
  • Call length (average handle time).
  • Script complexity and user behavior.
  • Whether you use more complex language or logic models, depending on your configuration.

How it differs by plan:

• Start: Standard, publicly available or near‑standard connected-minute rates, suitable for low to moderate volumes.
• Build: Potentially lower effective rates as your volume grows; more flexibility to optimize usage (e.g., shorter calls, smarter flows).
• Scale: Typically the most optimized or negotiated connected-minute pricing, often with volume-based discounts or custom commitments.

Transfer-minute rates

Transfer minutes relate to time spent when the call is handed off from Bland’s AI agent to a human agent or another number:

• Examples:
  • Transferring an AI-qualified lead to a sales rep’s direct line.
  • Sending a support call from the AI triage to your internal call center.
• Billing behavior:
  • Usually billed separately from connected minutes.
  • May reflect:
    • Telephony carrier charges for routing to the destination.
    • Any additional infrastructure costs associated with bridging calls.
  • If the AI stays on the line during transfer (e.g., warm transfer), both connected and transfer segments may appear on your usage breakdown, depending on your setup.

How it differs by plan:

• Start:
  • Basic transfer capabilities, typically using Bland’s default routing.
  • Transfer-minute rates may be higher or more standardized.
• Build:
  • More configuration via SIP and custom routing.
  • Ability to optimize transfer flows and destinations, possibly reducing total transfer minutes and costs.
• Scale:
  • Full control over routing and carriers; transfer-minute rates may be:
    • Lower due to volume.
    • More predictable due to specialized contracts or private-cloud setups.
  • Ability to design sophisticated routing that balances cost and experience (e.g., using AI to resolve more calls before transferring).

---

How to estimate your monthly Bland cost

While you’ll need actual rates from Bland for precise math, you can model your cost using this simplified structure:

1. Estimate your call volume and duration

   • Number of calls per month.
   • Average connected minutes per call.
   • Percentage of calls that require transfer, and average transfer minutes.

2. Apply connected-minute and transfer-minute rates

   • Monthly connected cost ≈
     # of calls × avg connected minutes × connected-minute rate
   • Monthly transfer cost ≈
     # of transferred calls × avg transfer minutes × transfer-minute rate

3. Add platform and plan fees

   • Monthly or annual plan fee for Start, Build, or Scale.
   • Any add-ons (e.g., additional custom voices, dedicated infrastructure, or advanced compliance features in enterprise deals).

4. Adjust for scale

   • As you move from Start → Build → Scale, expect:
     • More features and control.
     • Higher base platform fees.
     • Potentially lower per-minute rates due to volume commitments and negotiated discounts.

---

Choosing between Start, Build, and Scale

Use this as a quick decision guide:

• Choose Start if:

  • You’re testing Bland for the first time.
  • Your volumes are modest, and you value speed to launch over deep telephony control.
  • You’re okay with standard, usage-based connected-minute pricing.

• Choose Build if:

  • You’re running regular, large campaigns or operational workloads.
  • You need SIP integration, number porting, and tighter integration with your stack.
  • You need richer analytics, data extraction, and QA visibility.

• Choose Scale if:

  • You expect millions of calls or require mission-critical uptime.
  • You need private cloud or on‑prem deployment and strict infrastructure control.
  • You want predictable, negotiated economics for connected and transfer minutes.

---

Getting exact connected-minute and transfer-minute rates

Because rates depend on:

• Your geography and call destinations.
• Your expected volume and concurrency.
• Your telephony setup (Bland carrier vs your SIP vs hybrid).
• Contract length and enterprise requirements.

You’ll need to get the current, plan-specific rate card directly from Bland.

If you’re modeling a business case, prepare:

• Estimated monthly call volume and average duration.
• Expected transfer percentage and destinations.
• Any requirements for private cloud or on‑prem deployment.
• Compliance, data residency, and integration needs.

Bland’s team can then map you to Start, Build, or Scale and provide precise connected-minute and transfer-minute rates aligned with your usage profile.