StartConceptsPlaybooksFeature docsAPI & MCPChangelog
← All feature docs
Feature docs · /onboarding/dossier

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.

Open GTM Context Dossier → All docs

Overview

Instead of filling a long form, point us at your context at Settings, Your business. 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, what Scout uses to find relevant angles, and (since 1 September 2026) what every scheduled role reads before it does any work.

Until then the dossier fed the content products only. Now the same confirmed record is put in front of each of the nine roles on every run, so a pre-call brief, a renewal play or a partner note is written for your company and your buyer rather than for a generic one. Nothing changes about how you fill it in.

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.

Start from your website

The fastest way in is one field. Paste your website URL on Settings, Your business and press Read my site. We read your public pages, research your ICP and competitors, and hand back a draft in about a minute. You edit it and confirm; nothing is saved before that.

If your context lives somewhere else, open Point at something else instead for the other four sources (public repo, private repo, Google Drive, or a direct paste).

This is also the first item on your setup checklist. It used to ask for your role and territory, which is a question a founder has no answer to: a territory is the slice of a book a manager hands one seller. Telling us about the business replaced it, and moved first, because it is the one step you can finish before connecting anything and the one every role reads before it works.

The eight sections

Company identity, products, founder, voice samples, ICP, go-to-market plan, target accounts, and competitor intel. The last two are yours to write: nothing researches them for you, because your motion and your target list are decisions rather than facts about the world.

The go-to-market plan is how you sell, the motion, the segments, the stage you are at, the number you are working to, your typical cycle and deal size. A role reads it before it proposes anything, so it does not offer you an inbound play when you run outbound, or a scaled program when you have four customers.

Target accounts are the accounts you decided to go after, one per line as name, domain, why. Only the name is required. The reason is what lets a role tell an on-strategy account from an inbound accident, so give one where you have one.

The five sources

How to use it

  1. Open /onboarding/dossier and pick a source.
  2. Paste the text or enter the URL, then Scan & research.
  3. Review every field. Competitor and ICP items are researched, verify them.
  4. 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.

What your roles do with it

Your confirmed dossier is added to each role’s instructions as context: who you are, what you sell, who you sell to, and who you come up against. A role uses it to judge what matters, whose problem to lead with, and which accounts are on-strategy.

It is context, not evidence. Your ICP saying you sell to fintech CFOs does not tell a role that a particular CFO wants a call, and a role will not treat it that way. Where your dossier is silent, the role says so rather than filling the gap, which is the same rule your cited library already runs under. Sections you have left empty are left out entirely rather than sent as “unknown”.

If you have not built a dossier yet, nothing is added and your roles run exactly as they did before.

What your roles noticed

Once a day we read your own ledger: which accounts produced a reply, a meeting or a stage change over the past week. Where something has happened three or more times that your record does not reflect, you get a question at the top of Settings, Your business and in your morning line.

It proposes. It never edits your record. An account we noticed is held apart until you accept it, and until then no role sees it. Accepting adds it, with the observation as its reason. Declining closes the question and keeps what you wrote.

Two kinds of question: accounts worth adding to your target list, and industries worth adding to your ICP. An industry needs three separate accounts behind it, not three wins at one company, because one loud customer is not a segment. If a night turns up nothing, you hear nothing.

Completeness meter & consumed-by

At the top of /onboarding/dossier a completeness meter scores your saved dossier across its eight sections, company identity, products, founder/user, voice samples, ICP, go-to-market plan, target accounts, and competitor intel, and names the next one worth filling (for example, "4 of 8 sections filled, add voice samples to sharpen every product"). Voice samples matter most: they're what each writing product clones your tone from.

Consumed by shows which products have actually read your context. Core appears once your session pulls config (a verify_session or pull_config call), and each product 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 product." A compact version of the same card rides along on your Activity page.

The meter reflects your last saved or confirmed dossier, confirm your edits, then refresh to watch it move.