Entende o contexto
Lê a operação, o cliente e o histórico antes de propor qualquer coisa.
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.
Para empresas de qualquer setor que querem crescer com estrutura, controle e inteligência.
Painel ilustrativo do Sistema Centriu com sete frentes trabalhando: atendimento, comercial, operação, agentes, inteligência, conteúdo e marketing. Cada frente mostra o trabalho concluído ou o próximo passo.
Representação ilustrativa do trabalho em execução
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 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.
As áreas abaixo são partes da mesma operação, não produtos separados. Elas compartilham conta, permissões e histórico.
A inteligência artificial da Centriu participa da operação: entende contexto, prepara trabalho, executa rotinas e pede aprovação quando importa.
Lê a operação, o cliente e o histórico antes de propor qualquer coisa.
Redige, organiza, calcula e deixa pronto para revisão humana.
Roda o que é repetitivo dentro dos limites definidos pela empresa.
Cruza áreas, identifica prioridade e mostra o motivo da recomendação.
O que é sensível passa por uma pessoa antes de valer. Sem exceção silenciosa.
Registra o que aconteceu e usa o resultado para melhorar a próxima decisão.
Uma plataforma, várias frentes de trabalho. Tudo no mesmo contexto, com a IA participando do que dá para acelerar.
CRM, pipeline, oportunidades, propostas, follow-up e automações.
WhatsApp, Instagram, Messenger, chat do site e e-mail no mesmo contexto.
Tarefas, responsáveis, prazos, aprovações, agenda e capacidade.
Contas, cobranças, caixa, fiscal, margem, IR, orçamento e inteligência econômica.
Planejar, produzir, aprovar, publicar e medir conteúdo e campanhas.
Painéis, alertas, previsões, recomendações e leitura executiva.
Rotinas executadas continuamente pela IA com controle e aprovação.
Diagnóstico, estratégia, transformação, acompanhamento e especialistas.
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 funcionandoA 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
Uma conversa para entender onde a sua operação perde tempo, dinheiro ou capacidade — e o que a Centriu faria primeiro.
problema
A projection built in a spreadsheet answers the question correctly on the day it is built. Then it quietly goes stale. This happens the first time someone changes one assumption. It also happens if they forget to update every formula that depended on it. Centriu Oracle's scenario simulator keeps the premise and the output permanently locked together. It never stores the output at all. Eleven funnel and financial inputs feed a pure calculation function. These inputs are visitors, conversion rate, average ticket, CAC (customer acquisition cost), purchase frequency, retention, churn, media spend, content output, team capacity, and gross margin. The function runs fresh on every single read. It produces monthly and annual revenue, LTV (lifetime value), the LTV-to-CAC ratio, payback in months, a capacity flag, and a return score. It also produces a risk score. A consultant names each variant. These can be the current baseline, a conservative case, a likely case, an aggressive case, or a fully custom one. Exactly one scenario per project can hold the exclusive "baseline" flag at a time. The database itself enforces this. So, every comparison is measured against one clear reference point. It is never an outdated guess about which version was the real one.

A growth projection built in a spreadsheet is only current as of the last time someone remembered to open it. They also had to manually recompute every formula after changing one input. If you change the assumed conversion rate, the LTV (lifetime value) will not update itself. The payback period and the return score three tabs away also do not update themselves. They sit there, looking correct, but are silently wrong. This happens until whoever reads the deck next assumes they still reflect the current premise. The deeper problem gets worse when a team keeps several versions of "the numbers." One might be from the kickoff call. Another might be revised after a budget talk. Someone might have quietly cleaned up one before a client meeting. There is no single, database-enforced answer to which version is the actual reference point everyone should compare against.
A growth projection built in a spreadsheet is only current as of the last time someone remembered to open it. They also had to manually recompute every formula after changing one input. If you change the assumed conversion rate, the LTV (lifetime value) will not update itself. The payback period and the return score three tabs away also do not update themselves. They sit there, looking correct, but are silently wrong. This happens until whoever reads the deck next assumes they still reflect the current premise. The deeper problem gets worse when a team keeps several versions of "the numbers." One might be from the kickoff call. Another might be revised after a budget talk. Someone might have quietly cleaned up one before a client meeting. There is no single, database-enforced answer to which version is the actual reference point everyone should compare against.
A scenario is created with a name. It is one of five kinds: current/baseline, conservative, likely, aggressive, or custom. It has a structured set of up to eleven funnel and financial inputs. These are visitors per month, conversion rate, average ticket, customer acquisition cost (CAC), purchases per year, retention in months, monthly churn, monthly paid media spend, content output per month, team capacity percentage, and gross margin percentage. None of those inputs are required to compute the model. Every output degrades gracefully to null when the inputs it needs are missing. It does not guess. From whatever inputs are present, a pure calculation function derives new customers per month. This function has no database read, no network call, and no side effect. It also derives monthly and annual revenue, annual marketing spend, annual gross profit, lifetime value (LTV), the LTV-to-CAC ratio, and payback period in months. It also gives a capacity flag (ok, tight, or overflow, based on declared team capacity). It gives a 0-to-100 return score. This score is based on annual gross profit and the LTV:CAC ratio. It also gives a separate 0-to-100 risk score. This score is based on payback length, capacity strain, and a weak LTV:CAC ratio. This function runs fresh on every read. It is not computed once and stored. So, a scenario's numbers can never drift from its current inputs. There is no cached, stale output anywhere to accidentally show someone. Every scenario also carries its own required confidence level (low, medium, or high). It also has optional assumptions and limitations text. So, the premise behind a number travels with the number itself. Exactly one scenario per project can hold the "is baseline" flag. Promoting a new one to baseline automatically removes the flag from whichever scenario held it before. This is backed by a partial unique index in the database itself. It is not just application-level discipline. So, "which version is the real baseline" is never a matter of asking around.
Five named scenario kinds are available. These are baseline, conservative, likely, aggressive, and custom. Each carries its own set of up to eleven funnel and financial inputs.
A pure calculation function produces ten distinct outputs. These are new customers, monthly and annual revenue, annual marketing spend, annual gross profit, LTV (lifetime value), LTV:CAC ratio, payback months, a capacity flag, a return score, and a risk score. It has no side effects. It is confirmed to run fresh on every read. It is never stored.
A return-score and risk-score heuristic is used. It is deterministic and banded. This is confirmed directly in the scoring functions' own source. So, two scenarios with the same inputs always produce the exact same scores.
Exactly one exclusive baseline scenario is allowed per project. This is enforced by a database rule. Promoting a new baseline automatically removes the flag from the prior one in the same action.
A required confidence level (low/medium/high) is included. Optional assumptions and limitations text are also on every scenario. So, the premise behind a projection is never separated from the number it produced.
A baseline-comparison helper computes revenue and profit delta percentages. It compares any scenario and the current baseline. It guards against a zero or missing baseline. It does not divide by it.
An explicit on-page warning is built into the interface itself. It states that every output is an estimate based on stated premises. It is not a promise. It should be reviewed before being told to a client.
A "what if" question gets an immediate answer. The answer is recalculated live. You do not have to promise to follow up after rebuilding a spreadsheet. Every number a client sees stays permanently attached to the specific inputs. It also stays attached to the confidence level and stated limitations that produced it. This is because nothing is ever computed once and stored somewhere it could go stale. And a team stops collecting many slightly different "baseline" spreadsheets. The database itself allows exactly one baseline scenario per project at any given moment.
A "what if" question gets an immediate answer. The answer is recalculated live. You do not have to promise to follow up after rebuilding a spreadsheet. Every number a client sees stays permanently attached to the specific inputs. It also stays attached to the confidence level and stated limitations that produced it. This is because nothing is ever computed once and cached somewhere it could go stale. And a team stops collecting many slightly different "baseline" spreadsheets. The database itself allows exactly one baseline scenario per project at any given moment.
Mid-meeting, a client asks what happens to the numbers. They ask if paid media spend drops by roughly a fifth. They also ask if everything else stays steady. The consultant does not promise to "run the numbers and follow up." Instead, they duplicate the current baseline as a new custom scenario. They adjust only the media-spend input. The tool then recomputes every figure immediately. Annual marketing spend falls. Annual gross profit rises by the saved spend. This is because the funnel-driven revenue side of the model does not depend on media spend directly in this simplified method. The risk score shifts slightly based on the updated payback math. The consultant flags the scenario's confidence as "medium." They note in the limitations field that the model assumes conversion rate holds steady. This is true even with less paid traffic. This is an assumption worth testing, not a certainty. The comparison view shows the exact percentage difference in revenue and profit. It compares it against the untouched baseline scenario, side by side, before the meeting ends.

Only the inputs are saved. Every output is recalculated fresh by a pure function every time the scenario is read. These outputs include revenue, LTV (lifetime value), payback, return score, and risk score. So the numbers can never drift from the current inputs.
No. Exactly one scenario per project can hold the baseline flag at a time. This is enforced by a partial unique index in the database itself. Promoting a new baseline automatically removes the flag from whichever scenario held it before. This happens in the same action.
There are five scenario kinds: Current/baseline, conservative, likely, aggressive, and custom. A consultant can create any number of scenarios under any of these kinds for the same project.
No. The return score and risk score classify each scenario's profile. Choosing which scenario to present or act on stays a human decision. The interface itself carries an explicit "estimate, not promise" warning.
The model uses up to eleven funnel and financial inputs. These are visitors per month, conversion rate, average ticket, CAC (customer acquisition cost), purchases per year, retention in months, monthly churn, monthly media spend, content output per month, team capacity percentage, and gross margin percentage. Any part of these can be filled in. Missing inputs produce a null output for whatever metric depends on them. It does not guess.
It is sold by subscription with a published starting price. Exact current values are on the central pricing page.
A projection built in a spreadsheet answers the question correctly on the day it is built. Then it quietly goes stale. This happens the first time someone changes one assumption. It also happens if they forget to update every formula that depended on it. Centriu Oracle's scenario simulator keeps the premise and the output permanently locked together. It never stores the output at all. Eleven funnel and financial inputs feed a pure calculation function. These inputs are visitors, conversion rate, average ticket, CAC (customer acquisition cost), purchase frequency, retention, churn, media spend, content output, team capacity, and gross margin. The function runs fresh on every single read. It produces monthly and annual revenue, LTV (lifetime value), the LTV-to-CAC ratio, payback in months, a capacity flag, and a return score. It also produces a risk score. A consultant names each variant. These can be the current baseline, a conservative case, a likely case, an aggressive case, or a fully custom one. Exactly one scenario per project can hold the exclusive "baseline" flag at a time. The database itself enforces this. So, every comparison is measured against one clear reference point. It is never an outdated guess about which version was the real one.