The task
The same information is copied between inboxes, spreadsheets and business systems, with repeated checking and follow-up.
Concept Media · AI for service businesses and SMEs
Connect enquiries, documents, booking and follow-up in a workflow your team can understand. Use AI where information needs interpretation and fixed rules where the next step is predictable.
Your first enquiry is free of commitment. A paid audit, workshop or project starts only by agreement. Meet Patrick and Concept Media.
The same information is copied between inboxes, spreadsheets and business systems, with repeated checking and follow-up.
We map one workflow with one input, one output and one AI step across up to two systems using supported standard connectors. The delivery includes agreed triggers, validation, an exception path, tests and handover instructions. A custom API connection has separate scope.
A customer emails a service request with an address and a vague fault description. A workflow can identify the job type, collect the required fields and prepare a case. If the address is missing, the request goes to a person rather than creating an incomplete job. A forwarded copy must be recognised to avoid creating the same case twice. We also test what happens when the destination system is unavailable.
An illustration of a possible delivery, not a reported customer result.
An example to scope together
An agreed trigger starts the workflow, such as a new message in a specific inbox.
AI interprets the text and proposes the fields needed by the next system.
Rules check missing values and duplicates; a person handles exceptions.
Approved data is transferred, while failures are recorded with a named owner.
AI can sort a message, extract its meaning or prepare a draft. Integrations transfer validated data; fixed rules control prices, required fields and allowed actions.
An agreed process, representative inputs, supported system access and an owner for exceptions. We check existing software before proposing a new build.
Compare end-to-end handling time, review time, failed runs and corrections with the starting process.
The quote defines the expected result and who can approve it. These are acceptance tests, separate from your later measurement of time and business value.
The agreed example produces the expected output, ready for the responsible person to review.
Required fields stop the transfer and reach the person responsible for exceptions.
A repeated event follows the agreed duplicate rule without an unintended extra record.
The failure is visible. A permitted retry must preserve the duplicate rule.
A standard connector must support the agreed input and output. If the task needs a custom API connection or more workflows, we quote that scope separately.
From DKK 14,900excluding VAT · total project price
One input, one output and one AI step using existing supported standard connectors across up to two systems. Includes the audit, testing, an exception path, documentation and handover.
The workflow uses existing supported standard connectors for one simple input-to-output process. System integration covers a custom-built API connection with its own field mapping, validation, logging and exception handling. Additional directions and workflows are scoped separately.
A starting price does not guarantee that your task fits this scope. We check access, examples and acceptance criteria before you order and give a fixed quote. Licences and usage are separate.
The DKK 4,995 workflow audit is included in the total project price and fully credited against a subsequent solution for the same workflow. For example, a DKK 14,900 project leaves DKK 9,905 after the paid audit. If the task is already defined, necessary analysis is included in the project quote.
As an indicative planning estimate, allow 2–4 weeks for a small workflow once access and examples are ready.
This is a planning estimate, not an agreed delivery date. Availability, review and supplier dependencies are confirmed in the quote before work starts.
When variable input needs interpretation, such as free-text emails. If the fields are already structured, a conventional integration may be simpler and more predictable.
We agree stop rules, a visible exception path and a responsible person. Tests include missing fields, repeated events and system failures. Re-running follows the agreed duplicate rules.
Describe the task you want to make easier. We will discuss the fit and a concrete next step.