Party Minder Business Plan (Investor Narrative)
Summary
Party Minder is a social network built around gatherings, conversations, and communities. It is not a feed machine or a ticketing system. It is a WordPress plugin that empowers anyone to create their own community space, host events, invite guests, and keep conversations alive before, during, and after those gatherings. Instead of algorithms that amplify outrage or bury what matters, Party Minder uses a circles-of-trust model: your inner circle (communities you created), your trusted circle (communities they created), and your extended circle (one step further). Conversations appear in order, not filtered by ads or engagement tricks. Members see everything their circles share, and nothing is hidden.
To move forward, we need modest but critical support: standing up a Personal Data Server (PDS) to prepare for federation with the AT Protocol, training an in-house language model to power menu analysis and social prompts, and scaling hosting as installs grow. Investors can expect a capital-efficient business with distributed compute (WordPress sites run their own loads), multiple exit doors (plugin ecosystem acquisitions, strategic social buyers), and a realistic roadmap to revenue from Pro add-ons, hosted services, and integrations.
Narrative
We are here because the promise of social networks has been broken. Feeds designed to maximize time on screen have fragmented communities and left people isolated. Planning real-world gatherings has become harder, scattered across event platforms, group chats, and spreadsheets. None of the tools talk to each other, and none of them put the human host at the center.
Party Minder changes that. At its core it is a WordPress plugin, distributed through the WordPress.org directory, giving us instant reach into more than forty percent of the web. Any WordPress site can become a hub for events and conversations, owned by the community that runs it. An organizer creates an event, sends invitations, collects RSVPs, and keeps the conversation alive in a community space that persists. Guests don’t just show up once—they join the circle, reply, and remain part of the community for the next event.
The circles of trust model keeps it human-scaled. Instead of followers or algorithms, content flows through relationships: my communities, the communities of my members, and the communities one step beyond. Replies are always visible, discussions don’t vanish into feeds, and members can always find their way back to what matters. This structure means traction comes from circles that expand outward naturally, not from ad budgets.
The timeline is straightforward. In the next three months, we must complete plugin distribution and ambassador programs for early communities. In six months, we aim for thousands of installs and a growing set of recurring communities. Within a year, we will layer on hosted services: a companion dashboard for organizers, SMS reminders, and analytics. By year two, we plan to integrate our own LLM into the product, analyzing menus from vendors, suggesting meals for guests with allergies, and helping hosts write invitations or conversation starters. Costs are modest compared to traditional social apps. Compute is distributed across WordPress installs, so central hosting grows only with our companion services. Standing up a PDS for federation and training an LLM are the major capital expenses.
Revenue comes from three streams: Pro add-ons sold through WordPress (target $99/site/year), hosted dashboards and communication services ($19–$49/month per community), and transaction fees from optional vendor integrations. Conservatively, if we capture 25,000 active installs with 10 percent conversion to Pro and 5 percent conversion to hosted services, we project $1–2 million ARR within two years. At larger scale, those numbers multiply cleanly.
The company will be structured to run lean, using open-source distribution and partnerships with WP agencies and hosts. This keeps burn low and acquisition attractiveness high. Exit opportunities include strategic buyers in the WordPress ecosystem, which has a history of acquiring successful plugins, as well as larger social or event-driven platforms seeking a foothold in real communities. Investors receive early equity positions in a company designed for acquisition within three to five years.
AT Protocol matters because federation is the future of social. Owning a DID and connecting Party Minder communities to the open network makes us one of the first WordPress plugins to support true data sovereignty. AI matters because hosts need help: meal planning, RSVP prompts, conversation starters. Training our own LLM gives us control over privacy, cost, and performance. Together, federation and AI make Party Minder a forward-looking platform that grows with the next wave of social technology.
Goals
Our goals are clear. First, traction: to grow from hundreds to tens of thousands of installs, focusing on real communities hosting recurring events. Second, revenue: to convert those installs into Pro subscriptions and hosted service customers, hitting $500,000 ARR within 18 months and $1–2 million within 24 months. Traction and revenue together prove the model and make us an attractive acquisition.
Requirements
To get there, we need specific resources at specific times. We will outgrow our current shared hosting quickly, so we must prepare to scale companion services. Because we are a WordPress plugin, compute is distributed across installs, which keeps costs low, but central services must remain reliable. Standing up a PDS is required now, both for DID issuance and for preparing federation. Standing up an LLM training environment is also required now, even if early models are lightweight. This ensures that by the time we offer AI features to members, we own the stack and aren’t dependent on costly external APIs.
Strategy
Our roadmap is pragmatic. In the next quarter, we will launch to the WordPress directory, recruit early communities as ambassadors, and track key metrics: installs, active organizers, recurring events. In six months, we will launch hosted companion services and collect our first recurring revenue. In twelve months, we will demonstrate Pro conversion and begin training our LLM on real event and menu data. By year two, we will expand partnerships with agencies, hosts, and vendors. By year three, we will pursue acquisition discussions.
Resources to leverage include the WordPress ecosystem, which is both our distribution channel and our exit market. We will contact members through their existing communities: organizers who already manage clubs, faith groups, sports teams, and neighborhoods. We will attract members through those organizers, by making Party Minder the easiest way to invite, RSVP, and converse. Growth is viral by design: every event is an invitation to join the community, every reply is proof of engagement.
Appendix
Financial Tables: A 24-month projection showing installs, conversion rates, ARR, and expenses (hosting, PDS, LLM training, minimal staff).
More on AT Protocol: The AT Protocol is the backbone of Bluesky and other federated networks. A Personal Data Server (PDS) is where identities, handles, and data live. Standing up a PDS now allows us to issue DIDs to Party Minder members and future-proof our communities.
What’s a PDS? A PDS is a server that stores user data under their control, federates with other servers, and provides APIs for applications. By running one for Party Minder, we give every member an identity that can travel with them.
More AI: Large Language Models are trained on text data to generate useful responses. For Party Minder, AI can analyze vendor menus, suggest meals based on dietary restrictions, and help hosts compose messages. Training our own model ensures data privacy and predictable costs.
How to train an LLM: Start with open-source models, fine-tune on event and menu data, run inference locally for common tasks, and offload only heavy workloads when needed. The goal is not to compete with OpenAI but to own the features that matter to our members.
Exit Comparables: WordPress plugin acquisitions such as BuddyBoss and The Events Calendar, social app acquisitions such as BeReal and Gas, demonstrate realistic paths to exits in the tens to hundreds of millions range.
Would you like me to now expand the Appendix financial tables with hard numbers (hosting costs, PDS setup, projected installs, Pro conversions, ARR milestones) so you can actually show the math to investors?