Onboarding: brief, review and dossier
Start from a few sentences, a website, a document or a repo. Pythe drafts the fields, you correct them, and a dossier becomes the source of truth for every agent.
Updated 2026-10-13
Onboarding has one rule: nothing is generated from a guess you have not seen and cannot edit. It runs in two places. /onboard takes your brief and shows what Pythe understood. /setup holds the company dossier, the research settings and the research itself.
Step 1: your brief
The screen is titled “Tell Pythe what you are working on”. You choose how to start. Only the input for the option you choose is shown.
| Option | What you give | What Pythe does |
|---|---|---|
| Write a brief | Two or three sentences in your own words. | Expands them into fields for the next screen. |
| Use my website | An address such as yourproduct.com. | Reads the site and drafts the brief. You can add a note if the site is out of date. |
| Upload a document | A PRD, notes or research. | Reads the whole document. You can add a note if the document is old. |
Optional extras under the chooser: a public GitHub repo (github.com/you/your-repo) and files. Addresses are checked as you type. Only http and https addresses are read, and an address needs a full domain, so localhost is refused.
Step 2: check the details
Pythe turns your input into fields you can edit. They are grouped like this.
| Group | Fields |
|---|---|
| The essentials | What you are building · Who it is for · The problem you solve · Traction so far · Your next goal |
| Context | Company name · Industry · Main market · Product form · How you will charge · Competitors you already know |
| What Pythe read | The things it picked up from your input, so you can see where each field came from. |
| Pythe could not work these out | Questions it could not answer from what you gave. Answer what you can. |
| Assumptions Pythe is making | Anything it filled in by inference. Correct what is wrong. |
Pythe does not invent defaults for pricing, platform, stage, industry or region. If it could not tell, the field is left for you.
You can also add a logo for the workspace. It appears in the workspace switcher.
Step 3: set up, then the dossier
Pythe creates the workspace and hands you to /setup. There you see one company dossier instead of five pages of questions. It is split into six sections you can open and edit.
| Section | What it holds |
|---|---|
| Company | Name, what the company is (Pythe plans from this sentence more than any other), industry, market. |
| Stage and goals | Where the company is today, what success looks like in 12 months, and the next 90 days. |
| Customer | Who you sell to, the target customer, the problem in their words, and how much it hurts. |
| Product and model | What you offer, what is live and what ships next, the smallest useful version, how it makes money, and anything you have decided not to do. |
| Evidence | What proof you have, where the business is today, your strongest proof point, competitors, and why you could win. |
| Execution | Who is executing, what you are good at, what is constraining you, and how the roadmap should feel. |
Everything autosaves to the workspace. “Save and exit” is just leaving. You can resume on any device exactly where you stopped.
What happens to the dossier
- It is the first thing every agent reads, as a short “Company:”, “Website:”, “Product:”, “Customers:”, “Problem:” and “Founder’s goal:” block.
- Your corrections to the research are kept as “Founder’s corrections” and read by the team.
- You can change it later. The plan only changes when you regenerate or run the weekly review.
Related
Previous: Core concepts · Next: What Pythe can read: site, repo and files