What you receive
- One client-owned form and one flow using built-in connections supplied by the selected apps, with up to two additional client-owned apps and up to five total agreed steps, including the trigger.
- The agreed internal task, welcome-message draft, and job log, with mapped fields and approval points documented.
- Evidence from normal, duplicate, incomplete, and destination-failure tests.
- Manual recovery notes, a handover guide, and one consolidated in-scope preference revision.
Price and scope
The $149 USD fixed pilot covers one client-owned form, one flow using built-in connections supplied by the selected apps, up to two additional client-owned apps, and up to five total agreed steps after a written fit check. A step is one trigger, action, or transformation; the flow's trigger counts toward the five-step limit. The flow, fields, recipients, approval points, test cases, and maintenance owner are confirmed before work starts.
No custom API or webhook development, branching, complex transformation, payment action, contract acceptance, regulated or sensitive intake, or autonomous customer-facing send is included. If the available built-in connections or failure handling make the work materially larger, we stop after the fit review and provide a written custom quote.
Third-party subscriptions and usage fees are separate. Live enablement requires separate explicit permission after your named approver reviews the map, recipient rules, test results, and recovery path.
You review and approve the finished pilot, test results, and handover before payment is requested. Final editable files and handover materials follow confirmed payment.
What to provide
- Accounts your organization owns, the apps you want to connect, and the account owner who can grant the approved access.
- The accepted form fields, internal recipients, message draft, task and job-log requirements, and one named approver.
- Representative normal, duplicate, incomplete, and destination-failure cases.
Never place passwords, API keys, tokens, payment details, or sensitive customer records in the project inquiry.
From approved map to tested pilot
- Confirm feasibility, ownership, fields, recipients, approval points, steps, and failure boundaries.
- Build the pilot with the selected apps' built-in connections in the approved client-owned tools, without enabling live operation.
- Run and record the four agreed test cases, then prepare the recovery and handover notes.
- Your approver reviews the flow, tests, recipients, and recovery path before any separately authorized live enablement.
How the workflow is checked
- Confirm that a normal submission creates the agreed internal records without silently dropping a required field.
- Use the agreed stable reference to identify duplicate submissions and prevent duplicate internal work.
- Keep incomplete submissions visible for review rather than treating them as complete.
- Test a destination failure, record the incomplete step, and show the named owner how to recover.
What is outside this package
Custom APIs or webhooks, branches, migrations, complex transformations, payment actions, contract acceptance, regulated or sensitive intake, autonomous customer-facing sends, monitoring, and unlimited support are excluded. The pilot does not guarantee that a third-party connector or app will remain available or unchanged.
See procedure and reporting examples
The shared-drive handover procedure makes roles, checks, and approval points explicit. The service-request report shows how actual records can be organized for review. A connection between your apps still needs to be built and tested in a pilot.
Start with a description of the handoff
Tell us which form starts the work, which two apps receive information, and what should happen in no more than five total steps, including the trigger. We check the built-in app connections and boundaries before confirming the $149 pilot. No credentials or private records are needed for the first inquiry.
Clear scope. Careful checks.