When you log in for the first time, Specsight runs a short wizard. By the end you have an organisation, your first project, and the first analysis already running in the background.
The full path is four steps — Organisation, Codebase, Project, Plan. If you skip connecting GitHub the Project step drops out. Partnership organisations come in through an admin grant and skip the Plan step.
Step 1 — Organisation
Fill the Organisation name field and click Continue to move on to step 2.
Step 2 — Codebase
Click Connect GitHub and authorise the Specsight GitHub App on the account or organisation that owns your code. Pick All repositories or only specific ones. Full breakdown in connect GitHub. To come back later, click I'll connect GitHub later — the wizard skips the Project step and takes you straight to Plan.
Step 3 — Project
Pick the Repository, the Branch Specsight should watch (your default branch is preselected), and edit the Project name if needed. As soon as you pick a repo, Specsight measures it and shows a Your project card with the source-file count and approximate size — so you know upfront whether it fits your plan.
Click Continue to plan to move to the last step.
Step 4 — Plan
Pick a plan. Standard or BYOK — both confirm in Stripe Checkout, then you land on the dashboard. See plans and limits for what each one covers.
After the wizard
You land on your project page with a full-page Analysing codebase screen while Specsight reads the code. Most projects finish in a few minutes; large repos can take up to an hour. You can close the tab — Specsight emails you when the spec is ready.
When the analysis finishes, the page swaps to your project home — the Latest release, Recent activity, Reports, and What changed cards, plus an Ask Specsight anything bar at the top.