Plan a pilot
Pilot and pricing

Price the operation you actually need.

TheCall prepares a project proposal around the market, workflow, volume, staffing and integration scope instead of publishing a misleading universal per-call price.

Project modelLOCAL / DEFINED
PROJECT WORKFLOW04 defined stages
  1. 01Scope
  2. 02Pilot
  3. 03Review
  4. 04Scale
Why it mattersCOMPANY / CONTEXT FIRST

A price is meaningful only with an operating definition.

Two projects with the same lead volume can require different attempt logic, training, support categories, systems and staffing. A simple seat or call price can hide the work that determines service quality.

We use the brief to define the team and commercial model. Any minimums, setup work, ongoing charges or usage assumptions should be made explicit in the proposal before commitment.

Operating focus

What shapes a proposal

These inputs determine the operating workload and setup effort.

FOCUS / 01

Market and coverage

Country, language requirements, operating windows and local team availability.

FOCUS / 02

Workflow complexity

Script branches, attempt policy, statuses, upsell, escalation and support scope.

FOCUS / 03

Volume pattern

Expected leads or contacts, peak timing, seasonality and growth range.

FOCUS / 04

Systems and governance

Integration, reporting, QA, data access and client-side ownership.

Operating path

A practical pilot path

A pilot should test a commercial assumption and an operating assumption at the same time.

  1. 01
    Brief

    Define the project

    Choose market, offer, service, volume and systems.

  2. 02
    Proposal

    Agree scope and terms

    Document deliverables, responsibilities, pricing basis and readiness needs.

  3. 03
    Pilot

    Run the focused workflow

    Train, test and launch against agreed operating measures.

  4. 04
    Review

    Decide the next scope

    Use the evidence to adapt, scale or stop before wider commitment.

Scope definition

Bring these inputs for a useful estimate

Ranges are acceptable at the first conversation, but assumptions will be written down.

Discovery inputsPROJECT / DEFINED
  • 01Countries
  • 02Service required
  • 03Lead or contact volume
  • 04Operating schedule
  • 05Integration needs
  • 06Target launch timing
No invented rate card

Pricing is confirmed in a written project proposal.

This page deliberately avoids publishing a number before the staffing, workflow and data requirements are known.

Questions

Before the project is scoped.

Do you charge per lead, call, outcome or seat?

The appropriate commercial basis depends on the service and risk allocation. The proposal should state the model, assumptions and exclusions clearly.

Can we start with a small pilot?

A focused pilot can be discussed. Feasibility depends on setup effort, country, team availability, volume and the minimum scope needed to produce reliable learning.

Next step

Request a scoped pilot proposal.

Give us the six inputs above and the commercial problem you want the pilot to answer.

Plan the project