# Founder Onboarding SOP

This section documents all internal workflows, operating procedures, compliance steps, and operational standards for the successful functioning of TheAngel.

It ensures that every member of the team follows a unified, repeatable, and scalable process.

### Purpose of This Handbook

The Internal Operations Handbook exists to:

* Standardise operations
* Reduce human error
* Ensure regulatory compliance
* Protect investor and founder trust
* Create scalable workflows as the platform grows
* Clarify responsibilities within the team
* Provide a clear escalation pathway for complex issues

### TheAngel Operational Principles

All internal operations follow six core principles:

1\. Compliance-first  

2\. Documentation always  

3\. Transparency with internal teams  

4\. Data accuracy  

5\. Security at every step  

6\. Founders and investors must feel supported

### Team Roles & Responsibilities

Below is the default operational structure.

#### 1. Founder Success Team

Responsible for:

* Onboarding founders
* Reviewing pitch decks, materials, and listing content
* Coordinating tokenisation handover
* Supporting founders during fundraising

#### 2. Investor Operations Team

Responsible for:

* Investor KYC/AML review
* Investor category classification
* Wallet activation
* Transaction monitoring
* Communication during liquidity windows

#### 3. Tokenisation & Legal Structuring Team

Responsible for:

* SPV creation
* Luxembourg compartment setup (Filedgr)
* Equity transfer documentation
* Token issuance
* ISIN assignment coordination
* Prospectus drafting

#### 4. Compliance Team

Responsible for:

* AML/KYC escalation
* Regulatory reporting
* Suspicious activity reports (SAR)
* Accredited investor verification (US)
* Jurisdictional compliance reviews

#### 5. Engineering & Security Team

Responsible for:

* Smart contract operations
* Platform integrity
* Security audits
* Infrastructure stability
* Wallet integrations

#### 6. Liquidity & Marketplace Team

Responsible for:

* Opening/closing liquidity windows
* Updating valuation models
* Monitoring market activity
* Ensuring orderly trading

***

### Founder Onboarding SOP

This is one of the most critical workflows.

#### Step 1 — Founder Application Received

Checklist:

* Founder identity info
* Company registration
* Pitch deck
* Basic financials
* Company overview

Team: Founder Success

#### Step 2 — Compliance Review

Compliance team performs:

* KYC on founder(s)
* Fraud & sanctions screening
* Company legitimacy checks
* Jurisdiction suitability

Flags:

* PEP status
* Adverse media
* Jurisdiction risk (Tier 3 countries)

Team: Compliance

#### Step 3 — Business Quality Review

Founder Success evaluates:

* Clarity of problem/solution
* Product readiness
* Traction level
* Team experience
* Market opportunity
* Listing readiness checklist

Minimum standards must be met before approval.

#### Step 4 — Approval or Rejection

Internal rule:

* Approve if quality score ≥ 70
* Re-evaluate if 50–69
* Reject if < 50

Decision logged internally for audit trail.

#### Step 5 — Founder Listing Setup

Founder Success helps founders:

* Structure listing content
* Upload pitch deck
* Add product screenshots
* Record intro video
* Define tokenomics

Internal Review Points:

* No unrealistic claims
* No unverified revenue statements
* No misleading financial projections

#### Step 6 — Handover to Tokenisation Team

Triggers:

* Founder content approved
* Raise amount and valuation confirmed

Tokenisation team initiates SPV/Compartment setup.


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.theangel.app/operations-handbook-internal/founder-onboarding-sop.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.