How we work

Engineers in your room, not a dashboard.

We scope, build, test and tune your agent on your scripts and recordings — and stay until the metric moves.

Don't spend a year on a pilot that goes nowhere.
Value in a month, not a year.

The pilot plan

Four to six weeks to live calls.

1
Week 0–1 · Scope

One use case, one metric.

Script, systems (LMS/PAS/CRM/dialer), compliance constraints and baseline — written into a pilot charter.

2
Week 1–3 · Build

Graph, integrations, first model.

Frozen compliance lines per language, redaction rules, first fine-tune on consented recordings.

3
Week 3–4 · Test

Simulated customers first.

Headless simulations, barge-in tests, a compliance scorecard and a regression suite.

4
Week 4+ · Go live

Shadow, ramp, tune.

Shadow mode, then a controlled ramp against a control group, fine-tuned until the number moves.

Pilot charter · week 0
$ formant charter --pilot collections-hi --week 0
use_case early-bucket collections · outbound
metric promise-to-pay rate (one number, agreed)
baseline your dialer team, last 4 weeks
languages hi-IN · en-IN (parity-checked)
systems LMS · CRM · dialer · WhatsApp
frozen_lines disclosure · consent · grievance ✓ locked
go_live week 3 shadow → week 4 ramp
go/no-go: week 6 · signed by your ops lead + FormantAI delivery lead
charter v1 written · build starts
Week 0 output

One page. One number. Agreed up front.

The charter fixes the use case, the metric, the baseline and the frozen compliance lines before a line of the graph is built.

Illustrative charter. Yours is written on the scoping call.

Book a pilot scoping call
Who shows up

A team, not a ticket queue.

Engineering

Forward-deployed engineer

Owns graph, prompts, integrations and latency. Sits in your ops reviews.

Models

Speech & model engineer

Fine-tunes on your recordings; benchmarks providers per language.

Compliance

Compliance & QA analyst

Maps controls to RBI, IRDAI and DPDP; reviews flagged calls with you.

Delivery

Delivery lead

Runs the charter, the weekly review and the go/no-go. Accountable for the metric.

Change control

Prompt changes ship like code.

Diff review, regression run, bilingual parity and human approval. Frozen compliance lines can't be edited by a model or a hurried engineer.

Release · v41 → v42
v41→v42diff_reviewednode-8 · hi-IN + en-IN
v42regression_run38/38 scenarios · 0 red
v42parity_checkfrozen_lines exact-match
v42barge_in_suitepass
v42approvalclient ops lead
v42deployedcanary 10% → 100% · rollback ready
After go-live

Every morning starts with the facts.

Daily
performance report, per-call evidence
Weekly
QA review and fine-tune cycle
100%
of calls analysed, not a sample
1
accountable delivery lead
Bring one use case and your numbers

Scope a pilot in one call.

Book a pilot scoping call
Deployments

See what changed for others

See deployments