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

Client Portfolio Segmentation and Next-Best-Action Automation: Log an Event, Get a Segment and a Play

Knowing which fifty accounts and leads need attention this week usually means someone scrolling a spreadsheet by memory. Centriu Vesper computes it instead. Log an event against an account or lead — a purchase, a proposal sent, a renewal, a follow-up, fourteen real event types in total. The recency/frequency/monetary engine scores it. It classifies it into one of ten real segments (from Champions down to Lost). It attaches a concrete next-best-action: a goal, a message angle, a suggested offer, a routine, and a task list. This is adjusted further by what the entity's own most recent event was. The scoring and the segmentation are automatic and instant. The event log itself is something you build. You can enter it directly or import it by CSV. Today, it is not an automatic feed from a connected CRM.

Quero resolver isso

Why "who needs attention this week" is usually a memory exercise

A portfolio of accounts and leads is not one problem. It is dozens of small ones happening at different speeds. One account has gone quiet after being a reliable renewal for two years. Another lead engaged once and never came back. A third is close to a decision and just needs one more nudge. Answering "who needs attention and what should I actually do about it" for all of them at once is exactly the kind of task a spreadsheet handles badly. It can hold the data, but it cannot classify it. It certainly cannot suggest what to say to each one. The result is that attention goes to whoever is loudest or most recently top of mind. It does not go to whoever the underlying pattern says actually needs it.

A portfolio of accounts and leads is not one problem. It is dozens of small ones happening at different speeds. One account has gone quiet after being a reliable renewal for two years. Another lead engaged once and never came back. A third is close to a decision and just needs one more nudge. Answering "who needs attention and what should I actually do about it" for all of them at once is exactly the kind of task a spreadsheet handles badly. It can hold the data, but it cannot classify it. It certainly cannot suggest what to say to each one. The result is that attention goes to whoever is loudest or most recently top of mind. It does not go to whoever the underlying pattern says actually needs it.

Quero resolver isso

How Centriu Vesper scores, segments and suggests the next move

Every account or lead in the portfolio accumulates events over time. There are fourteen real event types. These include a first contact, a meeting, a proposal sent, a stage advance, a purchase, a closure, a renewal, a repurchase, an upsell, a reactivation, a follow-up, a visit, or an opportunity won or lost. From that event history, the engine computes three raw values per entity. These are days since the last event, the count of events inside a configured time window, and a monetary value. This value is either declared directly or summed from the window's monetary events. The engine scores each on a 1-to-5 scale using one of two real modes. Quintile scoring computes the cutoffs fresh from the actual portfolio's own distribution every time it runs. Fixed thresholds are defined once and kept stable. The three scores combine, by configurable weights, into a single RFM score. A real classification rule reads the three individual scores to assign one of ten segments. A genuinely high score on all three lands in Champions. A high recency score with low frequency and no prior activity lands in New. A low recency score combined with a history of high frequency and value lands in the Can't Lose segment. Each segment carries its own next-best-action template. This includes a goal, a message angle, a suggested offer, a routine of specific actions, and a task list. The template adapts to the entity's own recent history. An entity in a cooling segment whose last event was a proposal gets a follow-up task and message angle about that specific proposal. An entity new to the portfolio with two or fewer events gets an onboarding call added. A Champion with a recent purchase or renewal gets a case-study request and a referral-program suggestion layered on top. Individual entities can be manually overridden on their recency window, their event count, or their last-event date. This is for cases where an offline interaction is not reflected in the event log. Computation runs as a real, authenticated background job with a concurrency guard. A project cannot have two computations running at once. Every run's snapshot is retained. This shows how a portfolio's segment mix has shifted over time, not just its current state.

Ver como funciona

What is actually built today

Ten real RFM segments — Champions, Loyal, Potential Loyalist, New, Promising, Need Attention, About to Sleep, At Risk, Can't Lose, Lost — each with a concrete classification rule, not just a label.
Two real scoring modes: quintile scoring with cutoffs computed fresh from the portfolio's own distribution on every run, or fixed thresholds the business sets and keeps stable.
A next-best-action template per segment — goal, message angle, suggested offer, routine and task list — that adapts based on the entity's own most recent actual event, not just its segment label.
Fourteen real event types spanning first contact through purchase, renewal, repurchase, upsell, reactivation and opportunity won or lost, with monetary events aggregated for the M score.
Per-entity manual overrides for the recency window, event count and last-event date, for exceptions the event log alone would not capture.
A real, authenticated, asynchronous compute job per project with a concurrency lock preventing two simultaneous runs on the same portfolio.
A CSV import path for event data, alongside direct entry, both feeding the same engine.
Retained snapshot history, so segment shifts across a portfolio are visible over time rather than only as a current-state view.
Entities typed explicitly as accounts or leads, kept as Vesper's own portfolio records.

Conhecer os recursos

What changes operationally

The structural change is that portfolio triage stops depending on whoever is easiest to remember. It starts running on a rule applied identically to everyone. This is computed from an actual event history rather than an impression of one. A quietly cooling high-value account gets caught by the recency and frequency scores directly, not by luck. A brand-new lead and a long-dormant one get genuinely different next steps instead of the same generic outreach. Centriu attaches no figure to what that is worth. It depends entirely on portfolio size, deal values and how much attention was already being paid manually.

The structural change is that portfolio triage stops depending on whoever is easiest to remember. It starts running on a rule applied identically to everyone. This is computed from an actual event history rather than an impression of one. A quietly cooling high-value account gets caught by the recency and frequency scores directly, not by luck. A brand-new lead and a long-dormant one get genuinely different next steps instead of the same generic outreach. Centriu attaches no figure to what that is worth. It depends entirely on portfolio size, deal values and how much attention was already being paid manually.

Quero esses resultados

A cooling account gets a specific play, not a generic one (illustrative scenario, not a real client)

An account that renewed twice logs no new events for several weeks after a proposal for an upsell was sent. On the next scoring run, its recency score drops enough to move it from Loyal into Need Attention. Because the engine checks the entity's own last event, not just its new segment, it finds that event was specifically a proposal. The next-best-action for this account is not the generic "we miss you" template. It is a follow-up task on that specific proposal, with a message angle asking directly whether they want to move forward.

A separate lead who engaged once, three months ago, and never returned scores into Lost. Its next-best-action is a lighter touch entirely. This is a short survey asking what could have been done differently. It has a much longer routine than the cooling account above got. Lost and Need Attention are structurally different situations even though both involve reduced recent activity.

Neither classification required anyone to remember these two relationships specifically. Both came from the same event log and the same deterministic rule, applied consistently across everyone in the portfolio.

A cooling account gets a specific play, not a generic one (illustrative scenario, not a real client)

Conversar sobre meu caso

How to start

Começar agora

Frequently Asked Questions

Does the event data come in automatically from a CRM?

No — not today. Events are entered directly in Vesper or imported by CSV. An automatic connection to Orbit, Flow or another system is future work in the product, not a current feature.

How many segments does the engine classify entities into?

Ten: Champions, Loyal, Potential Loyalist, New, Promising, Need Attention, About to Sleep, At Risk, Can't Lose, and Lost — each with a concrete rule based on the recency, frequency and monetary scores.

Does the next-best-action change based on what actually happened with that specific account, or is it generic by segment?

Both — a segment has a default template. The engine checks the entity's own most recent real event. It adjusts the task list and message angle when a more specific pattern applies, such as a recent proposal or very few total events.

Does the system automatically send the suggested message or offer?

No. The next-best-action is a suggestion — goal, angle, offer, routine and tasks — for a person to act on. Nothing is sent automatically.

Can I override the score for a specific account manually?

Yes — the recency window, event count, or last-event date can be overridden per entity. This is for a case the event log alone does not fully capture.

Can two people accidentally run the scoring calculation at the same time?

No — the compute job is a real, authenticated background job with a concurrency lock. A second attempt while one is already running is rejected rather than allowed to run in parallel.

What does Centriu Vesper cost?

It is sold by tiered subscription with plans defined centrally. Exact current values are on the central pricing page.

Ainda tenho dúvida

See how Centriu Vesper segments a client portfolio

Knowing which fifty accounts and leads deserve attention this week usually means someone scrolling a spreadsheet by memory. Centriu Vesper computes it instead. Log an event against an account or lead — a purchase, a proposal sent, a renewal, a follow-up, fourteen real event types in total. The recency/frequency/monetary engine scores it. It classifies it into one of ten real segments (from Champions down to Lost). It attaches a concrete next-best-action: a goal, a message angle, a suggested offer, a routine, and a task list. This is adjusted further by what the entity's own most recent event was. The scoring and the segmentation are automatic and instant. The event log itself is something you build. You can enter it directly or import it by CSV. Today, it is not an automatic feed from a connected CRM.

Quero resolver isso