On July 30, 2026, Pixeldust launched Maisy, an AI-powered knowledge hub that taps into a company’s existing Microsoft 365 environment—SharePoint, Teams, emails, and files—to answer employee questions with approved internal information. The service targets small and midsized businesses drowning in scattered documents and tribal knowledge, promising to cut down on repetitive manager interruptions and speed up onboarding. But behind the promise of instant answers lies a hard truth: the AI is only as good as the messy file shares and sloppy permissions that many SMBs have ignored for years.

Turning Messy Files into a Searchable Company Brain

Maisy isn’t a standalone app you download and run. Pixeldust positions it as a managed knowledge management overhaul, built around Microsoft 365 and Copilot Studio. Employees type plain-language questions like “What’s the current customer refund policy?” or “How do we onboard a new contractor?” and Maisy responds using vetted company information, often linking back to the source document, Teams conversation, or email thread it pulled from. The goal is to transform years of scattered Word docs, PDFs, SharePoint sites, and institutional memory into a single, authoritative resource—without forcing the company to rip out its existing tools.

The under-the-hood stack is pure Microsoft: SharePoint for document storage, Teams for communication threads, Microsoft Entra ID for identity and access control, and Copilot Studio as the AI orchestration layer. Pixeldust’s team handles the heavy lifting: discovery sessions to map where knowledge actually lives, document cleanup to remove duplicates and outdated material, information architecture to structure content logically, plus configuration, testing, and employee training. Mick Southern, who leads the Maisy initiative, said in the announcement that “most small businesses do not have an information shortage. They have an organization problem.” The service is designed to solve that problem without the kind of enterprise-level overhead that usually comes with knowledge management projects.

The Permission Trap: Why Clean SharePoint Hygiene Is Non-Negotiable

Maisy’s security story rests entirely on a customer’s existing Microsoft 365 permissions. It uses Entra ID to authenticate users and surfaces only the content each person is authorized to see, following the same access boundaries already set in SharePoint and Teams. This avoids the complexity of building a separate permission system—but it also means Maisy inherits every over-permissioned folder, every “Everyone except external users” group, every forgotten link shared three years ago. If your HR folder is accidentally open to the whole company, Maisy will happily serve sensitive salary information to anyone who asks. The AI layer doesn’t fix access problems; it makes them instantly discoverable.

For IT administrators, the launch is a prompt to finally audit SharePoint permissions, review sensitivity labels, and lock down external sharing before flipping the switch on any AI search tool. The same caveat applies to content quality. If your shared drive contains five versions of the travel policy—three of them obsolete—Maisy might pull answers from the wrong one. Pixeldust’s implementation process includes document review and cleanup, but ongoing governance will be essential. Content owners must have a clear process for retiring superseded procedures and vetting answers that influence HR, finance, or customer-service decisions. Without that discipline, the knowledge hub could become a faster way to surface bad information.

Starting Small: The Phased Approach SMBs Can Actually Handle

Rather than demanding a company-wide overhaul, Maisy advocates for starting with a single, bounded problem. The press release suggests employee onboarding, HR questions, estimating procedures, customer service, or operational documentation as natural first targets. This lets an SMB prove value in one area while building the governance muscle needed for broader rollout. Pixeldust’s typical implementation steps include identifying high-value questions that employees ask repeatedly, reviewing existing documents, capturing knowledge from veteran staff, purging duplicate and stale files, organizing approved content in Microsoft 365, configuring and testing the AI assistant, and training staff on both use and content ownership. The result, the company says, isn’t just a chatbot but a maintained business knowledge system that grows more useful over time.

For organizations where IT support is lean and the knowledge base spans years of unmanaged files, this incremental path is likely the only realistic one. It also gives administrators room to experiment with Copilot Studio without committing the whole company to an untested workflow. Pixeldust hasn’t disclosed minimum Microsoft 365 licensing requirements, but Copilot Studio licenses are separate from standard M365 plans, so expect additional costs. Pricing for Maisy itself wasn’t made public in the announcement, leaving that to customer-specific discussions.

What’s Missing: Pricing, Licensing, and the Microsoft 365 Fine Print

The press release, distributed via IssueWire, left out several details that small businesses will need before signing up. No pricing tiers, no deployment timelines, and no clear list of which Microsoft 365 licenses are required. Copilot Studio, in particular, comes with its own consumption-based pricing, and grounding agents in large SharePoint libraries could drive up costs if not managed carefully. Additionally, while Maisy uses approved internal sources and provides document links for auditability, it’s unclear how the system handles conflicting information across sources—or how it distinguishes between the original version of a policy and a copy someone saved to their personal OneDrive. Pixeldust’s consulting-heavy approach likely addresses some of these gaps during implementation, but the opacity means any SMB considering Maisy must press for specifics early in the sales process.

What SMBs Should Do Now

If Maisy sounds like a fit, start by assessing the current state of your Microsoft 365 environment. Conduct a SharePoint permission audit: look for overly broad groups, stale external sharing links, and sites that haven’t been reviewed in years. Identify your most painful knowledge gaps—the questions that email your managers every week, the onboarding docs that new hires can never find, the process that only one departing employee understands. Document those pain points; they’ll form the scope of any pilot. Before engaging Pixeldust or any similar service, confirm which Microsoft 365 licenses you already hold and whether Copilot Studio licensing is already included or must be purchased separately. Finally, assign a content owner for each knowledge area you plan to surface through the AI assistant. Someone must be accountable for keeping answers current.

The Bigger Picture: AI Knowledge Hubs Are Coming, Ready or Not

Maisy’s launch reflects a broader shift. Microsoft is baking AI into every corner of M365, from Copilot in Word to agents in Teams. For SMBs, the question isn’t whether an AI knowledge hub will become available—it’s whether they’ll have the document hygiene to trust the answers. Pixeldust’s service is one of the early offerings that tries to bridge the gap between messy reality and the clean data AI demands. But it also serves as a warning: the hard work isn’t the technology. It’s the unglamorous, ongoing task of tidying up files, setting permissions, and deciding who owns the truth. Companies that start that work now, even without Maisy, will be better positioned for whatever AI tool they eventually adopt.