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

Business-Day and Holiday-Aware Scheduling Automation: The Fix That Scheduled Its Own First Run on a National Holiday

On 2026-09-05, Centriu's own agency shipped a fix. This fix was meant to stop new leads' first-approach dates and client follow-ups from landing on a Saturday or Sunday. That first version worked for weekends specifically. Its very first live calculation scheduled a real next-action for 2026-09-07. This was Independência do Brasil, a national holiday. It was caught the same day before it caused a missed approach. The corrected version shipped hours later. It replaces the fixed weekend-only offset with a real calendar function. This function lists nine fixed-date and eight already-published moveable national holidays across 2026 and 2027. It also has a loop-based resolver. This resolver walks forward one day at a time. It skips Saturday, Sunday, or a listed holiday. It continues until it lands on a day someone is actually working. Then it fixes the time at 9am São Paulo. The same resolver is now the single, shared mechanism behind every "next action" timestamp Orbit writes. So a lead's first approach, a follow-up date entered by a salesperson, and a nurture-sequence step all land on a real business day. They do not land on a calendar day that happens to fall five characters after "weekday."

Quero resolver isso

A fix that only handles weekends looks complete until a holiday falls on a weekday

Handling Saturday and Sunday correctly covers the overwhelming majority of calendar days by definition — five out of seven. This is exactly what makes a weekend-only fix look finished the moment it ships. The gap only becomes visible on the specific weekday, a handful of times a year. This is when a real holiday sits where a business day is otherwise assumed. By then, the fix has already scheduled something for a day nobody is actually working.

Handling Saturday and Sunday correctly covers the overwhelming majority of calendar days by definition — five out of seven — which is exactly what makes a weekend-only fix look finished the moment it ships. The gap only becomes visible on the specific weekday, a handful of times a year, when a real holiday sits where a business day is otherwise assumed, and by then the fix has already scheduled something for a day nobody is actually working.

Quero resolver isso

How the gap was caught the same day, and how the fix became a shared platform primitive

The first version of this fix shipped the morning of 2026-09-05. It replaced a bare `(now() + interval '2 days')::date`. This calculation had two separate real defects of its own. A Friday lead landed its next action on a Sunday. Also, a date with no time attached rendered on screen as 9pm the day before. This is because a plain date defaults to midnight UTC. That first fix corrected both. It resolved Saturday to the following Monday and Sunday to the following Monday. It also explicitly attached 9am São Paulo time to the result.

That version's own first live run happened the same morning. It computed a next-action date of 2026-09-07 for a batch of real leads and tasks. This was Brazil's Independence Day, a national holiday nobody works. The owner caught it before it caused a missed approach. A second migration shipped later the same day. It replaced the weekend-only check with a genuine calendar. This is a function listing nine holidays that fall on the same calendar date every year. These are New Year's Day, Tiradentes, Labor Day, Independence Day, Our Lady of Aparecida, All Souls' Day, Proclamation of the Republic, Black Consciousness Day, Christmas. It also lists eight specific moveable-holiday dates already published for 2026 and 2027. These are Carnival and Corpus Christi, which shift with the liturgical calendar and cannot be expressed as a fixed month-and-day.

The resolver itself changed from a single Saturday/Sunday branch into a loop. It starts from the requested date. It steps forward one day at a time. It is capped at ten iterations as a safety bound. It checks each candidate day against both the weekend condition and the holiday-lookup function. It stops on the first day that is neither. The final timestamp is always fixed at 9am São Paulo time. This replaces the earlier bare-date approach entirely. This resolver lives in the database as one shared function. So every place across Orbit that writes a "next action" timestamp now calls the identical calendar-aware logic. This includes a new lead's first-approach date, a salesperson's own follow-up entered through the record-updating tool, and a nurture-sequence step. This is better than each write path carrying its own copy of a business-day rule that could drift out of sync with the others. A corrective data migration in the same change moved the specific handful of real tasks and deals already miscalculated by the first version's weekend-only logic onto their correct next business day.

Ver como funciona

What is actually built today

A shared database function resolves any timestamp to the next real business day. It skips Saturday, Sunday, AND any of seventeen specifically listed Brazilian national holiday dates across 2026-2027.
The resolver distinguishes fixed-date holidays. These are checked by month-and-day, recurring every year. It also distinguishes moveable ones. These are checked against explicit published dates, since their calendar position shifts year to year.
Every resolved timestamp is anchored to 9am São Paulo time. This replaces an earlier bare-date calculation. Its lack of a time zone caused it to display as the previous evening on screen.
Every 'next action' timestamp Orbit writes now calls this identical shared function. This includes a new lead's first approach, a salesperson's follow-up, and a nurture-sequence step.
A same-day corrective migration moved the specific real records miscalculated by the fix's own first, weekend-only version onto their correct business-day timestamp.
Every recurring or daily routine belonging to a sales-facing role was separately updated to only run on weekdays. So scheduled outreach cannot itself fire on a day the underlying dates already skip.

Conhecer os recursos

What changes operationally

No next-action timestamp written anywhere in Orbit can land on a weekend or on one of seventeen specifically listed Brazilian national holidays through 2027. This closes a gap that, in its own first version, had already scheduled a real batch of client contact for a day the entire team was off.

No next-action timestamp written anywhere in Orbit can land on a weekend or on one of seventeen specifically listed Brazilian national holidays through 2027, closing a gap that, in its own first version, had already scheduled a real batch of client contact for a day the entire team was off.

Quero esses resultados

A fix that almost scheduled its own mistake (illustrative framing of the actual measured finding)

A lead is registered on a Friday afternoon. Under the very first version of this fix, its first-approach date correctly skips the coming weekend and lands on Monday. However, that Monday happens to be a national holiday nobody works. The batch of real records computed that same morning did exactly that. Under the corrected version, the identical Friday-afternoon lead resolves past both the weekend AND the holiday. It lands on the next day someone is genuinely at their desk.

Conversar sobre meu caso

Como começar

Começar agora

Perguntas frequentes

Why did the first version of this fix schedule something on a holiday?

It only checked for Saturday and Sunday. Its own first live calculation, the same morning it shipped, computed a next-action date that happened to fall on Brazil's Independence Day. It was caught the same day and corrected with a real holiday calendar hours later.

Which holidays does the calendar actually list?

Nine fixed-date national holidays (New Year's Day, Tiradentes, Labor Day, Independence Day, Our Lady of Aparecida, All Souls' Day, Proclamation of the Republic, Black Consciousness Day, Christmas) plus eight explicit moveable-holiday dates already published for 2026 and 2027 (Carnival and Corpus Christi).

What time does a resolved date land on?

9am, São Paulo time. This replaces an earlier bare-date calculation that had no time zone attached and could display as the previous evening on screen.

Does every part of Orbit use this same calendar logic?

Yes. It is a single shared database function. Every place that writes a next-action timestamp calls it. This is better than each write path carrying its own separate business-day rule.

What happened to the records miscalculated by the first version?

A same-day corrective migration moved the specific handful of real tasks and deals affected by the weekend-only logic onto their correct business-day timestamp.

What does Centriu Axis 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 Axis keeps every scheduled action on a real business day

Quero resolver isso