Operational standards
This page describes the operational standards we apply to every CorpFlowAI engagement. It is not a contract — final terms are confirmed in the written offer, invoice, or service agreement.
The four pillars
How an engagement is run
Review cadence
Every active engagement has at least one operator review per week. During a live delivery window, that becomes one review per business day. Reviews are scheduled by the operator, not the client - you do not have to chase us.
Monitoring
On a live engagement we monitor the agreed capture and follow-up path so drift is visible early. Exact channels and checks are defined in the written scope.
Payment after review
No card or banking details are collected on this website. No payment is taken when you request a diagnosis. If Lead Rescue is a fit, commercial terms are confirmed in the written offer. Cancellation windows before setup begins are published on the refund-policy page.
No revenue guarantees
We do not promise revenue, lead volume, or conversion lift. Our marketing pages avoid revenue claims and "X% uplift" language by policy.
What “done” means
Live verification, not just health checks
A change is only operationally complete when the customer-facing surface is verified live in production. CI green and a successful deploy are necessary, but they are not sufficient on their own.
- The deployment id and exact commit deployed
- The live URLs and flows tested after deployment
- Expected versus actual behaviour
- A final verdict: complete, partial, or failed
Governance
Visual assets and AI provenance
Buyer-facing assets are governed so their source, accessibility metadata, and allowed surfaces are known. Machine-generated assets are reviewed before publication.
Security posture
- Tenant isolation. Tenant data is isolated server-side and public marketing pages do not expose private client records.
- Diagnosis first, payment second. The public website does not capture card or banking details. Commercial terms are confirmed in writing before payment.
- Least access. We ask for the minimum access needed for the agreed scope.
- No card data on CorpFlowAI servers. Payment capture, when offered, happens off the public marketing surface.