# Hatchways Agentic Mode Business Case

Frame the smallest business case for adding HotTea as a Hatchways Agentic Mode without implying a partnership, procurement readiness, or finished GitHub App.

## Recommended Offer

Run a limited Agentic Mode pilot on one Hatchways-style GitHub assessment and evaluate whether the reviewer packet creates enough differentiated evidence to justify app-level integration.

## Value Hypotheses

### Defend practical assessments against AI-assisted interview feature pressure.

- Buyer signal: CodeSignal and HackerRank now publicly describe AI-assisted interview products; Hatchways can answer with evidence in its existing repo workflow.
- Proof: https://hottea.ai/hatchways/competitive.md

### Increase reviewer confidence without adding proctoring.

- Buyer signal: The sample packet gives hidden-check results, Claude JSONL exports, terminal/git/test telemetry, anomaly context, and an ATS-ready note.
- Proof: https://hottea.ai/sample-report

### Avoid a platform rewrite during early validation.

- Buyer signal: The verified GitHub Actions fallback can attach to a candidate repo before a real GitHub App exists.
- Proof: https://hottea.ai/hatchways/integration.md

### Create a narrow upsell story for AI-era technical assessments.

- Buyer signal: A buyer can evaluate the packet as Agentic Mode rather than as a replacement coding-test platform.
- Proof: https://hottea.ai/hatchways/decision.md

## Pilot Metrics

- Reviewer packet inspection time: One internal reviewer can inspect the sample packet and answer the pilot questions in under 10 minutes.
  - Evidence: https://hottea.ai/hatchways/pilot.md
- Evidence completeness: Packet includes transcript/session counts, hidden checks, git snapshots, public tests, VM events, and an ATS-ready note.
  - Evidence: https://hottea.ai/sample-report
- Workflow fit: Candidate repo, PR metadata, public tests, hidden grading, and human review remain intact.
  - Evidence: https://hottea.ai/hatchways/integration.md
- Current limits understood: GitHub App, SOC 2, DPA, SSO, retention SLA, and procurement gates are explicit before any enterprise claim.
  - Evidence: https://hottea.ai/hatchways/security.md

## Decision Path

1. If the sample packet is useful, configure the real GitHub App and run one partner-style pilot.
2. If the packet is useful but procurement blocks enterprise review, keep the GitHub Actions fallback for technical validation only.
3. If the packet is not useful to a Hatchways reviewer, stop before building deeper platform integration.

## Blocked Until Account Work

- Real GitHub App creation.
- GITHUB_APP_INSTALL_URL deployment configuration.
- Any claim of official Hatchways partnership or procurement readiness.

## Not Claimed

- No official Hatchways partnership.
- No real GitHub App before GITHUB_APP_INSTALL_URL is configured.
- No perfect anti-cheat or outside-AI prevention.
- No automated hiring decision.
- No enterprise security or procurement readiness beyond the named current controls.

## Proof URLs

- Business case JSON: https://hottea.ai/hatchways/business-case.json
- Decision brief: https://hottea.ai/hatchways/decision.md
- Pilot kit: https://hottea.ai/hatchways/pilot.md
- Integration guide: https://hottea.ai/hatchways/integration.md
- Competitive packet: https://hottea.ai/hatchways/competitive.md
- Security packet: https://hottea.ai/hatchways/security.md
- Sample reviewer packet: https://hottea.ai/sample-report