Coru
Book a demo

About us

Transforming finance in Latin America with AI

Building trust, empathy and inclusion.

+345 projects delivered
82% client satisfaction
+60 companies trust Coru

Regional context

Every market, its own set of rules

Operating in financial services in Latin America means dealing with different regulators, different document formats and different service expectations in each country. That context is built into the product rather than adapted afterwards.

Document CURP RFC
Language variant Mexican Spanish
What the product does The pronunciation dictionary reads the CURP field by field, and the RFC alphanumerically when the context is tax-related. Two different readings of the same kind of data.
Regulator and rule slot · pending legal

Four examples. The logic is the same in any market in the region.

Values

What we practise

Leadership

Who leads Coru

Eugenio Beccar Varela

CEO

in · LinkedIn

Agustín De Zuviría

CRO

in · LinkedIn

Manuel Patlán

CFO

in · LinkedIn

Adrián De Armas

in · LinkedIn

Operating model

A dedicated pod per client

On your side

01 Process ownerdefines the flow and accepts the KPI
02 IT and integrationopens access to the core and the channels
03 Risk and Complianceapproves the guardrails once

On Coru's side

01 Product owneranswers for the case, from design to KPI
02 AI engineersconfigure, test and tune the agent
03 Compliance liaisontranslates regulatory requirements into guardrails

Integration support is included and is not billed as consulting. The pod stays on from case design through KPI measurement in production.

Rollout

Three stages

Day 0

Define the case

One high-volume flow, with the KPI agreed before anything starts.

On your side

Picks the flow and accepts the success criterion.

On Coru's side

Designs the case and proposes the measurable KPI.

What comes out

A closed scope, with the number agreed in writing.

What does not happen

A three-month discovery before anything runs.

1–3 weeks from defined case to production · voice in 2–5 days on an already connected channel

The stages are proposed from what the platform does. The week-by-week distribution depends on confirmation from the implementation team.

Commercial model

Charging on results

What you contract The agreed outcome on one flow of your operation.
When the scope closes After the pilot, with the projection already validated on your numbers.
Who measures The KPI in your operation, on the dashboard both sides see.
If the KPI does not come The agent scope is revised, within the same contract.

The project-based column describes the category standard, without naming a vendor.

Investors

Who invests in Coru

Presence

We operate across Latin America

Three languages

Spanish, Portuguese and English — platform and customer service.

Variant per operation

The agent speaks the way its market speaks. The regional variant is configuration, not a new version.

Local context in the product

Document format, collections policy and pronunciation dictionary per operation.

Ask your questions

Try the platform your Risk team approves.

AI agents in production at regulated institutions across LatAm. Guardrails in code, deployment inside your network, and a first agent live in one to three weeks.

Guardrails in code

Deterministic filters before and after the LLM, three of them mandatory and non-disableable, with an auditable per-turn trail.

Full cycle, one approval

Origination, onboarding, transactions and collections on one platform. Compliance clearance happens once.

Weeks, not quarters

Sandbox on day one, voice on your SIP trunk in two to five days, integration included in the contract.

Shall we start?

Please use your work email.

By submitting you accept our privacy policy. We do not share your information with third parties.

Newsletter

Insights on AI in regulated operations, once a month.

Governance, architecture and what happens after go-live. No spam.

By subscribing you agree to receive communications from Coru.