Before you start
Implementation process questions
Is every implementation completed in 30 days?
No fixed delivery period is promised for every project. We agree the schedule after reviewing scope, access, data readiness, approvals, and provider dependencies. A focused sprint may be suitable, but a 30-day plan is only a commitment when it is explicitly agreed for that project.
How much time will our team need to contribute?
It depends on the workflow and the decisions required. We identify the process owner, walkthroughs, approval points, test reviews, and handover participation during scoping. A fixed three-to-five-hour total is not assumed.
Is the free audit the same as full discovery?
No. The initial free audit provides a one-page workflow summary and a 15-minute review call based on the information you share. Detailed technical discovery, access checks, proof-of-concept work, and implementation planning may require a separate agreed scope.
Do you always use AI or self-hosted infrastructure?
No. Rule-based workflows, native integrations, and managed or self-hosted platforms are assessed according to the requirements. AI, dedicated servers, and new databases are not assumed. Their data handling, licensing, operating costs, and maintenance responsibilities must be agreed if included.
What happens if an integration is not technically feasible?
We explain the limitation and assess supported alternatives before committing to that action. If a dependency changes during implementation, we review the impact and agree how to proceed rather than silently replacing the requirement or expanding the scope.
How do you decide the workflow is ready to launch?
The proposal defines acceptance criteria and test scenarios. We review the evidence, unresolved issues, known limitations, operational ownership, and fallback procedure before the agreed launch authorization. Testing reduces risk; it does not guarantee an error-free system.
What if we request changes during the build?
We review whether the request fits the approved scope. Additional actions, systems, revisions, or business rules may require a change agreement covering price, schedule, and testing before the work is added.
Do we receive every password or master key?
The handover provides the agreed account access, ownership arrangements, and recovery responsibilities. Authorization should use appropriate account roles or another agreed secure method—not a bundle of shared master passwords. Credentials are transferred or rotated only where required by the design and agreement.
Is 30-day support or 24/7 monitoring included?
Neither is included by default based on this page. Launch support has an agreed scope and period. Ongoing monitoring, response coverage, maintenance, and enhancements require explicit terms. Monitoring availability is not the same as a guaranteed human response time.
Who handles maintenance after handover?
The agreement identifies the owner for monitoring, credential renewal, platform changes, hosting, and future fixes. Optional support can be scoped separately. Third-party fees and responsibilities continue regardless of who built the workflow.