An AI assistant answers regulatory questions far more usefully when it knows seven things about your company: what you do, what you plan to do, which licences you hold, where you operate, your size and type, your critical products and your risk posture. This guide gives a template, shows the same question answered with and without it, and says what to leave out.
The same question gets different answers with and without context
In our ten-question test, one of the questions asked what a rule meant for the company. A general assistant cannot answer that well without knowing the company, and a good one says so. The practical step is to tell it, in a structured way, every time.
The gain is not accuracy of the underlying text, which the assistant either knows or does not. It is relevance: whether the answer is about your activities, your timeline and your constraints, or a generic list of what might apply to anyone.
The company profile in seven blocks
| Block | What to write | Example of the kind of detail |
|---|---|---|
| Activities today | What the company does now, in plain terms. | Operates a payments business for business customers, including cross-border payments settled with a stablecoin bought from a third party. |
| Activities planned | What is coming in the next 12 to 24 months. | Plans to hold stablecoin balances for customers and to serve business customers in two new countries. |
| Licences and registrations | What the company holds, and what it does not. | Authorised as a payment institution in one country; no licence in the new markets. |
| Jurisdictions | Where it operates and where it intends to. | One country today; two more planned. |
| Type and size | Kind of entity, size, legal entities by country. | Mid-sized fintech, about 150 people, no entity yet in the new countries. |
| Critical products and flows | The few products or flows that matter most. | Business-to-business cross-border payments. It issues no token. |
| Risk posture | How the company decides under uncertainty. | Conservative: prefers to wait for clarity before entering a new market. |
A copyable template
Paste the lines below at the start of a conversation, filling each bracket with your own facts. Keep each line to one or two sentences.
- Activities today: [what we do now].
- Activities planned: [what we plan within 12 to 24 months].
- Licences and registrations: [what we hold], and [what we do not hold].
- Jurisdictions: [where we operate], and [where we plan to].
- Type and size: [entity type, approximate size, entities by country].
- Critical products and flows: [the few that matter most], and [what we do not do].
- Risk posture: [how we decide when a rule is unclear].
Then ask your question, and ask the assistant to say which of its points rest on facts you gave and which on assumptions.
Before and after: the same question, with and without the profile
We asked a general-purpose assistant with no connected sources the same question twice: whether the EU markets in crypto-assets regulation applies to the company and what to do first. The second time we gave it the profile above, which is fictional.
| Without the profile | With the profile | |
|---|---|---|
| Shape of the answer | A general perimeter: who is likely in scope, who is likely outside, and a five-step checklist. | A statement on each of the company's own activities: today's operation separately from the planned custody and transfer services. |
| What it concluded | It could not say whether the rules applied and listed conditions to check. | That today's activity is generally outside scope unless it targets EU clients, and that the planned services would need authorisation from an EU authority. |
| Use of the plan and posture | None. | It noted that the authorisation timeline would likely run past the 12-month plan, and, given the conservative posture, advised launching only after authorisation. |
| Caveats | Asked to check current texts and technical standards. | The same, and it flagged points it was unsure about. |
How to read this
We did not grade the legal correctness of either answer, and neither should you rely on it. The difference is relevance: the second answer was about this company, its timeline and its stated posture. That is the benefit of context. Checking the answer against the primary texts is still your job.
What not to put in
- Personal data about employees or customers.
- Names of customers or counterparties, and anything under confidentiality.
- Sensitive figures, such as revenue, volumes or pricing, unless your security team has approved that use.
- Anything your policies say may not be shared with an external service.
The profile describes what the company does and where, not the data it holds. If you are unsure what your organisation allows, ask your information security team before pasting anything.
Keeping it current
- Name one owner, usually the head of regulatory affairs, and a backup.
- Review it every quarter, and sooner after a trigger: a new licence, a new product, a new jurisdiction or a change in risk posture.
- Keep a dated copy, so you can tell later which version a past answer was based on.
From a pasted profile to governed context
Pasting a profile at the start of each conversation works, but it has limits: it depends on every person remembering to do it, it lives in one chat, and the assistant still answers from memory rather than from a maintained source. The next step is to keep the profile in one place and let the assistant draw on a maintained regulatory base with cited sources.
That is how RegDoor works: the company profile informs the relevance score and the reason written for each item, and the same data is available inside the assistant your team already uses, through an MCP server and a Claude plugin. The Intelligence Layer page describes how jurisdiction-specific agents are built.
Frequently asked questions
How long should the company profile be?
One or two sentences per block, about half a page in total. A longer profile adds noise, and the assistant has less room to use what matters.
Is it safe to share company details with an AI assistant?
It depends on the assistant and your policies. Describe activities and jurisdictions rather than data, avoid personal data and confidential names, and ask your security team what is approved and how inputs are used.
How often should I update the profile?
Every quarter, and whenever a licence, product, jurisdiction or risk posture changes. Keep dated copies.
Does the profile replace checking the source?
No. It makes the answer more relevant to your company. You still need to verify the instrument, the article, the date and whether the rule is in force in the primary text.