Use casesClassification pipelines

Lead qualification and CRM enrichment

Batch personalisation where cost per record is the whole business case.

The problem

Outbound teams enrich leads with industry, size band, and trigger events before a rep calls. The model cost per lead determines whether the campaign is profitable. Spreadsheets hide it; a failed cron job that re-processes the whole CRM doubles it.

Why Ecko

Per-record metering
Log cost() next to each lead id. Finance can reconcile model spend against pipeline revenue without a separate billing export from the provider.
Typed CRM structs
Write enriched fields into records the CRM import expects. Missing industry codes fail before upload.
Offline replays
Re-run last month's file in mock mode to test a new prompt before spending again.

In practice

leads.ecko
fn enrich(lead: Lead) -> EnrichedLead {
  let out = ai "Firmographics JSON" from lead.domain
  log.info(lead.id, cost=cost())
  out
}

Further reading

Related cases

All 32 use cases →

Try it on your workload.

Install Ecko Open the playground