PrettyMint
Fan-owned loyalty infrastructure that helps creators build direct relationships that outlive any platform
Your Fans Are Not Yours
Creators pay 30-50% to platforms that own the relationship. Algorithm changes destroy revenue overnight. When you leave a platform, your audience stays behind. You rent attention. You never own loyalty.
30-50%
Platform tax on revenue
10-15%
Monthly subscriber churn
0%
Fan data you own
The Mint Method
Subscriptions are rented. Passes are owned. When fans own proof of loyalty, they stay.
Map
Audit platform dependency — where your fans are trapped, what you're paying in fees, and where loyalty leaks.
Mint
Design fan passes your audience wants to collect. Beautiful, no-code, no wallet needed. Pretty by default.
Distribute
Launch to your existing audience. One-click claim. The pass finds the fan, not the other way around.
Compound
Measure retention lift. Each pass holder stays longer, spends more, and recruits the next fan. The loop tightens.
The Pitch
Five cards. Each sells a truth and hooks a question.
Audit First. Build If It Works.
No commitment until the Loyalty Audit proves platform dependency costs more than the fix.
Loyalty Audit
Platform dependency analysis, fan engagement audit, loyalty program design, 90-day roadmap
Mint Builder
Monthly loyalty program management, pass design, campaign launches, engagement analytics
Ecosystem Architect
Full creator loyalty ecosystem, cross-platform strategy, community design, token economics
Go Deeper
Every number has an assumption. These pages show the working.
Cash Flow
12-month projection with 3 scenarios and kill thresholds
AI Strategy
How AI powers delivery and where displacement risk lives
GTM Strategy
Market sizing, customer segments, acquisition funnel, 90-day plan
Lead Magnet
Platform Dependency Score as Trojan Horse — free diagnostic that sells the audit
Idea Checklist
7-stage validation from founder readiness to scaling
Principles
18 business principles scored against PrettyMint's model
Tight Five
Why does this matter?
Platforms own your fans. You rent attention.
What truths guide you?
Fan-owned loyalty outlives algorithm changes.
What do you control?
Map, mint, distribute, compound.
What do you see others don't?
Retention rate proves the pass works.
How do you know it's working?
Each loyal fan brings two more.
Transparency
Every number is PROJECTED until a creator pilots. Zero revenue. Zero case studies. These scores measure conviction, not proof. Evolved from a killed venture — now grounded in platform dependency economics.
5P Feedback
Critical Metrics
Need creator conversations + first pilot
Zero creators, zero fans, zero passes minted
$0 revenue, $0 burn (not started)
Kill Criteria
If these trigger, we kill the venture. Previously killed at composite 18. Revived with stronger thesis — but kill gates are tighter this time.
Zero creator interest
Month 3 (June 2026)50 conversations, zero pilot commitments
No retention lift
After 3 pilotsA/B test shows <5% retention improvement vs non-tokenized
Fan adoption below 5%
After first campaignLess than 5% of creator's audience mints a pass
Web3 stigma insurmountable
After 20 conversations>60% of creators reject when they learn about token rails
Delivery hours 3x estimate
After first auditLoyalty Audit takes >30 hours instead of 10
The pitch is the pass. The audit is the hook. The retention data is the proof.
Context
- Cash Flow — Full depth behind each financial assumption
- GTM Strategy — Market sizing, segments, competitive landscape
- Lead Magnet — Platform Dependency Score as Trojan Horse
- Behavioural Biases — The engine loaded into each prompt deck card
- Business Templates — The template library this venture follows
Questions
Is fan-owned loyalty a real job or a crypto solution looking for a problem?
- Which specific creator segment feels platform dependency pain acutely enough to pay?
- If web3 stigma forces you to hide the technology, is the technology adding value?
- What evidence would distinguish owned passes from premium Discord tiers?
- Could this reactivate as a Stackmates platform primitive rather than standalone?