Pablo Palafox

We can gather the feedback faster from the customers and hence,

capture that context faster than anyone else.

So it's a bit of this iterative loop that Luis really realized we needed.

Maybe I'll start quickly.

We see ourselves as that layer of execution, really.

Like that's where the magic happens.

You have to start doing the work to capture that context.

So it's very important that we start with executing work, with getting the thing done, implementing one agent, implementing the second agent, connecting them through that context layer.

But the context layer happens after you're actually doing the work.

More than ever, the importance is on the execution layer.

For us, and Luis can comment on that more, that data piece is a very important piece, but it happens after the agent.

What we've built is twin.

Twin for us is really that data layer will reconnect systems of record of the customer, your CRM, your ERP, your transportation management system, whatever it is, your snowflake instance.

And where agents can also populate their own or restore their own context.

It's almost happy robot native data points.

So we've basically created this data layer that holds both customer records and happy robot agent created records, if you will.

So the pyramid of work, as we define it, is essentially

the easy, repeatable, low-hanging fruits type of work at the bottom.

Think about an easy B2B sales call, an easy customer service type of operation, some payment collection type of work.

Kind of the highly repeatable, easily automatable type of work.