PrivateDAO is being packaged as public-good governance and treasury infrastructure with a commercial model that is testable on Solana Testnet and simple enough for judges, buyers, and grant reviewers to understand quickly.
The rule is simple:
- price what consumes real execution, review, or operator effort
- keep the first billing lane visible on-chain
- do not pretend that a full mainnet subscription stack is already complete
PrivateDAO should not start by asking a buyer to understand every cryptographic rail. It should sell a clear operational outcome:
- private governance approval without leaking intent early
- confidential payroll, vendor payout, reward, or treasury operation rehearsal
- proof packet that a non-builder stakeholder can inspect
- hosted reads and operator support for teams that repeat the workflow
The business model is therefore:
- Open protocol for trust, adoption, and developer inspection.
- Fixed pilot for first paid conversion.
- Managed operations for recurring revenue.
- Sovereign deployment for high-value customers that need dedicated infrastructure.
The first paid product should be a bounded pilot, not an open-ended enterprise promise.
Initial posture:
- price:
$2,500 setup - length: four weeks
- buyer: DAO, grant committee, gaming guild, fund, or Web3 operating team
- deliverable: one configured workflow, one Testnet operating run, one proof packet, and one conversion recommendation
This is the cleanest judging-stage business motion because it is specific, purchasable, and tied to the live product.
Recurring revenue starts after the pilot when a team repeats the workflow.
Initial posture:
- price:
$750/monthstarting point - includes hosted reads, telemetry, proof exports, operator support, monthly readiness review, and managed governance or payout playbooks
- expands into payroll, confidential payout, gaming reward, API, or compliance-facing service lanes
These charges fit the lanes that consume privacy or runtime resources directly:
- reviewer-visible proof generation and export packaging
- confidential payout rehearsal and settlement coordination
- API and hosted-read usage above the free entry threshold
- operator-assisted governance or treasury execution
These plans fit DAOs, teams, and institutions that need a predictable product lane:
- pilot onboarding and configuration
- hosted reads and runtime reporting
- selective disclosure and reviewer handoff support
- launch, custody, and rollout coordination
PDAO can support:
- governance rights
- discount posture
- treasury alignment
- contributor incentives
Current boundary:
- the repo does not claim that PDAO is already the universal billing token for every operation
- the repo does claim that PDAO can become part of the pricing and governance posture without breaking the wallet-first product model
The current billing lane is a Testnet rehearsal:
- the visitor connects a Solana Testnet wallet
- the visitor selects a small service SKU
- the visitor signs a SOL transfer, or a configured PUSD SPL transfer, to the Testnet treasury receive address
- the chain records the signature and memo
- the visitor opens the explorer link and runtime proof
This matters because it proves that the product can already connect:
- business logic
- wallet UX
- on-chain payment proof
- reviewer-visible hashes and logs
Live route:
https://privatedao.org/services/testnet-billing-rehearsal/
This is not yet presented as:
- fiat checkout
- recurring card billing
- finished mainnet subscription infrastructure
| Service lane | Model | Initial posture |
|---|---|---|
| Open protocol access | free | public product, Testnet execution, source inspection, proof review |
| DAO onboarding and pilot activation | fixed setup | $2,500 four-week pilot or grant-backed setup |
| Managed governance operations | monthly subscription | $750/month starting point after a successful pilot |
| Hosted reads and telemetry | usage + support | free entry threshold, then usage-priced or bundled into plans |
| Reviewer-safe privacy packet | per packet | charge when a team needs buyer, auditor, or committee-ready exports |
| Confidential treasury or payout rail | per action or premium plan | charge when REFHE / MagicBlock-backed operation support is requested |
| PUSD payroll, grants, and gaming rewards | per transfer lane or premium plan | use Palm USD as the institutional stablecoin corridor through the prepared SPL transfer lane once the official Solana mint and treasury receive address are set |
| Operator support and launch coordination | monthly or milestone retainer | for teams that need higher-touch release help |
| Sovereign deployment | custom | customer cloud, dedicated controls, white-label, custom retention, and support scope |
The commercial model is not only pricing. It also depends on four internal modules that must keep improving:
- reduce wallet friction
- shorten the route from learn to live execution
- keep language understandable for normal users, not only protocol engineers
- keep the product readable for buyers, operators, and judges
- improve route continuity between story, learn, services, trust, and proof
- make the commercial lane feel like a real operating surface, not a brochure
- track which Testnet actions justify usage-based pricing while preserving older Devnet evidence as rehearsal history
- keep the free path generous enough for ecosystem learning
- protect the later enterprise lane from underpricing technical support and trust work
- fuzzing
- coverage
- runtime evidence
- CodeRabbit and reviewer passes
- launch and custody truth
The business model only remains credible if these assurance surfaces keep improving with the same seriousness as the product UI.
PrivateDAO can already show:
- a live browser product
- a live Solana Testnet governance path
- a live proof and trust path
- a live Testnet billing rehearsal with SOL and PUSD SPL transfer construction
- a plausible pricing and services structure
- a fixed pilot motion that can convert live Testnet proof into the first paid buyer conversation
That is enough to argue that the project is not only technically interesting. It is a credible infrastructure company in formation.
This document does not claim:
- live mainnet customer revenue
- finished institutional billing rails
- recurring subscription automation on-chain
- completed enterprise contracts
It documents the commercial model and the currently live Testnet billing rehearsal that make the model testable today.