Buildooor Discovery Session Terms
Version 0.1 | Effective Date: [DATE]
This summary is written for the paid discovery-session front door: one booked session, clear boundaries, and separately scoped follow-on work only if the session earns it.
1. Purpose Of The Discovery Session
The client is buying a limited paid session so Buildooor can review the current technical context, diagnose where the setup is brittle or blocked, and recommend the right next move. It is not, by itself, a promise to complete a full production build, launch, migration, or feature roadmap.
2. Commercials
Fees are prepaid for the booked discovery session or reserved work block. Reserved blocks may be used as live sessions or as independent Provider work against the agreed discovery lane.
3. Included In This Session
This session usually includes discovery, environment setup where reasonably needed, troubleshooting, limited debugging or implementation work tied to the diagnosis, and a short written recommendation or next-step plan.
4. Not Included In This Session
Unless expressly included, this session does not cover guaranteed feature completion, production deployment, SLA-backed support, compliance programs, full repo or platform transfer, or a guaranteed private-infrastructure buildout.
5. Rights And Reuse
Subject to full payment, the client may internally use the client-specific notes, recommendations, code changes, and configuration changes delivered in this session. Buildooor retains its reusable tools, workflows, internal methods, and shared improvements.
6. Confidentiality And Data Boundary
Mutual confidentiality applies to non-public business and technical information shared for the engagement. Regulated or specially protected data is out of scope unless separately agreed in writing.
7. Future Work And Follow-On Engagements
Later work, implementation, coaching, hosted modules, transition work, or expanded rights require separate written approval, invoice acceptance, or Stripe checkout acceptance. If a follow-on engagement does not say otherwise, it is governed by the same engagement letter.
8. Warranty And Liability
The work is exploratory and may involve incomplete systems, changing dependencies, and third-party constraints. Aggregate liability is capped at the fees actually paid under the engagement letter, to the maximum extent permitted by law.
9. Acceptance And Full Text
Full editable draft lives in docs/legal/discovery-session-engagement-letter-v0.1.md. Invoice payment, Stripe payment, and electronic acceptance against a proposal or checkout that references that draft are valid acceptance.