Introduction lead
Mgr. Karol Szekely
The Lead Intelligence Architect leads the initial alignment of mandate context and entry readiness.
Contact / access
Private mandate introductions stay named, jurisdiction-aware, and led under one operating line.
Use this route when a board, transaction, legal, or compliance-sensitive matter needs a calm first exchange with a visible owner before work opens.
- Named first contact: Mgr. Karol Székely leads the introduction from the public route onward.
- Legal identity, jurisdiction stance, and next-step routing stay visible before documents move.
- Once access is approved, the next member-only workflow can open without a generic detour.
Contact accountability
A private mandate introduction should show who fronts the route, who owns the communication, and under which legal line it runs.
Trust rises faster when the buyer can verify the operator, named contact owner, and jurisdiction stance before sharing sensitive detail.
Entry baseline
What stays explicit on the contact route
A premium advisory contact surface keeps the accountability chain visible before the first document or message is shared.
- Legal operator
- FIRST CLASS HOLDING s.r.o.
- Contact owner
- Mgr. Karol Székely, Lead Intelligence Architect
- Jurisdiction posture
- EU-first processing baseline with jurisdiction-sensitive alignment before case opening.
- Escalation routes
- Contact, DPA, and the access layer stay public so procurement, privacy, and mandate questions keep a clear owner.
Named introduction
The first route has a visible owner
Mgr. Karol Székely is visible before the first message so sensitive introductions do not disappear into a generic queue.
Jurisdiction cue
Cross-border sensitivity is treated as part of entry discipline
The contact route makes clear that mandate jurisdictions are aligned before the case opens and before broader material exchange begins.
Private review line
The contact route reads like a controlled advisory introduction
The public route stays tied to legal identity, named accountability, and the existing DPA or access paths instead of an open contact queue.
Entry guide
The first contact confirms the decision context before broader communication starts.
A private introduction does not replace intake. It confirms whether the mandate fits the EX AI HUB institutional frame, whether sensitivity and readiness justify this route, and what the first reply will route next.
What gets confirmed
Four entry criteria that let the first reply route the mandate
The contact page shows entry discipline and clear routing, not a pool of unstructured inquiries.
- Decision question
- Which decision, approval, or risk question the mandate needs to answer and who will own the next step.
- Subject framing
- Whether the subject is a person, company, transaction, market, or a combined context with multiple subjects.
- Sensitivity and jurisdiction
- How much privacy, legal, or reputational risk the introduction carries and which jurisdictions are involved.
- Entry readiness
- Whether the first reply should confirm access, request one missing signal, or define the member-only workflow that follows registration.
Private only
No public form funnel
This page avoids a conventional form because sensitive engagements need mandate details and communication boundaries aligned first.
Clear next step
The first reply states route, owner, and response window
The outcome is not a holding acknowledgment. The first reply confirms whether access opens, who owns the next step, and which response window governs the next exchange.
Legal frame
The first contact stays under FIRST CLASS HOLDING s.r.o.
Even the private introduction must show the legal and operating carrier of the mandate from the outset.
Entry paths
The next step depends on whether the mandate still needs alignment or a case file is already prepared.
The contact page does not add a third funnel. It helps the buyer choose between the two existing entry modes.
Path selection
How to distinguish the right entry
The decision depends on mandate readiness, not on a willingness to fill a long form.
Request access
Use this when purpose, materiality, review depth, or procurement framing still need alignment before the case opens.
Member workflow
Use this when a clear decision question, review boundaries, and starter materials already exist.
Client portal
Existing mandates, material supplements, and follow-up communication continue in the portal, not through a new public contact thread.
Diagnostic fit
Use the call when uncertainty still needs to be reduced first
This path fits leadership vetting, sensitive transactions, or mandate framing with multiple stakeholders.
Member workflow fit
Open the member workflow when the mandate is already decided
When the mandate is already defined, the contact path does not add another approvals loop.
No generic inbox
Communication keeps a clear owner
The private introduction exists to make a fast routing decision, not to accumulate loose messages without a next step.
Preparation
A fast introduction only needs a small but precise set of signals.
The buyer does not need to prepare a pitch deck. It is enough to frame the decision, subject, timing, and confidentiality boundary so the first reply can route the right next step without delay.
Before the call
Prepare these points for a smooth next step
This checklist does not replace intake. It shortens the time to the first relevant decision.
- Subject and objective
- Who or what needs review and which decision should follow from the introduction.
- Timing and urgency
- Whether this is driven by a board deadline, transaction window, onboarding milestone, or governance escalation.
- Starting materials
- If documents, subject lists, or an internal memo already exist, the private introduction can route the next step faster.
- Confidentiality boundary
- Clarify what can be shared immediately and what waits until the next alignment step.
Minimal prep
A clear decision context is enough, not a long brief
The contact page removes friction instead of creating it through another form or an open-ended email checklist.
Fast routing
The first reply should state the response window immediately
If the mandate is clear, contact does not slow case opening; if it is not, the reply still confirms the next owner, the alignment step, and the response window before the thread expands.
Governance first
Even a fast introduction must keep discipline
Even at the first touchpoint, the public page makes clear that mandate boundaries, materiality, and review boundaries will be documented.
Entry choice
Request access when the mandate belongs inside the member area.
The public web remains a briefing layer. Request access and, once approved, the detailed workflow, intake paths, and next steps become available inside the member area.
- The public layer stays free of intake workflow and detailed commercial branching.
- The next step is confirmed only after access approval and portal registration.
Access frame
- Invite-only entry
- Detailed workflow inside the member area
- Named contact owner
- First reply confirms route and owner
- First reply includes response window
- EU-first jurisdiction baseline
- FIRST CLASS HOLDING legal carrier