# RaidGuild AI Solutions Source Summary Version: updated after the `ai.raidguild.org` copy pass and AI-specific voice guide. ## Executive Summary RaidGuild AI Solutions is the guild's forward deployed AI operations front: a team of senior builders, operators, and agent specialists who embed inside real workflows to turn messy operations, fragmented knowledge, coordination debt, and stalled AI experiments into operated AI systems. The current public positioning is sharper and more buyer-legible than the earlier draft. "Forward Deployed AI Mercenaries" remains the memorable brand hook, but the conversion path now leans on calmer operator language: AI Ops Audit, Workflow Deployment, Operating Partnership, and Embedded AI Team. The core promise: > Bring RaidGuild one priority workflow or operational bottleneck. The AI Ops team will map the opportunity, connect the right context and tools, define a practical deployment path, and help turn the workflow into a working AI-assisted system with human checkpoints. Primary CTA: `https://ai.raidguild.org/contact` Primary CTA language: - Book an AI Ops Audit. - Schedule Consultation. - Talk to the AI Ops Team. - Bring us the bottleneck. ## What RaidGuild AI Solutions Is RaidGuild AI Solutions introduces itself with a dark tactical AI-fantasy aesthetic, but the offer is practical: senior AI operators embedded into the client's workflows to design, ship, and maintain systems built for real-world use. Source-backed positioning from the current site: - AI operators for messy workflows, fragmented knowledge, and coordination debt. - Senior builders and operators embedded into client workflows. - Practical AI systems: internal copilots, workflow automation, knowledge infrastructure, and agent-assisted operations. - Agents connected to docs, comms, tools, and APIs. - Human checkpoints, evaluations, and ongoing operational support. - One painful workflow turned into a working system. Plain-language translation: RaidGuild AI helps teams choose the first workflow, map the operational bottleneck, connect the right tools and context, deploy a working AI-assisted system, and keep improving it with review, evaluation, and operator support. ## Why The Division Exists Most teams do not need another abstract conversation about AI. They need a credible path from experiments to operations. The recurring problem is not usually a lack of tools. It is that work is spread across documents, CRMs, inboxes, Discords, APIs, spreadsheets, ticket queues, and contributor memory. Requests arrive through too many channels. Handoffs are manual. Reports, onboarding, approvals, support triage, follow-up, and internal documentation repeat every week. AI experiments may exist, but they often sit outside the workflows where the organization actually runs. RaidGuild AI exists to work inside that mess. The team starts with one operational bottleneck, maps the opportunity, reviews system and data readiness, and helps build a practical deployment path. The buyer does not have to start with a grand AI transformation program. They can start with one workflow that keeps stealing time. Narrative spine for future copy: 1. Teams are already experimenting with AI. 2. The hard part is turning experiments into durable operating systems. 3. The blockers are context, workflow design, tool integration, review paths, and ownership. 4. RaidGuild AI embeds senior operators to solve those blockers where the work actually happens. ## Team Roles And Capabilities Use these four roles as the canonical capability structure. ### Agent Architects Agent Architects design agents, memory, evaluations, and tool use around the work a team already does. Buyer value: - Define what agents should do. - Identify what context agents need. - Choose the tools and APIs agents can use. - Design evaluations and human review points. - Keep agent behavior grounded in real workflows. Best-fit language: - agent design - memory and context architecture - evaluation loops - tool use - human-reviewed agent workflows ### Workflow Weavers Workflow Weavers connect documents, CRMs, inboxes, APIs, and internal systems into reliable operating loops. Buyer value: - Turn fragmented tools into repeatable workflow paths. - Identify the handoffs where operational drag accumulates. - Connect intake, routing, status, and reporting. - Make the workflow legible enough for both humans and agents. Best-fit language: - workflow mapping - workflow redesign - systems integration - tool and API integrations - operating loops - intake, routing, and status flows ### Comms Operators Comms Operators deploy communication lines across Discord, X, email, and content channels with human checkpoints. Buyer value: - Help teams route, summarize, draft, publish, and coordinate communication. - Preserve human review before meaningful external or client-facing messages. - Support community-heavy and web3-native operating environments. Best-fit language: - Discord operations - X and content workflows - email and follow-up flows - human checkpoints - communication lines - content operations ### Automation Raiders Automation Raiders ship pragmatic systems that remove drag, surface signal, and keep improving after launch. Buyer value: - Turn workflow maps and agent designs into working systems. - Build practical automation around the existing stack. - Support launch, documentation, monitoring, and iteration. Best-fit language: - practical automation - working AI-assisted systems - launch support - operational leverage - signal surfacing - ongoing iteration ## Current Service Offering The current website uses a four-step progression: 1. Audit the opportunity. 2. Deploy the first workflow. 3. Operate and improve the system. 4. Embed a durable AI team. This should be the source of truth for launch and sales communications. ### AI Ops Audit Category: Assessment. Promise: The client gets one priority workflow mapped, the highest-leverage automation opportunities identified, and a practical deployment plan. Includes: - Workflow mapping. - Opportunity sizing. - System and data readiness review. - Deployment recommendations. - Prioritized next-step roadmap. Best for: - Teams that know AI matters but need clarity on where it should create operational leverage first. - Buyers who need an executive-grade read before committing to implementation. - Organizations that want a calm first step into AI-native operations. Useful framing: > Map one priority workflow, size the opportunity, and define the first deployment plan. ### Workflow Deployment Category: Implementation. Promise: The client gets one painful workflow turned into a working AI-assisted system with the right integrations, checkpoints, and handoff. Includes: - Workflow redesign. - Agent or automation buildout. - Tool and API integrations. - Human review checkpoints. - Launch support and documentation. Best for: - Teams ready to move from recommendation to a usable internal workflow. - Buyers who want practical proof of AI leverage through one concrete workflow shipped into real use. Useful framing: > Turn one painful workflow into a working AI-assisted system with the right integrations, checkpoints, and handoff. ### Operating Partnership Category: Ongoing Operations. Promise: The client gets continued monitoring, evaluation, and optimization for AI workflows already operating inside the business. Includes: - Workflow monitoring. - Evaluation and quality checks. - KPI tracking. - Iteration planning. - Operator enablement. Best for: - Teams with live automations or agent workflows that need durable support, measurement, and improvement. - Organizations whose tools, requirements, and workflows change over time. Useful framing: > Keep live AI workflows improving as the business, tools, and requirements change. ### Embedded AI Team Category: Retainer. Promise: The client gets an embedded AI operations team on retainer to keep building, deploying, and supporting workflow systems inside the organization. Includes: - Retainer model for continued work. - Full Refactory Deployment Package. - AI readiness roadmap. - Ongoing workflow implementations. - Support, iteration, and operational enablement. Best for: - Organizations ready to move from one-off workflow fixes into an AI-native operating layer. - Teams that want a durable implementation partner for AI readiness, Refactory deployment, and ongoing operational improvements. Useful framing: > Embed a durable AI team to keep building, deploying, and supporting operational systems inside the organization. ## Older Or Supporting Package Language The Portal post and prior planning materials include additional package names that can still inform sales collateral, but should not override the current website service path unless re-approved. Supporting names: - Operational Leverage Sprint. - AI Readiness Diagnostic + Build. - Refactory Deployment Package. - Internal Copilot Deployment. - Workflow Rescue Package. Recommended use: - Use these in internal planning, sales conversations, or future collateral where helpful. - For public launch copy, default to AI Ops Audit, Workflow Deployment, Operating Partnership, and Embedded AI Team. ## Example Workflows And Buyer Pains Use concrete workflows often. They make the offer easier to understand than abstract AI language. Current site examples: - Customer intake. - Invoicing. - Reporting. - Onboarding. - Approvals. - Follow-up flows. - Sales follow-up. - Support triage. - Internal reporting. - Knowledge retrieval. - Ops handoffs. - Content workflows. Additional relevant examples: - Internal copilots connected to company knowledge. - Discord, X, email, and content operations. - Workflow documentation. - Human review checkpoints. - Context lake and knowledge infrastructure. Common buyer pains: - "We know AI could help, but we do not know where to start." - "Our context is scattered across too many tools." - "Requests arrive through too many channels." - "Manual handoffs slow down everything." - "The team keeps repeating the same reporting, onboarding, or follow-up work." - "We built AI demos, but they never became daily operations." - "Our docs, comms, tools, and APIs do not work together." - "We need automation, but we still need human review." - "We need a deployment plan we can actually act on." ## Project Proof And Working Base The current proof base is strongest when described as internal tools, field experiments, and ecosystem collaborations that shape RaidGuild's AI operating practice. Do not overstate these as external client outcomes unless approved proof is available. ### Queen Raida Queen Raida is RaidGuild's internal AI agent. Source-backed attributes: - Context lake. - Intent understanding. - Discord, X, and content operations. Use as proof that RaidGuild AI is built from internal operational need, not only theory. ### Refactory Refactory is a Codex-first community automation and agentic solutions tool built with the Superprism ecosystem. Source-backed attributes: - Codex-first workflows. - Community automation. - Agentic solution patterns. Use when describing deeper deployment, readiness, knowledge, and operational workflow patterns. ### The Portal The Portal is an agent-first presentation and collaboration surface for turning context into shared strategy, demos, and client-ready narratives. Source-backed attributes: - Agent-led presentations. - Collaborative context. - Client-ready surfaces. Use when describing communication, presentation, strategy, and narrative surfaces. ### DAOhaus Hauskeeper Raid The DAOhaus work is a supporting pattern for AI-assisted maintenance readiness and human-governed automation. It is useful proof for: - Making systems legible before automation. - Agent-ready docs and workflow maps. - Human approval gates. - Refactory-style intake, triage, context retrieval, implementation support, review, and reporting. Use sparingly in broad AI Solutions launch materials unless the draft is specifically about maintenance, Refactory, or mature protocol operations. ## Key Messages ### Message 1: AI Experiments Are Not Operations Many teams have tried AI tools. The valuable work is wiring AI into workflows that survive daily use. Sample line: > The hard part is not testing AI. The hard part is wiring it into the workflows where work actually happens. ### Message 2: Start With The Bottleneck The first step is one priority workflow, not a vague transformation program. Sample line: > Bring us the workflow that keeps stealing time. ### Message 3: Operated Capability Beats AI Theater RaidGuild AI should sound like a team that ships and supports systems, not a team that produces impressive demos. Sample line: > Every track is designed to produce usable operational assets, not strategy decks that wait for someone else to implement them. ### Message 4: Context Is The Work AI systems become useful when connected to docs, comms, tools, APIs, and the real operating loop. Sample line: > Agents are only as useful as the context, tools, and review paths around them. ### Message 5: Human Checkpoints Create Trust Human review is part of the operating model. Sample line: > The system should remove drag without removing judgment. ### Message 6: Same Guild Instincts, New Operational Frontier The AI front should stay connected to RaidGuild's builder culture without overloading the buyer with lore. Sample line: > Same guild instincts. New operational frontier. ## Voice Guidance For Future Drafts Use the AI-specific voice guide as the source of truth. Tone: - Tactical. - Senior. - Practical. - Focused. - Proof-oriented. - Lightly mythic. Default buyer-facing language: - AI operators. - Senior builders. - Forward deployed. - Messy workflows. - Fragmented knowledge. - Coordination debt. - Operated capability. - AI Ops Audit. - Workflow Deployment. - Operating Partnership. - Embedded AI Team. - Workflow mapping. - Opportunity sizing. - System and data readiness. - Deployment plan. - Working AI-assisted system. - Tool and API integrations. - Human review checkpoints. - Evaluation and quality checks. - KPI tracking. - Operator enablement. Use sparingly: - Mercenaries. - Demons. - Battlefield. - Slay. - Quest. - Raid. Rule of thumb: Use one strong mythic or tactical phrase, then translate quickly into buyer value. ## Reusable Lines Short lines: - Bring us the bottleneck. We'll trace the system. - Book an AI Ops Audit. - One painful workflow turned into a working system. - From AI ambition to operated capability. - Forward deployed AI operators for messy workflows. - Start focused, then build toward operated capability. - Audit the opportunity. Deploy the first workflow. Operate and improve the system. - Agents connected to your docs, comms, tools, and APIs. - Human checkpoints are part of the system. - Useful AI starts where the work actually gets stuck. - Same guild instincts. New operational frontier. Longer lines: - RaidGuild AI embeds senior builders and operators into your workflows to design, ship, and maintain practical AI systems built for real-world use. - The work is not framed as a software handoff or a strategy deck. It is positioned as operated capability. - AI becomes valuable when it is wired into intake, reporting, approvals, onboarding, customer follow-up, documentation, support, and the recurring loops that determine how an organization actually runs. - Start with a narrow workflow, validate the impact, then move into deeper AI-native systems for coordination, knowledge, automation, and internal operations. - Turn one painful workflow into a working AI-assisted system with the right integrations, checkpoints, and handoff. ## Claim Boundaries Avoid unless approved: - Fully autonomous agents running production operations. - Replacing human operators, maintainers, or decision-makers. - Guaranteed efficiency percentages or ROI claims. - Unsupported deployment timelines. - Unsupported "enterprise" proof. - Client outcomes that are actually internal project proof. - Any implication that clients are broken, incompetent, or behind. Preferred phrasing: - AI-assisted workflow. - Operated capability. - Human checkpoints. - Evaluation and quality checks. - Practical automation. - Embedded senior builders and operators. - Working system. - Knowledge infrastructure. - Context lake. - Agent-assisted operations. - Ongoing operational support. Avoid or use carefully: - Fully autonomous. - Magic. - Replace your team. - Instant transformation. - Hands-off AI. - Generic "AI-powered" without explaining the workflow. ## Proof Gaps To Fill The CEO/copywriter feedback correctly identifies that the current proof is still mostly internal or ecosystem-facing. Future drafts will become stronger with approved proof such as: - Hours saved. - Operational load reduced. - Deployment timelines. - Number and type of integrations. - Before/after workflow examples. - Client examples. - Stack integrations. - Screenshots or diagrams of workflow loops. - Testimonials or short operator quotes. Until that proof is available, write with conservative proof language: - Grounded in internal tools, field experiments, and collaborations. - Built for real-world use. - One priority workflow mapped. - One painful workflow turned into a working AI-assisted system. - Practical deployment plan. ## CTA And Link References Primary CTA: - Book an AI Ops Audit / schedule a consultation: `https://ai.raidguild.org/contact` Supporting links: - Website: `https://ai.raidguild.org/` - Offerings page: `https://ai.raidguild.org/offerings` - Contact page: `https://ai.raidguild.org/contact` - Portal launch post: `https://portal.raidguild.org/posts/raidguild-ai-solutions-enters-the-field` - Queen Raida: `https://github.com/raid-guild/Queen-Raida` - Refactory: `https://refactory.superprism.io/` - Portal: `https://portal.raidguild.org/` Recommended CTA language: - Book an AI Ops Audit. - Schedule Consultation. - Talk to the AI Ops Team. - Bring us the bottleneck. - Tell us what is slowing the team down. - Start the conversation. Best all-purpose CTA: > If your team has a workflow that keeps stealing time, a coordination gap no one owns, or an AI experiment that has not made it into daily operations, book an AI Ops Audit with RaidGuild AI Solutions: `https://ai.raidguild.org/contact` ## Open Questions For Follow-On Drafts - Should public launch copy use "Book an AI Ops Audit" as the dominant CTA, with "Schedule Consultation" as supporting language? - Should long-form content lead with "Forward Deployed AI Operators" and reserve "Forward Deployed AI Mercenaries" for the hook? - Are there approved metrics, client quotes, screenshots, or concrete before/after examples that can support stronger proof claims? - Should Queen Raida and Refactory be linked directly in long-form public copy? - Should any older package names remain visible in public materials, or only in sales/internal collateral?