Scope first
Every project should have written scope, deliverables, exclusions, client responsibilities, approval points, and support terms before production activation.
Terms
Plain-language working terms.
These terms are practical MVP placeholders for scope control. They are not a substitute for professional legal review.
No revenue guarantees
TrueGuide systems are designed to reduce missed inquiries and improve follow-up consistency. They do not guarantee revenue, bookings, sales, reviews, or business outcomes.
Human approval
Outreach, proposals, customer-facing messages, sensitive-data handling, tool connections, production deployment, prices, and deadlines require human approval.
Client responsibilities
Clients must provide accurate business rules, approved copy, tool access, test feedback, and a manual fallback owner for each workflow.
Refund and scope control
If an agreed starter workflow cannot be delivered, a simple setup-fee refund can be offered according to written scope. New workflows or changed requirements are separate scope.
Sensitive data
Medical, patient, payment, legal, financial, and regulated data workflows are excluded unless a separate compliance review is completed.
Cancellation
Monthly support cancellation terms should be confirmed in writing, including renewal date, data handoff, support end date, and active workflow status.
Production readiness
The MVP should not be deployed to production or connected to client accounts without environment configuration, testing, approval, and documented fallback steps.