ANNAlife — Investor Walkthrough
Section 1 — Opening
This is not a traditional hiring model.

What we are presenting here is a structured execution system where headcount is directly tied to revenue generation and economic impact.

Every role in this system exists to move individuals from instability into participation — whether that is employment, business ownership, or content-based income.

Pause

In most organizations, headcount is treated as a cost.

In our model, headcount is the engine.

Each employee operates within a defined execution cluster and functions as a multiplier node — unlocking revenue capacity far beyond their individual salary cost.

Pause

The more we hire, the more revenue we generate — and the more people we help move into economic participation.

Platform Philosophy
Core Model Principle
Headcount =
Revenue Engine
Every hire unlocks a new tier of creators, consumers, and enterprise placements. Headcount is not overhead — it is the mechanism by which economic capacity scales.
13
Total Roles
2
Hiring Waves
4
Exec Clusters
$300K+
Revenue / Role
Section 2 — Multiplier Model
One employee. Thousands of outcomes.

Each employee operates within an execution cluster and functions as a multiplier node.

One employee supports approximately 100 creators.

Those creators engage thousands of consumers.

Those consumers convert into measurable economic outcomes — including placements, revenue, and education pathways.

Pause

At the end of that chain, every hire has the potential to unlock $300,000 or more in annual revenue capacity.

This threshold — the Multiplier Node minimum — is the gate before any additional hire is approved. Revenue yield per role is the metric that governs our headcount decisions.

Pause

The key point is simple: the more we hire, the more revenue we generate — and the more people we help.

Multiplier Node — Revenue Per Employee
1
Employee
Execution cluster. Activated on hire date.
100
Creators
Onboarded, activated, and monetising content.
5,000
Consumers
Subscribers driven by creator supply & ARPU.
~50
Placements
Verified profiles → enterprise recruitment bounties.
$300K+
Revenue Yield
Minimum threshold before next hire is approved.
“The more we hire, the more revenue capacity we unlock — and the more individuals we move into economic participation.
Section 3 — Execution Clusters
Four coordinated functions. One system.

Our system is structured into four execution clusters. These clusters are not isolated — they operate as a coordinated system where each one feeds into the next.

Cluster A focuses on infrastructure, AI systems, and safety. Without Cluster A, no other cluster can operate.

Cluster B focuses on data, compliance, and validation. This is what makes our funding eligibility defensible.

Pause

Cluster C focuses on recruitment and onboarding. It is the primary input to our revenue model — its performance determines cohort growth rates month over month.

Cluster D focuses on creators, content, and monetization. Cluster D is what drives the Income Statement — its output determines EBITDA margin expansion.

Pause

Each one feeds into the next, ensuring that growth is controlled, scalable, and compliant.

Execution Clusters A · B · C · D
A
Cluster A · Foundation
Core AI & Infrastructure
  • ANNA LLM architecture & TRL validation
  • AWS ca-central-1 cloud infrastructure
  • AI safety, bias auditing & platform integrity
  • Required for SR&ED T661 eligibility
B
Cluster B · Intelligence
Data & Compliance
  • Data quality, pipeline integrity, audit readiness
  • IRAP reporting & T2 preparation support
  • Enterprise compliance for B2B contracts
  • Verifiable reporting for capital partners
C
Cluster C · Scale
Recruitment & Onboarding
  • Creator & consumer cohort acquisition
  • Enterprise client pipeline management
  • CAC reduction through creator referral loops
  • ~100 creators activated per specialist per cycle
D
Cluster D · Monetization
Content & Revenue
  • Activates all 8 revenue streams
  • Manages ads, marketplace & content licensing
  • Platform share transition: 10% → 80%+
  • Primary driver of EBITDA margin expansion
Section 4 — System Flow
Drivers to financials. Every tab connected.

Work flows through the system in a single direction: Drivers → Execution Clusters → Revenue Generation → Financial Outputs.

The Drivers tab is the master assumption layer. Every number in this model — CAC, ARPU, churn, hiring dates, funding timing — is set here.

Those assumptions flow into the execution clusters, which generate creator, consumer, and enterprise activity.

Pause

That activity produces eight revenue streams, tracked monthly in the Revenue tab using cohort bridges: Beginning + New − Churn = Ending.

The financial outputs — Income Statement, Cash Flow, and Balance Sheet — are downstream results. SR&ED payroll recovery is netted against gross payroll at this layer.

Pause

Nothing in the financial statements is hardcoded. Everything flows from upstream assumptions.

Execution Flow — Drivers to Financial Outputs
Tab: Drivers
Assumptions & Parameters
CAC, ARPU, churn rates, growth targets, funding timing, CapEx thresholds. Three scenarios: Worst / Base / Best. Master control layer.
Cluster A
AI & Infrastructure
Platform integrity, safety, AWS cloud. SR&ED-eligible foundation.
Cluster B
Data & Compliance
Audit readiness, IRAP reporting, enterprise compliance gates.
Cluster C
Recruitment Engine
Creator/consumer acquisition. CAC declining. Cohort growth driver.
Cluster D
Monetization Layer
8 revenue streams activated. Platform share 10% → 80%+.
Tab: Revenue
8 Revenue Streams
Cohort bridges track consumer, creator, enterprise monthly. Subscriptions · Creator Rev · Enterprise Fees · Ads · Compliance · Education · Marketplace · SR&ED.
📊
Income Statement
EBITDA 33% → 74%
💵
Cash Flow
Indirect method
⚖️
Balance Sheet
Assets = L + Equity
📈
Dashboard
KPIs + Valuation
Section 5 — Safety & Funding Alignment
Compliance built in. Not bolted on.

One of the most important parts of this model is that safety and compliance are built into execution.

We are not retrofitting compliance after the fact. We are building with it from day one.

That allows us to scale responsibly while accessing non-dilutive funding.

Pause

Safety and compliance unlock three commercial outcomes simultaneously:

First — they make us eligible for SR&ED, IRAP, and Alberta Innovates funding programs. That is $264,000 to $505,000 in non-dilutive recovery across FY2026–FY2028.

Second — enterprise clients require verified data protection compliance before recruitment contracts can close.

Third — platform trust reduces churn, which directly improves LTV:CAC and margins over time.

Pause

This system is designed to meet regulatory and funding requirements while simultaneously building a scalable commercial engine.

Safety & Compliance as Commercial Infrastructure
Funding Eligibility
  • SR&ED T661: 75–80% payroll recovery on eligible roles
  • IRAP: Wave 1 roles at 75–80% cost coverage
  • Alberta Innovates: Wave 2 roles 65–70% coverage
  • All require Cluster B audit trails to qualify
  • FY2026: $164K recovery · FY2027: $210K · FY2028: $280K
Enterprise Adoption
  • Enterprise clients require data protection compliance
  • Recruitment bounties require verified identity infrastructure
  • Compliance-as-a-Service is Revenue Stream 5
  • $5,000/mo enterprise licensing fee per client
  • Without Cluster B, enterprise contracts cannot close
Platform Trust
  • Users choose ANNAlife because it is verifiably safer
  • Creator retention improves with fair, verified payouts
  • ANNA AI safety architecture differentiates vs. incumbents
  • Platform trust reduces churn → improves LTV:CAC
  • Trust is the primary long-term defensibility moat
“This system is designed to meet regulatory and funding requirements while simultaneously building a scalable commercial engine. Safety and compliance are not overhead — they are the mechanism by which non-dilutive capital is accessed and enterprise revenue is unlocked.”
Section 6 — Revenue Transition
From funded to self-sustaining.

This system is designed to transition from funding to revenue.

Early stages are supported by funding to build infrastructure and onboarding capacity. As the system matures, revenue begins to take over.

First through external monetization — YouTube and Twitch revenue share at 90% external.

Then through hybrid models — platform and enterprise revenue split 50/50 with external channels.

And eventually through a fully owned platform where ANNAlife captures 80%+ of all revenue generated.

Pause

By FY2028, platform revenue reaches $6.2M with an EBITDA margin of 74%.

The goal is independence — not reliance. Funding builds the system. Revenue proves it. Scale defends it.

Pause

This is not just a hiring model. It is a system designed to convert instability into income — and that is what makes it defensible.

Revenue Phase Transition — External to Owned Platform
Phase 1 · Build
Phase 2 · External
Phase 3 · Hybrid
Phase 4 · Owned ↗
Phase 1
Build & Setup
M1–3 · Pre-Revenue
  • R&D and AI safety
  • Clusters A & B established
  • Creator onboarding begins
  • Seed Round 1 funds ops
Revenue: $0
Phase 2
External Monetization
M4–6 · First Revenue
  • YouTube/Twitch (90%)
  • Early subscriptions live
  • Creator cohorts ramp
  • SR&ED refund received
Platform Share: 10%
Phase 3
Hybrid Model
M7–9 · Acceleration
  • ANNAlife + external 50/50
  • Enterprise activates
  • Compliance SaaS launches
  • Series A funds US scale
Platform Share: 50%
Phase 4
Owned Platform
M10+ · Self-Sustaining
  • ANNAlife dominates revenue
  • Funding replaced by rev
  • EBITDA margin 74%+
  • Late Private → IPO path
Platform Share: 80%+
FY2026 Revenue
$792K
incl. grants
FY2027 Revenue
$2.5M
incl. grants
FY2028 Revenue
$6.7M
incl. grants
FY2028 EBITDA
$4.9M
74% margin
IPO Target
$1B+
FY2030–31