The CRM that keeps every opportunity moving
Centralize contacts, deals, tasks and follow-ups in a visual pipeline with quality gates, cadences that keep the salesperson accountable and a complete history. Orbit leaves no opportunity without an owner and a next step.
Quality gates · Stalled-deal alert · Cadence with a human lock · Audit trail
Pipeline in cadence
Illustrative dataIllustrative data — no real amounts or companies.
Why Orbit
The problem is not generating leads — it is moving forward those already in
Scattered contacts, follow-up that arrives late, opportunities stalled without an owner or a next step. The pipeline cannot depend on the salesperson's memory.
Opportunities cool off out of forgetfulness
The lead existed, the conversation happened — and the sale is lost because nobody came back on the right day. Without a deadline and a recorded next step, follow-up becomes an intention, and intentions do not close deals.
The history lives in each salesperson's memory
What was discussed, proposed and agreed sits in notebooks, chats and side spreadsheets. When someone goes on vacation — or leaves the company — the context goes along.
The manager cannot see where the pipeline stopped
Without a per-stage reading, bottlenecks only show up at the end of the month. The manager finds out late which deals were left without an owner, a deadline or movement.
What changes
From the contact coming in to the recorded outcome
The path Orbit organizes — each step with an owner, a deadline and a record.
“No opportunity without an owner, a deadline and a next step.”
- The contact comes in — through the site form, the API or an import
- The history is centralized on the deal
- Every deal gets an owner
- And a pipeline stage, with a quality gate
- And a next step with a due date
- Every interaction enters the timeline
- The stalled list points at what got stuck
- The cadence demands the follow-up — and locks until the human touch is done
- The manager sees what stalled; the outcome records the reason
- The history remains — won or lost
What Orbit does
Seven capabilities to keep the pipeline moving
From registering the contact to the outcome report — with gates, cadences and the stalled-deal alert in between.
Kanban pipeline with quality gates
Multiple drag-and-drop pipelines, customizable stages (position, won and lost) and a list view with filters and presets such as "no contact for 14 days". Quality gates per stage: until the requirements are met, the deal does not advance on the Kanban.
Complete contacts and companies
Records with tax IDs (CNPJ/CPF), decision-maker and address; custom fields per organization; and a scan that flags possible duplicates by document, email and name — for you to review and dismiss what is not one. Initial load is done through the inbound API.
What stalled surfaces on its own
Every open deal should have a future activity. The ones that do not land in "no next step"; the ones without movement for days land in "stalled deals". Both lists open on the daily Dashboard, feed deal health and the next-action suggestion — "stalled for X days → create a follow-up".
Follow-up cadences with a human lock
Sequences with email, wait, task and note steps, with variables such as {{contato}} and {{empresa}}. The blocking step — call, WhatsApp, visit — locks the cadence until the salesperson completes it: the cadence keeps the salesperson accountable.
Stage automations
Rules on deal creation and on stage change, executed right away in the database, with conditions. Four actions: create a task, note on the timeline, change priority and change the owner.
Outbound email and WhatsApp touch
Email sent from inside the deal, with templates, attachments and everything recorded in the history. The WhatsApp touch opens the conversation in your own WhatsApp with a ready message — and records the touch on the timeline.
Forecast, funnel and team reports
Forecast by band — Commit, Best Case and Pipeline — each with its nominal value and deal count; per-rep performance; prospecting funnel with average ticket and time to decision; data quality; and the loss-reason report, with its own catalogue.
Want to see Orbit on your own pipeline design?
Talk to a specialistIn action
The pipeline and the deal, side by side
Two illustrative views of what Orbit shows day to day: the pipeline with its quality gates, and the detail of a deal with a cadence under way.
Sales pipeline
Illustrative dataContact made
Company A
Ana · 1 day in stage
Company B
Rui · 3 days in stage
Proposal sent
Company C
Ana · 9 days in stage
Deadline overrun — stalledCompany D
Lia · 4 days in stage
Quality gate · requirements 2/3Negotiation
Company E
Rui · 2 days in stage
Next step scheduledDeal detail
Illustrative dataCompany C
Timeline
Illustrative data — no real amounts, companies or people.
How it works
Seven steps — with the manager and the salesperson in charge
The path of a deal inside Orbit, from first contact to the recorded outcome. Review is human; the system organizes and follows up.
From entry to history
Illustrative dataThe contact comes in
Through your site's public form, the inbound API with token and scopes, or on-screen registration.
The deal gets an owner
Every deal has an owner — and each salesperson sees what is theirs, according to roles and permissions.
Stage and quality gate
The deal enters a pipeline stage. The quality gate defines what must be complete for it to advance — and without that, it does not.
The cadence steps in
Scheduled emails go out with the configured sender; manual touches — call, WhatsApp, visit — lock the sequence until they are completed.
The manager reviews what stalled
Stalled deals and deals with no next step surface for review. People decide where they go.
The outcome is recorded
Won or lost — and a loss carries a reason from the catalog, with source channel, presented proposal and objections.
The history remains
The complete timeline stays available and the reports aggregate forecast, performance and loss reasons.
Flow: the contact arrives through a public form, the inbound API or on-screen registration; the deal gets an owner; it gets a stage with a quality gate; the cadence schedules follow-ups and locks on manual touches; the manager reviews what stalled (control point); the outcome is recorded — won, or lost with a reason from the catalogue; the history stays available.
The stalled-deal and overdue-activity triggers run on demand. Automations do not send emails or messages: the actions are creating a task, noting on the timeline, changing priority and changing the owner. Activity notifications arrive via Web Push.
Where Orbit begins
Orbit takes care of the contact that has already come in
Two systems for different moments of the same commercial journey — used together, each on its own leg.
“Orbit begins when the contact comes in.”
Before the conversation
Finding, researching and prioritizing who is worth talking to is earlier work — done outside Orbit: by the team itself, through a referral or from a list that already exists.
After the entry: Orbit
Orbit organizes the contacts that already entered the operation: pipeline, owner, deadline, next step, follow-up and outcome. It is the work of moving forward to a decision.
Orbit does not go looking for new contacts: it organizes the ones that have already come in — each with a stage, an owner and a next step.
Where Orbit talks
Two confirmed integrations: Oracle and Flow
What comes in and what is read — confirmed in code, with no ecosystem promise.
Oracle → Orbit
Meetings and forwardings from Oracle become an opportunity or an activity in Orbit — with human approval and a quality lock: only what is marked as a real opportunity enters the pipeline.
Learn moreConfirmed integrationFlow × Orbit
Flow reads Orbit's pipelines and stages to use in its own flows. It is read-only: pipelines and stages keep being edited in Orbit.
Learn moreNot everything talks to everything. The two confirmed exchanges are: approved forwardings from Oracle become an opportunity or an activity in Orbit, and Flow reads Orbit's pipelines and stages (editing stays in Orbit). If your operation depends on a specific connection between systems, talk to us before contracting.
Control and limits
Governance in the database, not in the pitch
Access and limit rules are enforced where the data lives.
Isolation per organization
Each organization sees only its own data, with isolation enforced in the database (RLS).
Roles and permissions
Admin, manager and sales, with permissions configurable across dozens of keys — and each salesperson sees what is theirs.
Audit trail
Relevant actions are recorded: who did what and when — available to management.
Plan limits enforced by trigger
Starter includes 10 users, 3 pipelines, 5,000 deals and 10,000 contacts; Pro includes 15 users, 10 pipelines, 50,000 deals and 100,000 contacts; Max has no cap. Volume caps are checked by a trigger in the database itself, before the write — they do not depend on the interface behaving.
Security is a continuous practice, not an absolute promise. The protections above describe the product's current design.
Who it is for
For whoever moves opportunities forward to a decision
Orbit comes in where contacts already flow in — and what is missing is conduction with a deadline and an owner.
B2B sales teams
Consultative sales with long cycles: every opportunity with an owner, a stage, a deadline and the cadence demanding the next touch.
Agencies and consultancies
Proposals under conduction: quality gates define what must be ready before advancing — and the history records what was agreed.
Service and SaaS operations
Recurring pipeline with multiple pipelines — each commercial process with its own stages and quality gates.
Managers who decide with data
Forecast by band — Commit, Best Case and Pipeline — per-rep performance and aggregated loss reasons, to adjust the pipeline based on what actually happened.
System plans
Three tiers that unlock more as you grow. On Max, you get access to everything.
Starter
Essentials to start
- Visual Kanban pipeline with your own sales stages
- Contacts, companies and activities linked to the deal
- Daily dashboard: tasks, stalled deals and deals with no next step
- Custom fields, teams and owners
- Pipeline, sales and per-rep performance reports
Pro
Full operation
- Visual Kanban pipeline with your own sales stages
- Contacts, companies and activities linked to the deal
- Daily dashboard: tasks, stalled deals and deals with no next step
- Custom fields, teams and owners
- Pipeline, sales and per-rep performance reports
- Multiple pipelines, each with its own stages
- Quality gates: a deal cannot advance with a pending requirement
- Stage automations: create task, note, priority and owner
- Follow-up cadences with a blocking task and email
- Proposals with e-signature and a client portal
Max
EverythingEverything unlocked
- Visual Kanban pipeline with your own sales stages
- Contacts, companies and activities linked to the deal
- Daily dashboard: tasks, stalled deals and deals with no next step
- Custom fields, teams and owners
- Pipeline, sales and per-rep performance reports
- Multiple pipelines, each with its own stages
- Quality gates: a deal cannot advance with a pending requirement
- Stage automations: create task, note, priority and owner
- Follow-up cadences with a blocking task and email
- Proposals with e-signature and a client portal
- Unlimited pipelines, deals, contacts, automations and cadences
- Audit trail and exports that leave a record
- Privilege-based PII masking and GDPR-style anonymization
- Inbound API with token and scopes, plus outbound webhooks
Questions
Frequently asked questions
What is Centriu Orbit?
It is Centriu's pipeline CRM. It organizes contacts, companies, deals, tasks and follow-ups in visual pipelines with quality gates, lists of what stalled, cadences with a human lock, outbound email with history and reports on forecast, funnel and loss reasons. All with isolation per organization and an audit trail.
Does Orbit find new customers for me?
No. Orbit works after the contact has come in: pipeline, owner, deadline, next step, follow-up and outcome. Finding and qualifying someone who is not a contact yet is earlier work, done outside Orbit.
Does Orbit replace the CRM I already use?
It can. The inbound API with token and scopes creates contacts, deals and activities from the systems you already use, and your site's public form drops straight into the pipeline. To be direct: spreadsheet import is not available yet — the initial load goes through that API today, and this page will keep saying so for as long as it is true.
Which channels does Orbit cover?
Honestly: Orbit sends email from inside the deal — with templates, attachments and a configured sender — and records everything in the history. The WhatsApp touch opens the conversation in your own WhatsApp with a ready message and records the touch on the timeline. Orbit does not receive emails, has no telephony and does not answer WhatsApp from inside the CRM.
How does Orbit show what got stuck?
Through two lists, not a per-stage deadline. Every open deal should have a future activity: the ones that do not land in "no next step", and the ones without movement for days land in "stalled deals". Both open on the daily Dashboard, with a "see all" link to the full list. There is no automatic escalation and no warning before a due date: Orbit points, the review is human.
Does the system follow up on its own?
Partly — on purpose. Cadences send scheduled emails with the sender you configured, wait the intervals and create tasks. Human touches — call, WhatsApp, visit — lock the cadence until the salesperson completes them. Orbit demands the follow-up; it does not talk to your client on its own.
Does Orbit negotiate or decide on its own?
No. Orbit organizes, demands and records. Qualifying, negotiating, advancing stages and closing is the team's job — including at the quality gates, where advancing depends on the requirements being met.
Can I have more than one pipeline?
Yes. Pipelines are independent, with customizable stages — position, won and lost — and their own quality gates on each stage. Every commercial process can have its own design. The plan sets how many pipelines fit, and that cap is enforced in the database.
How is each organization's data protected?
Isolation per organization is enforced in the database (RLS), roles and permissions control who sees and does what — each salesperson sees what is theirs —, relevant actions enter the audit trail and plan limits are enforced in the database. Security is a continuous practice, not an absolute promise.
Put every opportunity in motion
Bring your contacts and deals into a pipeline with an owner, a deadline and a next step — and let the cadence demand what must not be forgotten. Request a demo.