You describe the problem and we assess the fit. Where deeper work is needed, we propose paid discovery with a clear scope. A pilot or implementation is a separate decision.
No. The current workflow, systems, recurring problems and desired change are useful starting points. The specification follows discovery.
No. Rule-based automation, integrations and conventional software are equally valid choices. AI is used when interpreting information justifies the additional complexity.
Yes, when it has known users, available information and explicit evaluation criteria. A pilot should test an important uncertainty in a bounded, coherent workflow.
02In practice
Scope and responsibility
Scope, risk, integrations and available information affect the estimate. Discovery and implementation are agreed separately. We do not publish one price for different problems.
We can start by reviewing the product, code, dependencies and release process. Available documentation and rights to the code affect the feasible scope.
Ownership, licences, repository and account access, and handover are agreed for each engagement. These responsibilities should be explicit before delivery.
We design permissions, validation, environment separation and failure handling around the data and workflow. Detailed controls are defined within the project scope.
03In practice
After the inquiry and after launch
The product can be handed over, supported under agreed terms or developed further. Scope, availability and any service level require a separate agreement.
The reply goes to the email address you provide. This website does not offer a guaranteed response time. If the form cannot save your inquiry, keep your message and email hello@evin.media.
