GTM Context Dossier
Onboard by pointing at where your company context already lives — a public repo, a private repo, a Google Drive folder, an upload, or your live website. We scan it and research your ICP and competitors into a reviewable dossier that teaches the content engine your voice.
Overview
Instead of filling a long form, point us at your context at /onboarding/dossier. The ingest agent reads what you give it and researches outward, then shows you a GTM Context Dossier: company identity, products, founder, voice samples, ICP, and competitor intel. You edit it, then confirm. The confirmed dossier is what the Writer clones your voice from and what Scout uses to find relevant angles.
It's the "feed the archive" step from the playbook this engine is modelled on — the Writer sounds like you because it's fed your real material.
The five sources
- Public repo (URL) — reads the repo's README. No auth.
- Private repo (GitHub) — same, for private repos: paste a fine-grained GitHub token (repo read) and we read its README.
- Google Drive folder — point at a Drive folder (paste its link or id) and we read the Google Docs and text/markdown files in it. Connect Drive in Cowork (read-only), or paste a Drive access token; no connection? paste the text instead.
- Local upload / paste — upload a folder of text/markdown docs (we extract and stage each file's text) or paste your context directly. Works for anyone, no auth.
- Live website crawl — reads your public site. No auth.
How to use it
- Open /onboarding/dossier and pick a source.
- Paste the text or enter the URL, then Scan & research.
- Review every field. Competitor and ICP items are researched — verify them.
- Confirm & save to Company OS. The content engine can now write in your voice.
Nothing is saved until you confirm — the dossier is always a draft for review first.
Completeness meter & consumed-by
At the top of /onboarding/dossier a completeness meter scores your saved dossier across its six sections — company identity, products, founder/user, voice samples, ICP, and competitor intel — and names the next one worth filling (for example, "4 of 6 sections filled — add voice samples to sharpen every plugin"). Voice samples matter most: they're what each writing plugin clones your tone from.
Consumed by shows which plugins have actually read your context. Core appears once your Cowork session pulls config (a verify_session or pull_config call), and each plugin appears with when it last synced brain state against your dossier — so you can see it flowing, not just saved. Until something reads it, it honestly says "not yet consumed by any plugin." A compact version of the same card rides along on your Cowork rollup.
The meter reflects your last saved or confirmed dossier — confirm your edits, then refresh to watch it move.