Engagement Standard
Clients own the delivered workflow logic and configuration.
Every project starts with a clear Statement of Work.
Systems are modular, documented, and maintainable.
Using this website or submitting an enquiry does not create a client relationship. Professional engagements begin only after a written Statement of Work is signed, defining scope, delivery phases, responsibilities, fees, and acceptance criteria.
After full payment, the client owns deliverables produced specifically for the engagement, including workflow maps, automation logic, custom documentation, and agreed configuration. Ductio retains rights to pre-existing methods, reusable patterns, and generic engineering know-how.
Ductio will not develop automations for deceptive practices, bulk unsolicited communication, or workflows that violate the policies of underlying platforms or model providers. Projects with high risk to data integrity or operational safety may be declined.
Ductio does not position fully autonomous AI as the default for critical business functions. Automations involving financial transactions, external client communication, legal records, or sensitive decisions should include human approval gates.
Workflows may depend on CRMs, APIs, storage providers, automation tools, model providers, and other third-party platforms. Ductio designs for resilience but does not control provider uptime, pricing, policy changes, or API availability.
Project fees, milestone schedules, expenses, taxes, cancellation rules, and maintenance retainers should be defined in the specific proposal or agreement. Late payments may pause monitoring services or API-based support functions.
CRM operations, reporting workflows, approvals, document handling, and AI-assisted internal tools.