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 Campaign Brief Creation and Generation Handoff Automation: From a Chat Message to a Structured Brief, Nothing Spent

Centriu's internal media-buying specialist agent used to have 8 tools onto Maestro. Every one of them was read-only. A dedicated migration adds a creation path. One tool builds a structured campaign brief. It checks the platform against a fixed list (Meta, Google, LinkedIn, TikTok, Google Business Profile). It needs a real business goal and target audience. It needs a positive number for the budget. The agent is told never to guess the budget. It warns if the client has no ad account for that platform. A second tool hands that brief to Maestro's own AI generation engine. This is the same engine already used from the app's own interface. Every campaign made is born awaiting human approval. Publishing it to the real ad platform stays a separate, human, in-app step. This is true no matter who asked for the generation.

Quero resolver isso

Why a chat agent that can only READ campaign data has an obvious next request

An internal specialist agent can describe a client's campaigns. But it cannot start a new one. This is useful for a status check. It is frustrating for the actual job it was hired to help with. Someone still has to open the app. They must fill in a form. They must start generation by hand every time a new campaign needs to exist. The natural next step is letting the conversation itself create the starting point. The risk in that next step is exactly as obvious. A chat agent that can create things needs the same rules about budgets, platforms, and approval. The human-facing app already enforces these rules. This is arguably more important for the agent. Nobody is watching it in real time. A person filling out a form gets a second look before submitting.

An internal specialist agent that can describe a client's campaigns but can't start a new one is useful for a status check and frustrating for the actual job it was hired to help with — someone still has to open the app, fill in a form, and kick off generation by hand every single time a new campaign needs to exist. The natural next step is letting the conversation itself create the starting point. The risk in that next step is exactly as obvious: a chat agent that can create things needs the same discipline about budgets, platforms, and approval that the human-facing app already enforces — arguably more, since nobody is looking over its shoulder in real time the way a person filling out a form gets a second look before submitting.

Quero resolver isso

How Centriu built the brief-creation and generation-handoff path for the agent

The starting state was recorded in the migration's own header. It was blunt. The agent's 8 existing Maestro tools were all read-only. There was also one action for responding to an optimization recommendation. There was no way to actually create anything. The owner's own instruction was quoted directly in the same header. It set the bar. Campaigns the agent helps create need to be genuinely high quality. There is no room for one to simply go wrong.

The brief-creation tool checks things before it writes a row. The platform argument is checked against a fixed list. This list includes meta, google, linkedin, tiktok, gmb. Common similar words are made normal first. For example, "facebook" and "instagram" both become "meta." "google ads" becomes "google." Anything else is rejected. A message names the valid options instead of a general error. A business goal and a target audience are both needed as real text. They cannot be placeholders. The budget must be a positive number. The tool's own instructions to the agent state the rule clearly. Never guess a budget. If the owner did not say one, ask. A budget type (daily or lifetime, accepting Portuguese similar words too) completes the needed fields. Once created, the brief comes back with the client's set up ad account for that platform if one exists. If one does not, the response carries a clear warning. The campaign can still be made and approved. But it will not be publishable until an ad account is registered. This shows the gap right away, not when it's time to publish.

The generation-handoff tool takes a brief ID. It calls the exact same AI generation engine Maestro's own app interface already uses. The existing page on that engine describes what it does with a structured brief in detail. This page does not repeat that. What is new here is how the request reaches it. The calling agent has no user session to show. So, the generation endpoint gained a second way to check who is calling. This is a service-to-service authentication path. It uses a shared internal secret header. This is the same pattern already used for the platform's other internal calls. It is paired with the target user's ID in the request body. This ID is specifically for the organization's own owner. It is read directly in the code. Every check that already applied to a person's own request still applies to this identity. This includes rate limiting, confirming the brief belongs to that user, and the plan's AI generation quota. Calling through the agent does not remove any of those limits. The response Maestro gives back clearly states that the resulting campaign is "awaiting approval." The tool's own instructions tell the agent never to describe it as "published." Publishing to the real ad platform remains a separate, human action inside the app.

The migration proves its own claims. It does not just say them. An embedded block was run at migration time. It used a real client account. It created a real brief. It confirmed the ad-account field came back filled. This was expected for a client with one on file. It confirmed a zero-budget attempt was rejected. It confirmed an invalid platform ("radio") was rejected. It confirmed the new brief actually appears in the listing tool's output. Then it deleted the test brief it created.

Ver como funciona

What is actually built today

A brief-creation tool checks the platform against a fixed, normal list. It checks the goal, audience, and budget. The budget is needed, positive, and never guessed by the agent. It does this before writing anything.
An clear warning appears the moment a brief is created. This happens if a client has no ad account for the requested platform. It is seen right away. It is not found later when publishing.
A generation-handoff tool calls Maestro's existing AI generation engine. It uses a new service-to-service authentication path built for this. This path uses a shared internal secret. It also uses a known owner identity. Every existing rate-limit, ownership, and plan-quota check is still enforced.
Every campaign made is born in an awaiting-approval state. The tool's own response and instructions to the agent clearly state this. It is never described as "published."
A read tool lists existing briefs. It lists every campaign made from each one. It shows its status.
A real, run self-test is part of the migration. It creates a brief. It checks rejections for a zero budget and a wrong platform. It confirms the listing shows the new brief. Then it cleans up. This is not just a comment saying it works.

Conhecer os recursos

What changes operationally

A campaign can start from a conversation. It does not need someone to open the app. It does not need them to fill in a form from scratch. Every safety rule the form would have enforced is still enforced. This includes a real platform, a real goal and audience, a real budget, and knowing about a missing ad account. These rules are enforced just as strictly in the chat path. The campaign made is always born awaiting approval. So, starting a campaign through the agent never bypasses the human decision to actually spend money.

A campaign can start from a conversation instead of requiring someone to open the app and fill in a form from scratch — while every guardrail the form itself would have enforced (a real platform, a real objective and audience, a real budget, awareness of a missing ad account) is enforced just as strictly in the chat path. And because the resulting campaign is always born awaiting approval, starting a campaign through the agent never becomes a shortcut around the human decision to actually spend money.

Quero esses resultados

A platform typo caught before it ever reaches generation (illustrative scenario, not a real client)

Someone asks the media-buying specialist agent to set up a campaign on "insta" for a client. The tool makes that into the correct platform code. It does not reject a common short word. But if someone names a platform the generation engine truly does not support, the brief-creation tool rejects it right away. It gives the actual list of valid options. It does not let a brief be created that would only fail later when given to generation.

Conversar sobre meu caso

How to start

Começar agora

Frequent questions

Could the media-buying specialist agent create campaigns before this change?

No — it had 8 tools onto Maestro, all read-only, plus one action for responding to an optimization recommendation. This migration added the first creation path.

Can the agent set an arbitrary or guessed budget for a campaign?

No — a real, positive budget number is required, and the tool's own instructions explicitly tell the agent to ask rather than guess when none was given.

What happens if the agent is asked to create a brief for a platform the generation engine doesn't support?

The request is rejected immediately, naming the actual supported platforms, rather than creating a brief that would only fail later.

Does a campaign generated through the agent get published automatically?

No — it is always born in an awaiting-approval state. Publishing to the real ad platform is a separate, human, in-app step.

How does the agent authenticate to the generation engine without a user login?

Through a new service-to-service path: a shared internal secret plus a resolved organization-owner identity, with every existing rate-limit, ownership and quota check still enforced against that identity.

What does Centriu Maestro 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 Maestro lets an AI agent create campaign briefs safely

Quero resolver isso