Business Model Canvas
Designed by: Andy Gayton |
Designed for: Dihan Chandra | Created: July 20, 2025 |
Updated: August 14, 2025 | Version: 0.2
Key Partnerships
- iroh for hole punching and P2P networking
- Integrations with Nushell, Datastar
- Overlapping tinkerer communities and indie dev networks
Key Activities
- Build and maintain signup, auth, and billing flows
- Keep infrastructure stable and reliable
- Produce clear docs, demos, and onboarding
- Host regular show & tell sessions
Value Propositions
- Feel like a capable builder again — instant feedback, clear understanding, safe to tweak
- Escape inscrutable error logs and heavy frameworks
- Capture anything (URL, clipboard, webhook) into a live stream in minutes
- Compose from small, understandable pieces instead of large opaque stacks
- Keep full control with append-only history for inspection and replay
- Share a digital garden
- Start locally, add always-on sync when ready
Customer Relationships
- Small, trust-based community
- Collaboration with other tinkerers and thinkers
- Feedback loops that shape the platform
- Users as co-creators, not just consumers
Customer Segments
- Indie devs, hackers, and small teams
- Tech-literate makers (spreadsheet level+)
- Tool-for-thought and digital garden builders
Key Resources
- Per-user isolated stream infrastructure
- Lightweight auth and token system
- Billing via Stripe
- Active founder/community network
Channels
- GitHub and open-source repos
- Discord, civic tech, and creative coding meetups
- Show & tell sessions and demos
- Indie tech forums (e.g., Hacker News)
Cost Structure
- Infrastructure per tenant (Fly.io, PhoenixNAP)
- Domains, SSL, email, Stripe fees
- Founder time and effort
Revenue Streams
- $3/month per Cloud Pop stream
- Upsells: multi-stream, digital garden publishing
- Long-term: $200K–$500K/year target
Value Propositions
Emotional Pain Points
- Frustration with modern stacks: "Every time I want to build something fun, I end up buried in incomprehensible JavaScript tracebacks and brittle Next.js configs."
- Loss of creative flow: "I can't just make a change and see it work anymore — there's always a delay, a rebuild, an error to chase down."
- Disconnection from the system: "I don't understand my tools deeply enough to feel confident changing them."
- Lack of ownership: "My creations feel trapped in frameworks and services I don't control."
2-Minute "Aha" Example — Capture a URL, Get a Screenshot Back in Your Stream
-
Start: The customer opens a terminal connected to their personal stream.
-
Capture: They run a single command to append a URL to the stream.
| -
Automation: A small, visible actor they can read and understand picks up the event, launches a screenshot service, and saves the image to the stream.
-
Feedback: Within seconds, the stream updates in their terminal — now showing the original URL and the screenshot as a new event.
-
Emotional payoff:
- Instant gratification: "I did that in two minutes."
- Understanding: "I can see exactly which actor did the work and how."
- Control: "I can swap the screenshot service, change the output format, or chain another step without touching anything else."
Other Proposed "Aha" Use Cases (High Level)
- Clipboard Watcher: Anything copied to the clipboard automatically appears in the stream, optionally transformed or tagged for later use.
- Discord Bot Listener: Messages in a specific channel become stream events that can trigger automations, like summarization or archiving.
- GitHub Webhook Trigger: Local scripts fire in response to repo events via smee.io — perfect for dev workflows without cloud CI/CD complexity.
- MCP Client Services: Run a local MCP server as a service to extend capabilities dynamically, without changing core code.
- Publishing Stream as a Digital Garden: Append raw thoughts to the stream; expand them over time; render the evolving state into a public site with minijina + http-nu.
Previous versions: v0.1 (July 20, 2025)