Pods

A defined piece of work.
A named team. A set length.

A pod is the smallest useful way to work with us. You see the scope and the price before anything starts, and you decide what happens next on the results. No long contract is needed to find out whether we are any good.

A team leader briefing a small team on the operations floor
A pod is a team you can name
2 weeks
The shortest pod: a design sprint
Up to 30
People in one trained class
0
Commitment beyond the pod itself

The pods

Pick the one closest
to your question.

Most clients begin with one of the first two. The others are for when you already know what you need.

01 AI Operations AI-Assisted

Design sprint

Leave with a plan you could run: which of your contacts AI should take, which need a person, and what a pilot would cost.

  • Your contact types mapped, each assigned a lead
  • A platform choice that fits your systems
  • Handover rules and data boundaries in writing
  • A pilot plan with a price
02 AI Operations and Services AI-Assisted

Pilot pod

Prove it on one or two contact types, with a trained team and AI agents live side by side.

  • A trained class of up to 30 people
  • AI agents on the agreed contact types
  • A weekly review with one accountable lead
  • A decision report at the end
03 Services Human-Led

Care pod

A managed customer care team, working in your systems to your quality standard.

  • Specialists recruited and trained for your product
  • Supervision, quality coaching and workforce planning
  • Voice, chat, email and messaging as needed
  • Reporting on the measures you choose
04 Services Human-Led

Sales pod

A sales team for a defined campaign: lead generation, qualification, renewals or retention.

  • People hired for conversation, not scripts
  • Approved offers and clear authority limits
  • AI qualification before the call, where it helps
  • Sales per hour and conversion, reported daily
05 Incubation and Expansion Human-Led

Launch pod

Your own team on a ready floor in Port of Spain: recruited, equipped and supported from the first day.

  • Equipped workstations in an access-controlled facility
  • Recruitment, onboarding and payroll
  • Devices and dedicated internet
  • Local HR and industrial relations support
06 Incubation and Expansion AI-Run

Overflow and redundancy pod

A second site for your peaks and your bad days, in a different place from your first.

  • Shared volumes and overflow handling
  • A redundant nearshore site
  • Routing integration, subject to technical scoping
  • Agents trained on your work in advance

Every pod is scoped and priced with you before it starts. Sizes and timings are typical and depend on the complexity of the program.

How a pod runs

Agree. Run.
Decide.

The same three moves every time, whatever the pod.

  1. Before

    Agree the work

    What is in, what is out, who is on the team, how long it runs and what it costs.

    • A written scope
    • A named lead on our side
    • The measures we will both look at
  2. During

    Run it in the open

    You see the same figures we do, every week, and you are welcome on the floor.

    • A weekly review
    • Exceptions and what we did about them
    • No surprises at the end
  3. After

    Decide on evidence

    Extend it, change it or stop. Whichever you choose, the findings are yours to keep.

    • A decision report
    • A costed next step, if you want one
    • No obligation to take it

Practical questions

Before you choose a pod.

What does a pod cost?

It depends on the work, the team and the hours of cover, so we price each pod with you before it starts. You will have a figure in writing before you commit to anything.

How quickly can a pod start?

A design sprint can begin as soon as we have agreed the scope. A 20-seat pilot can be live in as little as two weeks from signature, and classes of up to 30 people have been filled in as little as two weeks. Both depend on the complexity of the program.

Can a pod work in our existing systems?

Yes. Pods are scoped around your technology, your access controls and your integration requirements.

What if the pilot shows it is not working?

Then you have found that out in 90 days, with the evidence in your hands, rather than a year into a contract. The decision report says what we saw and why.

Can we combine pods?

Yes. A common route is a design sprint, then a pilot pod, then a care or sales pod at the size the pilot justified.

Start here

Not sure which pod?
Start with the sprint.

Two weeks, a small team on each side, and a plan at the end that is yours whether or not you go further.

DirecOne