New user
Getting started
Understand the product surfaces, create your first brief, and know what the first successful workflow looks like.
Open guideDocumentation
Everything around the OwlyVision brief workflow.
Use these docs to understand what OwlyVision is, how the Product Brief and Launch Check surfaces differ, and what belongs on each domain.
Read by job
Start from the problem you are solving.
Operator
Core workflows
See how Product Briefs, Launch Reports, share links, PDF export, and private workspace handoff fit together.
Open guideOwner
Deployment and domains
Review the high-level hosting split, public domain structure, and what belongs on each host.
Open guideLaunch Check buyer
Paid Launch Report
owly.vision collects one public URL, Stripe payment, and email. app.owlyvision.com is only the private handoff point for the report.
Open Launch CheckWhat the product actually does
OwlyVision has two related jobs: brief before build, crit before launch.
Generate a Product Brief
Paste in a domain, capture live signals, and turn the result into a structured brief instead of a raw scrape.
Check a public launch page
Use owly.vision after a page exists to get visual critique, annotated issues, and pasteable fix prompts.
Deliver the brief cleanly
Share it privately, export it as PDF, and keep the handoff tied to the Product Brief or Launch Report.
Current public shape
These docs describe the live split-domain product.
Pre-build Product Brief marketing belongs on owlyvision.com, post-build Launch Check belongs on owly.vision, private workspaces run on app.owlyvision.com, and docs belong on docs.owlyvision.com. Internal runbooks can stay in-repo; this surface should stay public, product-facing, and static.