# Tee Time Master — Organization ## Company At A Glance | Field | Detail | | -------------------------- | ------------------------------------------------- | | Organization name | Tee Time Master | | Website | [teetimemaster.com](https://teetimemaster.com/) | | Founder | Joshua Bing | | Stage | Pre-launch, building the founding-member waitlist | | Default operating timezone | America/New_York | | Default currency | USD | | Enabled departments | Growth, Engineering, Support | | Final human decision owner | Joshua Bing | ## What We Do Tee Time Master helps golfers secure high-demand tee times without waking up to race a booking window. A golfer connects their own course account, tells us the courses, dates, times, and group size they prefer, and creates a Watch. When a matching time opens, the service attempts to book it on that golfer's account and sends a clear confirmation or failure notice. We are a software tool acting on the golfer's instructions. We are not a golf-course broker, reseller, marketplace, or inventory owner. ## Customer Problem Our primary customers are: - golfers competing for weekend morning tee times; - regular foursomes that want to book together; - members of courses with short, predictable online release windows; and - golfers who value convenience but will not use a black-box or resale service. The central problem is that desirable tee times can disappear seconds after release. Manual booking forces golfers to be online at an inconvenient hour and still provides no reliable outcome. ## Product Boundaries The product includes: - preferred-time Watches; - monitoring of compatible online course-booking systems; - own-account booking attempts; - booking and manual-handoff notifications; - fairness controls when multiple Tee Time Master customers want the same slot; and - an audit trail that explains what was attempted and what happened. The product does not: - guarantee that a tee time will be available or booked; - hold, resell, transfer, auction, or hoard tee times; - book through an account the customer does not own or control; - defeat CAPTCHA, multi-factor authentication, identity checks, or course security controls; - override course prices, cancellation policies, or terms; or - represent itself as affiliated with a course unless that relationship is documented. ## Business Model - A customer's first successful booking is free. - Each later successful booking carries a flat USD 5 Tee Time Master service fee. - There is no monthly subscription and no long-term contract. - Course green fees, cart fees, and other course charges are separate and remain payable under the course's own terms. - The Tee Time Master service fee is ordinarily non-refundable after a successful booking because the service was performed. Exceptions required by law or granted at our discretion need human approval. ## Current Priorities In order: 1. Complete product, legal, security, and support readiness for launch. 2. Expand reliable course coverage without bypassing course rules or hard controls. 3. Convert qualified waitlist demand into connected accounts and first successful bookings. 4. Prove booking reliability, fair access, and clear customer communication. 5. Learn which courses and release windows create enough repeat value for sustainable growth. ## Company Health Metrics We review: - qualified waitlist growth by course and geography; - invited-user to connected-account conversion; - connected-account to active-Watch conversion; - Watch-to-match and match-to-successful-booking rates; - time from slot release to booking attempt; - manual-handoff rate; - successful service-fee collection; - customer-reported booking failures; - support response and resolution quality; and - security, privacy, fairness, payment, and course-policy exceptions. ## Organization Systems Of Record | Area | Source Of Truth | | ------------------------------------------------------------ | ----------------------------------------------------------------- | | Customer identity and account state | Production application database, keyed by internal customer UUID | | Watches, matches, booking attempts, and fairness decisions | Production application database | | Service fees and payment status | Stripe | | Product and funnel analytics | PostHog | | Launch leads and course-demand segments | HubSpot, with the raw waitlist register retained in Google Sheets | | Customer conversations | Help Scout | | Product roadmap, policies, decisions, and experiment history | Notion | | Source code, pull requests, releases, and technical issues | GitHub | See [Integrations](integrations.md) for access and usage boundaries. ## Decision-Making - Every material decision has one directly responsible owner. - The owner consults every function affected by customer, legal, security, reliability, or spend consequences. - Reversible decisions should move quickly with written evidence and an explicit rollback path. - Irreversible or consequential decisions require human approval before execution. - Customer trust and legal or security safety outrank reliability; reliability outranks launch speed; launch speed outranks scope. - Active work is limited to one major initiative per department plus urgent operational work. - Plans use a six-week outcome horizon and are reviewed weekly. ## Collaboration And Reporting - Written asynchronous updates are the default. - Meetings are reserved for incident command, blocked cross-functional decisions, or material disagreements that written discussion cannot resolve. - Weekly reports lead with outcomes, exceptions, owners, and next decisions. - Supporting detail should link to the source of truth rather than reproduce raw data. - Security, privacy, fairness, legal, payment, production, or customer-trust exceptions are escalated immediately rather than waiting for the weekly review. ## Human Approval Boundaries Oblive may research, analyze, compare, draft, prepare, validate, and recommend. A human must approve before Oblive or any connected system: - sends a customer reply, campaign, SMS, or public post; - changes a public claim, launch date, price, offer, or policy; - starts or increases paid spend; - charges, refunds, credits, writes off, or otherwise moves money; - deploys to production, performs a production write, or runs a schema migration; - changes a secret, credential, encryption rule, access control, or fairness control; - enables a new course adapter in production; - exports, corrects, or deletes customer data; - accepts legal terms or makes a legal commitment; or - bypasses or attempts to circumvent a course control. Joshua Bing may stop any automated or agent-assisted work immediately. Any suspected security, privacy, payment, fairness, or course-policy issue pauses the affected workflow until reviewed. ## Data And Security Sensitive data includes: - course-account credentials; - authentication data; - payment references; - customer contact details; - booking and cancellation history; - IP addresses and security logs; and - privacy-request and incident records. Our operating rules are: - course credentials are encrypted at rest and used only to operate the customer's own account; - secrets and full card numbers never appear in logs, support tickets, onboarding documents, or analytics; - access is scoped to the customer and task being handled; - course credentials are deleted when the customer disconnects the course account; - customer data is minimized in support and reporting surfaces; and - consequential data access, export, correction, or deletion remains human-controlled. ## External Communication Style We sound plainspoken, calm, golfer-friendly, specific, and trustworthy. We explain limits directly. We do not use unsupported superlatives, manufacture urgency, disparage courses, or imply guaranteed availability. ## Known Gaps Before Launch - The public Privacy Policy and Terms of Service are marked as drafts. - The governing-law and dispute section requires completion with counsel. - The final public launch date is not committed. - Course coverage must be published from verified production readiness, not waitlist demand alone. - Internal systems and service targets in this example must be replaced with the real owner's confirmed details before use. ## Public References - [Tee Time Master](https://teetimemaster.com/) - [Privacy Policy](https://teetimemaster.com/privacy) - [Terms of Service](https://teetimemaster.com/terms)