# Tee Time Master Onboarding Pack

This folder shows how a diligent business owner could document
[Tee Time Master](https://teetimemaster.com/) before onboarding it to Oblive.

The documents are intentionally written as normal business references. An owner can copy this
structure, replace the example details with verified company information, and provide the resulting
Markdown files during onboarding.

## Documents

- [Organization](organization.md) — who we are, what we sell, who we serve, how we make decisions,
  and which actions always remain human-controlled.
- [Integrations](integrations.md) — the tools we use, what each one is authoritative for, and how
  Oblive may use it.
- [Organization Workflows](workflows.md) — recurring cross-functional processes and their approval
  gates.
- [Growth](departments/growth.md) — acquisition, positioning, campaigns, experiments, budgets, and
  reporting.
- [Engineering](departments/engineering.md) — product delivery, course integrations, reliability,
  security, and incidents.
- [Support](departments/support.md) — customer communication, booking failures, refunds, privacy,
  escalation, and quality.

## How To Read This Example

Public product and policy details are based on Tee Time Master's website as of July 19, 2026.
Private operating details are realistic examples rather than claims about the company's actual
internal operations.

The example deliberately includes:

- named owners and systems of record;
- explicit approval boundaries;
- complete workflows with triggers, inputs, steps, outputs, and failure handling;
- department-specific preferences rather than one generic company voice;
- known limitations and unresolved legal work; and
- no credentials or secret values.

The integration inventory is onboarding evidence, not a live connector list. It deliberately omits
Apollo: connecting Apollo later should make it immediately usable, open a focused business-context
warning, and add an exact `connector_key = "apollo"` only after a reviewed mapping. The other listed
business systems remain valid Context even when they are external or not connected through Oblive.