Maisy is a secure AI knowledge hub that helps organizations preserve institutional knowledge, reduce repeated questions, improve onboarding and give employees faster access to approved information.
We build each Maisy implementation around the organization’s people, processes, existing technology, security requirements and highest-priority knowledge problems.
Understanding Maisy
What is Maisy?
Maisy is a secure AI knowledge hub that allows authorized employees to ask questions in plain language and receive answers based on approved organizational information.
A typical Maisy implementation combines SharePoint, Microsoft Teams, Microsoft Copilot Studio, Microsoft 365 permissions and a governed collection of policies, procedures, training materials, forms and institutional knowledge.
Is Maisy just a chatbot?
No. The conversational assistant is only the visible part of Maisy.
The larger system includes knowledge discovery, employee interviews, content cleanup, SharePoint organization, permissions, governance, testing, training and ongoing maintenance. The quality of Maisy depends on the quality and authority of the information beneath it.
What problems does Maisy solve?
Maisy is designed to address problems such as:
- Employees repeatedly asking the same questions.
- Important knowledge being concentrated in a few people.
- Slow and inconsistent employee onboarding.
- Outdated, duplicated or conflicting documents.
- Employees being unable to identify the correct procedure or form.
- Managers becoming bottlenecks for routine information.
- Knowledge disappearing when employees leave or change roles.
- AI tools producing generic answers without organizational context.
Will Maisy replace employees?
No. Maisy helps employees locate and understand approved information. It does not replace leadership, professional judgment, subject-matter experts or authorized decision-makers.
Maisy may explain a procedure or identify an escalation path. It should not independently approve spending, make employment decisions, interpret legal requirements or make other high-risk decisions.
How is Maisy different from ChatGPT or another public AI tool?
Public AI tools are useful for general research, drafting and analysis, but they do not automatically understand your organization’s approved policies, procedures, history, terminology, permissions or decision rules.
Maisy is configured around selected organizational knowledge and defined user roles. Its purpose is to provide answers grounded in the way your organization actually operates.
Knowledge and Content
What kinds of information can Maisy use?
Depending on the project, Maisy may use:
- Policies and standard operating procedures.
- Forms, checklists and templates.
- Training and onboarding materials.
- Employee handbooks and role guides.
- Product and service information.
- Safety and compliance procedures.
- Customer-service guidance.
- Vendor and partner information.
- Decision records and escalation paths.
- Project lessons and troubleshooting guidance.
- Knowledge captured from experienced employees.
- Links to authoritative business systems.
Only approved, relevant and appropriately permissioned sources should be connected to Maisy.
Can Maisy capture knowledge that is not written down?
Yes. Capturing institutional or tribal knowledge is a central part of the process.
We use interviews, questionnaires, workshops, process walkthroughs, document reviews and real operational examples to capture the judgment, exceptions and practical knowledge held by experienced employees.
That information is then reviewed and approved before Maisy treats it as authoritative.
Do we have to move every file into a new system?
No. We first review where your information currently lives and determine what should remain, move, be reorganized, be archived or be excluded.
The goal is not to upload everything. The goal is to create a controlled set of reliable knowledge sources.
What if our files are disorganized or outdated?
That is normal.
Most organizations begin with duplicate documents, inconsistent naming, outdated procedures, missing ownership and knowledge scattered across SharePoint, Teams, email, shared drives and employee memory.
Content cleanup and organization are part of the implementation when included in the Statement of Work.
What does “CC Maisy” mean?
“CC Maisy” is a simple habit for submitting useful new knowledge to the organization’s approved intake process.
An important email, meeting summary, decision, procedure or lesson can be sent to a controlled location for review. It does not automatically become official knowledge. A designated owner must review, classify and approve it first.
Does Maisy learn automatically?
No. Maisy improves as approved information is deliberately added, corrected and maintained.
Unanswered questions and incorrect answers can reveal missing or outdated knowledge, but someone must review the issue and update the authoritative source.
Can Maisy provide links to its sources?
Yes, where supported by the selected Microsoft tools and configuration, Maisy can cite or link to the source used for an answer.
Source visibility helps employees verify information and identify outdated or conflicting content.
What happens when Maisy does not know the answer?
Maisy should state that the approved information is missing, unclear or conflicting rather than inventing an answer.
It can then direct the employee to the appropriate person, department or escalation process. The unanswered question can also be recorded as a knowledge gap for future correction.
Can Maisy help write documents?
Maisy or connected Microsoft Copilot tools may assist with drafts, summaries, checklists and other content.
Generated material should still be reviewed by an authorized employee and follow the organization’s normal approval process.
Microsoft 365 and Integrations
Do we need Microsoft 365?
Microsoft 365 is our preferred platform because it provides SharePoint, Teams, Entra ID, permissions, versioning and Copilot Studio within a connected environment.
We review the organization’s current technology and licensing before confirming the architecture.
We already use SharePoint. Why do we need Maisy?
SharePoint may already store your files, but storage alone does not establish which information is authoritative, current, properly secured or suitable for AI retrieval.
We help organize SharePoint around real employee questions, knowledge domains, ownership, permissions, review dates and approved sources. Maisy then provides a conversational way to retrieve that information.
Where do employees access Maisy?
Depending on the implementation, employees may access Maisy through:
- Microsoft Teams.
- SharePoint.
- Microsoft 365 Copilot.
- A secured browser interface.
- Another approved organizational channel.
The goal is to make Maisy available through tools employees already use whenever practical.
Can Maisy connect to our CRM, ERP or other business systems?
Potentially.
Integration depends on the system’s APIs, connectors, permissions, licensing, data quality, vendor restrictions and the questions Maisy needs to answer.
Some systems may support live connections. Others may use approved exports, reporting databases, Dataverse or SharePoint lists. Each integration must be assessed individually.
Does Maisy replace our existing business systems?
Usually not.
Your CRM, case-management platform, accounting system, HR system or other operational software should remain the authoritative system for its transactions and records.
Maisy can help employees understand how to use those systems, locate approved procedures and retrieve selected information when an appropriate connection exists.
Can Maisy update records or take actions?
Maisy normally begins as a read-oriented knowledge assistant.
Actions such as updating records, sending messages, creating transactions or triggering workflows require separate design, permissions, approval rules and testing. They are not automatically included in a standard Maisy implementation.
Can Maisy be added to our public website?
Yes. A public Maisy assistant can answer approved customer or visitor questions from a separate public knowledge set.
A public website assistant should never be given unrestricted access to internal SharePoint content, employee records or confidential organizational information.
Security and Permissions
Is Maisy secure?
Maisy is designed around the organization’s Microsoft 365 identity, permissions and security controls.
A secure implementation includes authenticated users, approved knowledge sources, role-based groups, content classification, permission testing and ongoing review.
Security is not automatic. Existing permissions must be reviewed because AI can make previously over-shared information easier to discover.
Will Maisy respect our SharePoint permissions?
Maisy is designed to retrieve information according to the signed-in user’s existing access and the sources connected to the agent.
We test representative users from different roles before launch. Permission-aware retrieval does not fix incorrectly configured SharePoint permissions, which is why permission review and testing are part of the implementation.
Can different departments receive different answers?
Yes.
HR, finance, managers, executives, general employees, contractors and volunteers can be assigned different access based on Microsoft 365 groups and SharePoint permissions.
Maisy should only construct an answer from information the requesting user is authorized to access.
Can sensitive information be included?
Sensitive information may be included when there is a clear business need and appropriate security controls.
Confidential or restricted knowledge should be stored separately, assigned to controlled groups and tested carefully. Highly sensitive information may be excluded from AI retrieval entirely.
Is the public version of Maisy separated from the internal version?
Yes.
Public and internal assistants should use separate knowledge sources, permissions and testing standards. Public Maisy should use only information intentionally approved for external release.
Does Maisy give Microsoft or another AI provider ownership of our information?
Your organization retains ownership of its documents, knowledge and project deliverables.
Data handling depends on the Microsoft licenses, tenant configuration and services selected for the implementation. These requirements are reviewed during assessment and documented in the Statement of Work.
The Implementation Process
How do we get started?
We begin with an initial conversation and assessment questionnaire.
We review your goals, organization size, departments, knowledge sources, Microsoft 365 environment, permissions, documentation condition, priority use cases and desired outcomes.
What happens during a Maisy project?
A typical project includes:
- Initial assessment and scope definition.
- A written quote and Statement of Work.
- Leadership and stakeholder discovery.
- Knowledge inventory and risk assessment.
- Employee interviews and knowledge capture.
- Content cleanup and SharePoint organization.
- Permission and security design.
- Maisy configuration.
- User acceptance and permission testing.
- Training, launch and ongoing governance.
The exact process depends on the approved scope.
What does our organization need to provide?
Successful projects normally require:
- An executive sponsor.
- A primary project contact.
- Access to Microsoft 365 administrators or IT support.
- Department managers and subject-matter experts.
- Representative documents and systems.
- Timely decisions about content authority and permissions.
- Employees who can participate in testing.
- Named owners who will maintain knowledge after launch.
We can build the system, but the organization must determine which business information is correct and authoritative.
Do we need to organize the entire company at once?
No.
A focused departmental pilot is often the best starting point. Common first phases include HR, employee onboarding, operations, customer service or another area with frequent questions and well-defined information.
The pilot allows the organization to test content, permissions, answer quality and adoption before expanding.
How long does implementation take?
Most focused projects take approximately one to three months.
A smaller pilot may be completed sooner. Projects involving many departments, extensive content cleanup, complex permissions or custom integrations may require several phases.
The schedule is defined in the Statement of Work.
How is Maisy tested?
Testing uses real employee questions rather than simple demonstrations.
We test common questions, incomplete requests, conflicting information, outdated documents, restricted subjects, citations and escalation behavior. Different user roles are tested to confirm that permissions work as intended.
User acceptance testing is required before launch.
What happens after launch?
Maisy becomes a maintained organizational system rather than a completed document project.
Knowledge owners review content, employees report gaps, outdated sources are corrected or archived and new approved information is added. Maisy can then expand into additional departments, use cases or controlled workflows.
Pricing, Licensing and Ownership
How much does Maisy cost?
Typical Maisy projects range from approximately $10,000 to $50,000, with a $5,000 minimum project size.
Pricing depends on:
- Organization size.
- Number of departments and locations.
- Amount and condition of the information.
- Knowledge-capture requirements.
- SharePoint and permission complexity.
- Integrations and custom development.
- Microsoft licensing.
- Training, testing and ongoing support.
Every project is assessed and quoted individually.
Why do you not offer one fixed package?
A small organization with one organized department requires far less work than a multi-location organization with years of duplicate files, undocumented procedures and complex permissions.
A fixed package would either overcharge smaller organizations or fail to cover the work required by larger ones.
How are projects billed?
Projects normally begin with a deposit, followed by monthly billing based on terms defined within the Statement of Work.
The Statement of Work identifies the scope, deliverables, schedule, responsibilities, assumptions, payment terms and acceptance criteria.
Are Microsoft licenses included?
Licensing is reviewed during assessment and listed separately in the quote.
Clients normally purchase and maintain their Microsoft and third-party licenses directly. We do not retain control of the client’s licensing after the project.
Who owns the finished system?
The client owns its content, configurations, custom code and project deliverables.
We do not lock clients into a proprietary knowledge repository or require them to continue using us after implementation.
Is training included?
Training and documentation are normally included when specified in the Statement of Work.
We train users to work with Maisy and train designated owners to maintain content, permissions and governance.
Do you provide ongoing support?
Yes.
Support can be provided through a retainer or on an a-la-carte basis. Service-level agreements may also be available for mission-critical implementations.
Can another provider support Maisy later?
Yes.
The client owns the implementation and may maintain it internally or work with another qualified Microsoft provider.
Organizational Fit and Results
What types of organizations are a good fit for Maisy?
Maisy is best suited for organizations experiencing one or more of these conditions:
- Important knowledge is concentrated in a few employees.
- Staff repeatedly ask the same operational questions.
- Documentation is spread across several locations.
- New employees take too long to become productive.
- Several departments or locations operate differently.
- Leadership transitions or employee turnover create continuity risk.
- The organization already uses Microsoft 365.
- Management wants a controlled foundation for practical AI adoption.
Which industries do you serve?
We work primarily with nonprofits, service businesses and professional organizations.
Examples include human-service nonprofits, education organizations, churches, animal-welfare organizations, HVAC companies, plumbing and electrical contractors, construction firms, legal practices, accounting firms, medical-service businesses and other organizations with significant operational knowledge.
What results should we expect?
A successful Maisy implementation may help:
- Reduce time spent searching for information.
- Reduce repeated employee questions.
- Improve employee and volunteer onboarding.
- Produce more consistent answers.
- Preserve institutional knowledge.
- Reduce dependence on individual employees.
- Improve document ownership and review.
- Identify outdated and conflicting information.
- Create a stronger foundation for future AI use.
Results depend on source quality, employee participation, leadership support and ongoing maintenance.
Do you work onsite or remotely?
We provide onsite services throughout Central and East Texas, including College Station, Houston and Austin.
Remote discovery, implementation and support are also available for organizations across the United States.
What does Maisy not do?
Maisy does not:
- Replace your CRM, accounting, HR or case-management system.
- Automatically understand every file in your organization.
- Guarantee perfect AI accuracy.
- Repair bad permissions without review.
- Replace professional judgment or authorized decisions.
- Turn unapproved notes into official policy.
- Automatically connect every business system.
- Remain reliable without content ownership and maintenance.
