project-60f26edc
Here is a master prompt you can use to generate the AI web app. It is designed around the **sales rep handover** wedge, with scoped permissions, knowledge capture, and a simple enterprise UI.[1][2][3][4] ## Master prompt You are an expert product engineer, UX architect, and full-stack AI app builder. Build a secure, multi-tenant **AI Handover Web App** for enterprises that captures the knowledge of departing employees and turns it into an interactive handover assistant for managers and replacements. ### Product goal The app helps a manager answer: “What did this person know, do, and usually handle?” It must focus on one narrow use case first: **sales rep departure handover**. The app should ingest CRM data, email metadata/content, calendar events, documents, notes, and a short exit interview, then generate a concise knowledge-transfer brief and an ask-anything interface for the manager. The app should not try to become a full AI operating system. It should be a scoped, permission-aware enterprise product, similar in spirit to how Microsoft and Google manage AI agents with admin controls, user scoping, and data-source governance.[2][3][4][5][1] ### Core users - Sales manager. - Departing employee. - New owner / replacement rep. - Org admin / security admin. ### Core workflow 1. Admin connects approved data sources. 2. Manager selects a departing employee. 3. System imports data from CRM, email, calendar, and docs. 4. App runs a guided exit interview to capture tacit knowledge. 5. App produces: - executive summary, - account-by-account handover, - deal status and risks, - recurring patterns and playbooks, - key contacts and relationships, - open questions and missing information. 6. Manager can ask natural-language questions over the handover context. 7. Access is restricted by role, scope, and permissions. ### Non-negotiable product rules - Keep the first version limited to sales handover. - Do not build CEO dashboards, org-wide priority engines, cross-department planning, or generic automation. - Do not make the app depend on a huge number of integrations. - Use permission-aware retrieval only. - Never expose data across users, teams, or organizations without explicit access controls. - Make the app auditable, explainable, and admin-governed. This matches current enterprise AI control patterns.[3][4][1][2] ### Functional requirements - Authentication with org-based tenant separation. - Role-based access control for admin, manager, employee, and viewer. - Data connector setup for CRM, email, calendar, and documents. - Employee offboarding checklist. - AI-generated handover brief. - Q&A assistant grounded in imported data. - Change log and audit trail for all generated outputs. - Manual review and edit before publishing the final handover. - Export to PDF and share internally with permissions. ### AI behavior - Summarize only from authorized sources. - Cite which source types were used in each answer. - Distinguish between facts, inferred insights, and missing data. - Ask clarifying questions when important context is absent. - Highlight deal risk, customer relationships, active commitments, and unanswered tasks. - Never hallucinate account ownership, contract status, or next steps. ### Data model Design entities for: - Organization. - User. - Role. - Employee profile. - Departure event. - CRM account. - Deal. - Contact. - Email thread. - Calendar event. - Document. - Exit interview response. - Handover brief. - Question and answer. - Audit log. ### UI requirements Create a clean enterprise dashboard with: - left sidebar navigation, - employee selector, - source status panel, - handover brief editor, - ask-anything chat panel, - risk flags, - export/share actions, - admin controls for connectors and permissions. ### Security and governance - Tenant isolation. - Source-level access controls. - User-level visibility rules. - Admin approval for connectors. - Audit logging. - Data minimization. - Ability to disable a source without breaking the app. - Clear indicator of what data the AI can and cannot use. Enterprise AI systems increasingly rely on exactly these kinds of admin-scoped source controls and agent governance.[4][5][1][2][3] ### MVP acceptance criteria - A manager can upload or sync a rep’s data. - The app generates a useful handover brief in under 2 minutes. - The manager can ask at least 10 meaningful questions and get grounded answers. - The system respects permissions. - The output is immediately useful for a replacement rep within one day. ### Output format Return: 1. Product architecture. 2. Database schema. 3. Backend API design. 4. Frontend page structure. 5. AI prompt strategy. 6. Security model. 7. MVP scope. 8. Implementation plan for the first 30 days. ### Tone and design principles - Enterprise-ready. - Simple. - Trustworthy. - Scoped. - Not flashy. - Built for real adoption, not demo theater. ### Final instruction If there are multiple reasonable design choices, choose the simplest secure option that helps ship the MVP fastest. Prioritize working software over abstract platform thinking. ## Optional shorter version Build a permission-aware enterprise web app for sales rep handover. Ingest CRM, email, calendar, docs, and exit interview notes for a departing employee. Generate a manager-facing handover brief, account summary, risk flags, and an ask-anything assistant grounded only in approved sources. Include tenant isolation, role-based access control, audit logs, admin-managed connectors, and manual review before publishing. Do not build a full AI OS; build a narrow, useful knowledge-transfer product first.[1][2][3][4] If you want, I can turn this into a **code-generation prompt for Next.js + Supabase + OpenAI** next. Sources [1] Manage Copilot agents in the Microsoft 365 admin center https://learn.microsoft.com/en-us/microsoft-365/admin/manage/manage-copilot-agents-integrated-apps?view=o365-worldwide [2] Manage agents for Microsoft 365 Copilot | Microsoft Learn https://learn.microsoft.com/en-us/microsoft-365/copilot/extensibility/manage [3] Copilot Control System Management Controls | Microsoft Learn https://learn.microsoft.com/en-us/microsoft-365/copilot/copilot-control-system/management-controls [4] Microsoft 365 Copilot agents governance visual guide https://learn.microsoft.com/en-us/copilot/microsoft-365/agent-essentials/m365-agents-visual-map [5] Introducing Workspace Intelligence, with admin controls https://workspaceupdates.googleblog.com/2026/04/introducing-workspace-intelligence-with-admin-controls.html [6] [PDF] Administering and Governing Agents - Microsoft 365 Adoption https://adoption.microsoft.com/files/copilot-studio/Agent-governance-whitepaper.pdf [7] Controlar a Inteligência do Workspace para recursos de IA ... https://knowledge.workspace.google.com/admin/generative-ai/workspace-intelligence/control-workspace-intelligence?hl=pt-br [8] Control Agents as a Microsoft 365 Admin | Copilot Control System updates https://www.youtube.com/watch?v=cQU1GTm14S8 [9] What governance, access, and action controls can we apply to a ... https://learn.microsoft.com/en-us/answers/questions/5852075/what-governance-access-and-action-controls-can-we [10] Governance 101 for Microsoft Copilot Agents https://www.youtube.com/watch?v=vygjaGHsvoE
Comments (0)
Sign in to leave a comment
System Requirements
project-60f26edc
Introduction
The purpose of this document is to outline the system requirements for "project-60f26edc," a secure, multi-tenant AI Handover Web App designed to facilitate the handover process for departing sales representatives. The application focuses on capturing and transferring knowledge to managers and replacement reps, ensuring a smooth transition and continuity in sales operations.
System Overview
The AI Handover Web App is intended to serve as an enterprise tool that captures the knowledge of departing employees and transforms it into an interactive handover assistant. The app will ingest data from various sources such as CRM systems, email, calendar events, documents, and exit interviews to generate a comprehensive knowledge-transfer brief. The application will be permission-aware, ensuring data security and privacy through role-based access control and tenant isolation.
Source Content Inventory
- Title: Manage agents in the Microsoft 365 admin center
- Descriptions:
- "Microsoft 365 Copilot combines the power of large language models with your data and apps in Microsoft 365."
- "You can enable, disable, assign, block, or remove agents for your organization, and manage Copilot capabilities."
- Agent Types Described: Published by your organization, Shared by creator, Microsoft agents, External partner agents, Frontier agents (App Builder agent, Workflows agent)
- Admin Roles: AI Admin, Global Reader
- Agent Controls: View available, deployed, or blocked agents, Configure agent availability and access, Perform actions: publishing, deploying, blocking, removing agents
Functional Requirements as Story Points
- As a Sales Manager, I should be able to upload or sync a departing sales rep’s data to the app.
- As an Admin, I should be able to connect approved data sources such as CRM, email, calendar, and documents.
- As a Manager, I should be able to select a departing employee and initiate the handover process.
- As the System, I should import data from CRM, email, calendar, and documents.
- As the App, I should run a guided exit interview to capture tacit knowledge.
- As a Manager, I should receive an AI-generated handover brief that includes an executive summary, account-by-account handover, deal status and risks, recurring patterns and playbooks, key contacts and relationships, and open questions and missing information.
- As a Manager, I should be able to ask natural-language questions over the handover context and receive grounded answers.
- As an Admin, I should be able to manage role-based access control for admin, manager, employee, and viewer roles.
- As a User, I should be able to export the handover brief to PDF and share it internally with permissions.
- As an Admin, I should be able to view a change log and audit trail for all generated outputs.
- As a Manager, I should be able to manually review and edit the handover brief before publishing.
- As the System, I should ensure that access is restricted by role, scope, and permissions.
User Personas
- Sales Manager: Responsible for overseeing the handover process and ensuring continuity in sales operations.
- Departing Employee: The individual whose knowledge and responsibilities are being transferred.
- New Owner/Replacement Rep: The person taking over the responsibilities of the departing employee.
- Org Admin/Security Admin: Responsible for managing data sources, permissions, and security settings.
Core User Flows
- Admin connects approved data sources: Admin logs in -> navigates to data source settings -> connects CRM, email, calendar, and document sources.
- Manager selects a departing employee: Manager logs in -> selects employee from list -> initiates handover process.
- System imports data: System automatically imports data from connected sources.
- App runs exit interview: App prompts departing employee with guided questions -> captures responses.
- App generates handover brief: System processes data -> generates brief -> manager reviews and edits -> exports and shares.
Visuals Colors and Theme
- primary: #1A73E8 (a deep blue for a professional and trustworthy feel)
- primary_light: #E8F0FE (a light blue for hover states and secondary UI)
- secondary: #FF7043 (a coral hue for headlines and emphasis)
- accent: #FFD700 (a vibrant gold for CTAs and active states)
- highlight: #FFA726 (a warm orange for hover states and notifications)
- bg: #F5F5F5 (a light grey for the page background)
- surface: rgba(255, 255, 255, 0.8) (a white card/panel background)
- text: #212121 (a dark grey for primary text)
- text_muted: #757575 (a softer grey for secondary text)
- border: rgba(0, 0, 0, 0.1) (a subtle border color)
Signature Design Concept
The homepage will feature an interactive "Knowledge Transfer Journey" animation. As users scroll, they will see a visual representation of data flowing from various sources (CRM, email, calendar) into a central "handover brief" hub. This hub will transform and expand, revealing key insights and summaries. Users can click on different data streams to see detailed information pop-ups. The animation will use motion/react for smooth transitions and interactions, creating an engaging and informative experience.
Landing Hero Motion Brief
The hero section will depict a dynamic flow of data icons (representing CRM, email, calendar, documents) converging into a central hub. As the hub processes the data, it will transform into a clear, concise handover brief. This animation will loop every 10 seconds, with interactive elements allowing users to pause and explore specific data streams. The composition will use a layered SVG approach with motion/react for seamless animations.
Interaction Model & Motion Direction
- Intended Interaction Model: Animated
- The landing page will feature moderate scroll-triggered reveals and hover transitions, enhancing the user experience without overwhelming them. Interactive elements will have spring physics for a polished feel.
Non-Functional Requirements
- The system must ensure tenant isolation and role-based access control.
- The application should be auditable, with a comprehensive change log and audit trail.
- The app must be explainable, with clear indicators of data usage and permissions.
Tech Stack
- Frontend: React for Web
- Backend: Python, FastAPI
- Database: MySQL or MariaDB, using Alembic for migrations
- AI Models: GPT 5.4 for user-friendly responses
- AI Tools: Litellm for LLM Routing, Langchain
- Local Orchestration: Docker, docker-compose
- Server-side Orchestration: Kubernetes
Assumptions and Constraints
- The application will initially focus solely on the sales rep handover use case.
- The app will not attempt to become a full AI operating system.
- Data integration will be limited to essential sources to maintain simplicity and security.
Glossary
- CRM: Customer Relationship Management
- AI: Artificial Intelligence
- UI: User Interface
- MVP: Minimum Viable Product
- Q&A: Question and Answer
- PDF: Portable Document Format
This document outlines the comprehensive requirements for project-60f26edc, ensuring a focused and secure implementation of the AI Handover Web App.
Never Lose a Rep's Institutional Knowledge Again
Capture departing sales reps' expertise through guided exit interviews and AI analysis, then transfer it seamlessly to their successors.
Everything You Need for Seamless Handovers
From data capture to knowledge transfer, our platform handles every step of the sales rep departure process.
Guided Exit Interviews
AI-driven questionnaires capture tacit knowledge, key relationships, and institutional wisdom from departing reps.
Multi-Source Import
Connect CRM, email, calendar, and document repositories to automatically gather context before the interview.
AI-Generated Briefs
Comprehensive handover documents with executive summaries, deal risks, and recommended actions.
Natural Language Q&A
Managers and new owners ask questions about any account, process, or relationship and get grounded answers.
Role-Based Access
Granular permissions ensure only authorized users can view, edit, or share handover materials.
Complete Audit Trail
Every change, export, and access event is logged for compliance and full organizational accountability.
Five Steps to Knowledge Continuity
A streamlined process that transforms scattered knowledge into a structured, actionable handover brief.
Connect Sources
Link CRM, email, calendar, and document repositories to the platform.
Select Employee
Choose the departing rep and initiate the handover workflow.
AI Exit Interview
Guided questions capture critical knowledge, contacts, and risks.
Review & Edit
Manager reviews the AI-generated brief and refines key sections.
Share & Transfer
Export the brief, share with the new owner, and track completion.
Ready to Protect Your Team's Knowledge?
Start capturing institutional wisdom before it walks out the door. Set up your first handover in under five minutes.
Never Lose a Rep's Institutional Knowledge Again
Capture departing sales reps' expertise through guided exit interviews and AI analysis, then transfer it seamlessly to their successors.
Everything You Need for Seamless Handovers
From data capture to knowledge transfer, our platform handles every step of the sales rep departure process.
Guided Exit Interviews
AI-driven questionnaires capture tacit knowledge, key relationships, and institutional wisdom from departing reps.
Multi-Source Import
Connect CRM, email, calendar, and document repositories to automatically gather context before the interview.
AI-Generated Briefs
Comprehensive handover documents with executive summaries, deal risks, and recommended actions.
Natural Language Q&A
Managers and new owners ask questions about any account, process, or relationship and get grounded answers.
Role-Based Access
Granular permissions ensure only authorized users can view, edit, or share handover materials.
Complete Audit Trail
Every change, export, and access event is logged for compliance and full organizational accountability.
Five Steps to Knowledge Continuity
A streamlined process that transforms scattered knowledge into a structured, actionable handover brief.
Connect Sources
Link CRM, email, calendar, and document repositories to the platform.
Select Employee
Choose the departing rep and initiate the handover workflow.
AI Exit Interview
Guided questions capture critical knowledge, contacts, and risks.
Review & Edit
Manager reviews the AI-generated brief and refines key sections.
Share & Transfer
Export the brief, share with the new owner, and track completion.
Ready to Protect Your Team's Knowledge?
Start capturing institutional wisdom before it walks out the door. Set up your first handover in under five minutes.
No comments yet. Be the first!