Step weight and real forecast
The revenue forecast weighs each step, instead of adding everything up as closed.
Example "Proposal sent" is worth 40%. "Contract being signed" is worth 90%.
Funnels, rules, forms, automations, AI agents, projects, goals, WhatsApp, permissions and integrations. No feature is locked by plan: in the free trial you use everything.
The full map
Click a group to see the highlights with a usage example.
01 · Funnels and steps
Sales, support, purchasing, hiring: what runs through email or spreadsheets today becomes columns with an owner, a deadline and a rule.
The revenue forecast weighs each step, instead of adding everything up as closed.
Example "Proposal sent" is worth 40%. "Contract being signed" is worth 90%.
Training inside the process: it opens on its own the first time and records who watched it.
Example Whoever moves the order to "Invoicing" for the first time watches the 3-minute video first.
With one click on Play, the time at each step becomes project cost, in man-hours.
Example Answers "how much does paying a bank slip cost?": 12 minutes of finance × hourly rate, at each step.
02 · Flow rules
Nobody skips a step, not even the super admin: to change it, the rule has to be edited, and the edit is recorded. That is what makes the process hold without someone watching.
They limit entry to and exit from the stage: the project only enters or leaves when it meets every criterion.
By step, tag, status or form answer.
Example "Only enters Production with a signed proposal."
The tag is seen in every funnel and works as a trigger, without email or mentions.
Example The "manager support" tag makes the project show up in the manager's approval funnel.
Shows how many times the date was pushed back. Repeated rescheduling is a hidden blocker.
Example Forecast changed 6 times: the manager knows before the customer complains.
03 · Forms
The form collects the data, locks the step, feeds the AI, triggers the automation and exports to a spreadsheet.
Tree-shaped form. A required field keeps the project from leaving the step.
Example Supermarket order: bakery → cakes → quantity.
Catalog of internal requests. Each person sees only what they can request, without seeing the funnel.
Example The salesperson requests a lunch reimbursement. The director requests a trip. Nobody sends an email.
A link or a code snippet on your website. The answer already creates the project in the right funnel.
Example The website quote form creates the project in "New contact".
No need to build from scratch. In the conversation, Olie shows these features applied to your process.
04 · Automations
8 triggers, 4 conditions and 23 actions, configured on screen and chained up to 5 levels deep.
This is where it all starts: the trigger fires the automation.
Time idle at the step triggers cascading alerts.
Example 1 day: owner. 3 days: manager. 5 days: director.
Work split across the team without a rotation spreadsheet.
Example Each new contact is assigned by draw to one of the available salespeople.
A field changed, and the owner, tag or step changes.
Example Revenue went from R$ 10 thousand to R$ 1 million: assigns the senior salesperson.
05 · AI agents
The agent knows where it is in the process, reads what it needs and saves the answer in a field. From there, the rule takes over.
A new customer message arrived on the WhatsApp of project {{project.code}}.
Follow the instructions: check the project details, read the channel conversation and reply to the customer.The AI works at a position in the process: on entry, on exit or when someone asks.
Example A résumé arrives in "Screening", the agent evaluates it and saves the score. Below 75, a rejection tag.
Instruction sent (prompt), usage (tokens), cost and time of each run. You know how much the AI costs per process.
Example 163 runs in the month, each one with its cost on the statement.
Several specialists in sequence, with no human in between.
Example Article: extractor → writer → reviewer, each at a step.
06 · Projects and hierarchy
A ticket becomes a sale, the sale becomes a receivable. Same project, same code, three funnels. You see where it got stuck without asking.
The same item goes through the areas carrying its whole history.
Example Ticket → sale → receivable, always with #4812.
Parent, child, grandchild and great-grandchild. From strategy to micro-task, in one place.
Example Launch → campaigns → assets → revisions.
Mentions, assigned and created by me, with state: unread, replied, done.
Example You start the day with 6 mentions, not 60 emails.
07 · Goals and metrics
Metrics live at the step, where the action happens: average time, entries, bottlenecks and goals that trigger rules.
| Title | Type | Frequency | Status | Progress | Change | Target | Mode | % | History | Start | Actions |
|---|---|---|---|---|---|---|---|---|---|---|---|
| Proposals approved in the month | Projects in stage | 30 | Active | 8 | ↓ 74.19% | 30 | Target | 27% | 33 | 01/01/2025 | |
| Orders delivered on time | Projects in stage | 30 | Active | 33 | ↑ 6.45% | 30 | Target | 110% | 33 | 01/01/2025 | |
| Conversations started | Projects in stage | 30 | Active | 17 | ↓ 8.11% | 30 | Target | 57% | 33 | 01/01/2025 | |
| Tickets solved by AI | Projects in stage | 30 | Active | 42 | ↑ 12.50% | 40 | Target | 105% | 20 | 01/01/2025 | |
| Customers activated | Projects in stage | 30 | Active | 16 | ↓ 5.88% | 30 | Target | 53% | 33 | 01/01/2025 | |
| New customers served by AI | Projects in stage | 30 | Active | 120 | ↑ 18.40% | 100 | Target | 120% | 12 | 01/01/2025 | |
| Hires this semester | Projects in stage | 30 | Completed | 9 | ↓ 10.00% | 10 | Target | 90% | 6 | 01/01/2026 |
Average time, entries, maximum and minimum, over 3 periods.
Example "Average acceptance time: 9 hours." Whoever asks knows how long they will wait.
Target or limit, in cycles of 1 to 365 days, per person or per team.
Example Key result: 40 proposals in the quarter. The goal shows 27 of 40 and who contributed.
The goal or limit was exceeded: the rule acts. It is not a number on a dashboard.
Example More than 10 open tickets: notifies the supervisor.
08 · WhatsApp and conversations
Several numbers, each in its own funnel. The message becomes a project, the agent replies, the human takes over when needed.
Whoever answers doesn't choose where the reply comes from. The conversation is recorded in the company.
Example The sales number goes to the sales funnel; the support number, to the support funnel.
When a Facebook or Instagram ad opens WhatsApp, the campaign data goes into the form.
Example You know which ad brought the customer that closed R$ 48 thousand.
Part of the team works without opening the platform: receives, replies and moves through WhatsApp.
Example The order from 4 stores arrives and is handled without anyone opening Olie.
09 · Permissions
Permissions by role and by funnel: the role says what each person can create, edit and see. Funnels are built and the platform is managed by the super admin, who comes with the subscription.
The combined permissions define the type: Operational, Managerial or Partner (the subscription's super admin).
Example The sales coordinator moves the sales projects, but doesn't see the cost or get past the approval step.
All projects, only assigned ones or only those I created.
Example A project without an owner stays invisible until management distributes it.
Edit and movement logs in each project.
Example "Who changed the proposal value?" is answered in one click.
10 · Integrations
REST API, MCP, webhook and WhatsApp. What the screen does, the API does too, with the same permissions.
Projects, funnels, forms, customers, goals and automations, with the same permissions as the screen.
Example The ERP creates the order in Olie when the invoice is issued.
The protocol that connects Olie to ChatGPT or Claude. With the Git plugin in the same assistant, it calls both in the same question.
Example At Sifat Sistemas, the project number is the Git branch name: the question about the project cross-checks Olie and Git.
Through the API and webhooks, these tools talk to Olie.
Example An n8n flow creates the project and Olie takes care of the rest.
Yes. There is no basic plan and no locked feature. The Subscription includes every feature and the super admin, who configures the funnels and manages the platform. Each additional person who executes is an operational user. AI agents use prepaid credits.
No. Funnels, forms, automations and agents are built on screen by the super admin, who comes with the subscription. The API and the advanced syntax exist for those who want to go further, and in the Enterprise implementation Olie builds it with you.
Yes: through spreadsheet import or with technical support from Olie. The API also creates projects in bulk. Moving cards without the flow's locks is something else: only the super admin does it, with activation in three places, and everything is recorded.
The agent saves the answer in a field, and the rule decides what happens. You choose where human approval comes in; if the AI fails, the card goes to a person for review. Each run is recorded.
There is no native customizable dashboard. The metrics live in the step and the funnel, where the action happens, and the tailored view comes through MCP: you ask ChatGPT or Claude and the answer comes with Olie's data.
In the conversation, Olie draws your flow on screen. If you prefer to evaluate on your own, there are 30 days free, with full access.