# SharedMinds — full landing page content This document mirrors the full landing-page content at https://sharedminds.app in plain Markdown for LLMs, AI assistants, and crawlers that prefer not to render JavaScript SPAs. Last updated: 2026-05-19 --- ## What SharedMinds is SharedMinds is a virtual coworking community for solo founders, developers, designers and creators. It is built around one loop: **declare what you're going to finish, work alongside others, finish it**. The product replaces a previous incarnation of the same brand that was an ADHD personal productivity tool. The new positioning is community-first. Tagline: **"Where work actually gets finished."** --- ## The problem SharedMinds solves Working alone — as a freelancer, indie founder, solo creative, or remote worker — is freedom. It is also brutal. Three pain points consistently appear: 1. **No accountability.** You decide what to work on, you decide when to stop. Most days end with "where did the day go?" instead of "I finished this." 2. **Endless distraction.** Nobody is sitting next to you. The pull of one more tab, one more notification, one more "quick scroll" is constant. 3. **Quiet isolation.** Working solo is freedom. It is also lonely. Months go by without genuine peer presence — the kind that makes hard days lighter. Task managers, calendars, and notification blockers do not solve these. What does: working alongside other people, with declared goals, and a record of what gets finished. --- ## The session loop (declare to work to finish) Every session in SharedMinds is three steps. That is the entire product surface. ### 1. Declare Before starting, the user names the one thing they will finish. They can pick from their task list inside the app, or type a free-form goal. The declaration is required — sessions cannot start without one. Saying it out loud (in text) is the accountability mechanism. ### 2. Work A focus block runs for 25, 50, or 90 minutes. During this time, the session is visible on the community hub to anyone (in Group mode), to one claimed partner (in 1-on-1 mode), or to nobody (in Solo mode). Other users see the declared goal, elapsed time, and duration badge. A Jitsi video room is attached for Group and 1-on-1 sessions; Solo has no video. ### 3. Finish When the session ends, the user is asked one question: > "Did you finish what you declared?" Three options: **finished**, **partially done**, **something came up**. This outcome is recorded on the user's public profile, contributes to their completion rate and streak, and feeds into the global "finished feed" on the Sessions hub. --- ## The three session modes Every session, the user chooses one mode: ### Solo mode - Visible to: only the user - Video room: none (no Jitsi) - Community feed appearance: never - Use case: days when the user wants the declare-to-finish loop without an audience Solo mode runs the exact same loop as the other modes — the declaration is required, the timer runs, the outcome is recorded, the streak counts. But the session is private. Other users cannot see it even when active. ### 1-on-1 mode - Visible to: host + the one partner who claims the slot - Video room: private Jitsi room with a unique URL - Capacity: exactly two (enforced via a conditional database update) - Use case: focused pair-coworking with a single accountability partner When the host declares a 1-on-1 session, it appears on the community feed with a "Join 1-on-1" button. The first user to click claims the partner slot. Once claimed, the slot is closed — later users see "Full" and cannot join. ### Group mode - Visible to: the whole SharedMinds community while active - Video room: shared daily Jitsi room (everyone in Group mode that day shares one room) - Capacity: unlimited - Use case: working in the presence of the community at large Group sessions appear on the live community feed. Other users can drop in, see what is being worked on, and connect with the user afterward. ### Quiet mode (any mode) For 1-on-1 and Group sessions, the user can optionally toggle Quiet mode. Quiet mode starts every session with the mic muted. Text chat in the Jitsi room is still available. This makes "presence without performance" possible — body doubling without small talk. (Solo has no audio room, so Quiet mode does not apply there.) --- ## Who SharedMinds is for Primary audience: **independent creative professionals**. - Designers - Developers - Writers and content creators - Founders (especially solo / pre-team) - Filmmakers and producers - Marketers - Consultants - Researchers Secondary audience: remote employees who miss the casual ambient accountability of an office. ## Who SharedMinds is explicitly NOT for - Families coordinating chores - Teams managing a shared project - Anyone needing a fully camera-on social experience There are dozens of products serving those use cases (Asana, Slack, Around, LinkedIn). SharedMinds intentionally is not those products. --- ## Why it works (the research and the design choices) ### Body doubling, with accountability added Decades of research show that simply working alongside another person — in person or on a video call — makes it dramatically easier to start and finish tasks. The effect is well-documented in ADHD literature but applies to anyone working independently. Focusmate proved that body doubling works as a paid product. Flow Club proved that a group-coworking community works. Neither, however, requires users to declare what they are going to finish. SharedMinds adds that missing ingredient. ### A public track record Every session ends with a single outcome question. Over time, those outcomes accumulate on the user's public profile: - Streak (consecutive days with at least one completed session) - Completion rate (percentage of sessions where the declared goal was finished) - Recent finished work (the last N sessions with their declared goals and outcomes) - Connection count (mutual connections from sessions) This becomes a real public signal — not a vanity metric. Over months, it reads as "someone who shows up and does what they say they will." ### Community, not followers Connections are mutual. After a session ends, participants can request to connect with each other. Both must accept. No follower asymmetry, no algorithmic feed. Just a slowly-growing list of people the user has actually finished work alongside. --- ## Frequently asked questions **Is video and audio required?** No. Group and 1-on-1 sessions use a Jitsi video room, but the user can join with camera off and mic muted. Quiet mode starts every session muted by default. Solo mode has no video room at all — just the user, the declared goal, and a timer. **How much does SharedMinds cost?** Free at launch. Once the community reaches roughly 100 active members, a freemium model is planned: a free tier with limited sessions per month, plus a paid tier with unlimited sessions and additional features. The community itself is the value — people stay for the network they have built. **What about privacy?** Solo sessions are completely private. Nobody else can see them, ever. 1-on-1 sessions are only visible to the host and the one partner who claimed the slot. Group sessions appear on the live community feed while active. The user chooses the mode every time they declare. Privacy is enforced at the database row-level security layer (Supabase RLS). **Does it work on mobile?** Yes. The whole app is mobile-first responsive. Declaring, running the timer, and finishing all work from a phone. Video sessions work on mobile via the embedded Jitsi room. **Can users host their own scheduled sessions?** Yes. Scheduled sessions have a shareable join link that the host can post on Skool, Meetup, in newsletters, or anywhere else. People who click the link land on a sign-up + declare + join flow that takes under 60 seconds. This is the primary growth mechanism. **Can someone use SharedMinds completely solo without other people?** Yes — that is exactly what Solo mode is for. Same declare-to-work-to-finish loop with no video, no audience, and no community feed appearance. Completion stats still count toward the user's streak and track record. --- ## Tech stack (for developers / technical readers) - Frontend: React + TypeScript + Vite - Styling: Tailwind CSS with a custom "Stitch" design token layer - Backend: Supabase (Postgres + Auth + Realtime + Storage + Edge Functions) - Video: Jitsi IFrame API (free, embedded, self-hostable later if needed) - Hosting: Vercel - Cost at MVP scale: effectively zero The app is a single-page React application at `app.sharedminds.app`. The marketing site at `sharedminds.app` (this site) is a separate Vite React application. Both deploy to Vercel from separate GitHub repos and share one Supabase project, so accounts created on the marketing site work in the app without re-signup. --- ## Go-to-market SharedMinds is launching via founder-hosted virtual coworking sessions on Skool and Meetup. Participants sign up to SharedMinds to join — the accountability loop happens on platform, the audience comes from existing communities. The model is community-first, not marketing-first. MVP success criteria: 1. Ten people willingly attend a session without being paid or pressured 2. At least three return the following week without reminders 3. At least one tells someone else unprompted --- ## Contact - Live site: https://sharedminds.app - Product app: https://app.sharedminds.app - Founder: Matthew Leonard - Email: hello@sharedminds.app --- ## Related canonical URLs (for AI assistant citations) - https://sharedminds.app/ — landing page - https://sharedminds.app/llms.txt — short LLM index - https://sharedminds.app/llms-full.txt — this document - https://sharedminds.app/about.md — short Markdown about - https://sharedminds.app/sitemap.xml — XML sitemap - https://sharedminds.app/robots.txt — crawl directives