Para empresas que querem crescer com controle

Um sistema para operar sua empresa com IA.

Vendas, marketing, atendimento, operação, financeiro e inteligência trabalhando sobre o mesmo contexto — para sua empresa ganhar escala sem perder controle.

Sua empresa inteira. Uma operação. IA trabalhando.

Ver a Centriu funcionando

Para empresas de qualquer setor que querem crescer com estrutura, controle e inteligência.

Representação ilustrativa do trabalho em execução

O problema

Sua empresa não deveria operar em pedaços

Não é falta de ferramenta. É que cada ferramenta resolve um pedaço, e ninguém é dono do todo. O custo disso não aparece numa fatura — aparece no mês seguinte.

Sistemas que não se falam
O mesmo dado é digitado de novo — e cada cópia conta uma história diferente.
Dados duplicados
Ninguém sabe qual versão é a verdadeira na hora de decidir.
Conversas perdidas
O cliente repete o contexto a cada canal e a cada pessoa.
Tarefas espalhadas
O trabalho vive em planilhas, mensagens e na memória de alguém.
Decisões sem contexto
A escolha é feita com o recorte que estava à mão, não com o que importava.
Automações desconectadas
Cada ferramenta automatiza um pedaço e ninguém enxerga o todo.

Nenhum desses problemas se resolve comprando mais um software. Eles se resolvem quando a operação inteira passa a trabalhar sobre o mesmo contexto.

A resposta

Tudo trabalha sobre o mesmo contexto.

A Centriu não é uma coleção de produtos. É uma plataforma em que clientes, áreas e agentes leem e escrevem no mesmo lugar.

Cliente 360

Um contexto, não vários cadastros

Cada conversa, tarefa, campanha, cobrança e decisão fica ligada ao cliente e à operação — não a um sistema isolado.

Clientes
Comercial
Atendimento
Operação
Financeiro
Marketing
Inteligência
Agentes
Consultoria

As áreas abaixo são partes da mesma operação, não produtos separados. Elas compartilham conta, permissões e histórico.

IA que trabalha — não um chatbot ao lado

A inteligência artificial da Centriu participa da operação: entende contexto, prepara trabalho, executa rotinas e pede aprovação quando importa.

Entende o contexto

Lê a operação, o cliente e o histórico antes de propor qualquer coisa.

Prepara o trabalho

Redige, organiza, calcula e deixa pronto para revisão humana.

Executa rotinas

Roda o que é repetitivo dentro dos limites definidos pela empresa.

Recomenda a próxima ação

Cruza áreas, identifica prioridade e mostra o motivo da recomendação.

Pede aprovação

O que é sensível passa por uma pessoa antes de valer. Sem exceção silenciosa.

Mantém histórico e aprende

Registra o que aconteceu e usa o resultado para melhorar a próxima decisão.

O que a Centriu faz

Uma plataforma, várias frentes de trabalho. Tudo no mesmo contexto, com a IA participando do que dá para acelerar.

Comercial

CRM, pipeline, oportunidades, propostas, follow-up e automações.

Atendimento

WhatsApp, Instagram, Messenger, chat do site e e-mail no mesmo contexto.

Operação

Tarefas, responsáveis, prazos, aprovações, agenda e capacidade.

Financeiro

Contas, cobranças, caixa, fiscal, margem, IR, orçamento e inteligência econômica.

Marketing

Planejar, produzir, aprovar, publicar e medir conteúdo e campanhas.

Inteligência

Painéis, alertas, previsões, recomendações e leitura executiva.

Agentes

Rotinas executadas continuamente pela IA com controle e aprovação.

Consultoria

Diagnóstico, estratégia, transformação, acompanhamento e especialistas.

Para quem é

Para empresas que querem crescer — e crescer certo.

A Centriu faz sentido quando o volume aumenta e a estrutura precisa acompanhar. Não é sobre setor nem tamanho: é sobre a operação conseguir sustentar o próximo estágio.

As vendas crescem, mas o processo não acompanha.

As áreas trabalham separadas e o cliente sente.

A operação depende de pessoas específicas.

O financeiro ficou complexo e o caixa perde visibilidade.

O atendimento cresce em volume e em canais.

A IA entra sem contexto, controle ou histórico.

Se a empresa ainda não começou a crescer, a Centriu também ajuda a preparar a estrutura para o primeiro salto.

Ver a Centriu funcionando

Consultoria

Tecnologia sozinha não resolve uma operação mal desenhada.

A Centriu combina tecnologia, inteligência, método e acompanhamento. A consultoria diagnostica, desenha, implanta e acompanha — com evidências, não com apresentação.

Diagnóstico e imersão na operação

Estratégia e prioridades

Roadmap de transformação

Desenho da arquitetura operacional

Implantação conduzida

Acompanhamento com evidências

Benchmarking e leitura de mercado

Especialistas, rede e inteligência coletiva

A participação de especialistas depende da solução e do contrato. Não é um item incluído automaticamente em toda contratação, e não prometemos acompanhamento humano ilimitado.

Veja a Centriu funcionando na sua operação

Uma conversa para entender onde a sua operação perde tempo, dinheiro ou capacidade — e o que a Centriu faria primeiro.

Ver a Centriu funcionando

problema

AI-Agent-Driven Client Strategy Project Creation Automation: From a Chat Request to 25 Modules Filling In the Background

Until a recent fix, none of Centriu's internal AI agents had any way to create or fill a client's strategy project in Vesper. The capability existed only in Vesper's own chat interface. It was tied to a real user session. A request to create strategy for every client had nowhere to go inside the agent network at all. The fix adds a role-gated internal route. This route is authenticated by a shared server-to-server secret. It does not use a user login. It finds or creates the client's active strategy project. It dispatches the exact same 25-module bulk-fill engine Vesper's own chat already uses. It is never a separate, parallel one. The corresponding agent tool is restricted to the roles that should reasonably touch a client's strategy. These roles are strategy, account, direction, and a dedicated internal specialist role. It explicitly excludes roles like security that have no business writing strategy. Its own returned instructions tell the calling agent never to claim the strategy is "ready" immediately. Filling 25 modules takes minutes in the background. So the tool reports that the work was dispatched. It points to a separate status-check tool to confirm completion.

Quero resolver isso

Why a chat-only creation flow becomes a real gap the moment an agent needs it

Building a strategy-creation flow around a real, logged-in user session is a reasonable starting point. It's how the product's own wizard and its own chat-based bulk-fill both work. The gap only becomes visible the first time someone reasonably expects an internal AI agent to do the same thing on request. This is not a person clicking through the UI. An agent has no browser session to inherit. So a capability built only around one doesn't just work worse for an agent. It doesn't exist for one at all. The only way to find that out is to actually ask for it. Then you watch the request go nowhere.

Building a strategy-creation flow around a real, logged-in user session is a reasonable starting point — it's how the product's own wizard and its own chat-based bulk-fill both work. The gap only becomes visible the first time someone reasonably expects an internal AI agent, not a person clicking through the UI, to be able to do the same thing on request. An agent has no browser session to inherit, so a capability built exclusively around one doesn't just work worse for an agent — it doesn't exist for one at all, and the only way to find that out is to actually ask for it and watch the request go nowhere.

Quero resolver isso

How Centriu built the agent-facing creation path without duplicating the fill engine

The gap was surfaced by a direct, real request. It was not a planning exercise. An owner asked the internal team chat who had access to Vesper. Then they asked that person's agent to create every client's strategy inside it. The agent that received the follow-up request discovered, by trying, that no agent anywhere in the network had a single write tool onto Vesper. The request came back explicitly blocked. A portfolio-wide check found 11 of 18 active clients with no strategy project in Vesper at all.

The fix adds one new internal route to Vesper itself. It is authenticated by a shared secret header. It does not use a user session. This is the same pattern the platform already uses for other internal, service-to-service calls. It uses the fallback debug token used elsewhere in development. Without that secret configured on the server, the route doesn't function at all. It does not fall open. The route verifies the requested client actually belongs to the calling organization before touching anything. Then it either reuses the client's existing active strategy project or creates a new one. It gets a starting cycle objective from whatever the client already has on record when none is explicitly given. Whichever path it takes, it dispatches the fill job through the exact same background engine Vesper's own chat-based bulk-fill already calls. So the actual work of populating 25 strategy modules (ICP, personas, positioning, customer journey, growth plan, and more) runs through one single, already-proven code path. This happens regardless of whether a person or an agent triggered it. It is not a second implementation that would need to be kept in sync forever.

The corresponding agent-facing tool is deliberately narrow about who can use it. The migration restricts it to roles that plausibly own client strategy. These are strategy, account, direction, and a dedicated internal specialist role. It explicitly does not include the security role that had wrongly claimed Vesper access in the original incident. It accepts up to twelve client names in one call. It finds each by a case-insensitive partial match against the organization's own active clients. It refuses to guess when a name matches more than one client. It does not pick one arbitrarily. The fill itself takes minutes and runs in the background. So the tool's own returned guidance is clear. The calling agent must never describe the strategy as finished the moment the tool returns. It should report that the work was dispatched, for which clients. It should point to a separate, paired read-only tool to check real completion status afterward.

Ver como funciona

What is actually built today

A new internal, secret-authenticated route in Vesper. It finds or creates a client's active strategy project. It dispatches the fill of all 25 strategy modules. It is closed entirely (no route behavior) if the shared secret isn't configured.
Reuse of the client's existing active project when one exists. It does not create a duplicate every time the tool is called again.
The exact same background fill engine Vesper's own chat-based bulk-fill already uses. It is not a separate, parallel implementation to maintain.
An agent-facing creation tool restricted by role. It is for strategy, account, direction and a dedicated internal specialist. It explicitly excludes roles with no legitimate reason to write a client's strategy. This is enforced by an executed self-test in the migration itself.
Batch support for up to twelve clients in one call. Ambiguous name matches are refused. They are not guessed.
A paired, read-only status tool. It reports per-client project existence. It shows modules completed out of 25. It shows whether a fill job is currently running or previously failed. It is separate from the creation tool. So an agent is never left guessing whether "dispatched" ever actually finished.

Conhecer os recursos

What changes operationally

A client no longer needs someone to manually open Vesper. They do not need to click through a wizard for a strategy project to exist. A portfolio-wide sweep can be dispatched from the same conversational surface. This surface is already used for everything else. It is restricted to the roles that should reasonably be doing it. It always reuses the one real fill engine. It does not use a second one built just for this path. The tool is clear that dispatching is not the same as finishing. So nobody managing the agent has to guess if a background job that takes minutes actually completed. A dedicated status check exists specifically to answer that.

A client no longer needs someone to manually open Vesper and click through a wizard for a strategy project to exist — a portfolio-wide sweep can be dispatched from the same conversational surface already used for everything else, restricted to the roles that should reasonably be doing it, and always reusing the one real fill engine rather than a second one built just for this path. And because the tool is explicit that dispatching is not the same as finishing, nobody managing the agent has to guess whether a background job that takes minutes actually completed — a dedicated status check exists specifically to answer that.

Quero esses resultados

A batch request that skips what's already done (illustrative scenario, not a real client)

Someone asks an agent to set up strategy for a list of clients. Several of them already have a project. Some modules are filled from a previous run. The creation tool doesn't restart any of them from zero. An existing active project is reused. Only the modules still marked incomplete are queued for filling. This happens alongside genuinely new projects created for whichever names on the list had none at all.

Conversar sobre meu caso

How to start

Começar agora

Frequent questions

Could any internal AI agent create or fill a client's Vesper strategy before this change?

No — the capability existed only through Vesper's own chat interface tied to a real user session. A portfolio-wide check at the time found 11 of 18 active clients with no strategy project at all, because nothing agent-facing could create one.

Does the agent-facing tool use a different engine to fill the 25 strategy modules?

No — it dispatches the exact same background fill engine Vesper's own chat-based bulk-fill already uses, not a separate implementation.

Which agent roles can actually create a client's strategy this way?

Strategy, account, direction and a dedicated internal specialist role. Roles like security are explicitly excluded, and that restriction is checked by an executed test at migration time.

Does the tool say the strategy is ready as soon as it responds?

No — filling 25 modules takes minutes in the background. The tool's own instructions require reporting that the work was dispatched, and checking a separate read-only tool afterward to confirm real completion.

What happens if I ask it to create strategy for a client that already has a project?

The existing active project is reused, not duplicated — and only modules still marked incomplete are queued for filling.

What does Centriu Vesper cost?

It is sold by subscription with a published starting price — exact current values are on the central pricing page.

Ainda tenho dúvida

See how Centriu Vesper lets an AI agent dispatch client strategy creation safely

Quero resolver isso