If you don't like it, you get your money back

An AI customer service agent,that updates customers before they ask.

It tells each customer where their order is, handles the exchange or return and, for those who are happy with their order, asks for a review. Every exchange and return is logged.

Book a free consultationSee what the agent does
Free demoYou own the codeBuilt around your business

What happens today after every online sale. The purchase has been paid for; what comes next counts too.

  1. 01

    Two days after buying, the customer writes to ask where their order is.

  2. 02

    If nobody answers, they leave a one-star review.

  3. 03

    An exchange gets arranged through twenty messages back and forth.

  4. 04

    Returns aren't logged, and later nobody knows what came back or why.

  5. 05

    A customer who received their order and is happy is never asked to leave a review.

  6. 06

    The reviews that end up published are from the people who had a problem.

What the agent does. Each piece answers one of those problems, with your store's orders.

01

Gives shipping updates. It writes to each customer when the order ships, when it's out for delivery and when it arrives, using the carrier's tracking, before they have to ask.

02

Handles the exchange and sends the label. It takes the exchange request under the store's policy, confirms the new size or product and sends the customer the prepaid return label.

03

Logs every return. Each return is recorded with the product, the reason and the status, so you know what comes back and why.

04

Asks satisfied customers for a review. When the order has arrived and the customer is happy, it asks them to leave a review, with a direct link to the product page.

Projects we built

See the portfolio

For your demo

A free demo, with nothing invested before you see it.

$0

Of the code is yours

Deployed on infrastructure in your name.

100%

From idea to production

Weeks, not months.

Weeks

We pick the stack the project needs

  • Claude Code
  • Codex
  • Cursor
  • Next.js
  • React
  • TypeScript
  • Node.js
  • Supabase
  • Neon
  • Vercel
  • PostgreSQL
  • React Native
  • Python
  • .NET
  • Docker
  • AWS
  • Google Cloud

How we work. From idea to production in under a month, with no months of discovery before you see something working.

  1. Step 01

    Discovery

    We work out what your company does and which part hurts most. Half an hour on a call, not a three-week audit: the scope and the price come out of it, both closed.

    • Requirements
    • Technical planning
    • Scope and timeline
    RRelevamiento
    AlcancecerradoEquipo3Entrega12 sepEstadoen curso
    ProcesosEntrevistasAlcancePlazos

    Procesos que tocamos

    Cómo entra un pedido hoyrelevado
    Quién lo carga y en qué sistemarelevado
    Dónde se traba la operaciónrelevado
    Qué se factura a manopendiente
    Qué reportes pide gerenciapendiente
    Qué se integra con el ERPpendiente
  2. Step 02

    Design and architecture

    The blueprint: screens and data model, approved by you. You see them before a line of code exists, so changing something costs a conversation instead of a week.

    • Interface design
    • Architecture
    • Data model
    DiseñoPantallas del sistema3 de 4 aprobadas por vos
    Listado
    Ficha
    Alta
    Reporteen revisión
    Pedir un cambio
    Modelo de datos
    clientes
    • id
    • razon_social
    • cuit
    pedidos
    • id
    • cliente_id
    • total
  3. Step 03

    Development

    You see progress every week and give feedback on something real, not on a status report. We build with Claude Code, Codex and Cursor, on Neon and Supabase.

    • Sprint-based work
    • Code review
    • Regular demos
  4. Step 04

    Testing

    That it works with your data and your people, not just on our machines. We load real cases and someone from your team tries it before it goes live.

    • Functional testing
    • Performance
    • Security
    Corrida #128rama entrega · hace 4 min1 para revisar
    142pasaron1para revisar3,4 sla corrida entera
    • Importar 12.000 filas del ERP1.840 ms
    • Permisos por rol120 ms
    • !Facturar sin CUIT cargadodeja pasar la factura sin CUIT—
    • Cerrar caja con pedidos abiertos310 ms
    • Remito con stock insuficiente95 ms
    • Alta de cliente duplicado64 ms
  5. Step 05

    Launch and support

    It ships documented and with your team trained. The infrastructure is in your name and the code is yours: we stay on if you want us to, not because you depend on us.

    • Deployment
    • Documentation
    • Ongoing support
    sistema.tuempresa.comen línea
    Pedidos del díaNuevo

    38

    Del día

    12

    A facturar

    4

    Demorados

    PedidoClienteTotalEstado
    PD-4417Ferretería Sur184.500confirmado
    PD-4418Corralón Andes62.300confirmado
    PD-4419Distribuidora Río910.000frenado
    PD-4420Metalúrgica Paz245.900confirmado
See the process step by step

Shall we start?

Thirty minutes, no strings. You leave with a concrete recommendation, whether we go ahead or not.

Book a call

Questions about the AI customer service agent for ecommerce. The ones we hear most before the first call.

It connects through an API to the store's platform —Shopify, WooCommerce, BigCommerce or a custom-built one— and to the carrier or shipping software you use, such as UPS, USPS, FedEx or ShipStation, to read tracking. Which ones you use is confirmed on the first call.

The agent applies the store's return policy: time windows, the condition of the product, who pays for shipping. Anything outside that policy goes to a person with the full conversation.

From USD 3,000 to build it, plus maintenance from USD 300 a month. The exact price depends on the process and the integrations: we scope it on the first call and fix the price in writing. AI model usage is billed separately.

It says so and hands the conversation to a person with the full history. When it hands off, and which actions need sign-off from someone on your team, is defined during scoping.

First we build a demo with real cases from your business, so you see how it responds before it's connected to anything in production. Then it's connected with minimum permissions, every action is logged, and for the first few weeks everything it does gets reviewed.

See every question

Last step. Thirty minutes to understand how you operate and tell you what to build first.

No strings. You leave with a concrete recommendation, whether we go ahead or not.

Pick a day and time