Workflow Audit
A handoff review for one Softr app or client portal before production transfer.
- Workspace, billing, role, and integration map
- Missing launch evidence and access cleanup list
- Client-ready handoff checklist
Softr consultant handoff
Hand a Softr app to the client without becoming the billing or support owner.
Use this checklist when you are building for a client in Softr and need a clean line between prototype work, client-owned production access, nonprofit billing questions, and long-term maintenance.
Checklist
The handoff fields to settle before production.
1Workspace OwnerConfirm the client owns the production Softr workspace before launch. Keep your sandbox only for prototypes, duplicate testing, or reusable components.
2Billing and PlanSeparate your consulting fee from the Softr subscription. Have the client handle nonprofit discount eligibility and plan payment directly with Softr.
3Access RolesList every admin, collaborator, client owner, and data-source owner. Remove temporary access after acceptance unless ongoing support is included.
4Data SourcesDocument Airtable, Google Sheets, HubSpot, Stripe, Make, Zapier, or other connected accounts, including which client account owns each integration.
5Domain and DNSRecord the custom domain, DNS host, verification records, SSL status, and the person responsible for future domain changes.
6Support BoundaryDefine what is included after launch: bug fixes, content edits, user invites, data updates, billing questions, and feature requests.
Deliverables
What TinyOps can produce for a Softr handoff.
Build or Handoff Cleanup
A bounded implementation pass around one Softr app, workflow, or launch checklist.
- One agreed trigger, page flow, or integration path
- Acceptance checks and rollback notes
- Plain-English client handoff packet
Client packet
What the client should receive.
App map
Pages, user groups, gated content, data sources, automations, and custom code or embeds.
Launch evidence
Test users, key screenshots, payment or form test notes, DNS status, and known limitations.
Maintenance notes
Where to edit content, where user data lives, what should not be changed, and who handles billing/support.
Need a second set of eyes before client handoff?
Send the app purpose, current owner, connected tools, plan/billing status, and what the client needs to operate after launch.