Data Capture
Clarify relevant sources and access, such as ERP, CRM, documents or production data. Start with the information the selected process actually needs.
AI & PROCESS AUTOMATION
Handle enquiries faster. Compare offers on a sound basis. Make company knowledge accessible. We connect AI to your workflows and guide implementation through to handover.
120 units, delivery in week 12.
Quantity and date identified. Item details missing.
Your team reviews the draft and approves sending.
Human approvalThree familiar tasks. A traceable workflow. These examples show possible features using fictitious data.
Incoming emails and attachments are structured into customer, product, quantity, timing and missing information. The output is a reviewable draft for clarification or internal quotation preparation.
Prices, delivery commitments and sending remain subject to defined approvals. Missing information is made visible.
Time per enquiry; completeness rate; rework.
Thank you for your enquiry. To assess pricing and delivery, we still need the item number or a drawing.Human approval
Quotations and order confirmations are structured using agreed fields. Differences in price, quantity, dates or scope are highlighted for review.
The comparison exposes missing data. Responsible staff assess technical equivalence and make the commercial decision.
Time to comparable quotations; detected discrepancies; manual review effort.
| Supplier | Unit price | Freight |
|---|---|---|
| A | €12.40 | included |
| B | €11.90 | unconfirmed |
1,000 units: €500 price difference. Freight and technical equivalence must be clarified before deciding.
Human approvalAn assistant supports searching approved manuals, work instructions or product documentation and points to the underlying sources.
Access follows existing permissions. Unclear or conflicting sources trigger clarification rather than an authoritative answer.
Search effort; proportion of source-backed answers; questions escalated to specialists.
Document the discrepancy, inform procurement and agree next steps with the process owner.
Example source: Process manual · Section 4.2 · Version 3.0
Answers from approved sources, respecting access permissions.
Agreed data from existing systems is combined for recurring reports. Exceptions are shown with their supporting data for expert assessment.
Metric definitions and data quality are clarified first. Approvals and the origin of values remain traceable.
How we measure value: Preparation effort; data freshness; time to address an exception.
Clarify relevant sources and access, such as ERP, CRM, documents or production data. Start with the information the selected process actually needs.
Align fields, terminology and ownership. Duplicates, gaps and conflicting definitions are surfaced and handled using agreed rules.
Analyse, classify or use information to draft responses for the specific use case. Quality is assessed against representative test cases.
Bring results into the workflow with approvals, logging, exception handling and a clear handover to your team.
Up to 3 processes and 3 interviews. Prioritised use cases, business case and decision brief. Indicative timing: 10 working days after receiving inputs.
Discuss your opportunity1 process, up to 2 standard integrations and 10 pilot users. Test plan, approvals and handover. Indicative timing: 4–6 weeks after technical review.
Discuss your opportunity1 workflow and 4 support hours per month. Reviews, adjustments and user support. Term and response times as agreed in the proposal.
Discuss your opportunityFor businesses only. All prices exclude applicable VAT. Licences, API usage and additional integrations are separate. Indicative service description; binding scope follows assessment and an individual proposal.
A standard integration uses an existing, documented interface with sufficient permissions and test access. Suitability is checked before the proposal. Custom interface development, data migration and additional systems are priced separately.
Sample structure, not a client reference: process brief with current effort, data and interface assessment, benefit calculation with assumptions, and a prioritised pilot recommendation with effort and acceptance criteria.
Choose the tool after understanding the process. Compare value, the consequences of errors and ongoing effort for each task.
The outcome should define what is automated, what remains with people and who operates the solution after handover.
An estimate based on your assumptions. Capacity value is not guaranteed cash savings. Use time saved after human review and rework. All inputs remain in your browser.
Calculation: cases × minutes ÷ 60 × realisable share = usable hours. Hours × full hourly cost = capacity value.
Annual values assume twelve identical months. Modelled capacity value less running costs, and less the one-time investment in year one. This is not a profit or cash-flow promise.
The initial investment is your total budget for the project being assessed. It differs from the starting price of an individual service package. Ramp-up time and utilisation can reduce first-year benefits.
From the first useful use case to controlled operations. Black Darter® leads process analysis, business case and project management. Our technical implementation partner delivers the solution and integration.
Your contact for process assessment, the business case and project management. We agree requirements and acceptance with your team.
Handles the agreed architecture, integration and development. Providers, access rights and the operating model are defined before implementation.
Appoints process owners, supplies approved data and reviews results. Production actions follow the agreed approvals.
The proposal identifies the contracting party, usage rights, acceptance, operation and support. Any direct contract with the technical partner is stated explicitly.
Not automatically. We first assess whether existing systems can provide the data and workflows needed. A suitable interface may be enough. Integration, data quality and access limitations are documented upfront.
Agreed test cases and a credible before-and-after comparison. Errors, rework and team adoption matter alongside time savings. Wider rollout makes sense once quality, costs and operational accountability fit together.
No. Released time is initially additional capacity. Cash impact occurs, for example, when overtime, external expense or required resources actually decrease. We therefore distinguish capacity value from realisable financial impact.
We agree contacts, interviews and test dates in advance. The AI opportunity assessment includes up to three interviews. A pilot requires feedback from process specialists and acceptance.
Approval rules are defined explicitly in the project. In the workflow shown here, prices, delivery commitments and binding decisions remain with the responsible people.
Before implementation, we clarify required data, access rights, providers and storage locations. Accounts, usage rights, documentation and operating responsibilities are defined in the proposal and at handover.
Tell us about the task, the systems involved and the outcome you need. Together, we define a useful first step.
Discuss your opportunity