Operational standards
Last updated: May 2026. This page may be updated from time to time.
This page describes the operational standards we apply to every CorpFlowAI engagement. It is not a contract — final terms are confirmed on the invoice or service agreement — but it is an honest description of how we work, written so a prospective client can decide whether the standard fits before any payment is taken.
The four pillars
How an engagement is run
Review cadence
Every active engagement has at least one operator review per week. During the seven-day pilot monitoring 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: every lead-source capture path with a synthetic test ping, the alert delivery path on the owner's preferred channel (email, SMS, or WhatsApp), the daily summary delivery, and the running log of captured leads versus follow-up status so we can spot drift early.
Payment after review
No card or banking details are collected on this website. After intake review, we send the appropriate invoice route (MUR for Mauritius, USD for international clients). The cancellation window before pilot setup begins is published separately 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. If you need revenue forecasting, that is a different engagement - and one we do not currently offer.
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. For every change we ship on your behalf, we record:
- The deployment id and the exact commit deployed
- The live URLs and flows we tested after deployment
- Expected versus actual behaviour
- A final verdict: complete, partial, or failed
If a change is not on the production deployment’s commit, the verdict cannot be “complete”. If a client-facing URL is broken, the verdict is “failed” — even when internal endpoints are healthy. This standard is codified in our internal delivery rules and applied to factory infrastructure work and client engagement work alike.
Governance
Visual assets and AI provenance
Every visual that ships on a CorpFlowAI surface is governed by a manifest that records the asset’s source, licence tier, accessibility metadata, and allowed surfaces. AI-generated images carry an additional provenance record that names the prompt used (linked to our internal prompt library), the model and version, and the human reviewer. AI-generated images appear on the page with an unobtrusive “About this visual” disclosure so visitors can see that the asset was machine-generated and human-reviewed.
The hand-crafted SVG diagrams on this site (including the timeline at the top of the process page and the journey on the onboarding page) are CorpFlowAI-owned artwork and do not carry an AI provenance disclosure - there is no AI to disclose.
Security posture
- Tenant isolation. Tenant data is isolated server-side. Webhooks validate HMAC. Authentication never collects card data on this site.
- Intake first, payment second. The public website does not capture card or banking details. Payment routes are issued only after intake review, on the appropriate currency channel.
- Least-access pilots. A pilot requires access to one lead source and an owner notification channel - nothing more. If a pilot would need broader access (deep CRM, production database, payment processor), we say so before payment, not after.
- Hand-over by default. Every artifact we build (Google Sheets, scripts, configurations) belongs to the client. If you choose to step away, you take everything with you.
Boundaries of this page
What this page is, and what it is not
This page describes how we operate. It is not a contract and it is not legal, tax, or accounting advice. Final terms are confirmed on the invoice or service agreement. The published standard may be updated; we will continue to honour whatever standard was in effect at the time of your engagement.