SOW & Commercial Sync

Lorikeet × Konfío

Aligning on technical scope, Section 3.8, and revised commercial structure.

DateFriday, May 15, 2026
FromRyan Collins · Nate Houghton
Konfío×Lorikeet
Agenda
Today's call

Three working sessions, one meeting.

01

UI + Lorikeet SDK integration

How Lorikeet sits behind the interface Nicolás's team built.

Item 4
02

Section 3.8 — Bank conversion adequacy

Confirm the adjustment language Esther's team is looking for.

Item 5
03

Commercial alignment

Revised pricing structure and proposed SLA framework.

Commercial

Items 1–2 (SLAs Section 1.5 + closed-ticket definition) reserved for a dedicated commercial deep-dive once Konfío has reviewed the SLA structure proposed today.

Konfío×Lorikeet
Snapshot
Where we are

Pilot-ready. Two clean items between us and kickoff.

Kickoff
Apr 8
Simulation report
Apr 20
NDA redlines
Apr 27
SOW received
May 12
5
SOW + commercial sync
Today
6
NDA signed
Next
7
Pilot kickoff
Phase 1
Closed

Technical evaluation

29 scenarios, 7 guardrails, 13 KB articles validated. Reported April 20.

In motion

NDA

Konfío legal incorporating Lorikeet redlines on Sections 6 & 11.

Today

SOW + Commercial

Walk Sections 1.5 and 3.8; share revised pricing structure.

Konfío×Lorikeet
Simulation Recap · Apr 20
What we proved

The agent works on Konfío's actual scenarios.

29
Test scenarios
Built from Konfío's product surface.
10/13
New scenarios at 100%
Across cobros, onboarding, tarjeta.
100%
Liquidación Anticipada
From zero-baseline to fully resolved.
Coverage shipped
  • 13 manual KB articles authored (OXXO/SPEI, MSI, cashback, terminales, activación)
  • 3 new subworkflows: Cobros Digitales · Onboarding · Programas de Tarjeta
  • Stronger search-first triage + new routing
  • All 7 guardrails activated, assertions on all 29 scenarios
Known gaps · Phase 1 backlog
  • Transferencia SPEI — prohibited uses missing
  • Límite de Tarjeta — "how to check available credit" path
  • Problemas App — troubleshooting workflow
  • Info General Productos — search efficiency tuning
Konfío×Lorikeet
Item 4 · Technical alignment
Item 4

Lorikeet sits behind Nicolás's UI.

Konfío owns the customer-facing experience. Lorikeet powers the resolution engine over your existing API surface.

Konfío UI
Web · App · WhatsApp embed
Lorikeet SDK / API
Conversation orchestration, RAG, tools
Konfío systems
Core, ledger, ticketing, KYC

Konfío owns

  • Front-end shell, theming, brand
  • Authentication & session
  • API gateway and entitlements
  • System-of-record state changes

Lorikeet owns

  • Conversation state & turn-taking
  • RAG over knowledge base
  • Tool calls into Konfío APIs (read & action)
  • Guardrails, escalation, ticket logging
Confirm today

SDK embed pattern, auth handoff (JWT vs session token), and which Konfío endpoints are in-scope for Phase 1 read access.

Konfío×Lorikeet
Item 4 · Phasing
Phased rollout

Two phases, two integration depths.

Phase 1 — Pilot

FAQ · Auth · Knowledge Base

  • Read-only access to identity & basic account state
  • RAG over Konfío's KB (extends the 13 articles already loaded)
  • Triage + routing into human queue for anything transactional
  • Frames Eduardo's April 9 scope

Trigger for Phase 2: agreed quality bar on Phase 1 tickets + greenlight from Eugenio + Product on go-live.

Phase 2 — Expansion

Voice + Transactional

  • Outbound + inbound voice (Spanish, MX phone numbers)
  • Action tools: payment plans, MSI changes, card actions
  • Cobros Digitales workflows promoted to agent-resolvable
  • Deeper write access scoped per integration endpoint

Procurement engagement happens between Phase 1 close and Phase 2 scope freeze.

Konfío×Lorikeet
Item 5 · Section 3.8
Item 5

Bank conversion clauses · what Esther's team needs.

Konfío's migration from SOFOM to bank charter (or future regulatory step-up) cannot leave the service contract behind. Our position:

Successor entity
Service continues uninterrupted to the successor regulated entity under the same terms, with notice not consent.
Regulatory adjustments
If new banking regulations require data residency, audit, or control changes, Lorikeet commits to a good-faith adjustment window (typical: 90 days) to meet them or to a structured exit.
Pricing on conversion
Conversion alone does not re-open pricing. Pricing changes only follow scope changes (Phase 2 expansion, new volume tier).
Termination protection
If regulatory change blocks service Konfío side, mutual termination right with pro-rata refund — no penalty.
Audit cooperation
Lorikeet supports regulator-facing audit requests (SOC 2 Type II, ISO 27001 — both available now via Trust Center).
Need from Konfío today

Specific 3.8 language Compliance wants to see — we'll redline against the CSA in parallel with NDA execution.

Konfío×Lorikeet
Commercial · What we heard
Commercial · what we heard

Three asks from your May 6 note.

Ask 1

More competitive

"Pricing is currently above what we can accommodate."

Our response: revised structure on the next slide.

Ask 2

Channel-based rates

Different rates for voice vs written resolutions.

Our response: Scenario A — two rates by channel.

Ask 3

Volume-based tiers

Single blended rate dropping as committed volume increases.

Our response: Scenario B — committed volume slab.

Confirmed

Platform access for managing the agent, workflows, and configuration is included. No platform fee, no implementation fee, no support fee.

Konfío×Lorikeet
Commercial · Scenario A
Scenario A · By channel
Scenario B · By committed volume

Pay by channel.

Two rates tied to the channel the agent resolves on. Voice carries the higher rate to reflect telephony and per-minute cost; written (chat + email) is priced lower. You only pay for resolutions — non-resolved tickets that escalate aren't billed.

ChannelDefinitionRate (USD)
Voice resolution Agent resolves the customer's intent end-to-end on a voice call. No human handoff. $1.00 / resolution
Written resolution Agent resolves the customer's intent end-to-end on chat or email. No human handoff. $0.70 / resolution
At Konfío's expected volume

~10k tickets/month (120k/year). At a ~75% agent resolution rate and a ~30/70 voice/written mix, blended ACV lands at ~$72k annual (27k voice × $1 + 63k written × $0.70). Annual commit, true-up quarterly.

Rates are illustrative pending VP sign-off — structure is firm, exact rates to be confirmed in revised CSA this week.

Konfío×Lorikeet
Commercial · Scenario B
Scenario A · By channel
Scenario B · By committed volume

Commit to volume, lock the rate.

A single blended rate per resolution across voice and written, dropping as committed volume increases. Predictable monthly burn for budget planning.

Annual committed resolutionsEffective rateAnnual ACV
Up to 90,000 resolutions$0.80 / resolution$72,000
90,001 – 180,000 resolutions$0.70 / resolution$126,000
180,001 – 300,000 resolutions$0.60 / resolution$180,000
300,000+CustomPhase 2 territory
How "resolved" maps to Section 1.5

Resolved = end-to-end resolution as defined in the SOW closed-ticket definition, identical to Scenario A. Scenario B blends voice and written into a single rate. Tickets that escalate to a human are not metered.

Volume slabs are illustrative — final structure confirmed alongside the revised CSA. Annual commit, billed monthly.

Konfío×Lorikeet
SLA Structure Proposal · Section 1.5
Proposed SLA structure

For your internal review ahead of the commercial deep-dive.

Tiered to commitment level. The structure below is what we propose to incorporate into Section 1.5 of the SOW.

Platform uptime
99.9% monthly measured at the API edge. Service credits at 99.5% (10%) and 99.0% (25%) of monthly fees.
Severity 1 response
30 minutes business hours · 1 hour after-hours. Production-down or guardrail breach.
Severity 2 response
4 business hours. Degraded behavior on a meaningful workflow.
Severity 3 response
1 business day. Cosmetic, configuration, or low-impact requests.
Support hours
Business hours follow Konfío's CDMX working day. After-hours pager for Sev 1 only.
Quality SLA
Maintain agreed quality bar on Phase 1 scenario suite. Monthly review with shared scorecard; remediation plan if any scenario falls below 90% pass rate for two consecutive months.

Konfío to review and return any required adjustments before the dedicated commercial session.

Konfío×Lorikeet
Closed-ticket definition · Section 1.5
Closed-ticket definition

The metering rule that ties to either pricing scenario.

How we mark a ticket as resolved, assisted, or contained — and how that flows into invoicing.

Resolved

Final outbound message from agent. No human reply within 72 hours. No reopen within 7 days on same intent.

Assisted

Agent worked the ticket but human took over before the close criteria above. Counts at the assisted rate (Scenario A only).

Contained

Customer engaged but no system action and no human handoff (FAQ only). Free in Scenario B.

Audit & dispute

Konfío sees ticket-level metering in the dashboard. Any disputed ticket within 30 days of invoice triggers a joint review; agreed adjustments credited on the next invoice.

Konfío×Lorikeet
Next Steps
From here

What we leave today's call with.

This week

Revised CSA

Lorikeet sends updated commercial reflecting the structure agreed today, with SLAs Section 1.5 embedded.

This week

NDA execution

Konfío legal returns redlined NDA reflecting Sections 6 & 11 adjustments. Ryan signs (AE, Lorikeet).

Next week

Section 3.8 redline

Compliance team confirms exact language; we incorporate into the CSA in parallel.

Next week

Commercial deep-dive

Dedicated session on SLAs (1.5) and closed-ticket definition once Konfío has reviewed the SLA structure proposed today.

Following

Pilot kickoff

Phase 1 scope confirmed with Eugenio + Product. Go-live date locked.

June 16 · CDMX

Lorikeet event

Co-hosted investor event at Hotel CondesaDF — invitation extended to Konfío stakeholders.

Thank you

Let's get the pilot live.

Two clean items between us and kickoff. Ready when you are.

Ryan Collinsryan.collins@lorikeetcx.ai
Nate Houghtonnate@lorikeetcx.ai
Lorikeetlorikeetcx.ai