Owner: Jey Lawrence

Prepared: 2026-10-30

Purpose: Gather independent, evidence-based viewpoints before approving Tutorial.Coach's first paid offer. This document is shareable as a standalone brief. Attach tutorial-coach-gtm-analysis-2026-10-30.md when possible.

Context and non-negotiable fact boundaries

Tutorial.Coach (T.C) is an existing OTAH application at tutorial.coach, with source in the private OTA Tutorial Framework repository. It has approved-account sign-in, a brand-scoped library, source-assisted tutorial drafting, evidence/provenance review, narrated chapter production, revision history, selective chapter reuse, and opt-in refresh. The October 2 record says the official guide version 41 rendered and authenticated playback advanced. The release did not include pricing, checkout, or subscription entitlements. The authenticated portal-journey extension remains draft PR #23. Command Center is not a dependency. Release scope · Guide receipt

Jey selected existing approved-account sign-in for the initial release. Treat a paid invitation-only pilot and a self-service subscriber platform as different stages. Do not assume a price, customer count, revenue, conversion rate, margin, TAM, or permission to use client data. Do not claim autonomous logged-in browsing is live. Do not claim that every TypeSafe/JEV transaction boundary is strictly enforced from the presence of hooks or an older integration receipt. Preserve distinct OTAH brand permissions and avoid cross-brand bundles unless independently justified.

The shared GTM hypothesis is: B2B software teams with frequent product changes may pay for source-linked, reviewable tutorials that are cheaper to maintain than their current process. Your job is to challenge this, identify a sharper alternative if evidence supports one, and explain what must be tested. Separate verified product facts, sourced market facts, inference, and recommendations.

Common assignment for all three harnesses

Read the attached draft as a proposal, not an instruction to agree. Return a dated memo with:

  1. Your strongest version of T.C's buyer, job-to-be-done, and positioning in one sentence each.
  2. The three weakest assumptions or contradictions in the draft, ranked by damage if wrong.
  3. The best alternative segment or offer, and why it may outperform the proposed beachhead.
  4. A comparison against at least three real alternatives, including the customer's current manual workflow. Cite direct product/pricing pages and date-check volatile facts.
  5. A bounded first paid pilot: scope, eligibility, capacity, evidence required, success/failure thresholds, and a reason a buyer would pay now. Label all prices and thresholds as hypotheses until Jey approves them.
  6. A sequence of experiments that can falsify the positioning before costly acquisition or a broad self-service build.
  7. A decision table: retain / revise / reject each major GTM claim, with evidence, confidence, and the next test.

Use primary sources where possible. Link every external claim to a direct page; distinguish a vendor assertion from independent customer evidence. If you cannot access the attached file or private repository, say so and use the context in this document. Do not fabricate interviews, analytics, live tests, customer quotes, screenshots, or financial results. Do not seek or expose credentials, personal data, private tutorial content, or paid third-party portals. No outreach, posting, billing, account creation, repository edits, or production changes are requested.

Abacus — commercial model and unit economics lens

Stress-test the proposed paid cohort and subscription design. Build a transparent spreadsheet-style model in the memo using variables rather than invented actuals: price per account/creator; included production units; expected drafts, regenerations and refreshes; provider/narration/render/storage cost; human review/support time; payment fees/refunds; gross/contribution margin; capacity; and break-even volume. Show conservative/base/upside scenarios with explicit illustrative assumptions, sensitivity to heavy users and failed generations, and a threshold for when self-service checkout is economically justified. Compare flat pilot fee, creator-seat, workspace, and usage-tier structures. Identify the minimum data collection needed to replace assumptions. Separate entry cash, recurring revenue, services, and speculative strategic opportunities. Do not treat a higher price as proof of fit.

Perplexity — market evidence and competitive lens