Assessed Approvals and provider connectors. Approvals did not create a signed, tamper-evident agreement or certificate, and external users introduced guest and possible licensing requirements. Provider-backed flows were viable but would split activation-critical retry and status logic across systems.
- What worked
- The available connectors offered a plausible low-code orchestration option around an electronic-signature provider.
- What got in the way
- Approvals were not a substitute for signatures, and distributing critical workflow state between the application and flows complicated reliability and support.