Ask the business
Plain-language questions over ERP, CRM and reports. Numbers come with the records they were built from.
- ERP
- CRM
- BI
- Spreadsheets
MetricHours → minutes per question
A library of the problems we solve most often, by function and by industry: what the platform does, which systems it connects, and the metric we use to measure the result. Any of them can become a pilot. If yours isn't on the list, that doesn't mean we don't solve it.
For each function: typical use cases, and the metric we use to measure the result. Details for every use case are in the library below.
Plain-language answers about the business, a daily digest of deviations, tracking of directives, meeting preparation.
Metric · time to answerCounterparty reconciliations, receivables control, consolidated reporting from ERP and accounting, source-document checks, plan vs. actual.
Metric · days to closeOutput plan vs. actual, downtime, quality control, procurement and inventory, on-site video analytics.
Metric · downtime, lossesLead qualification, proposal drafting, channel analytics, monitoring of sales activity in the CRM.
Metric · conversion, cycle timeMultilingual voice and text agents, request routing, response-time tracking, call analysis.
Metric · resolved without an operatorContract review against a checklist, regulatory search, standard document drafting, deadline control.
Metric · time per contract reviewRésumé screening, policy questions from staff, onboarding, a company knowledge base.
Metric · time to hireA single access point to data for analytics, first-line internal support, systems documentation.
Metric · first-line ticket loadEvery use case runs on the same model of your organization. The second one ships faster than the first, and each one after that costs less.
Whether it is a reconciliation, a citizen request or a contract review, the path is the same: your systems feed one model of the organization, an agent does the routine work, a person approves what matters, and the result goes back into the system of record.
ERP · CRM · documents · mail · telephony · cameras
Entities, processes, people and rules, linked
Executive · Operations · Documents · Knowledge · Voice · Vision
Required above $500,000 or low confidence
Written back, every step traceable
Typical scope for each use case. The systems listed are examples of what we connect; the exact set is confirmed during the diagnostic.
MetricTime to answer
Plain-language questions over ERP, CRM and reports. Numbers come with the records they were built from.
MetricHours → minutes per question
Each morning: what moved outside plan, by branch or project, ranked by money at stake.
MetricDeviations seen the same day
Decisions from meetings become tasks with owners and deadlines. Overdue items surface on their own.
MetricDirectives closed on time
A one-page brief before each meeting: open issues, latest figures, previous decisions.
MetricPreparation time
MetricDays to close
Matches statements, invoices and the ledger, drafts reconciliation statements and flags every discrepancy.
MetricDays per reconciliation
Aging by customer, drafted reminders, escalation of large amounts. Write-offs above $500,000 need a person.
MetricOverdue receivables
The monthly pack assembled from several entities and accounting systems, with variances explained.
MetricDays to close
Invoices and delivery notes checked against contracts and purchase orders before payment.
MetricErrors caught before payment
MetricDowntime, losses
Output against plan by line and shift, with the likely cause of each gap.
MetricTime to detect a deviation
Stock-outs, excess stock and late suppliers flagged before they stop production.
MetricStock-out days
Protective equipment, restricted zones and occupancy watched on your existing cameras.
MetricViolations detected
Process engineers ask about procedures, past incidents and equipment manuals and get quoted answers.
MetricTime to find an answer
MetricConversion, cycle time
Incoming requests scored, enriched and routed to the right person within minutes.
MetricTime to first response
Draft proposals from price lists, past proposals and the client's request, ready for a manager to edit.
MetricHours per proposal
Stalled deals, missing next steps and silent accounts flagged to managers each week.
MetricCycle time
MetricResolved without an operator
Answer routine questions in the customer's language by phone, chat and messengers, around the clock.
MetricResolved without an operator
Classifies each request, sends it to the right queue and hands the operator a short case summary.
MetricAverage handling time
Every call scored against your checklist, not a 2% sample; coaching cases flagged.
MetricShare of calls reviewed
MetricTime per contract review
Checks a draft against your checklist and standard terms, marks risky clauses and proposes wording.
MetricHours per review
Questions over laws, regulations and internal policies, answered with the exact clause cited.
MetricTime to a cited answer
Renewals, licenses, filings and court dates extracted from documents and tracked.
MetricMissed deadlines
Powers of attorney, letters and standard agreements drafted from templates and case data.
MetricDrafting time
MetricTime to hire
Applications checked against the role's criteria and summarized; a recruiter makes every decision.
MetricTime to shortlist
Staff ask about leave, travel, benefits and procedures and get answers quoted from the policy.
MetricQuestions answered without a ticket
A personal plan for each new hire, reminders for managers, answers to first-week questions.
MetricTime to productivity
MetricFirst-line ticket load
Governed, permission-aware access to company data for analytics, instead of ad-hoc exports.
MetricAnalytics backlog
Password, access and how-to requests resolved or routed with the diagnosis already done.
MetricFirst-line ticket load
Answers about your own systems from wikis, runbooks and configuration records.
MetricTime to find an answer
Typical problems we see in each sector, what the platform does about them, and what changes. These are patterns, not case studies; we name clients only with their consent.
Routes requests to the right agency, tracks directives against deadlines, answers legal questions with citations and gives leadership one console. Runs on-premises or air-gapped with local models.
Response times become visible, overdue directives surface on their own, and every answer is traceable to its source.
Joins production, ERP and sensor exports into one view by line and shift, watches safety on existing cameras and gives process engineers a quoted assistant.
Deviations are seen in the same shift, downtime has classified causes, and supplier risks are flagged before they stop a line.
One knowledge base over projects, estimates and procedures, schedule and budget control per site, tender drafting from past bids, and a staff assistant in corporate chat.
Overruns are flagged while they can still be managed, and tender teams start from a draft instead of a blank page.
In-app agents that take payments by voice, text or a photo of a document, automated package checks, analysis of requests and calls, all inside the bank's closed perimeter.
Checks take minutes instead of hours, routine requests resolve without an operator, and every agent action sits in the audit log.
Takes dealer orders automatically, controls receivables and inventory by region, runs loyalty programs for partners and installers, and reports regional sales.
Orders arrive structured, overdue debt and dead stock are visible weekly, and regional managers stop building reports by hand.
Video analytics of passenger flow and zone occupancy, multilingual answers for passengers, maintenance planning from asset records, and consolidated analytics for leadership.
Bottlenecks show up while they form, front-line staff spend less time on repeat questions, and maintenance moves from reactive to planned.
Voice agents for outage and billing hotlines, extraction of field reports into structured records, search over asset documentation, and drafts of regulatory reports. Critical infrastructure runs on-premises.
Hotlines absorb peaks without extra staff, field data becomes usable the same day, and reports start from verified numbers.
Checks referral and claims documents for completeness, handles appointment requests by phone and chat, and answers staff questions from internal procedures. No clinical decisions.
Fewer rejected claims for missing data, shorter phone queues, and administrators spend more time on exceptions than on routine.
Multilingual voice and chat agents for support, classification and routing of technical tickets, a weekly churn-risk digest from CRM and billing, and an assistant for tariffs and contracts.
More requests resolved without an operator, at-risk customers reached earlier, and engineers receive tickets already triaged.
Three roles, one day. Times, names and numbers are illustrative; the pattern is what we build.
Reads the morning digest on the phone: one region 12% behind plan, a key supplier contract expiring in nine days, two overdue directives.
Asks: “Why is the North region behind plan this month?” Gets a breakdown by branch and product, with links to the source records.
Opens a one-page brief for the board meeting, assembled from minutes, reports and open issues.
After the meeting, decisions are captured as tasks with owners and deadlines.
Deputies receive their overdue items automatically. Nobody had to chase them.
Overnight reconciliations are done: 212 counterparties matched, 9 discrepancies drafted for review.
Receivables: 14 invoices over 60 days, reminders drafted. One write-off above $500,000 waits for approval.
Asks for plan vs. actual operating costs by entity for the quarter, then drills into the largest variance.
Reviews the draft month-end pack; the agent lists three source documents still missing.
Approves flagged payments. Every approval is written to the audit log.
Overnight report: the voice agent handled calls in four languages, 68% resolved without an operator, three escalations.
A spike in calls about a billing change is detected; the answer is added to the knowledge base in minutes.
Quality: all of yesterday's calls scored against the checklist; five flagged for coaching.
Complex cases go to senior operators with a summary already written.
The daily service report goes to leadership without anyone compiling it.
Each use case runs in a platform module. Packages differ in how many modules and processes they include. The mapping below shows typical fit.
| Use case | Module | Foundation | Enterprise | Sovereign |
|---|---|---|---|---|
| Leadership | ||||
| Plain-language answers about the business | Executive | ✓ | ✓ | ✓ |
| Daily deviation digest | Executive | ✓ | ✓ | ✓ |
| Directive and deadline tracking | Operations | 1 module of choice | ✓ | ✓ |
| Finance & operations | ||||
| Reconciliations and receivables control | Operations | 1 module of choice | ✓ | ✓ |
| Plan vs. actual by shift or branch | Operations | 1 module of choice | ✓ | ✓ |
| Source-document and package checks | Documents | 1 module of choice | ✓ | ✓ |
| Legal, HR and IT | ||||
| Contract review against a checklist | Documents | 1 module of choice | ✓ | ✓ |
| Policy, regulation and procedures assistant | Knowledge | 1 module of choice | ✓ | ✓ |
| First-line internal support | Knowledge | 1 module of choice | ✓ | ✓ |
| Contact center and sites | ||||
| Multilingual voice agents | Voice | — | Add-on | ✓ |
| Safety, flow and occupancy video analytics | Vision | — | Add-on | ✓ |
| Scope | ||||
| Business functions | One | 3–5 | Organization-wide | |
| Processes | Up to 3 | Up to 15 | Unlimited | |
Foundation includes the Executive module plus one module of your choice; Enterprise includes all core modules, with Voice and Vision as add-ons; Sovereign includes every module. Exact scope is fixed in the proposal. See packages and the full comparison.
The signs we look for during the diagnostic. The more of them a process has, the faster the pilot pays back.
Dozens or hundreds of similar operations a week.
Even if it's spread across systems and spreadsheets.
Hours, days, errors, money: something you can compare before and after.
A person this process frustrates, who wants it changed.
The first process shouldn't be one where a single error is expensive.
Leadership should be able to see the pilot's impact and decide on scaling.
The use cases are the same everywhere; languages, data-residency rules and the usual deployment differ. We design every deployment to support compliance with local rules; your legal team keeps the final word.
| Region | Working languages | Rules we design for | Typical deployment |
|---|---|---|---|
| Europe | English, German, French, Spanish, Portuguese and others | GDPR, UK GDPR, EU AI Act | BlackGust Cloud in an EU region, private cloud or on-premises |
| United States & Canada | English, Spanish, French | CCPA/CPRA and other state privacy laws, HIPAA for health administration, PIPEDA | In-region cloud, your private cloud, on-premises for the public sector |
| Latin America | Spanish, Portuguese | LGPD in Brazil, national data-protection laws elsewhere | In-region cloud, private cloud or on-premises |
| China | Chinese | PIPL, Data Security Law, rules for generative AI services | On-premises or private cloud inside mainland China, local models |
| Japan | Japanese | APPI | In-region cloud, private cloud or on-premises |
| Korea | Korean | PIPA | In-region cloud, private cloud or on-premises |
| Australia | English | Privacy Act 1988 and the Australian Privacy Principles | In-region cloud, private cloud or on-premises |
More on data residency and deployment options on the security page.
The one that happens every day, has data, can be measured and has an owner who wants it changed. The diagnostic scores 3–5 candidates on exactly these points and recommends one; see how we choose.
Probably. The library shows what we see most often, not everything we do. If the work involves reading, checking, routing or reporting on information in your systems, it is usually a fit. Describe it in a request and an engineer will answer.
No. Most clients start with data spread across an ERP, spreadsheets and mailboxes. The platform connects to where it lives. If records are missing entirely, we say so in the diagnostic and recommend fixing record-keeping first.
ERP and accounting systems such as SAP, Oracle and Microsoft Dynamics, CRMs such as Salesforce, document stores, mail, telephony, databases, spreadsheets and cameras. If a system has an API, a database replica or a file export, we can usually connect it.
We don't promise a number before the diagnostic. It produces an ROI estimate with a conservative and an expected case for your process, and the pilot measures the real result against a baseline.
Only where you allow it. By default agents prepare and propose; a person approves actions above $500,000 or when the agent is not confident. Every step is logged.
No. Cloud models are used through enterprise APIs whose terms exclude training on customer data, and local models run inside your infrastructure. See security.
Yes. Public bodies, banks, energy companies and healthcare administrators usually choose on-premises or air-gapped deployment with local models. See AI for government.
Text agents work in all major languages. Voice agents support English, Spanish, Portuguese, German, French, Chinese, Japanese and Korean, among others.
What runs underneath every use case on this page.
Open →ApproachHow forward-deployed engineers take a use case to daily use.
Open →GovernmentSovereign, on-premises deployment for ministries and agencies.
Open →PricingFoundation, Enterprise and Sovereign compared.
Open →Describe it in your request. An engineer will tell you whether it's solvable and where to start.