- Scope counts and provider billing differ
- Triggers, actions, and paths define our delivery scope. They do not represent provider billing tasks or executions. We agree expected volume and the provider usage budget before kickoff.
- One workflow using supported connectors
- Your apps must offer the required native connectors, permissions, and plan features. Recovery and alerts depend on platform capabilities; the package does not include continuous monitoring or a guaranteed business outcome.
- Your inputs and accounts
- We confirm fit, scope, one language, and required access before work. You supply final content, branding, approved policies, and suitable provider accounts. Accounts and licenses stay in your name.
- Two payment milestones
- 50% at kickoff. The remaining 50% is due after you approve the preview, before any agreed activation and handover.
- A schedule we agree together
- Estimates begin after we receive the deposit, complete inputs, and access. Timing depends on compatibility, provider approvals where needed, and timely, consolidated feedback.
- Handover and agreed-scope fixes
- The agreed deliverables and any included walkthrough follow final payment. For 14 days after handover, corrections for failures against the agreed scope are included. New requirements and ongoing maintenance are quoted separately.
- Agreed acceptance checks
- We agree acceptance checks before work and review the deliverables against them before handover. Prototypes and review reports are checked against their agreed questions and scope.
