// verdict #15 · 1 Jun 2026 · 12:25 UTC

dilloo.doitnownow.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 Dilloo, I see a grant readiness workspace that promises to organize evidence and draft applications for mission-led organizations. Let me work through the critical questions. **VENDOR LOCK-IN CONCERNS** This is a proprietary SaaS platform with no mention of data export capabilities or open-source alternatives. All organizational knowledge gets siloed into their system - policies, financial documents, strategic plans. The "email-to-Dilloo inbox" creates a particularly concerning dependency where critical funder communications flow through their infrastructure. If Dilloo disappears or changes terms, BLKOUT loses both the organized evidence AND the workflow that created it. **GUARDRAIL VIOLATIONS** Clear violation of **Schema ownership**. Dilloo maintains its own database of member/organizational data across "12 readiness areas" rather than reading from BLKOUT's authoritative CRM schema. This creates the exact data fragmentation the guardrail exists to prevent. **WISHLIST MAPPING** This doesn't map to any Tier 1 priority. The closest connection is "Bookkeeping, financial regulations and fundraising" (Tier 2), but that item specifically calls for "the right person as much as the right tool" and emphasizes the Treasurer role being load-bearing. Dilloo is a tool-first solution to what BLKOUT has identified as a people-and-process challenge. **OPERATIONAL OVERHEAD** £49/month base cost plus £7 per staff member creates ongoing financial commitment. More concerning is the operational overhead of maintaining yet another system when the Year One guardrails explicitly prioritize "Infrastructure before application" and "Tech stability and system resilience." Adding Dilloo means another service to monitor, another potential failure point, another integration to maintain. **SEQUENCING PROBLEMS** BLKOUT is in Year One infrastructure-building mode. The wishlist makes clear that foundational stability comes before application-layer tools. Dilloo assumes an organization ready to systematize grant applications - but BLKOUT hasn't even established basic compliance infrastructure yet (that's Tier 2: "Evidence of governance, financial stewardship, and community benefit must be buildable in real time"). **SURVEILLANCE MECHANICS** The AI drafting functionality raises questions about how organizational knowledge gets processed and stored. The platform ingests sensitive organizational documents, financial information, and strategic plans. No clear data sovereignty guarantees visible. This is a classic case of a compelling tool arriving at the wrong time. Dilloo might be valuable for an organization with stable infrastructure looking to systematize fundraising, but BLKOUT needs foundational resilience first. The schema violation alone disqualifies it under current guardrails. RECOMMENDATION: PASS

// 02 · ethicist

Murray

pass

values, sovereignty, community benefit.

Looking at Dilloo against BLKOUT's principles and current needs, I see both promise and significant concerns. **What Dilloo gets right:** This directly addresses "Bookkeeping, financial regulations and fundraising" from the Tier 2 wishlist — the CBS obligation and active funder pipeline. The tool's approach of organizing scattered evidence into fundable narratives could be genuinely valuable for a small organization managing compliance requirements while building toward grant applications. The "drafts, you decide" principle aligns with keeping human agency in the loop, and the proportionate expectations based on organizational size shows awareness of grassroots realities. **Where the values alignment breaks down:** **Data sovereignty concerns:** The tool requires uploading policies, accounts, plans, and forwarding emails to their system. There's no mention of data ownership, export capabilities, or what happens to BLKOUT's sensitive organizational information if the relationship ends. For a community benefit society handling member data, this is a significant sovereignty risk. **AI transparency gaps:** While they say "AI drafts from your evidence," there's no information about what AI models they use, where data is processed, or what their AI policy actually is. Given that BLKOUT's own "AI policy, à la New Public" is the top Tier 1 item, adopting a tool with opaque AI practices would be inconsistent. **Dependency risk:** This creates a single point of failure for fundraising capacity. The "person who held it all just left" problem they describe could simply transfer from a former trustee to Dilloo itself. **Mission vs. commercial incentives:** While not extractive in the surveillance sense, this is clearly a commercial tool optimized for recurring revenue. The "expert support" at £50+ per session and staff seats at £7/month could quickly become expensive for a small CBS. **Against the guardrails:** The tool doesn't violate any specific Year One guardrails, but it does create operational complexity that should be weighed against the "Infrastructure before application" principle. **Better alternatives exist:** The actual need here — organizing compliance evidence and grant applications — could be addressed through the existing CRM system plus structured document management, without introducing data sovereignty risks. The tool addresses a real need but at the cost of values alignment that BLKOUT cannot afford to compromise, especially while still building foundational infrastructure. RECOMMENDATION: PASS

// 03 · builder

Rustin

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

Looking at Dilloo through the builder's lens — this is a grant readiness workspace that turns scattered organizational evidence into funder-ready applications. Let me break down the buildability and fit. ## VIBE-CODEABILITY & STACK COMPATIBILITY This is a SaaS tool, not something we'd self-host. The integration surface is clean — email forwarding to a private address, document uploads, and what appears to be a structured workspace. No exotic infrastructure requirements since it's hosted. The DX looks reasonable for non-technical users, which matters since this would likely be used by community organizers and leadership. ## SPEED OF DEPLOYMENT & LIFT ASSESSMENT **Accessible tier.** Free 30-day trial, then £49/month. Setup appears to be: create account, upload existing documents, forward emails to their inbox system. This could be operational within days, not weeks. The learning curve seems designed for mission-led orgs that don't have dedicated grant writers. ## MAINTAINABILITY & INTEGRATION POTENTIAL Low maintenance burden since it's hosted. The integration points are straightforward — email forwarding and document management. Could connect to the **compliance infrastructure** work from Tier 2 of the wishlist. The "12 readiness areas" (Identity, Strategy, Governance, Finance, etc.) map well to CBS compliance needs. ## GUARDRAIL CHECK ✅ Passes all guardrails. Doesn't duplicate existing BLKOUT functionality, doesn't require n8n, doesn't touch the CRM schema, doesn't need Stripe integration, doesn't add operational complexity to the VPS. ## WISHLIST MAPPING This maps directly to **"Compliance infrastructure — demonstration not monitoring"** from Tier 2. The wishlist says: *"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."* Dilloo is literally designed for this — turning everyday organizational work into "fundable evidence" that demonstrates governance and stewardship. The CBS obligation and active funder pipeline make this timely. Secondary mapping to **"Bookkeeping, financial regulations and fundraising"** — this handles the fundraising readiness side while the Treasurer role handles the financial management side. ## THE BUILDER'S VERDICT This tool addresses a real operational need that BLKOUT has right now. CBS compliance requirements, active Trust for London proposal, and the general need to demonstrate community benefit all require exactly what Dilloo provides. The £49/month cost is reasonable for the capacity it would free up. The failure mode is manageable — if it doesn't work out, the organizational documents and evidence gathering work still exists and transfers elsewhere. The success mode is significant — professional grant readiness without hiring consultants at £500-£2000 per application. RECOMMENDATION: GO

// 04 · inclusion

Rivera

pass

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

Looking at Dilloo through the lens of who gets left on the street when "mission-led organisations" get their grants sorted. **WHO IS THIS TOOL NOT FOR?** The fundamental exclusion here is **organisational capacity**. Dilloo assumes you are already an organisation with trustees, audited accounts, safeguarding policies, and theories of change. It's designed for groups that have reached institutional form — registered charities, CICs, community benefit societies. But what about the Black queer mutual aid network that operates through WhatsApp and cash apps? The informal collective that meets in someone's front room? The grassroots response that emerges after police violence but hasn't incorporated because incorporation feels like a trap? Dilloo's "12 readiness areas" (Identity, Strategy, Governance, Finance, Safeguarding) are the exact institutional requirements that keep grassroots organising unfunded. **ACCESSIBILITY BARRIERS:** - **Literacy demands**: This tool requires comfort with grant language, policy documents, and organisational frameworks. The interface assumes familiarity with terms like "theory of change" and "safeguarding policy." - **Device assumptions**: Requires sustained computer access for document management, not phone-friendly for people managing everything mobile. - **Administrative capacity**: Assumes someone has time to "bring what you already have" and organize it systematically. **GEOGRAPHIC AND CULTURAL REACH:** The opportunity board shows "Greater London Foundation" and "London boroughs" — this is London-centric infrastructure that reinforces existing funding geography. Smaller cities and rural areas get less funder attention, and this tool won't change that dynamic. **THE DEEPER PROBLEM:** Dilloo optimizes for the funding system as it exists rather than challenging who that system serves. It makes grant applications more efficient for groups that already have the capacity to write them. But the groups most in need — the informal networks, the mutual aid collectives, the kitchen table organizations — remain locked out of the institutional funding that Dilloo helps access. The £49/month cost (after free trial) puts it out of reach for truly grassroots groups operating on cash donations and volunteer labor. **DOES IT WIDEN REACH?** Not meaningfully. It serves mission-led organisations that are "under-organised" rather than under-resourced. The problem it solves — scattered evidence across former trustees' laptops — is a middle-class organisational problem. Groups that never had trustees' laptops remain unserved. **BLKOUT CONTEXT:** For BLKOUT specifically, this could be useful infrastructure once you're at the scale of multiple grant applications. But it doesn't address the wishlist priorities around member experience, co-production, or reaching isolated community members. It's an efficiency tool for institutional capacity you're still building. Against the guardrails: it's not schema-breaking or technically problematic, but it doesn't map to current wishlist priorities. The "Bookkeeping, financial regulations and fundraising" item mentions needing "the right person as much as the right tool" — Dilloo is a tool that assumes you already have the right person. This tool serves the over-served: organizations with enough capacity to have documents scattered across laptops rather than organizations with no laptops at all. 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).