Trust Commerce
What if you could turn every satisfied customer into a paid, reputation-verified salesperson — and settle the commission in under a second?
The Job
When someone discovers a product that genuinely helped them, help them recommend it to people they know — so the buyer gets a trusted recommendation, the coach-seller earns a commission, and the product gains a customer through the highest-converting channel that exists.
| Trigger Event | Current Failure | Desired Progress |
|---|---|---|
| Friend asks "what tool do you use for X?" | No incentive, no tracking, no reputation — value leaks | Instant referral link, sub-second commission settlement, reputation receipt on-chain |
| Business needs more customers | Spends $5-15 CPC on strangers via ad platforms | Pays micropayment commission only on actual conversion through trusted networks |
| Buyer researches a purchase | Overwhelmed by fake reviews and biased ads | Sees verifiable reputation of the person recommending, backed by on-chain history |
The Thesis
Advertising spends billions guessing who to target. A friend already knows.
A great teacher explains a complex subject in simple terms. A great coach makes the meaning important to you. That's the difference between advertising and selling. The coach already knows your Zone of Proximal Development — where you are and where you could be. They're not inferring your ICP profile from behavioral data. They had coffee with you yesterday.
| Advertising | Coach-Selling |
|---|---|
| Algorithm guesses your gap | Friend knows your gap |
| "People like you bought this" | "I know this would help you because..." |
| Platform owns the relationship | The coach owns the relationship |
| Conversion = persuasion | Conversion = progress |
| Reputation is platform-locked | Reputation is portable and on-chain |
| 2-3% conversion on cold traffic | 15-30%+ on warm referral |
| Commission settles in 30-90 days | Commission settles in under a second |
| $5-15 CPC regardless of outcome | Micropayment only on actual conversion |
The ZPD dynamic is the key: everyone is coach and student. Context determines which. The buyer today becomes the seller tomorrow. They used the product, it worked, now they recommend it to someone in their network who has the same gap. The trust graph grows because every satisfied customer is a potential coach for the next one.
This is not affiliate marketing. Affiliate marketing pays for clicks. Trust commerce pays for outcomes, and the reputation receipt makes every transaction an investment in future credibility.
Priority Score
PRIORITY = Pain x Demand x Edge x Trend x Conversion
| Dimension | Score (1-5) | Evidence |
|---|---|---|
| Pain — What's broken? | 3 | Global digital ad market ~$700B/yr, estimated 30-50% waste on mismatched targeting. Word-of-mouth converts 5-10x better but lacks scalable infrastructure. Quantifiable market pain but not acute for us today. |
| Demand — What is needed? | 2 | Internal vision. Coach archetype, trust principles, affiliate specs, incentive engineering docs exist as foundation. No external conversations or demand signals yet. |
| Edge — What is everyone missing? | 4 | Novel integration: coach-as-seller philosophy (ZPD-based selling) + Sui object model (recommendation as living, history-accumulating object) + existing trust/tokenomics/affiliate/reputation infrastructure across 11+ KB pages. Competitors would need 6+ months to replicate the philosophical + technical integration. |
| Trend — Where is this heading? | 5 | Structural shift: Web3 social commerce, on-chain reputation, creator economy direct monetization, Sui ecosystem growth, AI agents + crypto feedback loops. Market 2x+ in 3 years. |
| Conversion — Who needs convincing? | 1 | No revenue model defined. Protocol fees? Token? SaaS layer for businesses? Not specified. Cannot invoice this month. |
| Composite | 120 | 3 x 2 x 4 x 5 x 1 = 120 (Promising — needs demand validation and revenue model) |
Demand-Side Jobs
Job 1: Turn Satisfied Customers into Revenue-Generating Coaches
Situation: Customer genuinely loves a product. Friend asks "what do you use for X?"
| Element | Detail |
|---|---|
| Struggling moment | No easy way to recommend AND get rewarded. Informal word-of-mouth leaks value. |
| Current workaround | Share a link, maybe an affiliate code with 30-90 day payout and no reputation benefit |
| What progress looks like | Every recommendation generates: instant micropayment commission + on-chain reputation receipt that compounds future credibility |
| Hidden objection | "I don't want to feel like I'm selling to my friends" — the coach frame solves this: you're helping them make progress, not pushing product |
| Switch trigger | When a platform-locked affiliate program fails to pay, changes terms, or provides no reputation portability |
Features that serve this job:
- Referral link generation with embedded coach identity
- Sub-second commission settlement on Sui
- Reputation receipt minted as Sui object after successful purchase
- Coach dashboard showing earnings, reputation score, recommendation history
Job 2: Validate Purchase Decisions Through Verifiable Social Proof
Situation: Considering a purchase, overwhelmed by options, don't trust marketing.
| Element | Detail |
|---|---|
| Struggling moment | "Reviews could be fake, ads are biased, who do I actually trust?" |
| Current workaround | Ask friends informally, read Amazon reviews, hope for the best |
| What progress looks like | See verifiable on-chain reputation of the person recommending — their history of good recommendations, satisfaction rates, domain expertise |
| Hidden objection | "What if even my friend is just trying to earn a commission?" — on-chain reputation makes the track record transparent |
| Switch trigger | Getting burned by a purchase based on fake reviews or biased influencer content |
Features that serve this job:
- Public reputation profile showing recommendation history and satisfaction outcomes
- Domain-specific credibility scores (e.g., trusted for construction tools, not for skincare)
- Buyer satisfaction feedback that updates coach reputation
- Reputation decay for inactive or low-quality recommenders
Job 3: Build Portable Sales Reputation Across Products and Networks
Situation: Good at recommending products but reputation is locked in platforms.
| Element | Detail |
|---|---|
| Struggling moment | Starts recommending on a new platform — reputation doesn't transfer. Amazon stars don't help on LinkedIn. |
| Current workaround | Build reputation from scratch each time. Lose everything when platform changes TOS. |
| What progress looks like | On-chain reputation object follows you across products, platforms, and networks. Verifiable by anyone. |
| Hidden objection | "What if my bad recommendations are permanent?" — reputation should be recoverable through consistently good future recommendations |
| Switch trigger | Losing built-up reputation when a platform shuts down, changes rules, or deplatforms |
Features that serve this job:
- Sui identity object with composable reputation modules
- Cross-product reputation aggregation
- Reputation recovery mechanics (recent performance weighted higher)
- zkLogin onboarding — no wallet required to start recommending
Why Sui
The chain matters. Sui's architecture maps directly to the trust commerce data model.
| Requirement | Why Sui | Alternative Limitation |
|---|---|---|
| Recommendation as object | Sui's object-centric model — each recommendation is an owned object with history, not a row in a ledger | EVM chains use account-based model — reputation is a mapping, not a composable object |
| Sub-second settlement | ~400ms finality — commission settles before the buyer closes the tab | Ethereum L1: 12s blocks. Bitcoin: 10min. Even L2s add bridge latency |
| Micropayment economics | Gas costs measured in fractions of a cent — $0.01 commission is viable | ETH gas makes sub-$5 transactions uneconomical |
| Mainstream onboarding | zkLogin: sign in with Google, no wallet install | Other chains require wallet download + seed phrase management |
| Sponsored transactions | Business can cover gas costs — buyer/coach never sees crypto | Most chains expose the user to gas mechanics |
| Safety | Move language: resources can't be accidentally destroyed, compile-time ownership checks | Solidity: runtime errors, reentrancy risks, lost funds |
The Sui Wallet Safety PRD provides the safety patterns. The Sui platform docs describe the five primitives this builds on: Data Sovereignty, Truth, Identity, Trust, Data Verticals.
Architecture: The Trust Graph
COACH (recommender) BUYER
│ │
├─ Creates recommendation ────────┤
│ (Sui object: product, │
│ context, coach identity) │
│ │
│ Buyer purchases ──→ Smart contract executes:
│ 1. Product payment to merchant
│ 2. Commission to coach (instant)
│ 3. Reputation receipt minted
│ │
│ Buyer rates experience
│ │
├─ Reputation updated ←───────────┤
│ (satisfaction score, │
│ domain credibility, │
│ recommendation count) │
│ │
└─ Coach credibility compounds Buyer becomes potential coach
across all recommendations for their own network
Core Entities (Sui Objects)
| Entity | Owner | Contains | Composable With |
|---|---|---|---|
| Coach Profile | The recommender | Reputation score, domain expertise, recommendation history | Identity module from Sui Wallet PRD |
| Recommendation | Shared (coach + product) | Product reference, context ("why this helps you"), coach identity | Any product/service listing |
| Purchase Receipt | The buyer | Product, price, coach who recommended, satisfaction rating | Loyalty module from Sui Wallet PRD |
| Reputation Delta | The coach | +/- credibility based on buyer satisfaction | Coach Profile (auto-updates) |
Bootstrap Bridge from SPO
Trust Commerce takes the qualification outcomes, satisfaction data, and relationship proof that Sales Process Optimisation generates — and makes them verifiable, portable, and economically incentivized on Sui.
Without SPO operating and generating real outcomes, Trust Commerce has nothing to put on-chain. Objects need data to contain.
The Data Flow
SPO Qualification Proof Trust Commerce
───────────────────── ──────────────
4-layer ICP score + evidence trail → Basis for on-chain reputation
Satisfaction outcomes (buy? happy?) → Reputation Delta objects
Relationship data (who → whom) → Trust graph seed data
The Bootstrap Strategy
SPO's first paying clients become the first trust commerce network nodes:
| SPO Client | Trust Commerce Seed |
|---|---|
| HRV (Sneakers Media) | Satisfied customers become first coaches. They had the ventilation installed. They know which friends are homeowners with moisture problems. |
| Kitchen Studio | Completed renovations become social proof. The homeowner shows their new kitchen to visitors. "Who did this?" → referral link → commission → reputation receipt. |
| Construction/solar EPC | Builders who use the RFP tool successfully recommend it to peers. Professional trust network with verifiable project history. |
The warm referral leads from Trust Commerce flow back into the Sales Dev Agent pipeline, pre-qualified by the trust graph. Cold outreach becomes unnecessary for the portion of pipeline that comes through the trust network.
Success Criteria
| Criteria | Metric | Target | How to Measure |
|---|---|---|---|
| Referral conversion rate | % of recommendations that result in purchase | >15% (vs 2-3% for cold ads) | On-chain purchase receipts / total recommendations |
| Commission settlement speed | Time from purchase to coach payout | <1 second | Sui transaction finality timestamps |
| Reputation accuracy | % of high-reputation coaches whose recommendations satisfy buyers | >80% satisfaction rate for coaches with score >70 | Buyer feedback on purchase receipts |
| Network growth | New coaches joining per month (satisfied buyers who start recommending) | >20% of buyers become coaches within 90 days | Coach Profile creation rate vs Purchase Receipt count |
| Cost efficiency vs ads | Cost per acquisition through trust network vs paid channels | >50% reduction in CAC | Commission paid / customers acquired vs ad spend / customers acquired |
Commissioning
| Component | Status | Evidence |
|---|---|---|
| Trust commerce thesis | Spec complete | This PRD + trust/coach/incentive KB |
| Sui object model design | Not started | Needs: Coach Profile, Recommendation, Receipt, Reputation Delta objects in Move |
| Smart contract (commission settlement) | Not started | Needs: atomic swap — payment splits to merchant + coach |
| zkLogin integration | Not started | Depends on Sui Wallet PRD patterns |
| Coach dashboard UI | Not started | Depends on Identity & Access PRD |
| Reputation scoring algorithm | Not started | Needs: decay function, domain weighting, satisfaction integration |
| Buyer feedback loop | Not started | Needs: post-purchase satisfaction rating that updates reputation |
Composition
This PRD composes from existing capabilities:
| Dependency | What It Provides | Status |
|---|---|---|
| Sui Wallet Safety | zkLogin, safety patterns, Move modules (Identity, Loyalty) | L1 |
| Sales CRM & RFP | Pipeline tracking, lead attribution | L2 |
| Agent Platform | Agent identity, comms dispatch (for AI coach-agents) | L1 |
| Sales Process Optimisation | ICP validation, qualification scoring | L0 |
| Incentive Engineering | Token design principles, incentive alignment | KB |
| Affiliate Spec | Partner recruitment, commission tracking, fraud prevention | Spec |
New code required: ~40%. Sui Move contracts (recommendation objects, reputation scoring, commission settlement), trust graph queries, coach dashboard.
Risk + Kill Signal
| Risk | Likelihood | Impact | Mitigation |
|---|---|---|---|
| Commission incentive corrupts authentic recommendations | H | H | Reputation scoring penalizes low-satisfaction referrals. Transparency is the antibody — all recommendations are on-chain. |
| Sybil attacks (fake coaches farming reputation) | M | H | Require verified identity (zkLogin), minimum purchase history before earning coach status, network analysis for anomalous patterns |
| Network bootstrap problem (no coaches = no buyers = no coaches) | H | H | Bootstrap through SPO's clients (see Bootstrap Bridge): HRV satisfied customers → first coaches, Kitchen Studio renovations → social proof, construction/solar peers → professional trust network. |
| Regulatory risk (referral fees as securities/money transmission) | M | M | Structure as payment processing, not investment. Consult legal before launch. Commission is for service (recommendation), not equity. |
| Sui ecosystem risk | L | H | Architecture allows chain migration — core logic is in the trust graph model, not chain-specific. Move contracts are the implementation, not the thesis. |
Kill signal: First 100 coach-sellers produce fewer than 15 purchases AND buyer satisfaction on recommended purchases is below 60% — meaning the trust premium doesn't exist in practice.
Revenue Model (TBD — Conversion Score = 1)
This is the weakest dimension. Possible models to validate:
| Model | How It Works | Who Pays | Risk | Phase |
|---|---|---|---|---|
| SaaS layer | Businesses pay monthly for coach management dashboard, reputation analytics, referral link tools. Sui settlement is free; the tooling costs. | Merchants ($50-200/mo per active product) | Requires merchant adoption | Start here |
| Per-commission fee | Small % of each commission settlement (like Stripe's 2.9% but for trust commerce) | Coach (deducted from commission) | Reduces coach incentive. Needs volume. | Phase 2 |
| Protocol fee | 1-3% of commission goes to protocol treasury | Network (shared) | Requires governance structure | Phase 3 |
| Reputation-as-a-service | Businesses pay to access trust graph data for targeting | Merchants | Privacy concerns | Phase 3 |
| Token model | Governance/utility token for the trust network | Network participants | Regulatory complexity (especially NZ). Only if community governance genuinely adds value. | Maybe never |
Recommended sequence: Start with SaaS layer (businesses pay per active coach or per commission processed). This proves merchant willingness to pay. Add per-commission fee when volume justifies it. Token only if community governance model genuinely adds value — most successful crypto products use hybrid (free protocol + paid SaaS + optional token).
Action needed: Validate which model before building. Run 5 conversations with potential merchants and 5 with potential coach-sellers.
Build Sequence
| Phase | What | Validates | Depends On | Sui Layer |
|---|---|---|---|---|
| 0. Demand validation | 10 conversations: 5 merchants + 5 potential coach-sellers | Is there pull? Will merchants participate? Will people recommend for micropayments? | Nothing — do this first | — |
| 1. Paper prototype | Mock the flow: recommend → purchase → commission → reputation update | UX clarity, does the coach frame feel natural? | Phase 0 positive signal | — |
| 2. Sui Move contracts | Coach Profile, Recommendation, Receipt, Reputation Delta objects | Technical feasibility, gas costs, settlement speed | Sui Wallet PRD patterns (L1) | Today's mainnet |
| 3. MVP | Single product, single vertical (HRV satisfied customers as first coaches via SPO bootstrap), 20 coach-sellers. SaaS revenue model tested. | Conversion rate vs cold outreach, reputation accuracy, merchant willingness to pay | Phases 1-2 + SPO generating real outcomes | Today's mainnet |
| 4. Network effects | Buyer-to-coach conversion, cross-product reputation aggregation | Does the flywheel spin? | Phase 3 positive metrics | Today's mainnet |
| 5. Privacy layer | Selective disclosure — aggregate reputation proofs without individual transaction exposure | Trust at scale without surveillance | Sui 2026 privacy upgrade | 2026 upgrade required |
What's Buildable Now vs 2026
| Capability | Today's Sui Mainnet | Requires 2026 Privacy Upgrade |
|---|---|---|
| Coach Profile objects | Yes — owned objects with history | — |
| Recommendation objects (shared) | Yes — shared objects with PTBs | — |
| Sub-second commission settlement | Yes — ~400ms finality | — |
| zkLogin onboarding | Yes — Google/Apple sign-in | — |
| Sponsored transactions | Yes — business covers gas | — |
| Purchase receipts + satisfaction | Yes — standard object operations | — |
| Aggregate reputation proofs | No — individual transactions visible | Yes — selective disclosure |
| Private recommendation context | No — context is on-chain | Yes — encrypted fields |
| Anonymous coach identity | No — coach identity visible | Yes — zero-knowledge proofs |
The MVP works entirely on today's Sui mainnet. Privacy-dependent features (aggregate reputation without individual exposure, anonymous coaching) are gated on the 2026 upgrade. Build for what exists, design for what's coming.
Relationship to Other PRDs
HORIZON 1: PROVE IT WORKS (Now → 90 days)
Sales Dev Agent — generates outreach data + first customers
│ feeds into
▼
HORIZON 2: ORCHESTRATE THE TEAM (90 days → 6 months)
Sales Process Optimisation — qualification proof + satisfaction data
│ generates the data for
▼
HORIZON 3: MAKE IT A PROTOCOL (6 months → 18 months) ← THIS PRD
Trust Commerce — on-chain reputation + micropayment settlement
What this PRD receives from SPO:
- Qualification proof — structured evidence from SPO's 4-layer ICP model becomes the basis for on-chain reputation
- Satisfaction outcomes — did the qualified lead buy? Were they satisfied? This is the Reputation Delta input
- Relationship data — who recommended whom, through what channel, with what result. Trust graph seed data.
What this PRD returns to H1:
Warm referral leads flow back into the Sales Dev Agent pipeline, pre-qualified by the trust graph. The trust premium reduces CAC for the portion of pipeline coming through the network.
The Vision
The goodwill principle says: "The quality of people who gather around you is the scoreboard. Not your net worth — your network worth."
Trust commerce makes network worth measurable and portable. Every recommendation is an investment. Every satisfied buyer is compound interest. The trust graph doesn't just record transactions — it records integrity.
The mycelium metaphor is literal here. Underground trust connections surface value wherever conditions are right. The coach who just crossed your gap IS the best salesperson — not because they're skilled at persuasion, but because they understand your Zone of Proximal Development and genuinely want you to make progress.
Verifiable truth replaces the need for trust with proof. But in trust commerce, the proof IS the trust — accumulated, on-chain, and compounding.
Context
- Coach Archetype — The philosophical foundation: coach = seller, ZPD = targeting
- Trust — Trust architecture, four levels, integrity as currency
- Goodwill — Network worth, reciprocity loops, status through contribution
- Incentive Engineering — Token design, incentive alignment, anti-extraction
- Sui Platform — Object model, zkLogin, sub-second finality
- Sui Wallet Safety — Move modules: Identity, Loyalty, safety patterns
- Selling — The dream side of dream engineering
- Verifiable Truth — Blockchain as attestation layer
- Advertising — The DePIN disruption this extends
- Loyalty Tokens — Web3 loyalty mechanics