01Your custom workflow
- One bounded trigger-to-outcome process with simple logic.
- Define the trigger, required inputs, and intended output.
- Configure the approved steps and field mapping.
- Test the agreed path, document how to use it, and configure appropriate error handling and monitoring.
- Maintain the accepted workflow while its monthly service is active.
Workflow capacity (slots) measures build complexity, not execution count: simple = 1 slot, standard = 2, complex = 4. For example, 24 slots can fund 24 simple, 12 standard, 6 complex workflows, or a mixture. Agent and connection limits are separate; API usage is separate. Integrations are approved, bounded connections—not unlimited custom API development. Included capacity is counted once; the same work is not charged again as an add-on. This buys one scoped workflow, not a package of unrelated processes. Starting/reference configurations cover bounded standard-complexity work. Exact deliverables, capacity, dependencies, and acceptance milestones are confirmed and costed before the deposit. Requirements beyond that scope need an approved quote. Scope is confirmed before payment. Third-party subscriptions, API/voice usage, hardware, and applicable taxes are separate. No unlimited usage or support is implied.