Embodied social rituals that measurably increase trust and belonging in an AI-first world
AI-native business plan
Touch For Fun is not just a pitch. A venture folder should show the idea, the economics, the go-to-market path, the AI leverage, the delivery loop, and the proof gates needed to run it. Missing artifacts stay visible until they are authored.
Artifacts
0
Covered
7
Needed
2
Revenue, delivery cost, burn, runway, scenarios, break-even, and kill thresholds.
Each Community Program client costs $0-300 to acquire, generates $500/month at 60% margin, pays back in month 1, retains 6 months — 10:1 LTV:CAC.
Ideal customer profile, wedge, channels, acquisition loop, 90-day plan, and conversion proof.
Zero customer conversations. Community facilitators exist but paid protocol market unvalidated.
Where AI creates leverage, what remains human judgment, and what data compounds.
Browser-as-instrument — WebAudio + WebRTC + on-device measurement
Packages, price points, first paid unit, margins, and the smallest sellable promise.
TBD
The diagnostic or proof asset that turns interest into a named prospect.
Missing from the public operating model. This is the next planning gap to author.
Founder readiness, pain evidence, demand signals, risk gates, and next experiment.
Covered on this overview from venture data.
Business principles, constraints, leverage, distribution, and what not to optimize.
Missing from the public operating model. This is the next planning gap to author.
How the business runs week to week: learn, sell, deliver, measure, improve, teach.
Facilitate one free session. Run pre/post trust measurement.
Metrics, evidence state, proof gaps, reactivation conditions, and kill criteria.
Repeat attendance unproven
Planning standard: cash flow model, go-to-market plan, AI strategy, offer/pricing, lead magnet, validation checklist, principles audit, operating loop, and proof/kill signals. Business instruments hold the reusable templates; venture folders hold the business-specific plan.
Playbook depth
Venture pages should stay specific to the business. When a reader needs depth, context, reusable templates, or the operating model behind the bet, route them into the playbook instead of adding another local nav layer.
How to choose and run the business model after the workflow is redesigned.
Model revenue, burn, runway, break-even, scenarios, and kill thresholds.
Define the ideal customer profile, wedge, channels, acquisition loop, and 90-day conversion plan.
How to run the business: process, owners, platforms, gauges, and cadence.
Architecture and stack choices, including what Stackmates has built or must build.
What app surfaces and software categories the business model needs.
Separate human judgment, agent work, data loops, and automation leverage.
Use the reusable blueprint library; keep venture folders business-specific.
Why does this matter?
Digital connection can't replace physical trust.
What truths guide you?
Consent first. Measure trust, not vibes.
What do you control?
Protocol quality, facilitator standards.
What do you see others don't?
Touch is infrastructure, not entertainment.
How do you know it's working?
Trust delta, repeat attendance rate.
Need 2 live pilots with trust measurement data
Need facilitator community + recurring sessions
$0 revenue, $0 burn (pre-pilot)
| ID | Feature | Why |
|---|---|---|
| AUTH-001 | User registration | Facilitator and participant accounts |
| USER-001 | User profiles | Facilitator identity and credentials |
| USER-002 | Organisation management | Group and club management |
| COLB-001 | Team chat | Community coordination |
| AI-002 | Conversational AI | Onboarding and protocol guidance |
What would change if Touch For Fun measured facilitator vitality alongside participant trust?