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 Usage-Quota Consumption Timing Integrity Automation: Billed Before It Happened

Centriu Gauge's Income Tax module meters a client organization's plan-based usage. This includes AI questions asked and documents processed. This usage is checked against a limited monthly allotment. A pre-launch certification audit found the meter was running ahead of the actual event in two separate places. Asking the AI chat a question consumed one unit of quota BEFORE the system had decided whether it would call an AI model at all. A question that ended without ever reaching a model still consumed the same quota as a question that was genuinely answered. This happened because it was out of scope, needed a human professional, or was a clarifying follow-up. Reading a document consumed one unit of quota BEFORE the system confirmed that document actually existed. It also consumed quota before confirming it belonged to the requester under the database's own access rules. A mistyped or someone-else's document identifier burned real quota. It returned nothing but a not-found error. A related, compounding defect was in the same chat code. The mechanism preventing an accidental duplicate charge, like a double-click or a retried network request, built its uniqueness key from the current time. This was measured to the millisecond. So, even a genuine, immediate double-click produced two different keys and was billed twice. All three are fixed. Quota consumption now happens only after the engine has decided a model will genuinely be called. It also happens only after a document read has been confirmed against real, row-level-security-checked ownership. The duplicate-charge key is now built from a ten-second window instead of a raw timestamp.

Quero resolver isso

A meter that runs before the metered event happens will always overcharge

Charging for a unit of usage makes sense only once the specific thing being metered has genuinely occurred. Or, it is guaranteed to occur as a direct result of the charge. The moment a metering step runs earlier than that, it counts every case where the underlying work never actually happens. This is before a decision is made or before an identifier is confirmed valid. A request that gets rejected, redirected, or fails validation still gets charged. This is purely because charging happened first and the actual outcome was discovered second.

Charging for a unit of usage makes sense only once the specific thing being metered has genuinely occurred. Or, it is guaranteed to occur as a direct result of the charge. The moment a metering step runs earlier than that, it counts every case where the underlying work never actually happens. This is before a decision is made or before an identifier is confirmed valid. A request that gets rejected, redirected, or fails validation still gets charged. This is purely because charging happened first and the actual outcome was discovered second.

Quero resolver isso

How Centriu Gauge moved the meter to after the fact, twice, and fixed a related double-charge

This was found during the same pre-launch certification audit. That audit identified the CRITICAL conversation-ownership gap and the HIGH-severity dual-approval defect. These are covered on this pillar's companion pages. The review specifically traced not just whether a feature worked. It also traced exactly when each metering call fired relative to the work it represented.

In the AI chat function, usage was being consumed as an early step. This was before the system had done any of the work of deciding how to handle the question. This included the genuine possibility that no AI model would be called at all. This could happen because the question was outside the module's scope. Or, it needed to be routed to a human tax professional. Or, it was answered with a clarifying follow-up question instead of a model call. Every one of those non-model outcomes had still been charged the same as a fully-answered question. The fix moves the quota-consumption call to after that determination is made. So, quota is only spent on a question that genuinely reaches a model.

In the document-reading function, usage was being consumed before the system confirmed the requested document actually existed. It was also consumed before confirming it belonged to the requester. This check is enforced by the database's own row-level security. This happens when the read occurs under the requesting user's own access, not the backend's elevated one. A wrong or someone else's document identifier would consume a unit of quota. It would return only a not-found response. This was charging for a document that was never actually read. The fix moves quota consumption to after that existence-and-ownership confirmation succeeds. It separately makes the charge idempotent by the document's own identifier. So, deliberately re-reading the same already-processed document does not consume quota a second time. This is a legitimate part of reprocessing a failed extraction.

A third, related defect lived in the same chat function's own duplicate-charge protection. The mechanism was meant to stop an accidental double-charge. This could be a double-click or a retried network request. It built its uniqueness key using the exact current time. This was precise to well under a second. Two calls arriving a few milliseconds apart generated two different keys. This is exactly what an accidental double-click produces. They were treated, and billed, as two entirely separate questions. The fix rebuilds that key around a ten-second time window instead of an exact instant. Two calls landing inside the same ten-second window are recognized as the same attempt and charged once. A genuinely new question asked more than ten seconds later is correctly treated and charged as new. This is true even about the same topic.

Ver como funciona

What is actually built today

AI chat usage quota is consumed only after the engine has determined a model will genuinely be called. A question that ends as out-of-scope, forwarded, or a clarifying follow-up no longer consumes the same quota as an answered one.
Document-read usage quota is consumed only after the specific document has been confirmed to exist. It is also consumed only after it is confirmed to belong to the requester under row-level security. An invalid or foreign document identifier no longer consumes quota before failing.
Idempotent document-read charging is keyed to the document's own identifier. So, a deliberate re-read of an already-processed document does not consume quota again. This is part of legitimate reprocessing.
A duplicate-charge protection key is rebuilt around a ten-second time window rather than a millisecond-precision timestamp. An accidental double-click or network retry within that window is recognized and charged once.
A genuinely new question, even on the same topic, asked outside that ten-second window is still correctly treated and charged as a new, distinct request.
Confirmed today via direct inspection of both edge functions: the quota-consumption call in each sits after, not before, the relevant validation step.

Conhecer os recursos

What changes operationally

An organization's AI usage quota for the Income Tax module now reflects genuine, completed work. This means questions actually answered by a model and documents actually read and processed. It does not reflect every attempt regardless of outcome. A rejected request, an invalid document reference, or an accidental double-click no longer reduces a limited monthly allotment for work that never happened.

An organization's AI usage quota for the Income Tax module now reflects genuine, completed work. This means questions actually answered by a model and documents actually read and processed. It does not reflect every attempt regardless of outcome. A rejected request, an invalid document reference, or an accidental double-click no longer reduces a limited monthly allotment for work that never happened.

Quero esses resultados

A question that costs nothing when it goes nowhere (illustrative scenario, not a real client)

Someone asks the Income Tax AI chat a question. It turns out to be outside the module's scope. It gets routed to a human tax professional instead of an AI-generated answer. Before the fix, that question would still have consumed a unit of the organization's monthly quota. This was identical to a question the AI genuinely answered. After the fix, quota is only consumed once the system has determined a model will actually be called. A question redirected before that point costs nothing.

Conversar sobre meu caso

How to get started

Começar agora

Frequently asked questions

Did asking a question that the AI never actually answered still cost quota before this fix?

Yes — quota was consumed before the system decided whether a model would be called at all. So an out-of-scope, forwarded, or follow-up question was charged the same as a genuinely answered one.

What happened if someone requested a document that didn't exist or belonged to someone else?

The read consumed a unit of quota before that was checked. So an invalid or foreign document identifier burned real quota and returned only a not-found error.

Why did an exact double-click get charged twice before this fix?

The duplicate-charge protection key was built from the current time. This was measured to well under a second. So two calls made milliseconds apart generated two different keys. They were billed as two separate questions.

Does re-reading the same document for reprocessing purposes cost quota again now?

No — the document-read charge is idempotent by the document's own identifier. So a deliberate re-read of an already-processed document doesn't consume quota a second time.

Does this fix change the plan's usage limits or pricing?

No — it corrects when a charge is applied relative to the actual work. It does not change the limits or pricing themselves. These remain a separate commercial decision.

What does Centriu Gauge 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 Gauge only charges AI usage quota for work that actually happened

Quero resolver isso