Cost the team. Resolve the operating details. Keep assumptions visible.

Use your own internal hiring assumptions, then work through the decisions that belong in the written order. The calculator does not treat the two models as equivalent and the checklist does not promise a launch date, replacement time or commercial outcome.

Published Alba cost inputs

3 caller seats: $6,018 a month plus $2,500 setup once; $74,716 across the first twelve months.
4 caller seats: $8,024 a month plus $3,000 setup once; $99,288 across the first twelve months.
5 caller seats: $10,030 a month plus $3,500 setup once; $123,860 across the first twelve months.

Input-based cost model

The interactive calculator asks the buyer for salary, benefits, tools and data, management allocation, and recruiting and onboarding. It preloads no salary benchmark and forecasts no result.

This is a cost model, not a claim that an internal SDR and an Alba caller have equivalent skills, scope, capacity or output.
It does not forecast meetings, pipeline, revenue, return or productivity. Changing the inputs changes only the arithmetic.
The Alba column uses the published standard Growth configuration: standard caller, parallel dialer and Budget data for each seat, plus the published setup fee.
The internal column includes only the five inputs shown. Add any taxes, facilities, legal, finance, sales leadership, CRM, turnover or other costs that belong in your own model.
The Order Confirmation, Services Agreement and selected billing cadence govern an actual Alba order. This planning tool is not a quote or service commitment.

Commercial scope

Put the exact configuration and governing documents in one written order record.

Seat count: Joint: Record whether the order covers three, four or five caller seats and whether seats launch together or in phases.
Caller and data tiers: Joint: Identify standard or experienced callers, Budget or Premium data, and every optional product line.
Billing and order documents: Joint: Confirm recurring cadence, setup fee, billing date, taxes, Order Confirmation, Services Agreement and any addendum.
Included work and exclusions: Joint: List the channels, markets, hours, handoff tasks and anything that is outside the engagement.

Roles and launch dependencies

A launch date is confirmed in writing after the inputs below are settled. This checklist does not create a blanket launch time.

Named owners: Joint: Name the Alba delivery owner and the customer owner with authority to approve scope, data, script and changes.
Offer and claims: Customer: Customer confirms the offer, commercial terms and substantiation for every claim callers may make.
Written ICP and exclusions: Customer: Customer approves target criteria, disqualifiers, named-account exclusions and territory rules.
Approved script: Joint: Alba develops the script and the customer approves the final version in writing before use.
Data source and contact rules: Joint: Identify the source, the party responsible for lawful use, and any required registry scrub before records are transferred or dialled.
Suppression instructions: Joint: Customer supplies current written do-not-call, suppression and consent instructions. Alba confirms in writing when an instruction has been applied; no fixed turnaround is implied here.
Calendar, CRM and handoff: Joint: Confirm systems, access, field mapping, qualification criteria, meeting owner and routing test.
Written campaign launch date: Joint: Record the date only after the agreed dependencies are complete, including who can move it and how a change is documented.

Reporting and quality review

The published agreement defines weekly activity reporting. The engagement still needs a written quality-review method.

Weekly report fields: Alba: Confirm dials, connects, conversations and meetings booked, plus the source system and reporting owner.
Shared definitions: Joint: Define dispositions, connects, conversations, qualification and meeting handoff so both teams read the report the same way.
Recording decision: Joint: Confirm whether recording is enabled, the required notice or consent allocation, access and retention.
Quality-review sample: Joint: Agree the number or selection method for calls reviewed, review frequency and evidence retained. No default sample or cadence is promised here.
Quality scorecard: Joint: Agree the fields to inspect, such as script adherence, claim accuracy, discovery, qualification evidence and disposition accuracy.
Feedback and escalation: Joint: Name who reviews findings, who can approve a script or ICP change, and how unresolved issues are escalated.

Continuity and backfill

Continuity terms are not inferred from the number of seats. Put each operational decision in the Order Confirmation or addendum.

Absence coverage: Joint: Agree what happens to scheduled service, reporting and billing during planned or unplanned caller absence.
Backfill trigger and approval: Joint: Define when a replacement search begins, who approves a proposed caller and what evidence accompanies that decision.
Backfill timing: Joint: If a target timeline is required, write it into the order. This page does not promise an automatic replacement or a fixed replacement time.
Handover and access changes: Alba: Record script, account context and open work before access is removed from one caller and granted to another.
Commercial treatment: Joint: Agree how unavailable service days, a phased start or a backfill period affect delivery and billing.

Cancellation, ownership, data and security

The signed documents control. Review the public documents, then record engagement-specific requirements and limitations.

Cancellation and renewal: Joint: The published Services Agreement describes notice before the next billing date and service through the current prepaid period. Review the selected billing period, end date, setup-fee treatment and refund position in the signed documents.
Data ownership and return: Joint: The published Services Agreement assigns customer data, approved scripts and customer deliverables to the customer. Confirm the required export format, access handoff, retention and deletion instructions.
Systems and processing locations: Joint: Identify every system, sub-processor, personnel location and international-transfer document that applies before personal data is transferred.
Security controls and evidence: Joint: Request the controls and evidence your review requires. The public DPA is not a security certification, and unavailable controls must be identified in writing before processing.
Access and offboarding: Joint: Define account ownership, authentication, logging where available, least-required access, review points and removal at end of need.
Incident contacts and process: Joint: Name both incident contacts and review the notification, cooperation and audit provisions in the signed DPA.
Customer legal review: Customer: Customer confirms its own counsel has reviewed the markets, lists, scripts, recording choices and outreach instructions where required.

Documents to review

Services Agreement: Commercial terms, reporting, cancellation, ownership and liability.
Data Processing Agreement: Processing scope, sub-processors, transfers, security schedule, retention and data rights.
Privacy notice: How Alba handles personal information on its own website and services.
Line-item pricing: Current product choices and published prices.

Planning limitation

This checklist is a planning aid, not a contract, legal opinion, security certification, launch commitment, replacement commitment or outcome forecast. The signed Order Confirmation, Services Agreement, DPA and any addendum govern the engagement.

Use the cost calculator and checklist