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

Automatic Lead Capture and Pipeline Handoff Automation: Fixing a Chain That Had Never Once Fired

A check on Centriu Flow found its automation chain was completely broken. It had zero runs in the product's history. This was due to four separate reasons. The widget intake saved a form submission but never created a contact record. Automation dispatch needs a contact record. No intake path actually called the automation engine. The deployed worker linked its dispatch event to a name that no longer existed. The executor only accepted one type of input, but the dispatcher sent another. Two database triggers now fix half of that chain for every submission. This includes both widget and form submissions. One trigger automatically creates or updates the matching Flow contact. It uses the account and email before anything else runs. A second trigger sends out any active "form submitted" nurture sequence. This is a fire-and-forget call. It only happens after checking that a sequence is active. A third trigger was also fixed in the same release. It turns a good submission into a real company, contact, and deal inside Orbit's pipeline. It checks for existing open deals to avoid duplicates. It is also protected so that no bug in the connection can ever stop lead capture itself.

Quero resolver isso

Why "the automation looks configured" is not the same as "the automation runs"

A marketing automation feature can look completely finished from the settings screen. A trigger can be selected. An email can be written. A wait time can be set. But it still may never run a single time. This happens if any link is broken in the chain. This chain goes from "someone submits a form" to "the automation engine receives that event." The settings screen cannot show this problem. The only way to find it is to follow what actually happens to a real submission. You must trace it from start to finish, through every way it can be received.

A marketing automation feature can look completely finished from the settings screen — a trigger selected, an email drafted, a wait period configured — and still never fire a single time, if any one link in the chain between "someone submits a form" and "the automation engine receives that event" is broken. The settings screen has no way to show that gap; the only way to find it is to trace what actually happens to a real submission, end to end, through every intake path.

Quero resolver isso

How Centriu Flow rebuilt the chain, and fail-closed the part with real consequences if it broke

The first check, written in the fix's own notes, listed four separate problems. It was not just one vague "automation doesn't work" issue. The widget intake wrote a form submission row. But it never added its contact reference. The dispatch logic needs that reference to exist. No intake path called the automation engine at all. The deployed handler for one intake route used a function name that was no longer active. The error was hidden instead of shown. The deployed worker's own event-routing map pointed a dispatch event type to another name that also no longer existed. The executor accepted one input name, but the dispatcher sent a different one. This page only talks about the two fixes that are in the database as triggers. You can check these directly against the fix. You do not need to check a deployed function's current state.

The first trigger runs BEFORE a form submission row is even added. If the incoming data has a valid email, and the submission does not already have a contact reference, it looks for an existing Flow contact. It uses that email under the same account and reuses it. It updates a last-seen time. Or, it creates a new contact from the name, phone, and company fields in the submission. This must happen before the row is added. This way, everything that follows, like the dispatch trigger and the Orbit connection, sees a contact reference right away. It does not have to wait for a later update.

The second trigger runs AFTER that row is added. It sends out any matching nurture sequence. But it only does this after checking that the account has an ACTIVE automation. This automation must be set for a "form submitted" trigger. If no such automation exists, the trigger stops. It does not make a network call. If one does exist, the dispatch is a fire-and-forget HTTP call to the automation engine. It uses a service-role credential for security. This credential comes from the platform's secret storage. It is not built into the trigger itself. This is the same method the platform's scheduled jobs already use.

A third system, the Flow-to-Orbit connection, turns a good submission into a real sales-pipeline record. It finds the lead's name, email, phone, and company. It prefers the newly-created Flow contact. If not available, it uses the submission's raw fields. It checks if the organization has an open pipeline stage. It also checks for an active profile to own the deal. If either is missing, it stops quietly. It does not create a bad record. Then it checks for an existing Orbit contact. This contact must have the same email and already be linked to an OPEN deal. If one exists, the connection adds a note to that deal's timeline. It does not create a duplicate. Otherwise, it creates a truly new company, contact, and deal. It marks the source as "site." It also sets a reminder for a next action one day later.

Both triggers that handle the lead right when it arrives have the same clear safety rule. This rule is written in their error-handling notes. The connection that sends a lead to Orbit "can never take down lead capture itself." Any unexpected error inside either trigger is caught. It is logged as a warning for someone to check later. The original submission row still gets saved. A bug in the automation or CRM handoff means "this one lead did not get its nurture email or its deal yet." It never means "the form silently failed to submit."

Ver como funciona

What is actually built today

A BEFORE INSERT trigger that finds or creates the matching Flow contact for every form or widget submission. It uses the account and email. This happens before any other logic runs.
An AFTER INSERT trigger that sends out an active "form submitted" nurture automation. This is a fire-and-forget call. But it only happens after checking that one is active. So, an account with no automation set up does not make a network call.
A separate AFTER INSERT trigger that creates a real Orbit company, contact, and deal from a good lead. Or, if a matching open deal already exists, it adds a note to the timeline instead of creating a duplicate.
Two quiet, safe exit conditions on the Orbit connection. No open pipeline stage is set up. Or, no active profile to own the deal. Both skip cleanly instead of creating a bad record.
A fail-closed guarantee for errors on both lead-arrival triggers. Any unexpected error is caught and logged as a warning. The original submission always still saves.
Agent-built nurture automations that clearly state who enters and who does not. They also state the message limit and the exit condition. Agent-written email campaigns always start as a draft. They need human approval before anything is sent.

Conhecer os recursos

What changes operationally

A website form submission now reliably becomes a real contact. You can search for this contact. An active nurture sequence, when set up, reliably runs. It does not silently fail to run. A good lead reliably reaches the sales pipeline as a deal. It does not depend on someone manually adding it again. Both triggers are designed to fail safely. They always save the original submission. So, a future bug in either system means a missed nurture email or a missed deal creation. It never means a lost lead.

A website form submission now reliably becomes a real, queryable contact, an active nurture sequence (when one is configured) reliably fires instead of silently never running, and a qualifying lead reliably reaches the sales pipeline as a deal rather than depending on someone manually re-entering it. And because both triggers fail closed on the side of preserving the original submission, a future bug in either mechanism degrades to a missed nurture email or a missed deal creation — never to a lost lead.

Quero esses resultados

A lead who already has an open deal (example, not a real client)

Someone submitted a contact form two weeks ago. They already have an open deal in Orbit from that first submission. They fill out a second form on a different page of the same site. For example, they request a quote. The connection finds the existing open deal. It matches by email. Instead of creating a second, competing deal for the same person, it adds a note to the timeline of the existing deal. This way, the salesperson sees both signals on one record. They do not see two separate leads.

Conversar sobre meu caso

How to get started

Começar agora

Frequently asked questions

Why did Flow's automation chain never fire before this fix?

Four separate, named defects: the widget intake never created a contact for the submission, no intake path actually called the automation engine, the worker mapped its dispatch event to a slug that no longer existed, and the executor expected a different argument name than the dispatcher sent.

How does a form submission get a contact now?

A BEFORE INSERT trigger finds an existing Flow contact by account and email. Or, it creates a new one from the submission's own fields. This happens before anything else runs.

Does every form submission create a deal in Orbit?

No — only when the organization has an open pipeline stage and an active profile to own it; both missing conditions cause the bridge to exit silently rather than create a malformed record.

What happens if a lead who submitted before submits again?

If a matching Orbit contact already has an OPEN deal, the connection adds a note to that deal's timeline. It does not create a duplicate.

Can a bug in the automation or Orbit-handoff triggers break lead capture itself?

No — both triggers catch any unexpected error. They log it as a warning. The original form submission still saves no matter what.

What does Centriu Flow 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 Flow captures leads and hands them to the pipeline automatically

Quero resolver isso