Founder Letter

Give each kind of work its own Palari.

Palari exists for a simple tension: teams need shared standards, and workers need enough room for the work to feel human.

Quetzali Ramirez Guillen

Quetzali Ramirez Guillen

Founder of Palari. Building scoped coworkers for real office work.

Companies want shared standards. Workers want their own space.

That tension is everywhere now. A team wants consistent work, clear sources, and control over what tools can touch. A worker wants help that knows their day, their sources, and their style.

One giant team chat feels cold. Personal AI chats can be useful, but they scatter context and rules across private prompts. Palari is the middle point.

A Palari is a named coworker with clear scope. Sofia might help with funding materials. Leo might keep operations moving. Alfred might prepare management packets. Each one should know the sources it can use, the standards it should follow, the memory that belongs in scope, and the moments where a person needs to review the work.

The goal is to standardize the work, not the person doing it.

The team defines the standards: which sources are approved, what good output looks like, what needs review, and what a Palari is allowed to do. The worker still gets help that feels close to the work in front of them.

I come from institutions where evidence matters. A claim is not useful because it sounds right. It is useful because you know where it came from, what it applies to, and what authority it should have.

That is how I think workplace AI should work too. It should show sources. It should remember only what belongs in scope. It should make task outputs reviewable. And when it is about to send, change, share, or expand access, it should ask.

  • Clear scope for the work.
  • Approved sources and visible context.
  • Reviewable memory and team policies.
  • Permission before sending, changing, or sharing.

I am from Zacatecas. Public schools. I taught myself English at 17, became a Fulbright scholar, studied at Harvard, and now work as a research analyst forecasting sovereign crises. I am not an engineer by training. I build because I need the thing to exist, and then I learn whatever I need to build it.

Palari began as my own attempt to make AI usable without losing control. Now I am building it for offices and small teams that need help with real work but cannot accept a black-box system making moves on its own.

The future is not one shared AI chat sitting above the organization. It is a network of trusted Palaris attached to people, domains, and tasks.

Give each kind of work its own Palari. Start with one domain.

Next reads

The product promise is trust you can inspect.

Read the product controls behind the letter: the rules, review records, and domain boundaries that keep a Palari useful without becoming broad by default.