Kaigoo delivers digital labor for cash flow management to companies and the advisors who serve them. It answers a concrete question: how much of the receivables due is likely to arrive, and when? The Cash Flow Copilot turns that context into recurring, human-supervised financial work above the company’s existing management system.
The Receivables Diagnostic reveals collection-timing exposure. The Cash Flow Copilot monitors and performs recurring financial work. The Partner Cockpit brings this operation to each client company in a partner’s portfolio.
Copiloto de Liquidez · The recurring service that monitors expected receipts, explains cash pressure and carries financial tasks through human approval, ERP posting and reconciliation.
Cockpit · The partner workspace that organizes client access, cash flow signals and recurring financial work for accounting, advisory and BPO firms.
Raio-X de Recebíveis · The free diagnostic that compares scheduled and probable receipts for the selected company, with separate results for each authorized ERP app.
TechProd Official Report V2 · Product, commercial and operational reference. Three products · Four journeys · Definition of Done.
Kaigoo adds a specialist cash flow management service to the financial workflow a company already uses.
Kaigoo delivers digital labor for cash flow management: a layer above the existing ERP that uses payment behavior to distinguish scheduled receivables from probable cash arrivals and turns that insight into recurring, supervised financial work for companies and their advisors.
One operating cycle connects monitoring, diagnosis, preparation, human approval, ERP posting and reconciliation. The Receivables Diagnostic opens the relationship; the Cash Flow Copilot delivers recurring work; the Partner Cockpit organizes delivery across client companies. Explore the product capabilities.
For companies using Omie with recurring receivables, payment history and collection-timing exposure, Kaigoo makes the gap between due dates and likely receipts visible and connects it to a concrete financial action.
The company keeps its ERP and gains an ongoing operation for cash visibility, financial questions, document processing and supervised execution. The fit is strongest when payment timing and repetitive financial work materially affect the business.
For financial advisory firms, accountants and BPOs, Kaigoo provides a repeatable cash flow workflow across client companies: find the exception, understand it, prepare the work and verify its outcome.
The partner distributes and operates Kaigoo through the free Cockpit while each company subscribes to the recurring Copilot. Company context and permissions stay separate as the analyst moves between clients.
Each financial job has an input, an output and an observable conclusion. Kaigoo connects monitoring → diagnosis → proposed action → authorized execution → verified result. Human approval governs effective ERP posting; exceptions remain visible for review and resolution.
The competitive thesis: specialist payment-behavior modeling, maintained financial integrations and a complete operating cycle combine with partner distribution. The value is the financial work delivered within company context. Accuracy, productivity and cost comparisons use measured results; AI, WhatsApp and approval gates alone are not exclusive capabilities.
These categories overlap. ERPs include financial management; BPOs use automation; partner platforms use AI. The comparison uses official vendor descriptions reviewed on 10 October 2026.
| Alternative | What is already available | Why companies and partners choose Kaigoo | How to assess the value |
|---|---|---|---|
| ERP | Omie documents cash planning and, with Omie.Cash, collection, payment and reconciliation automation. Its offering also includes WhatsApp actions and a client panel for accountants. Official sources. | A specialist cash flow management service above Omie: payment-behavior estimates, supervised work and reconciliation while the company retains its existing ERP. | Incremental decision value, synchronization quality and effort per completed financial task compared with the configured ERP workflow. |
| Financial management software | Conta Azul documents automatic matching and condition-based reconciliation. Nibo documents future receipts/payments and cash projection adjustments. Official sources. | Behavior-based expected receipts, explicit data coverage and calculation dates, connected to recurring monitoring and approved financial work. | Receipt-amount error and bias at 7, 30 and 90 days, eligible-data coverage and whether the information changes a real decision. |
| Financial BPO and partner platforms | BPO services can perform reconciliation, collections and cash monitoring with customer approval. Nibo BPO supplies multi-client software, document intake and AI-assisted financial entries. These are distinct service and software examples. Official sources. | An operating layer for partners that combines portfolio context, cash flow priorities, document intake and supervised execution while preserving the client relationship. | Analyst time per resolved exception, correction rate, service margin and quality of the client operation. |
| AI agents and automation platforms | n8n documents agents calling tools, pausing for human review and executing or cancelling a tool call after the decision. This is infrastructure, not a ready-made Brazilian financial service. Official documentation. | An integrated financial service with company context, maintained Omie integration, defined outputs and a recurring routine the company and its partner can operate. | Permission controls, completed financial tasks, error recovery, maintenance effort and total operating cost against an equivalent configured agent. |
Kaigoo’s differentiation is the combination of cash flow expertise and delivered financial work. Comparative claims about superiority, exclusivity, savings or forecast accuracy use measured results from equivalent workflows.
Three offers connect acquisition, recurring delivery and partner operations in one financial workflow.
The Receivables Diagnostic compares scheduled receipts, probable receipts and their difference over 7, 30 and 90 days for the selected company, separately for each authorized Omie app.
Company access is checked before the analysis is displayed. The report retains the model date, distinguishes missing values from zero and handles absent, stale or insufficient analysis explicitly.
Coverage: eligible modeled receivables due within each horizon. Overdue titles are outside this comparison. The Diagnostic is a receivables view; full cash flow monitoring in the Copilot also uses bank balances and accounts payable.
The free Receivables Diagnostic starts the commercial conversation. The Cash Flow Copilot provides the recurring service at BRL 399 per company per month. The Partner Cockpit is free for partners, with separate Copilot subscriptions for client companies.
The journey connects the diagnostic, offer, contract, automated billing, subscription confirmation and Copilot access. Each offer has a distinct role in acquisition and service delivery.
Teteu receives messages, documents, photos and audio through WhatsApp, answers financial questions in Portuguese and prepares financial drafts. Authorized people review, correct, approve or reject the work before effective posting to Omie.
The operation connects submission, draft, approval, ERP outcome and reconciliation. Daily monitoring and contextual alerts return the resulting financial context to the company and its authorized partner. Follow the complete workflow.
The company buys recurring cash flow management; the partner operates across its authorized client portfolio. Free Diagnostic access, partner access and paid Copilot subscriptions have distinct commercial roles.
Commercial reporting separates free users, paying companies, collected revenue and renewals. Development participation remains a learning relationship and is never counted as collected subscription revenue.
Product reference: offer definitions, 17 touchpoints and four complete journeys. The same descriptions support commercial artifacts and the Definition of Done.
Use these descriptions in commercial materials, investor presentations and applications, preserving the product scope and commercial facts.
Kaigoo delivers digital labor for cash flow management to companies and the financial partners who serve them. It combines payment-behavior forecasts with a complete financial operating cycle: monitoring, diagnosis, document capture, human approval, Omie posting and reconciliation. The free Receivables Diagnostic starts adoption; the Cash Flow Copilot is the recurring service; the free Partner Cockpit organizes delivery across client companies.
How much of the money due is likely to arrive when you need it? Kaigoo compares scheduled and probable receipts, monitors your cash flow and helps carry out day-to-day financial work. Through Teteu on WhatsApp, you ask questions, send documents and review financial drafts. You retain approval, and Kaigoo connects the approved work to Omie and reconciliation.
Kaigoo brings your client portfolio into a shared cash flow workspace. Your team identifies the company that needs attention, opens its diagnostic and manages recurring financial work in the correct client context. The Cockpit is free for partners; each client company subscribes to the Copilot. Human review and company permissions govern the operation.
| Topic | Product description | Communication boundary |
|---|---|---|
| Differentiation | Specialist cash flow management above Omie, combining scheduled versus probable receipts with supervised execution. | Use like-for-like measurements for claims of better, faster, cheaper or unique. |
| Digital labor | Recurring financial jobs with document intake, review, authorized posting and reconciliation. | Describe the job and its outcome; human approval remains part of the service. |
| Diagnostic | Free Raio-X with 7/30/90-day comparisons, calculation dates and separate results per authorized app. | Eligible modeled receivables are the scope. Do not describe the Diagnostic as the entire cash position. |
| Integration and WhatsApp | Omie integration and WhatsApp messages, documents, photos, audio and financial questions. | Name the supported integration. A financial question does not authorize posting or funds movement. |
| Traction and pricing | BRL 399 per company/month for the Copilot; free Diagnostic and Partner Cockpit. | Report collected revenue and renewals from billing records. Free users and development partners remain separate. |
| Partner efficiency | Portfolio context, cash flow signals and repeatable financial workflows for partner teams. | Publish capacity or savings claims with a baseline, period, denominator and measured result. |
The complete product connects the same four outcomes described throughout this report: authorized delivery, financial consistency, subscription activation and partner operation.
The Diagnostic journey connects company access, ERP data, calculation timestamp and report output. Missing data, zero values, stale analysis and multiple authorized apps retain their correct meaning and company context.
The write journey connects intake, draft, correction or rejection, authorized approval, ERP record and reconciliation. Failed writes and retries preserve a traceable outcome; duplicate submissions do not produce duplicate financial actions.
The forecasting layer uses the same receivable records and defined 7-, 30- and 90-day horizons. Calculation dates, eligible-data coverage and sample confidence remain visible in the financial interpretation.
Quality review uses receipt-amount error and bias, with due dates and historical delay as comparison baselines. Financial explanations retain the source amounts and distinguish a modeled estimate from a guaranteed receipt.
The free Diagnostic connects to the Copilot offer, contract, automated billing, confirmation and company access. The recurring scope, price and company subscription are consistent throughout the journey.
Commercial records distinguish contacted, eligible, diagnostic completed, offer, paid and renewed. Collected amounts, discounts and cancellations are recorded separately from free access and development participation.
The partner moves from portfolio to the authorized company, reviews cash flow signals and the Diagnostic, operates the company’s financial workflow and returns to the portfolio. Viewing, editing and financial approval retain their separate permissions.
The operation exposes completed tasks, corrections and unresolved exceptions. Analyst effort, onboarding and support costs can be assessed against the same client workflow, without mixing data or authority across companies.
Business, product and engineering use the same product definitions, touchpoint IDs and journeys in this report. Commercial artifacts describe these delivered workflows; completion is assessed against their inputs, permissions and observable outcomes.
Try R02, C01 or coverage. Search includes the entire document, including collapsed details.
One recurring service, a free acquisition diagnostic and a partner operating channel. Each offer has a distinct role in adoption and financial delivery.
Anticipate cash shortfalls and support day-to-day financial decisions.
Commercial model reference: WOW Pitch 2026.2 (EN), p. 8.
Recurring digital labor for cash flow management, from monitoring and conversation to approved ERP posting and reconciliation.
The recurring service combines collection monitoring, financial explanations and supervised operational tasks. Documents, photos and audio become drafts for human review; approved work proceeds to Omie, with outcomes and discrepancies carried into reconciliation.
Kaigoo does not transfer funds, provide credit or act as a credit intermediary. Rates are indicative; companies negotiate with their chosen financing provider.
C01–C03 · monitoring, alerts and conversation · C04–C06 · capture, approval and outcome
J3 · understand cash flow and act · J4 · submit, review and post
GTM · pp. 3–4, 6–7 · Pitch EN · pp. 4–6, 8 · Forecasting Engine · p. 1
Bring each client company’s cash flow context into one partner workspace.
Commercial model reference: WOW Pitch 2026.2 (EN), p. 8.
A complete partner workspace for client access, portfolio cash flow and recurring financial work.
A workspace for managing a partner’s client portfolio. It brings client companies together and provides access to each company’s diagnostic and financial workflows, distributing the Copilot through accounting and advisory firms.
The portfolio combines prioritization, filters and permissions with each company’s financial workflows. Analyst capacity and savings are measured within the partner’s operation.
See the difference between scheduled receivables and likely collections.
Commercial model reference: WOW Pitch 2026.2 (EN), p. 8.
A complete receivables diagnostic, with authorized company access, model dates and separate results for each connected Omie app.
The Diagnostic reads model outputs for authorized ERP app connections and compares scheduled receivables with probable receipts. It makes collection-timing exposure visible and connects that insight to the recurring support provided by the Copilot.
The Diagnostic compares eligible receivables per Omie app connection without aggregating portfolios. It preserves missing values and zero and displays the model date. Without bank balances and accounts payable, this is not the company’s complete net cash position.
Free Receivables Diagnostic to uncover the issue; Cash Flow Copilot for ongoing cash flow monitoring.
Partner Cockpit to serve the client portfolio; Receivables Diagnostic as the entry diagnostic; each company has its own subscription to the Copilot.
The two commercial entry paths are described in GTM · pp. 6, 8; per-company subscriptions are described in Pitch EN · p. 8
.NVIDIA GPUs support financial-document processing, Teteu’s conversational inference and forecasting-data preparation. The three workloads preserve the same financial calculations, authorized company context and human approval boundaries.
Product role: turn documents and images into structured financial drafts, including batches of submissions.
Acceleration approach: NeMo Retriever with Nemotron Parse for GPU-backed document transcription, layout and table extraction. This combines a document model suited to complex layouts with parallel inference for batches of submissions.
Integration: parsing operates before draft review. Extracted text maps into the draft schema, amounts and dates are validated, and human approval precedes effective ERP posting. The workflow handles Brazilian Portuguese business documents.
How we measure success: compare field accuracy, table fidelity, correction rate, 95th-percentile processing time and total cost per document against the baseline. Test Brazilian document formats, poor scans and complex layouts on compatible hardware.
NVIDIA document extraction documentation · Capture and review workflow
Product role: serve financial explanations and concurrent manager conversations.
Acceleration approach: a supported language model served through NVIDIA NIM, using a TensorRT-LLM profile where supported. GPU inference and batching serve concurrent conversations.
Integration: the model serves Teteu’s conversational interface. Controlled tools retrieve the authorized company’s financial context, while cash calculations remain in the financial engine. Quality checks cover Portuguese answers, numerical consistency and missing-data handling.
How we measure success: use a fixed question set and representative concurrency. Measure correct answers, unsupported statements, complete-response latency and cost per accepted answer. Use NVIDIA AIPerf for model-serving benchmarks and separate application tests for quality and end-to-end latency.
NVIDIA inference benchmarking · NIM serving configuration · Financial questions workflow
Product role: prepare payment histories and client data for diagnostic and forecast refreshes.
Acceleration approach: NVIDIA RAPIDS cuDF for large joins, grouped aggregations and payer-history transformations in a separate GPU batch job.
Integration: cuDF runs in a GPU batch job outside BigQuery for data transformations, preserving the payer/sector model and calculation rules. Evaluation includes export, transfer and result-loading time and cost.
How we measure success: compare total refresh time, cost per batch and output parity. Keep forecast quality consistent through time-based backtests, and focus GPU processing on batches large enough to benefit after transfer costs.
RAPIDS workload fit and limitations · Forecasting methodology
The acceleration layer operates within Kaigoo’s architecture: company data isolation, grounded financial answers and human approval. The statistical engine calculates cash projections; accelerated models process documents and questions.
NVIDIA model and GPU compatibility · Google Cloud GPU deployment requirements
Technology references: official NVIDIA, RAPIDS and Google Cloud documentation. Quality, latency and cost measurements accompany each workload; no numerical performance claim is implied by the architecture.
The Copilot is the core product. The Diagnostic in the Console, reuse in the Partner Cockpit, forecasts and alerts, financial questions on WhatsApp, and capture with approval form one complete product. Each company enters through the Diagnostic or a partner and continues through the recurring financial service.
Kaigoo does not move money or offer credit; the rate is a negotiation reference. It works above the business management system, without requiring migration.
The shared company and ERP foundation connects the Diagnostic, Partner Cockpit, recurring forecasts and alerts, financial questions on WhatsApp, and document capture with human approval.
The Console displays the selected company’s Diagnostic, separately for each authorized Omie app, with 7/30/90-day comparisons, calculation dates and explicit absent-data handling.
The user reaches a useful receivables comparison from the Hub. Eligible records, missing values and zero retain their meaning, and results remain within the authorized company context.
Sign-in, the Hub, company and ERP connection modals, ingestion progress and the reconciliation queue provide the common foundation for the three products.
The account reaches its permitted company context, connects Omie, follows preparation progress and enters the relevant diagnostic or operational workflow.
The Cockpit groups client companies and Omie apps, manages invitations and permissions, and connects portfolio cash flow signals to each company’s Diagnostic and recurring work.
The partner identifies a company that needs attention, opens its authorized context and returns to the portfolio. Financial approval is governed separately from access and invitations.
Daily monitoring covers 7-, 30- and 90-day horizons. WhatsApp alerts explain projected pressure, while financial questions return company-specific explanations and suggested actions.
The manager sees the date, amount and cause of the issue, understands the financial context and retains the decision. Questions and guidance do not authorize an ERP write.
Messages, documents, photos and audio produce drafts for review. Authorized people correct, approve or reject the work; effective posting to Omie follows approval.
The operation exposes the ERP result and continues through reconciliation. Draft persistence, effective posting and funds movement remain distinct; errors and exceptions stay available for human resolution.
The Diagnostic entry opens the sales conversation and the company’s Console journey. The recurring path connects the Copilot offer, contract, automated billing and subscription confirmation.
The subscribing company receives Copilot access and a clear recurring scope. Free Diagnostic access and partner access remain distinct from the company’s paid subscription.
Companies connect their data, review a diagnostic, work with an advisor and use the Copilot. These four journeys describe the complete operation, from entry to the financial or commercial outcome.
Start with the shared foundation, then follow the route that matches the user’s goal. Select a node to open its full workflow.
The map connects the four journeys through the same account, company and ERP context. Each route leads to its detailed workflow, including human review and exception handling.
Sign-in → Hub → ERP connection → ingestion progress → Diagnostic.
Open the full workflow below for branches, conditions and outcomes.
Outcome: The selected company reaches its receivables comparison and can continue to the recurring Copilot subscription.
Portfolio → company → diagnostic or financial workflow → portfolio.
Open the full workflow below for branches, conditions and outcomes.
Outcome: Cash flow signals and permissions stay connected to the selected company as the partner works across clients.
Daily monitoring over 7/30/90 days → contextual WhatsApp alert → recommendation and questions.
Open the full workflow below for branches, conditions and outcomes.
Outcome: The manager understands the issue, cause and next action within the company’s financial context.
Content → draft pending approval → approved ERP posting → outcome and reconciliation.
Open the full workflow below for branches, conditions and outcomes.
Outcome: Human review connects draft correction or rejection to authorized execution and a traceable outcome.
The complete inventory, detailed workflows and sources are available below. Expand a section or follow a reference link directly to the cited item.
Experience inventory by product. Each item describes a page, modal dialog, message or interface responsibility, with what the user sees, does and achieves.
Sign in, connect an ERP, track ingestion and select a company.
The shared foundation carries account access, company selection, Omie connection and preparation status into the Diagnostic and recurring financial operation.
Sign-in, email verification and registration completion, when required.
Enters an email address, follows the sign-in link and completes registration.
Access to the Hub and company context permitted for the account.
Product reference: COD · Shared Console foundation.
Email sign-in establishes the account context available in the Hub.
Account access opens only the company context permitted for the signed-in user.
Companies, registration options and ERP connections.
Selects an existing company or starts a new connection.
The company's context or the start of onboarding.
Product reference: COD · Shared Console foundation.
The Hub lets an account select an existing company or begin a new connection.
Company selection preserves the account’s access boundaries throughout the connected journey.
Modal dialogs for companies and advisory firms, ERP connection validation and company identification.
Enters connection details and a name, then selects "Get started".
Data preparation begins. These are Hub modal dialogs, rather than additional pages.
Product reference: COD · Shared Console foundation.
A Hub modal collects connection details and begins data preparation.
Company and advisory-firm connection dialogs operate within the Hub, with connection validation before preparation.
Data preparation status within the Hub.
Tracks preparation progress and selects “View Diagnostic”.
Data preparation visibility and access to the selected company’s Diagnostic.
Product reference: COD · Shared Console foundation.
The Hub exposes data-preparation progress and the Diagnostic entry point.
The preparation journey connects the selected company’s authorized ERP data to its Diagnostic analysis.
The day's queue items awaiting analysis.
Reviews items and performs the corresponding human action in the ERPs.
The reviewed item progresses through the financial workflow, with human resolution of reconciliation exceptions.
Product reference: COD · Shared Console foundation.
People review the day’s queue and perform the corresponding human action in the ERP.
Human review resolves the queue’s financial discrepancies and exceptions.
Documented routes: /entrar, /verificar-email, /completar-cadastro, /hub and /conciliacao. The /dev/progresso route is a development simulation and is excluded from the actual user journey.
Users review their company's diagnostic before deciding whether to subscribe to ongoing monitoring.
A sales call to action for the Diagnostic.
Selects the button on the marketing page.
Opens the sales WhatsApp conversation and connects the company to the Console Diagnostic journey.
Product reference: COD · Shared Console foundation.
The marketing call to action opens a sales WhatsApp conversation and the company’s Diagnostic journey.
The sales conversation connects to the Console journey for company access, ERP connection and the free Diagnostic.
Per ERP app: scheduled inflows, predicted collections and their difference over 7, 30 and 90 days, with the model date.
Selects "View Diagnostic" in the Hub and reviews the selected company.
A comparison of eligible receivables for each authorized app, with calculation dates and explicit missing-data handling. Full cash flow monitoring also includes bank balances and payables in the Copilot.
Product reference: PR61 · Receivables Diagnostic.
The Diagnostic compares scheduled and likely collections for the selected company, separately for each authorized ERP app.
Eligible modeled receivables due within each horizon form the comparison. Bank balances, payables and overdue titles are outside this Diagnostic view.
The next step after the free diagnostic.
Reviews the offer and decides whether to subscribe to the Copilot.
Completes the offer, contract and automated billing, receives confirmation and gains access to the recurring Copilot.
The free Diagnostic connects to the recurring Copilot subscription.
The transition includes the offer, contract, automated billing, confirmation and company access to the Copilot.
Move between the portfolio and individual companies, reusing the diagnostic and financial workflows.
The partner advisory firm's Hub and associated client companies.
Selects the company to monitor.
Enters the client's context within the user's access permissions.
Product reference: COD · Shared Console foundation.
A partner selects an associated client company and enters its permitted context.
The selected client context preserves company access and financial authority throughout the partner’s operation.
Access management and invitation controls.
Reviews or manages existing relationships.
Access administration. An invitation does not, by itself, grant financial approval authority.
Product reference: COD · Shared Console foundation.
The partner administers relationships through access and invitation controls.
Viewing, editing and financial approval have separate permissions. An invitation alone does not grant financial approval authority.
A multi-company view of diagnostics and attention signals.
Selects a company and opens its diagnostic or financial workflows.
The partner reaches the selected company’s Diagnostic or Copilot workflow and returns to the portfolio, with company permissions and data isolation preserved.
Portfolio cash flow signals and prioritization connect the partner to each permitted company’s Diagnostic and financial workflows.
The portfolio view routes a selected company to its Diagnostic or Copilot workflows.
Portfolio signals and prioritization retain each company’s context. Client data remains isolated throughout navigation.
The Cockpit provides free partner access and a separate Copilot subscription for each company. PITCH · p. 8
Understand cash flow, ask financial questions and manage financial workflows with human oversight.
Daily monitoring covers 7/30/90 days. Teteu on WhatsApp connects forecasts, contextual alerts, financial questions and document submission to the company’s operational context.
Daily projections over 7-, 30- and 90-day horizons, highlighting cash pressure.
Reviews the forecast, the receivables amount to bring forward and the risk-based reference rate.
Context for a financial decision. The product does not provide credit, transfer funds or guarantee outcomes.
The daily forecast provides context for a financial decision over 7, 30 and 90 days.
The product provides financial guidance. It does not provide credit, transfer funds or guarantee collection outcomes.
A projected cash shortfall with its date, amount and context or cause, delivered through WhatsApp.
Reads the context and decides which issue to investigate.
A suggested next action and, where applicable, the receivables amount to bring forward. Alerts connect the projected deficit or funding need to its financial context.
A contextual WhatsApp alert explains the projected shortfall and a possible next action.
The alert relates a projected deficit or funding need to its date, amount and cause, with guidance for the manager’s decision.
A WhatsApp conversation within the company's context.
Asks a question about the company's financial position.
An answer in clear Portuguese explaining the issue, its cause and a suggested action. Financial questions provide decision support; effective ERP posting requires separate human approval.
A contextual question leads to an explanation of the issue, its cause and a suggested action.
Teteu answers in clear Portuguese, grounded in the authorized company’s financial context. A question does not authorize an operation.
A WhatsApp conversation for submitting an invoice, boleto payment slip, Pix payment receipt, photo or audio.
Submits content from which a draft is prepared.
A financial draft with the supporting information available for human review before effective ERP posting.
Submitted documents, photos and audio become a financial draft for human review.
The draft carries its supporting information into review. Draft persistence and effective ERP posting are distinct steps.
The draft and supporting information within the authorized review workflow.
The authorized manager reviews, corrects, approves or rejects the draft; people resolve exceptions.
Approved work proceeds to effective Omie posting. Draft persistence and posting remain distinct, and the operation does not move funds.
The authorized manager reviews, corrects, approves or rejects a draft before effective ERP posting.
Approval governs effective posting to Omie. The result reflects the financial action taken; Kaigoo does not move funds.
Operation outcome and daily reconciliation of bank statements, accounting entries and documents, including discrepancies and exceptions.
Checks the outcome and reviews exceptions such as interest, penalties and partial payments.
A traceable ERP outcome and reconciled financial information that continues to feed forecasts and alerts.
People check operation outcomes and reconcile exceptions so financial work and forecasts continue.
Reconciliation connects statements, ERP entries and supporting documents. People resolve discrepancies, including interest, penalties and partial payments.
The WhatsApp operation connects media processing, financial questions, draft review and authorized execution, with subscription context, opt-out handling and company access boundaries.
Each step links to the inventory above. The diagrams connect user actions, company context, human review and the completed financial or commercial outcome.
Goal: connect an ERP and obtain a useful view of likely collections.
The company connects its authorized ERP data, reviews the Receivables Diagnostic and continues to the Copilot subscription.
The journey connects sales conversation, company access, ERP preparation, Diagnostic and the recurring offer. Missing or insufficient data remains explicit.
The sales conversation connects to the Console. The company signs in, selects its context, connects Omie, follows preparation and reviews the Diagnostic. The commercial path continues to the Copilot offer, contract, billing, confirmation and access.
Goal: reach the correct company's context while preserving access boundaries.
The partner reaches a selected company’s Diagnostic or financial workflow while preserving access boundaries.
Portfolio signals connect to the selected client’s analysis and recurring financial work. Viewing, editing and approval have separate permissions.
The partner operates through company access, invitations, portfolio cash flow signals and individual Diagnostic links. The selected company’s context and permissions remain active throughout its recurring workflow and the return to the portfolio.
Goal: turn forecasts, alerts and conversation into an informed decision.
Forecasts, contextual alerts and questions provide complementary routes to an informed financial decision.
Forecasts, alerts and questions are complementary routes. Guidance retains the company context; the manager chooses the next action, and financial execution requires human approval.
Forecasts, alerts and questions complement one another; they do not form a mandatory four-screen sequence. The product provides guidance on the amount needed and an indicative rate, without providing credit or transferring funds. PITCH · p. 4–6 · EST · p. 1
Goal: reduce manual work while retaining human review and exception handling.
Content becomes a draft for human review, approved ERP posting, an operation outcome and reconciliation.
Draft preparation, effective posting and funds movement are distinct. Human review governs posting; correction, rejection and recovery keep the operation traceable.
Submitted content becomes a draft for review. The authorized manager corrects, rejects or approves it; effective Omie posting follows approval. The operation result continues to reconciliation and exception handling. Draft persistence and effective posting are distinct, and Kaigoo does not move funds.
The report connects commercial descriptions, product responsibilities and detailed workflows through stable IDs and source references.
The product definitions describe the complete service, its users, commercial role and financial boundaries.
Sign-in, company context, ERP connections, preparation and reconciliation support the three products.
The Diagnostic compares eligible scheduled and probable receipts, with model dates and separate authorized app results.
The inventory describes what users see, do and achieve at each touchpoint, using the same IDs throughout the report.
Review, correction, rejection and approval govern financial execution. Company access and financial authority remain distinct.
Source documents and implementation references preserve the origins of the product definitions and journeys.
The same product descriptions support business artifacts and the Definition of Done. Commercial results and comparative performance claims use their own dated, measured evidence.
Product documents, commercial records, implementation references and official competitor descriptions form the reference set retained from the original report. Source dates identify their historical versions.
12 pages; product content on pp. 1–8.
pp. 1–5: roles of the three products · p. 5: free Diagnostic and automated report · p. 6: two commercial entry paths · pp. 6–7: capture, drafts and reconciliation.
Source access: Use the document title, version and cited pages. Source access follows the permissions in its original channel.
16 pages. English version referenced on October 2, 2026. The deck’s metrics belong to its dated snapshot.
pp. 4–6: capture, reconciliation, forecasting, human approval and conversation · p. 8: BRL 399 per company per month, free analysis and free Partner Cockpit · pp. 9, 11: channel and commercial development · pp. 13–16: historical data and glossary.
Source access: Use the document title, version and cited pages. Source access follows the permissions in its original channel.
4 pages. Forecasting methodology, formula, table and diagram on pp. 2–3.
p. 1: cash flow calculation and recommendations · pp. 2–3: risk, confidence, payer/industry blending and weights · p. 4: next steps.
Source access: Use the document title, version and cited pages. Source access follows the permissions in its original channel.
Google Doc · 1 October 2026. Origin of the product, touchpoint and journey inventory reproduced in this report.
IDs E01–E05, R01–R03, P01–P03, C01–C06 and J1–J4 are retained for continuity between the reports.
Source access: Use the document title, version and cited pages. Source access follows the permissions in its original channel.
Code references recorded in the 1 October document, covering the shared Console foundation and financial integration.
Console: CtaSection.tsx, onboarding/empresa/route.ts, OnboardingModal.tsx, hub/page.tsx, progresso-store.ts, fila-do-dia.tsx and whatsapp-inbound.ts. Intelligence layer: forecasting models referenced in the earlier report.
Historical Diagnostic implementation record, retained as an origin reference for the Console experience.
EmpresaBloco.tsx · RaioX.tsx · API /api/raio-x · read access to estimador.p1_gatilho_diario · branch codex/raio-x-v1.
The product sequence connects the Diagnostic, Partner Cockpit, forecasts and alerts, financial questions on WhatsApp, and document capture with approval.
The three-product structure and financial boundaries are preserved from the source materials.
V2 reproduces the report with the complete product described in operation, as the shared reference for business artifacts and Definition of Done.
Terminology: ERP is the category; Omie names the integration covered by the product descriptions in this report.
Internal checkpoint, 2 October 2026: digital labor positioning, Diagnostic as a prospecting instrument and the subscription model. WOW assessment, 7 October 2026: differentiation and willingness to pay as commercial evaluation topics.
The assessment’s eight free development partners are historical product-learning participation. That count is not used as paid adoption or collected revenue in this report.
Console PR #61 · Diagnostic reference: per-app 7/30/90-day comparison, company access validation, calculation dates and absent-data handling.
Console PR #62 · Three-offer commercial architecture: recurring Copilot, free Diagnostic and free Partner Cockpit, with separate company subscriptions.
Console main: 97876da176df0b61a470f38834f553aa23052988, 10 October 2026. Intelligence main: 9a9fdd6a8843a81f2479549607dfc5e1b800d299, 5 October 2026.
WhatsApp inbound handler · Diagnostic API · Reconciliation-check scope change.
Repository references retain their original access permissions and snapshot dates.
Financial management and Omie.Cash automation · Accountant panel and WhatsApp functions. Reviewed 10 October 2026. Vendor descriptions, not independently measured results.
Conta Azul automatic bank reconciliation · Nibo cash-flow projections. Reviewed 10 October 2026.
Contabilizze financial BPO service, an illustrative service provider, and Nibo’s platform for BPO firms, a software supplier. Reviewed 10 October 2026. One service provider does not represent the entire BPO category.
n8n human review for AI tool calls. Reviewed 10 October 2026. Establishes available agent infrastructure, not an out-of-the-box financial product.
This site is the complete Kaigoo product and technology reference for business, product and engineering teams.
Use the product definitions, user journeys and commercial descriptions to create business artifacts. The same inputs, permissions and outcomes form the Definition of Done.
Repositories cited in the earlier document: techteu-console and camada-inteligencia-kaigoo. Access depends on the account's permissions.
TechProd Official Report V2 · 10 October 2026. Source dates identify the historical reference versions retained from the original report.