Prep is a planning tool
The future Terms should make clear that Prep provides planning support, estimates, and structured outputs. It should not be described as a guarantee of final schedules, budgets, or production outcomes.
Prep. terms
This is a working placeholder for the Terms behind the future paid product.
It explains the intended structure and the legal work still to be done.
What this page is
This page is a product-facing draft of the terms logic we expect to need. It is here so the product language, privacy model, pricing model, and consultancy boundary can be shaped honestly before a final Terms document is written and reviewed.
Users remain responsible
The final responsibility for production decisions, financial commitments, delivery obligations, staffing choices, and contractual obligations will remain with the user and their project team.
Outputs remain advisory
AI script checks, schedules, budgets, and reports are working materials for review. They should be checked by the project team before they are used for commitments or delivery decisions.
Consultancy is separate
Using the app and working with us directly are related but different things. The Terms should make clear that consultancy, bespoke schedules, bespoke budgets, and independent advice are governed separately from the self-serve product.
Likely topics in the final Terms
What Prep is and is not.
Account, subscription, and payment terms.
Acceptable use and user responsibilities.
Limits of liability and no guarantee language.
Intellectual property and ownership of user inputs and outputs.
AI script analysis, saved reports, and provider/data-handling commitments.
What happens when a subscription ends or an account is closed.
Next steps
Decide the pricing and subscription structure for the paid product.
Define what export, save, compare, and collaboration features belong in each plan.
Draft the final Terms around the real billing and product model.
Run a legal review before taking paid users.
Related
Privacy and Terms need to be written together, because saved projects, billing, support access, and account controls all affect both.