Getting started
Run the first useful OwlyVision loop in one sitting.
The product family has two clear moments: Product Brief before build, Launch Check before launch. This guide keeps those surfaces separate so the first run does not turn into a generic AI workspace.
1. Know the three surfaces
- Product Brief: public positioning, pricing, sample, and checkout on owlyvision.com.
- Launch Check: free launch review and paid Launch Report intake on owly.vision.
- Private workspace: Product Brief output, paid Launch Report handoff, sharing, and exports on app.owlyvision.com.
The app is the only place where state changes happen. Marketing explains the product. Docs explain how to use and operate it.
Today, new workspaces are opened deliberately and then accessed with a workspace access code. Existing workspaces can manage billing from inside the app once they are signed in.
2. Create the first brief
- Open the app.Go to the dashboard and start a new brief from any live company URL.
- Use a real target.Pick a site where positioning and messaging actually matter. Thin placeholder sites are valid but produce thinner reads.
- Wait for the brief to resolve.The product should return a structured brief, not a generic audit dump.
Expectation
A successful first brief gives you a readable positioning summary, audience cues, competitive angle, and visible evidence of what the site is actually saying.
3. Use the brief as a decision record
The brief matters when it captures a real product decision: who the page is for, what to say, what proof is missing, where risk sits, and what to build next.
- Review the executive read before acting on individual bullets.
- Use refresh when the source page has materially changed.
- Use Launch Check only after the page exists publicly.
5. What “set up correctly” looks like
- You can create a brief without runtime errors.
- The brief opens inside the private workspace.
- A share link can be created and revoked.
- PDF export returns a usable document.
- The public host split is still clear: marketing on apex, app on app., docs on docs.