PREYTORIAN v6.4 — Founder Console

Source-aware rebuild from the updated project specs. This dashboard combines actual Claude/API usage, founder desk labor hours, build economics, launch-gate readiness, schema maturity, ops-dashboard maturity, Advisory deliverable readiness, and the longer build-to-own path from Terminal validation to Enterprise Advisory.
Actual Claude/API Cost
$0.00
Parsed locally from Claude logs
AI-Assisted Build Cost
$0.00
Claude/API + founder desk labor
Startup Equivalent
$0.00
Lean startup-style build cost
Enterprise Equivalent
$0.00
Governed full-org build cost
Current Product Stage
Launch-Gated
Auth/billing are live; public launch still gated
Data Maturity
Prototype
Based on accumulation months

Executive Controls

Accumulated Data Months
Labor Hours Source
Labor Hours at Desk
Legacy Minutes / Event
Active Gap Cap Minutes
Your Loaded Hourly Cost
Startup Months
Startup FTE
Enterprise Months
Enterprise FTE
Loaded Hourly Cost / FTE
Enterprise Friction %
Startup Friction %
Labor-hours model: this represents hands-on time sitting at the desk entering commands, reviewing output, steering work, testing, and making decisions. Claude JSON time is diagnostic only.

Scenario Presets

Presets affect modeling assumptions only. Actual API spend always comes from parsed Claude usage when logs are loaded.

Labor Time Model Diagnostics

Load Claude logs to calculate API/token cost and diagnostic time only. Labor Hours at Desk remains the cost driver unless you intentionally select a diagnostic model.

Why Event Counts Overstate Hours

Claude JSON logs may include tool calls, subagent records, repeated usage entries, cache reads, and background continuation records. v6.3 defaults to timestamp-based active session time instead of multiplying every event by several minutes.

Recommended Setting

Default is User-message active time: idle-cap walk over founder-typed messages (subagent traffic filtered via isSidechain). Switch to Manual desk-input estimate if you want to override with a hand-tuned hours value.

Public Launch Readiness

Strategic Launch Decision

AI vs Startup vs Enterprise Build Comparison

DimensionAI-AssistedStartupEnterprise

Build Cost Composition

Time Compression

Cost by Developer Domain

Traditional build cost concentration compared with AI-assisted equivalent.

Estimated Domain Hours

WorkstreamStartup HoursEnterprise Hours

Operating Economics Controls

Terminal Subscribers
Advisory Customers
Terminal Price / Month
Advisory Price / Month
Infra Fixed Cost
Shared Pipeline Runs / Day
Shared Run Cost
Deep Dive Cost
Terminal Dives / Mo
Advisory Dives / Mo
Advisory Report Cost
Explorer Infra Allocation

Platform Operating Snapshot

Monthly Revenue
$0.00
Monthly Operating Cost
$0.00
Contribution Margin
0%

Pipeline Amortization

Product Costs

Break-Even

Data Maturity Roadmap

Schema-Gated Product / Economics Maturity

Advisory Report-Readiness Gates

Database Schema → Business Value Map

Schema LayerRequired Tables / ControlsEconomic MeaningMaturity Gate

Advisory Deliverable Quality Gates

Tier / Product Economics

Product Readiness: Explorer → Terminal → Advisory

Schema-Aligned Feature Scope

Project Breadth Snapshot

Roadmap / Launch Sequencing

Open Risk / GAP Pressure

Actual Cost by Model

Actual Token Mix

Actual Cost by Day

Executive Narrative

Data Intake & Processing

Process project Markdown source documents and Claude JSON/JSONL logs here. This keeps operational intake near the bottom of the dashboard, separated from the executive summary, economics, maturity, schema, and product-readiness views.

Process Project Source Documents

Load the current PREYTORIAN Markdown files before trusting the dashboard. The scanner identifies which required project documents were provided, what is missing, what is stale, and which dashboard areas each file supports.
Recommended repo scan root: the directory containing PRODUCT.md, ROADMAP.md, TASKS.md, GAPS.md, DECISIONS.md, SCHEMA.md, SAFETY.md, OPS_DASHBOARD.md, HOSTING.md, IMPLEMENTATION.md, and docs/ADVISORY_BRIEF_SPEC.md.

Process Claude JSON / JSONL Logs

Use Choose Folder for recursive scans of copied Claude Code project logs, or choose individual JSON/JSONL/log files. Processing stays local in the browser.
WSL recommended: rsync -av --delete ~/.claude/projects/ /mnt/c/claude-logs/projects/, then choose C:\claude-logs\projects.
ZIP recommended: cd ~ && zip -r claude-logs.zip .claude/projects/, then upload the zip here.

Dashboard Source Freshness

Freshness
Not Scanned
Required Found
0 / 0
Missing Required
0
Newest Source
No Markdown sources scanned yet.

Anthropic Rates / MTok

Opus input/output
Sonnet input/output
Haiku input/output
Cache read uses 10% of input price. Cache write uses input price by default.

Required Markdown Manifest

MD File Required Status Detected Sections / Signals Dashboard Sections Fed

Source Coverage by Dashboard Area

Missing / Stale Source Actions

Parsed Claude Usage Events