// verdict #12 · 21 May 2026 · 10:45 UTC

outsavvy.com/

PASS

three or more voices said no. release without guilt.

submitted by Rob · BLKOUT · model anthropic/claude-sonnet-4 · against wishlist of 2026-04-27T11:18:37z · visit the tool → · back to history

// the four voices, in parallel

What the Council said

// 01 · critic

Baldwin

pass

technical risk, lock-in, sequencing — the master's tools.

Looking at OutSavvy, this is a UK-focused LGBTQ+ event discovery and ticketing platform. Let me stress-test this against BLKOUT's context and guardrails. **VENDOR LOCK-IN CONCERNS:** This is a third-party platform where BLKOUT would be a customer, not the infrastructure owner. Event data, attendee lists, and payment processing would live in OutSavvy's system. No clear data export capabilities mentioned. This creates dependency on a commercial platform for core event management functions. **GUARDRAIL VIOLATIONS:** - **"RSVP and Stripe are already built"** - This directly violates this guardrail. BLKOUT has already built frontend and backend for event RSVPs. OutSavvy duplicates this existing capability rather than addressing the actual gap (credentials and table connections). - **Pre-order model mismatch** - OutSavvy is built for traditional event ticketing, not BLKOUT's waiting-list/pre-order model with CBS tiers. **OPERATIONAL OVERHEAD:** Platform fees aren't disclosed on the public site, but event platforms typically take 3-5% plus payment processing. For a small organization, this represents ongoing revenue leakage. Also requires learning and maintaining another platform's admin interface. **SEQUENCING PROBLEMS:** This doesn't address Tier 1 priorities. BLKOUT needs "Tech stability and system resilience" before adding more external dependencies. The **Regular events calendar** wishlist item (Tier 2) could be served by OutSavvy, but it's premature when foundational infrastructure isn't solid. **WISHLIST ALIGNMENT:** Partially maps to "Regular events calendar and Brunch 2030" but doesn't address the core need - which is programming and venue relationships, not ticketing infrastructure. The constraint isn't technical capability but "delegate the programming" and maintaining "key venue relationships." **SURVEILLANCE MECHANICS:** OutSavvy collects attendee data that would live outside BLKOUT's data sovereignty principles. This contradicts the **"Schema ownership"** guardrail - member data should flow through CRM tables, not external platforms. The fundamental issue: this solves a problem BLKOUT doesn't have (ticketing infrastructure) while creating problems it's trying to avoid (external data dependencies, platform fees, duplicated capabilities). **RECOMMENDATION: PASS**

// 02 · ethicist

Murray

pass

values, sovereignty, community benefit.

Looking at OutSavvy through BLKOUT's values lens and wishlist priorities, I see several concerning misalignments alongside some potential utility. **Values Assessment:** **Data Sovereignty & Anti-Surveillance:** OutSavvy operates as a commercial ticketing platform that necessarily collects member data for event bookings. While they mention LGBTQ+ charity support, there's no indication members control their data or can see what's held about them. The platform's business model depends on data aggregation across users and events — fundamentally at odds with BLKOUT's data sovereignty principles. **Community Benefit vs. Extraction:** This is a commercial platform that takes transaction fees from both organisers and attendees. While it serves LGBTQ+ events, it extracts value from the community rather than being accountable to it. The "proudly supporting LGBTQ+ charities" messaging suggests charitable giving rather than community ownership or control. **Transparency & Member Agency:** No evidence that users can audit what data is held about them, how it's used, or have meaningful control over their information. The platform centralises event discovery and ticketing without apparent community input into how these systems operate. **Wishlist Mapping:** This tool doesn't clearly map to any specific wishlist item. The closest might be **"Regular events calendar and Brunch 2030"** — but OutSavvy is a discovery platform for existing events, not a tool for BLKOUT to manage its own calendar. For **"Non-intrusive lead generation"**, OutSavvy's commercial model and data practices would likely violate the "values-consistent methodology" requirement. **Guardrail Conflicts:** The **"Pre-order model, not always-on store"** guardrail is relevant here. BLKOUT operates a waiting-list/pre-order model with CBS tiers, while OutSavvy assumes always-on event ticketing. This is a category mismatch for BLKOUT's current operational model. **Practical Concerns:** OutSavvy would create operational dependency on a proprietary platform with no self-hosting option and unclear data export capabilities. This conflicts with BLKOUT's open-source alignment and infrastructure ownership principles. The platform might be useful for BLKOUT members to discover community events, but adopting it organisationally would mean surrendering data sovereignty and community control to a commercial entity whose interests may not align with BLKOUT's mission over time. RECOMMENDATION: PASS

// 03 · builder

Rustin

pass

vibe-codeability, stack fit, lift — what'll actually ship.

Looking at OutSavvy — this is an LGBTQ+-focused event discovery and ticketing platform, essentially a queer-specific Eventbrite competitor. ## VIBE-CODEABILITY & STACK COMPATIBILITY **Major red flag**: This isn't a self-hosted tool at all. OutSavvy is a third-party SaaS platform where BLKOUT would list events alongside other organizers. There's no code to deploy, no containers to manage, no integration with our Coolify stack. It's purely a listing service. ## GUARDRAIL VIOLATIONS This hits multiple guardrails hard: - **"RSVP and Stripe are already built"**: BLKOUT has functional event creation and RSVP systems. OutSavvy duplicates this entirely — it's not filling a gap, it's replacing existing capability. - **"Pre-order model, not always-on store"**: OutSavvy assumes traditional event ticketing with immediate sales. BLKOUT operates on waiting lists and pre-orders with CBS tiers. - **"Schema ownership"**: Event data would live in OutSavvy's database, not BLKOUT's CRM. Complete loss of data sovereignty. ## WISHLIST MAPPING This doesn't map to any wishlist item. The closest might be "Regular events calendar" but that's about programming consistency, not ticketing infrastructure. OutSavvy solves discovery for attendees, not operational capacity for BLKOUT. ## LIFT ASSESSMENT vs. VALUE While OutSavvy would be "accessible" to implement (just create an account), it undermines the entire digital infrastructure BLKOUT has built. The team has already solved event management — the constraint is programming and promotion, not ticketing mechanics. ## INTEGRATION IMPOSSIBILITY OutSavvy can't integrate with BLKOUT's CRM, member pages, or AIvor because it's a walled garden. Any member data collected through OutSavvy stays in OutSavvy. ## THE REAL QUESTION If BLKOUT wants better event discovery, the solution is improving SEO, social media presence, and community partnerships — not abandoning the custom infrastructure for a generic platform that doesn't understand CBS models or community sovereignty principles. OutSavvy might be useful for *discovering* other queer events to promote to members, but as a hosting platform it's a category mismatch with BLKOUT's values and technical architecture. RECOMMENDATION: PASS

// 04 · inclusion

Rivera

pass

reach, the under-served, who's on the street.

Looking at OutSavvy through the lens of reach and inclusion for BLKOUT's community. **WHO IS THIS TOOL NOT FOR?** **ACCESSIBILITY FLOOR**: OutSavvy assumes smartphone ownership and app literacy. The heavy emphasis on "Download the app" and mobile-first design shuts out people using older phones, shared devices, or basic mobile plans. The interface is image-heavy which means slow loading on poor connections - common for people in temporary housing, rural areas, or managing data costs carefully. **PRIVACY ARCHITECTURE**: This is where OutSavvy becomes dangerous for BLKOUT's community. Event discovery platforms create digital footprints - your location, event interests, social connections, and attendance patterns all become data points. For closeted people, asylum seekers, or anyone in unsafe households, having "Queer Bachata Workshop" or "Best In Queer Comedy" in your browsing history or app downloads could be life-threatening. The platform offers no obvious privacy controls or anonymous browsing options. **SYNC vs ASYNC**: The tool works asynchronously for discovery, which is good. But the social features and "personalised recommendations" suggest it's building behavioral profiles that require consistent engagement to be useful - penalizing people with variable capacity. **GEOGRAPHIC REACH**: Heavily London-centric despite claiming UK coverage. The sample events are all London-based, and the "set your preferred location" feature acknowledges this bias. For BLKOUT members in Manchester, Birmingham, Cardiff, or rural England, this becomes another London-first tool that treats them as afterthoughts. **COST TO USER**: While many events show "Pay What You Can" or "FREE", the platform itself requires smartphone ownership and data plans. The booking fees aren't visible on the main page but likely exist - a hidden cost barrier. **ISOLATION vs NETWORK**: This is complex. OutSavvy could help isolated people discover community events, which is valuable. But it assumes people are ready to be "out" enough to attend public queer events - a huge assumption. Someone taking their first tentative steps toward community might need more private, low-key entry points than "Queer House Party" listings. **PERFORMANCE DEMANDS**: The platform's aesthetic is very much about being "out and proud" - the tagline "Get In. Stand Out. Break The Norms" assumes confidence and visibility that many community members aren't ready for or can't safely perform. **Against BLKOUT's wishlist**: This doesn't map cleanly to any wishlist item. It's adjacent to "Regular events calendar" but OutSavvy is a discovery platform, not a calendar tool. It might support "Non-intrusive lead generation" but the surveillance mechanics (behavioral tracking, location data) violate the "values-consistent methodology" requirement. **The fundamental problem**: OutSavvy serves people who are already out, already networked, already confident enough to attend public queer events in major cities. It deepens the infrastructure for the over-served while creating new barriers (privacy risks, device requirements, geographic bias) for everyone else. For someone taking their first steps toward Black queer community, or someone who needs to stay closeted for safety, or someone outside London managing on a tight budget, this tool could be actively harmful rather than helpful. RECOMMENDATION: PASS

// context at time of judgement

The Wishlist, as it was then +

this is the document the council was asked to hold this tool against. click to expand.

BLKOUT Digital Strategy — Living Document

This document is the authoritative context for the Dreamcatcher Council. It combines BLKOUT's Year One guardrails with the fifteen-item wish list. The Council reads this fresh on every evaluation — edits here immediately reshape every future verdict.

Last revised April 2026. For board and community input.

Year One Guardrails

Rules that hold while foundational infrastructure is being built. Harder than tier priorities — these do not negotiate.

— No n8n. All automations use node-cron or Supabase triggers. n8n was tried and removed; the operational cost of a workflow engine outweighed the benefit for a small team.

— Schema ownership. The CRM's 001_crm_complete_schema.sql is authoritative. Any new tool that touches member data reads from CRM tables — it does not maintain a separate schema.

— Pre-order model, not always-on store. The BLKOUT shop is a waiting-list / pre-order surface with CBS tiers (free / £3 per month / £10 per month). Tools that assume always-on e-commerce are a category mismatch.

— Stripe pre-flight. Stripe routes stay disabled until credentials are confirmed in Coolify. Test mode only — no tool that requires live payment provisioning on adoption.

— CRM mock data stays until migrations verified. Nothing removes CRM mock data until the equivalent migration has been confirmed via supabase-query.mjs. Tools that auto-migrate are held until verification is possible.

— RSVP and Stripe are already built. Frontend and backend exist in the platform. Tools that duplicate these are a category mismatch — the gap is credentials and tables, not code.

— Infrastructure before application. Debug infrastructure (CPU, disk, running services, Docker images) before application code. Tools that add operational complexity must justify themselves against this order.

Wish List — fifteen capabilities

Prioritised by potential impact and capacity to instigate change. First draft March 2026, living document since.

Tiers: do now (accessible) — plan and build (moderate lift) — develop with intent (significant undertaking)

Categories: infrastructure — member experience — co-production

Tier 1 — do now

High impact, low barrier — no dependency blockers.

— AI policy, à la New Public infrastructure accessible Unlocks the integrity of everything beneath it. Determines what BLKOUT will and won't do with AI, and why. Data sovereignty and privacy follow from this document, not the other way around. Mainly a thinking and writing exercise — the hardest part is the thinking.

— CRM — values-embedded member system member experience accessible Already in active use. Develop with transparency and member control principles baked in before habits calcify around the wrong defaults. Needs connecting to member pages, AIvor, and the directory as those mature.

— Leania.ai — AI ops audit infrastructure accessible Quick diagnostic of workflows, tools and bottlenecks. Keep / kill / replace / automate recommendations. Low cost, high information value. Caveat: recommendations will skew commercial — use the diagnostic layer, not the prescription.

— Tech stability and system resilience infrastructure moderate lift Without this, everything built on the infrastructure will fail. The VPS, Coolify, and all modules need to be reliable and recoverable before more is added. Foundational before ambitious.

Tier 2 — plan and build

High impact, requires resourcing, people or sequencing.

— Bookkeeping, financial regulations and fundraising infrastructure moderate lift CBS obligation, funder pipeline active. Needs the right person as much as the right tool — the Treasurer role is load-bearing. Required before significant grant income flows through the organisation.

— Compliance infrastructure — demonstration not monitoring infrastructure moderate lift Mission risk if left too long. Evidence of governance, financial stewardship, and community benefit must be buildable in real time, not reconstructed after challenge. Systems need building before they are needed.

— Regular events calendar and Brunch 2030 member experience moderate lift Visible, reliable rhythm signals organisational health. Monthly social, film screening at The Arzner, community organisers gathering, seasonal specials, Berto Pasuka day. Key venue relationships held — Stanley Arts, The Arzner. Delegate the programming.

— Non-intrusive lead generation member experience moderate lift Community-appropriate discovery. Transparent about the win on all sides. Values-consistent methodology — games welcome if honest, surveillance mechanics excluded. The question is whether the constraint is capacity, visibility, or trust, because each has a different solution.

— Live directory of Black queer civil society co-production moderate lift Co-production and community research — built by the community, kept live by the community. Feeds CRM, AIvor, lead generation, and network mapping simultaneously. The gaps in the directory are as revealing as what is in it.

— Partner tool and project management dashboard infrastructure moderate lift Operational capacity for transparent relationships with organisations of all sizes. Sits on stable infrastructure. Enables partnerships to be held without depending on founder memory.

— Network mapping — loneliness co-production moderate lift How loneliness manifests for Black queer men — which responses are proximate, which require greater effort. Research question still needs articulating before design. Board community lead to own this. Brunch network exercise as potential methodology.

Tier 3 — develop with intent

Transformative — significant undertaking, dependencies to resolve first.

— Unique member pages — member-controlled data as feature member experience significant Members see exactly what BLKOUT holds about them, can edit or delete any of it, and are equipped to ask the same of others. Policy as education. Significant data architecture. Needs CRM foundation first. The feature that most visibly demonstrates the values.

— Next-level AIvor — orchestration on member need member experience significant From broadcaster to responder — receiving member need signals and acting on them, with care and ethical guardrails. The line between care and surveillance must be designed in from the start. Depends on knowing what members actually need. Network mapping and directory must precede.

— Co-designed member consultation with iterative learning loop co-production significant Design the consultation process in consultation. Radical transparency, shared results, member agency in decisions that follow insight. Includes autoresearch-style closed feedback cycle with co-designed metrics. Never a failure, always a lesson — at organisational scale. The most ambitious item on the list and the one that could make every other item more effective.

— Youth leadership intervention co-production significant Form and content both need co-producing — this cannot be designed for young people, only with them. Requires funding. Can begin relationship-building and scoping conversations now, against the backdrop of Black youth unemployment returning to 1981 levels.

— Enterprise and wealth — pop-up / shebeen / art model co-production significant Still forming. The relationship between enterprise, workplaces, community and intergenerational wealth remains to be discovered. An inquiry that in its form embodies potential elements of the final proposal — collaborative, cultural, accessible, profitable, sociable. Trust for London proposal as the discovery vehicle.

BLKOUT Creative Ltd — Community Benefit Society Living document — edited in situ via the Dreamcatcher editor

---Podcast hosting — added April 2026, surfaced via Commons page build

What we want: A hosted podcast platform with a brand-themeable embeddable player (we'll skin to obsidian/gold), an RSS feed for distribution to Spotify/Apple Podcasts, and basic listener analytics. Should integrate with the Commons + Critical Frequency pages without a generic Drive iframe.

Why now: We're starting to publish AI-generated audio (NotebookLM Deep Dives, future episodes from the Compass material). Drive embed is the current workaround — generic player, no podcast-app distribution, no analytics, asset lives in personal Drive.

Constraints / what we won't: Free tier or low monthly cost (BLKOUT is small); no extractive licensing on community audio; option to self-host or export RSS to migrate (no lock-in); accessible player UI; no Spotify exclusivity.

On the radar for Council review when surfaced: Castopod (open source, self-hostable on Coolify — natural fit), Transistor (paid, neutral, RSS-first), Buzzsprout, Spotify for Podcasters / Anchor (free + reach but sovereignty concerns).