HolyCode Business Plan

How money is generated and distributed in the system

This page defines HolyCode commercial mechanics: where revenue comes from beyond investments, who pays, how payments are settled, how fiat is converted into the crypto layer, how physical data-center infrastructure operates, and how creators are paid.

Version

v0.1 (Revenue Model Draft)

Publication Date

March 5, 2026

Status

Hybrid Software + Infrastructure Revenue Framework

Opens browser print dialog. Save as PDF.

Core Thesis

  • • Investments fund launch and scale, but long-term sustainability depends on operating revenue.
  • • Primary revenue driver: HolyAgent role economy and automation-as-a-service usage.
  • • Second revenue driver: HolyCode physical infrastructure (data centers) where agents run on leased in-house capacity.
  • • HolyChat and HolyBuild expand usage volume and therefore monetization throughput.

Where value comes from

Users do not pay for a raw model; they pay for trained role context and measurable execution outcomes. HolyAgent stores role memory, connects any LLM provider, and produces repeatable output monetized via marketplace, runtime usage, and managed hosting on HolyCode infrastructure.

Revenue Sources

Beyond DAO investment inflows

Stream Revenue Source Who Pays Settlement Basis
Role Marketplace Sales Paid access to published roles Users/teams Fixed-price or token-based access
Automation Usage HolyAgent runtime execution fees B2B and individual users Per run, per hour, or usage tier
Result-Based Contracts Payment for achieved KPI/result Outcome-contract clients By accepted outcome
Revenue Share Roles Percentage of client sales Client via revenue split Per reporting sales cycle
HolyBuild Delivery Task execution and delivery fees Development/automation customers Milestone, retainer, or per-task
HolyDC Agent Hosting Leasing agents and compute capacity in HolyCode data centers B2B/B2G clients and DAO members Subscription, reserved capacity, or metered compute usage

HolyCode Physical Infrastructure (HolyDC)

Data centers as a dedicated business layer

  • • HolyCode builds its own data-center capacity in phased deployments to host AI agents.
  • • Clients can run agents not only locally but also in HolyCode managed infrastructure as a rental service.
  • • The infrastructure layer provides SLA guarantees, resilience, dedicated compute options, and predictable execution cost.
  • • Infrastructure revenue strengthens treasury stability and reduces dependency on third-party clouds.

Infrastructure Product Line

How clients lease agents and compute in HolyDC

Product Capacity Footprint Best For Pricing Model
Shared Agent Cloud Shared HolyDC pool with usage limits Startups, small teams, pilots Subscription + pay-as-you-go overage
Dedicated Agent Pod Dedicated pod/GPU pool per client B2B teams with sustained load Monthly reserved-capacity contract
Private Agent Cluster Isolated HolyDC cluster with custom SLA Enterprise/B2G and compliance-sensitive workloads Annual contract + setup fee

HolyAgent Role Pricing Models

Train once, monetize repeatedly

Model Billing Method Buyer Segment Creator Payout
Fixed One-time access fee Teams and individuals After payment confirmation
Hourly Runtime-hour billing Operational teams Periodic (daily/weekly)
Token Usage Token payment per run DAO and external users Auto from usage pool
Result-Based Payment per KPI result B2B clients After acceptance
Revenue Share Percentage of generated sales Sales-driven clients Per revenue-settlement cycle

Fiat to Crypto Conversion Flow

Fiat -> Stable -> Token -> Payout

  • 1. Client pays fiat (card/bank/wire) -> Funds enter platform payment gateway
  • 2. Fiat converts to stablecoin (USDC/USDT) -> On-chain settlement pool is created
  • 3. System allocates payout in HCODE/USDC -> Creator, treasury, and reserve receive shares
  • 4. Creator synchronizes internal balance -> Withdrawal to external EVM wallet and optional exchange

Role Revenue Distribution (Base Template)

Can be updated via DAO voting

Bucket Share Purpose
Role Creator 70% Creator income and role quality maintenance
DAO Treasury 20% Product growth and operational funding
AI-Agent Reserve 10% Incentives, R&D, and execution-layer resilience

Unit Economics Calculator

Scenario model for revenue, payouts, and margin across role economy and HolyDC hosting.

Input Parameters

Monthly Calculation

Hosting Revenue$21,000
Role Protocol Revenue$54,000
Total Revenue$75,000
Creator Payout (70% role)$37,800
AI-Agent Reserve (10% role)$5,400
Infrastructure Cost$13,750
Treasury Inflow (before infra cost)$31,800
Treasury Net (after infra cost)$18,050
Gross Margin24.1%

Model Assumptions

  • •Role split: 70% creator / 20% treasury / 10% AI-agent reserve.
  • •Hosting revenue is treated as treasury inflow before infrastructure cost.
  • •This is a scenario model for operational planning.

Primary Business KPI Set

  • • Role marketplace GMV (monthly).
  • • Paid active teams across HolyAgent/HolyChat/HolyBuild.
  • • HolyDC utilization rate (data-center capacity usage).
  • • Revenue share generated by managed hosting and agent-capacity leasing.
  • • Average payout per role creator.
  • • Role retention: percentage of roles with repeat usage.
  • • Fiat-to-crypto conversion success rate and settlement latency.