jataíOne journey. Four pieces. No lead forgotten.
Jataí works as a four-piece journey: Pólen (discovery) finds organizations and contacts in public sources you declare; Enxame (agents) qualifies with cited evidence and writes the first contact; Rotas (sequences) send touches on time and cancel when the person replies; Entrega (handoff) creates the lead in your CRM only once it is a conversation, with the history attached.
From public source to CRM, what happens to each organization — and when you step in.
From Pólen to Entrega.
- PÓLENdiscovers organizations and contacts
- organization releasedENXAMEqualifies and writes the contact
- contact writtenROTASfollow up on time
- responseENXAMEtriages the response and proposes the reply
- conversationENTREGAhands off to your CRM, with the history
↺ Your CRM reports back: whoever moved forward leaves the Rota.
What happens, in order.
1. You declare.
Public sources, brand profile (industry, size, region, job title), tone of voice, destination CRM, and each operator's approval limit. A new brand starts in shadow mode: nothing goes out until you turn it off.
2. Pólen discovers.
It scans the sources you declared and returns records: organization, contact, source, signals. It does not repeat an organization it has already visited. → Pólen
3. Enxame qualifies and writes.
Fit, cited evidence for every signal, angle, and touch 1 written for the person. The operator approves within their approval limit. → Enxame
4. Rotas follow up on time.
Touches with the waits the brand defined, from the brand's domain. They stop when the person replies, a human takes over, or they ask to opt out; whoever said "not now" comes back in the recycling Rota. → Rotas
5. Entrega hands off to the CRM.
Only the conversation. With the history. Without touching the stage. And your CRM reports back, to cancel Rotas for anyone who moved forward. → Entrega
What is yours, what is Jataí's.
| Moment | You | Jataí |
|---|---|---|
| Declare sources, profile, tone | ✓ | guides |
| Discover and qualify | follow along | ✓ |
| Write each touch | approve, within your approval limit | ✓ |
| Send and follow up | — | ✓ |
| Read the response and propose a reply | approve, within your approval limit | ✓ |
| Negotiate, propose, close | ✓ | never |
| Move the stage in the CRM | ✓ | never |
A working day, from Pólen to Entrega.
- You ask in one sentence for "40 language schools in Goiás". Pólen starts from the public CNPJ registry and the sources you declared and finds 38 new organizations. None repeated.
- Enxame qualifies each one with cited evidence and writes 38 first contacts. They wait in the Review queue; the operator reads, edits if they want and releases, within their approval limit.
- Rotas go out from the right brand's domain, within the daily quota and the spacing window between brands.
- Helena replies "send pricing, the committee meets on the 22nd". Her Rota cancels on its own. Enxame proposes a reply anchored on the 22nd.
- Entrega puts Helena in the pre-CRM, with the history. When the card reaches the last step, she goes to your CRM with temperature 82. Stage in the CRM: yours, untouched.
Illustrative example: times and numbers vary by brand and by search profile.
Three things we do not do.
We do not sell lists.
Organizations come from public sources you declare, and you see where each contact came from.
We do not close sales.
Jataí hands off the started conversation; the negotiation happens in your CRM, with your rep.
We do not touch your pipeline.
We write activity and temperature in the CRM — never the stage. Two systems fighting over the same field destroy the team's trust in the CRM, and that does not come back.
The same journey, thirty-five times, without collisions.
Each brand has its own sending domain, isolated reputation, and its own search profile. Nothing gives away a common origin, and two of your brands never write to the same company in the same week. How it works for groups and agencies →
Frequently asked questions
How long until the first Colheita (harvest)?
It depends on the sending domain: a new domain needs to be warmed up before sending volume, and the first reply comes after the first touches of the Rota. We do not promise meetings per month.
Do I need to configure a lot?
Configuring the brand — sources, profile, tone, destination CRM, and approval limits — is the up-front work. After that, the day-to-day time is spent on approvals, and it shrinks as the approval limit goes up.
Can I use just one piece?
No. The four exist because the gap between them is the problem: discovering without writing well, or writing without stopping when the person replies, lets the lead go cold in the middle.
Does Jataí work for B2C?
The journey is B2B: the organization comes before the person. It was not designed for B2C.
What if I already use Apollo, Instantly, or Ramper?
See the comparisons; Jataí replaces the discovery, sequencing, and triage layers, and coexists with your CRM.