For introducers
Introducer Program — Success Fee
We are looking for qualified introducers (success fee) for high‑confidentiality, high‑value B2B engagements—e.g., private bankers, family offices, SIers/consultants, procurement advisors, and audit/legal boutiques. We deliver audit‑ready computation results as an Evidence Pack (canonical JSON). This page is not for the general public.
This page
This is a limited guide for introducers. It is not a general public page, but a pre-brief for safely introducing high-confidentiality, high-value B2B cases.
Who this is for
It is for practitioners who introduce cases in a trusted way, such as private bankers, family offices, SIers, consultants, and audit or legal boutiques.
Next
Move to contact without sending confidential information, and check the public transaction scope if you need the public conditions first. Individual terms are fixed in writing.
Do not send confidential information before NDA (design docs, raw data, keys, restricted URLs, etc.). Public‑level summary is sufficient.
What we deliver (avoid misread)
- Deliverable is the Evidence Pack (canonical JSON).
- Recipients (or third parties) can verify the delivery through SCU's verification procedure.
- We do not disclose underlying formulas, implementations, or operational procedures.
- This is not an investment product or fundraising. It is a deliverable that enables acceptance, audit, and submission.
Ideal clients to introduce (profile)
We target organizations that match one or more of the following (examples).
- Audit/regulatory/third‑party submission is required and accountability is high
- Cannot disclose internal methods due to confidentiality, but needs an acceptably verifiable deliverable
- Procurement/legal/audit stakeholders require more than PDFs or verbal explanations
- Able to contract and pay as a legal entity / research institution / public organization (B2B)
(We do not restrict domains. It can fit space/GNSS/time sync/infrastructure audits/joint research acceptance, but is not limited to them.)
Success fee (template)
Success fee is defined by a written Introducer Agreement. Below is a template definition (numbers are examples; not final).
Success definition (example)
- We execute an individual contract (SOW/agreement) with the referred party, and
- Remaining balance payment is confirmed (total consideration received is finalized)
Payment terms (example)
- Success fee = fixed amount (example: JPY 0.5–2.0 million; fixed within this range per case)
- Payment: paid in a single tranche after remaining balance is confirmed. Not paid from the deposit.
- Repeat (example): on the second successful case by the same introducer, with a different referred party (different legal entity), we pay the same amount as the initial success fee once more (no payments from the third case onward).
- Payee: as a rule, a legal entity (introducer’s firm or controllable entity)
Eligibility (only if)
A success fee is owed only if all of the following conditions are met. Anything else is not eligible.
- You must contact us first (/contact?from=introducer), obtain a receipt ID, and receive our written confirmation that we accept the introduction and treat you as the introducer (no retroactive claims).
- The referred party must not already exist in our inquiry/deal history.
- One success fee per referred party (same legal entity/group); it does not increase by splitting contracts, add‑ons, or renewals.
- Repeat (second success): only for a different referred party (different legal entity); we pay the same amount as the initial success fee once more (no payments from the third case onward).
- Introducer assignment is determined by our written confirmation (if multiple claims exist, we pay to zero or one introducer).
- No bypassing caps by name splitting (affiliates/agents, etc.). If we reasonably determine it is effectively the same introducer, we treat it as the same.
- Consideration must not be reversed (refund/uncollectible, etc.); if reversed, no fee is owed or paid fees are offset/returned as defined in the individual agreement.
Exclusions (example)
- Introductions that violate the counterparty’s policies, laws, or licensing requirements
- Spam‑like mass outreach, list brokering, or indiscriminate introductions
- Cases rejected by our safeguards (sanctions, illegal use, etc.)
Process (introduction flow)
- Introducer contacts us first (/contact).
- We provide an introducer agreement outline (success fee terms).
- If possible, a three‑party intro call (introducer attends).
- Eligibility check → SOW/terms → contract → payment → execution → delivery → acceptance.
What to send (Pre‑NDA)
Do not send confidential information before NDA. The minimum info below is sufficient.
- Introducer: affiliation, role, regulatory position (as appropriate)
- Referred party: organization type, region, decision range (rough)
- Use: public‑level summary (whether third‑party submission is required, timeline)
- Expected contract type: one‑off / annual slot, etc. (unknown is OK)
Compliance notes (required)
- This page is not investment solicitation.
- Introducers must comply with their firm/client agreements, laws, licensing requirements, and conflict disclosures.
- We may decline cases based on safeguards (sanctions, illegal use, etc.).
- Final terms (including success fee) require written agreement.
Contact as an introducer (do not send confidential info)