Details on this page
What you receive
- One form and one straightforward workflow connecting up to two additional client-owned apps.
- An internal task, welcome-message draft and job log.
- Normal, duplicate, incomplete and failed-submission tests, plus a handover guide.
Price and scope
The proposed pilot fee is $350 USD for one form, one flow and up to two additional apps. The price becomes a project quote only after feasibility and acceptance checks are agreed.
The interactive example shows local intake logic. It does not establish that a particular pair of apps can be integrated. A working pilot in the approved tools must demonstrate capability before live activation or a payment request.
Third-party software costs, access, review steps and support limits are confirmed in the written scope. There is no “buy now” or live integration on this site.
What to provide
- Client-owned accounts, named destination apps and authorization for the required access.
- Approved fields, internal recipients, templates and a named approver.
- Examples of normal, duplicate, incomplete and failed requests. Never send passwords or API keys in the project brief.
How the work is checked
- Reject incomplete records and make missing information visible.
- Use a stable reference to prevent duplicate jobs and duplicate notifications.
- Test a destination failure, record the incomplete step and show the recovery path.
- Review mapped fields, notification content and handover instructions before enabling the live flow.
What is outside this package
Payments, contract acceptance, regulated or sensitive intake, complex custom APIs and unlimited support are excluded. No external welcome message is sent by the demonstration.
Inspect a fictional example
See the inputs, rules, output and open questions in a clearly labeled demonstration.
What can be automated
Intake validation, job creation, checklist preparation, internal notification preparation and missing-information drafts can be automated within approved boundaries.
A person reviews the exceptions and agreed checks before delivery. Automation does not approve business decisions or expand access to your systems.
Agree the work before payment
Start with a brief description and a redacted or fictional example. Scope, required inputs, timing, fees, revision allowance and payment arrangements are confirmed in writing first.
Operations & Research Support