Pre-application meeting: costs drivers
Pre-application meeting: costs drivers. A pre-application meeting is the first working session with the competent authority before a formal authorisation file is lodged. Its length, and the effort it takes to prepare for it, depend on how complete your documentation already is, how many registers and jurisdictions the business touches, and whether the model has been finalised before the meeting is booked.
Why this meeting happens
Authorities responsible for authorisation of digital asset businesses hold a pre-application meeting so that obvious gaps surface before the clock on a formal application starts running. It is not a hearing and it produces no binding decision. It is a working conversation, and its cost to you is mostly the cost of preparation, not the meeting itself.
Under the applicable regulatory framework, the authority uses the meeting to flag missing elements in a proposed file: an unclear ownership chain, an incomplete description of the business model, or a custody arrangement that has not been thought through. None of this is decided at the meeting. It is only named.
What drives the cost
The table below lists the factors that most often decide whether a pre-application meeting takes one session or several, and whether preparation takes days or weeks.
| Driver | Effect on preparation and meeting length |
|---|---|
| Number of registers the business must appear in | Each additional register adds a document set and a separate point of contact |
| Number of jurisdictions involved | Cross-border structures usually require more than one meeting round |
| Whether the business model is finalised | An unfinished model turns the meeting into a scoping session rather than a review |
| Existing disputes or third-party claims | Any open dispute is disclosed before the meeting and slows the file down |
| Readiness of ownership and control documentation | Gaps here are the single most common reason for a second meeting |
Practical effect on timing and risk
A well-prepared file turns the pre-application meeting into a single confirmation session. A poorly prepared one turns it into the first of several. Every additional round pushes back the date on which the formal application can be lodged, and that date is the point from which statutory review periods start to run.
The risk is not that the authority will refuse anything at this stage. It cannot: there is nothing yet to refuse. The risk is time. A business that treats the pre-application meeting as a formality typically loses several weeks to a second or third round.
What to do before the meeting
- Assemble the ownership chain first. The owner or a designated director confirms who ultimately controls the applicant entity, with no gaps in the chain.
- Fix the business model in writing. The founder or product lead describes what the business does, in the terms the authority will expect to see in the formal file.
- Check underlying rights before the meeting, not after. Where the technology or the platform was built by contractors, confirm who owns it — the question of what a register shows when B2B software and SaaS — when freelancers signed nothing comes up more often than founders expect.
- Prepare the data-handling section. The person responsible for compliance sets out how client data is collected and stored, and how personal data in data and security is evidenced when the authority asks for proof rather than a description.
- Disclose anything unresolved. Any pending claim, dispute, or unfinished contract is named before the meeting, not discovered during it.
- Confirm who attends on your side. The authority expects to speak to someone with authority to answer, not to relay questions afterwards.
Who decides and how long it takes
The competent authority sets the date once it receives a request for a pre-application meeting, and confirms attendance in writing. No formal decision is issued at this stage — the meeting produces a list of points to address, not an approval or a refusal.
In practice, a single-jurisdiction file with a finalised model is reviewed in one meeting. A file spanning more than one register, or one with an unfinished model, is usually reviewed over two or three sessions before the authority confirms the file is ready to be lodged formally.
If your situation differs
If your file is straightforward — one jurisdiction, one register, a finished model — a single meeting is realistic, and preparation should take days rather than weeks.
If a third party disputes your right to the underlying technology or the token itself, resolve or at least document that dispute before booking the meeting. A file where when the creator disputes the mint is still an open question is not ready to be presented, and the authority will say so.
If your business already holds a mark or a name that is contested elsewhere, that dispute belongs in a different track. The steps involved in interim relief in brand disputes step by step run separately from an authorisation file and rarely need to be resolved before the meeting, but they should be disclosed if they touch the same entity.
What this page does not cover
This page does not cover the formal application itself, the documents that make it up, or the review period once it is lodged. It does not state a fee, a statutory deadline, or a specific legal basis for the meeting: those depend on the jurisdiction and the register involved, and belong in the file-specific brief rather than in a general procedural overview.
Verified
Reviewed against current published guidance from the competent national authorities on pre-application practice, checked as of the current review cycle for this page. Where a jurisdiction has not published a formal pre-application procedure, the description above reflects standing practice reported by applicants and confirmed informally by authority staff. No statutory reference is cited on this page; procedural detail of this kind is jurisdiction-specific and is confirmed file by file, not generalised here. For a structured view of costs and requirements once the meeting is done, an initial review against your file can be arranged directly — the first response from a partner arrives within minutes during working hours, and a price for the work follows within one working day.
Related reading
The next stage after the meeting is covered in file assembly and submission step by step, which sets out what changes once the pre-application points have been addressed.
FAQ
How long does pre-application meeting take in practice?
A single meeting, for a straightforward single-jurisdiction file, typically runs to one working session. Files spanning more than one register or jurisdiction usually need two or three rounds before the authority confirms the file is ready.
Which documents are needed to start?
At minimum: a description of the business model, the ownership and control chain, and a summary of how client data is handled. Gaps in any of these are the most common reason a second meeting is needed.
What happens if the other side does not respond?
A pre-application meeting has no opposing party in the usual sense — it is a session between the applicant and the authority. Where a third-party dispute is relevant, its lack of a response does not stop the meeting, but it must still be disclosed as an open matter.
Where a token issuance structure involves a related platform, the questions raised at pre-application stage often surface again later — see the issuer and the platform are related token issuance for the first steps to take when that relationship needs to be untangled.