├── Docs ├── Operations │ └── Hiring │ │ ├── Job-Openings │ │ └── Senior-Marketing-Analyst │ │ │ ├── Candidates │ │ │ ├── Example-Candidate-C-Weak │ │ │ │ ├── CV.md │ │ │ │ ├── Fathom-Screening-Interview.md │ │ │ │ ├── Final-Score.md │ │ │ │ ├── AI-Notes.md │ │ │ │ ├── Evaluation.md │ │ │ │ ├── Fathom-Technical-Interview.md │ │ │ │ └── Screening-Evaluation.md │ │ │ ├── Template │ │ │ │ ├── CV.md │ │ │ │ ├── Fathom-Screening-Interview.md │ │ │ │ ├── AI-Notes.md │ │ │ │ ├── Fathom-Technical-Interview.md │ │ │ │ ├── Final-Score.md │ │ │ │ ├── Evaluation.md │ │ │ │ └── Screening-Evaluation.md │ │ │ ├── Example-Candidate-B-Average │ │ │ │ ├── Evaluation.md │ │ │ │ ├── AI-Notes.md │ │ │ │ ├── Final-Score.md │ │ │ │ ├── CV.md │ │ │ │ └── README.md │ │ │ ├── Example-Candidate-A-Strong │ │ │ │ ├── AI-Notes.md │ │ │ │ ├── Fathom-Screening-Interview.md │ │ │ │ ├── Final-Score.md │ │ │ │ ├── Screening-Evaluation.md │ │ │ │ └── CV.md │ │ │ └── README.md │ │ │ ├── Full Evaluation Agent │ │ │ ├── agent-config.json │ │ │ ├── run-agent.sh │ │ │ ├── agent-prompt.md │ │ │ └── README.md │ │ │ ├── Scoring-Rules.md │ │ │ ├── Position-Description.md │ │ │ ├── Screening-Agent │ │ │ ├── run-agent.sh │ │ │ ├── agent-config.json │ │ │ ├── agent-prompt.md │ │ │ └── README.md │ │ │ ├── Candidate-Pipeline.md │ │ │ └── Role-Competency-Matrix.md │ │ ├── Global-Rules │ │ ├── Scoring-Framework.md │ │ ├── General-Hiring-Policy.md │ │ └── Interview-Guidelines.md │ │ └── README.md ├── SePersonalCRM │ └── MainCRM │ │ ├── Contacts │ │ ├── Contact-C │ │ │ ├── Contact-C-emails.md │ │ │ └── Contact-C.md │ │ ├── Contact-A │ │ │ └── Contact-A-telegram.md │ │ ├── Contact-G │ │ │ └── Contact-G-linkedin.md │ │ ├── Contact-E │ │ │ ├── Contact-E-linkedin.md │ │ │ └── Contact-E.md │ │ ├── Contact-D │ │ │ ├── Contact-D-emails.md │ │ │ └── Contact-D.md │ │ └── Contact-B │ │ │ ├── Contact-B-emails.md │ │ │ └── Contact-B.md │ │ └── Inbox │ │ ├── telegram ai inbox.md │ │ ├── logs │ │ ├── 2025-11-11-batch10-inbox-to-processing-log.md │ │ └── README.md │ │ └── processing_tasks.md ├── SalesAndMarketing │ ├── Client-Meetings-Analysis │ │ ├── README.md │ │ ├── AI-Review-Update-Process.md │ │ └── AI-Projects-Review-Analysis_2025-07-28.md │ ├── Sales Calls │ │ └── XS Discovery Call v01 │ │ │ ├── Short Version for Slack.md │ │ │ └── Notion Extended Version.md │ ├── Media activities │ │ └── core-product-announcements.md │ └── User comprehension testing research │ │ └── README.md └── Strategy │ ├── Business-Model │ └── Price-Calculator-Template-Guide.md │ ├── Team │ └── team-overview.md │ ├── Company-Overview │ └── company-info.md │ └── Investor-Updates │ └── example-quarterly-update-template.md ├── scripts ├── sales-meeting-automation │ ├── requirements.txt │ ├── .env │ ├── env-example │ ├── prompt_internal.txt │ └── README.md ├── README.md ├── notion-integration │ └── README.md ├── check_range.py └── CURSOR_RULES.md ├── Projects ├── Status-Projects │ ├── .gitignore │ ├── README.md │ ├── Client-Beauty2-Status-Card.md │ ├── Client-Beauty1-Status-Card.md │ ├── Client-Food-Status-Card.md │ └── Client-EdTech-Status-Card.md └── Transcripts │ └── README.md ├── AI-First-Workspace-Template.code-workspace ├── .gitignore ├── .gitignore.template ├── Dev ├── DevRepo1 │ └── README.md ├── DevRepo3 │ └── README.md └── DevRepo2 │ └── README.md ├── Sales Calls └── XS Discovery Call Demo │ ├── Short Version for Slack.md │ └── Notion Extended Version.md ├── setup ├── update-all.sh ├── README.md └── update-all.ps1 └── DEMO-QUICK-START.md /Docs/Operations/Hiring/Job-Openings/Senior-Marketing-Analyst/Candidates/Example-Candidate-C-Weak/CV.md: -------------------------------------------------------------------------------- 1 | -------------------------------------------------------------------------------- /scripts/sales-meeting-automation/requirements.txt: -------------------------------------------------------------------------------- 1 | requests>=2.31.0 2 | openai>=1.0.0 3 | python-dotenv>=1.0.0 4 | -------------------------------------------------------------------------------- /Docs/Operations/Hiring/Job-Openings/Senior-Marketing-Analyst/Candidates/Example-Candidate-C-Weak/Fathom-Screening-Interview.md: -------------------------------------------------------------------------------- 1 | -------------------------------------------------------------------------------- /Projects/Status-Projects/.gitignore: -------------------------------------------------------------------------------- 1 | # Ignore mapping files for demo security 2 | Client-Mapping.md 3 | *mapping* 4 | *Mapping* -------------------------------------------------------------------------------- /Docs/Operations/Hiring/Job-Openings/Senior-Marketing-Analyst/Candidates/Template/CV.md: -------------------------------------------------------------------------------- 1 | # Candidate CV 2 | 3 | [CV content will be placed here] -------------------------------------------------------------------------------- /Docs/SePersonalCRM/MainCRM/Contacts/Contact-C/Contact-C-emails.md: -------------------------------------------------------------------------------- 1 | # Contact C 2 | 3 | ## Email history with contact.c@example.com 4 | 5 | 6 | -------------------------------------------------------------------------------- /Docs/Operations/Hiring/Job-Openings/Senior-Marketing-Analyst/Candidates/Template/Fathom-Screening-Interview.md: -------------------------------------------------------------------------------- 1 | # Candidate Screening Interview 2 | 3 | Date: [Date] 4 | Duration: [Duration] 5 | VIEW RECORDING: [Recording Link] 6 | 7 | ## Interview Summary 8 | 9 | [Interview content will be placed here] -------------------------------------------------------------------------------- /Docs/SePersonalCRM/MainCRM/Contacts/Contact-A/Contact-A-telegram.md: -------------------------------------------------------------------------------- 1 | # Contact A 2 | 3 | ## Telegram history with Contact A (Company Beta, Company Alpha, Community Alpha '22) (handle: @contact_a) 4 | 5 | 6 | ## Update from 2025-10-27T22:56:40.585032 7 | ### Messages after 2025-10-27T21:47:53.076180 8 | 9 | 10 | -------------------------------------------------------------------------------- /Projects/Status-Projects/README.md: -------------------------------------------------------------------------------- 1 | # Project Status (Working Documents) 2 | 3 | - Store current project status cards used in demos here. 4 | - After each demo, manually rollback the card to template. 5 | - Mandatory anonymization: names → segments, numbers → depersonalized, don't publish negative statuses. 6 | 7 | Rollback: 8 | 1) Save demo artifacts (copy if needed) 9 | 2) Replace card content with template 10 | -------------------------------------------------------------------------------- /AI-First-Workspace-Template.code-workspace: -------------------------------------------------------------------------------- 1 | { 2 | "folders": [ 3 | { 4 | "path": "." 5 | } 6 | ], 7 | "settings": { 8 | "files.exclude": { 9 | "**/node_modules": true, 10 | "**/.git": true, 11 | "**/.DS_Store": true 12 | } 13 | }, 14 | "extensions": { 15 | "recommendations": [ 16 | "ms-vscode.vscode-typescript-next", 17 | "ms-python.python", 18 | "ms-toolsai.jupyter", 19 | "GitHub.copilot", 20 | "GitHub.copilot-chat" 21 | ] 22 | } 23 | } -------------------------------------------------------------------------------- /Docs/Operations/Hiring/Job-Openings/Senior-Marketing-Analyst/Candidates/Example-Candidate-C-Weak/Final-Score.md: -------------------------------------------------------------------------------- 1 | # Final Candidate Score 2 | 3 | ## Technical Competency: [Score 1-10] 4 | [Justification for score] 5 | 6 | ## Experience Relevance: [Score 1-10] 7 | [Justification for score] 8 | 9 | ## Cultural Fit: [Score 1-10] 10 | [Justification for score] 11 | 12 | ## Communication Skills: [Score 1-10] 13 | [Justification for score] 14 | 15 | ## Overall Score: [Average of above scores] 16 | -------------------------------------------------------------------------------- /Docs/Operations/Hiring/Job-Openings/Senior-Marketing-Analyst/Candidates/Template/AI-Notes.md: -------------------------------------------------------------------------------- 1 | # AI Analysis Notes 2 | 3 | ## CV Analysis 4 | [AI analysis of candidate CV] 5 | 6 | ## Interview Analysis 7 | [AI analysis of screening interview] 8 | 9 | ## Technical Skills Assessment 10 | [AI assessment of technical skills] 11 | 12 | ## Cultural Fit Assessment 13 | [AI assessment of cultural fit] 14 | 15 | ## Recommended Questions for Follow-up 16 | [List of recommended questions for next interview stage] -------------------------------------------------------------------------------- /Docs/Operations/Hiring/Job-Openings/Senior-Marketing-Analyst/Candidates/Example-Candidate-C-Weak/AI-Notes.md: -------------------------------------------------------------------------------- 1 | # AI Analysis Notes 2 | 3 | ## CV Analysis 4 | [AI analysis of candidate CV] 5 | 6 | ## Interview Analysis 7 | [AI analysis of screening interview] 8 | 9 | ## Technical Skills Assessment 10 | [AI assessment of technical skills] 11 | 12 | ## Cultural Fit Assessment 13 | [AI assessment of cultural fit] 14 | 15 | ## Recommended Questions for Follow-up 16 | [List of recommended questions for next interview stage] 17 | -------------------------------------------------------------------------------- /scripts/sales-meeting-automation/.env: -------------------------------------------------------------------------------- 1 | # Fireflies.ai API Configuration 2 | FIREFLIES_API_TOKEN=your_fireflies_token_here 3 | 4 | # OpenAI API Configuration 5 | OPENAI_API_KEY=your_openai_key_here 6 | 7 | # Optional: Notion Integration (for advanced features) 8 | NOTION_API_KEY=your_notion_token_here 9 | NOTION_DATABASE_ID=your_notion_database_id_here 10 | 11 | # Optional: Telegram Notifications (for advanced features) 12 | TELEGRAM_BOT_TOKEN=your_telegram_bot_token_here 13 | TELEGRAM_CHAT_ID=your_telegram_chat_id_here 14 | -------------------------------------------------------------------------------- /scripts/sales-meeting-automation/env-example: -------------------------------------------------------------------------------- 1 | # Fireflies.ai API Configuration 2 | FIREFLIES_API_TOKEN=your_fireflies_token_here 3 | 4 | # OpenAI API Configuration 5 | OPENAI_API_KEY=your_openai_key_here 6 | 7 | # Optional: Notion Integration (for advanced features) 8 | NOTION_API_KEY=your_notion_token_here 9 | NOTION_DATABASE_ID=your_notion_database_id_here 10 | 11 | # Optional: Telegram Notifications (for advanced features) 12 | TELEGRAM_BOT_TOKEN=your_telegram_bot_token_here 13 | TELEGRAM_CHAT_ID=your_telegram_chat_id_here 14 | -------------------------------------------------------------------------------- /Docs/SePersonalCRM/MainCRM/Inbox/telegram ai inbox.md: -------------------------------------------------------------------------------- 1 | # AI Inbox - Telegram Messages 2 | 3 | **Last sync**: 2025-11-11 (Batch 10 processed) 4 | 5 | --- 6 | 7 | **All messages processed and archived as of November 11, 2025 - Batch 10** 8 | 9 | All inbox messages successfully processed. 10 | 11 | **Latest batch:** 1 voice message archived - Contact A meeting (transcribed via OpenAI Whisper) 12 | 13 | See [archive](./telegram%20ai%20inbox%20archive.md) and [Stage 1 log](./logs/2025-11-11-batch10-inbox-to-processing-log.md) for details. 14 | 15 | Next sync will add new messages here. 16 | 17 | --- 18 | 19 | 20 | -------------------------------------------------------------------------------- /Docs/Operations/Hiring/Job-Openings/Senior-Marketing-Analyst/Candidates/Template/Fathom-Technical-Interview.md: -------------------------------------------------------------------------------- 1 | # Technical Interview 2 | 3 | Date: [Date] 4 | Duration: [Duration] 5 | VIEW RECORDING: [Recording Link] 6 | 7 | ## Technical Assessment 8 | 9 | ### SQL Skills 10 | [Assessment of SQL skills] 11 | 12 | ### Power BI Skills 13 | [Assessment of Power BI skills] 14 | 15 | ### API Experience 16 | [Assessment of API experience] 17 | 18 | ### Additional Technical Skills 19 | [Assessment of other relevant technical skills] 20 | 21 | ## Overall Technical Evaluation 22 | [Summary of technical capabilities and fit for the role] -------------------------------------------------------------------------------- /.gitignore: -------------------------------------------------------------------------------- 1 | # AI First Workspace Template - Repository .gitignore 2 | # This file is for the template repository itself, not for end users 3 | 4 | # macOS system files 5 | .DS_Store 6 | .DS_Store? 7 | ._* 8 | .Spotlight-V100 9 | .Trashes 10 | ehthumbs.db 11 | Thumbs.db 12 | 13 | # Editor files 14 | .vscode/ 15 | .cursor/ 16 | *.swp 17 | *.swo 18 | *~ 19 | 20 | # Logs 21 | *.log 22 | npm-debug.log* 23 | yarn-debug.log* 24 | yarn-error.log* 25 | 26 | # Personal development folders (if any) 27 | Personal/ 28 | .personal/ 29 | 30 | # Temporary files 31 | *.tmp 32 | *.temp 33 | .cache/ 34 | 35 | # Node modules (if any) 36 | node_modules/ -------------------------------------------------------------------------------- /Docs/Operations/Hiring/Job-Openings/Senior-Marketing-Analyst/Candidates/Template/Final-Score.md: -------------------------------------------------------------------------------- 1 | # Final Candidate Score 2 | 3 | ## Technical Competency: [Score 1-10] 4 | [Justification for score] 5 | 6 | ## Experience Relevance: [Score 1-10] 7 | [Justification for score] 8 | 9 | ## Cultural Fit: [Score 1-10] 10 | [Justification for score] 11 | 12 | ## Communication Skills: [Score 1-10] 13 | [Justification for score] 14 | 15 | ## Overall Score: [Average of above scores] 16 | 17 | ## Final Decision 18 | - [ ] Extend Offer 19 | - [ ] Keep in Talent Pool 20 | - [ ] Reject 21 | 22 | ## Decision Maker 23 | [Name and title of decision maker] 24 | 25 | ## Date of Decision 26 | [Date] -------------------------------------------------------------------------------- /Docs/Operations/Hiring/Job-Openings/Senior-Marketing-Analyst/Candidates/Template/Evaluation.md: -------------------------------------------------------------------------------- 1 | # Comprehensive Evaluation 2 | 3 | ## Technical Skills 4 | - SQL: [Score 1-10] 5 | - Power BI: [Score 1-10] 6 | - API Experience: [Score 1-10] 7 | - Data Processing: [Score 1-10] 8 | - Technical Communication: [Score 1-10] 9 | 10 | ## Soft Skills 11 | - Communication: [Score 1-10] 12 | - Problem-solving: [Score 1-10] 13 | - Client Interaction: [Score 1-10] 14 | - Adaptability: [Score 1-10] 15 | - Team Fit: [Score 1-10] 16 | 17 | ## Overall Assessment 18 | [Comprehensive assessment of the candidate] 19 | 20 | ## Hiring Recommendation 21 | - [ ] Strong Hire 22 | - [ ] Hire 23 | - [ ] Consider Hiring 24 | - [ ] Do Not Hire -------------------------------------------------------------------------------- /Docs/Operations/Hiring/Job-Openings/Senior-Marketing-Analyst/Candidates/Example-Candidate-C-Weak/Evaluation.md: -------------------------------------------------------------------------------- 1 | # Comprehensive Evaluation 2 | 3 | ## Technical Skills 4 | - SQL: [Score/10] 5 | - Power BI: [Score/10] 6 | - API Integration: [Score/10] 7 | - Data Processing: [Score/10] 8 | - Technical Communication: [Score/10] 9 | 10 | ## Soft Skills 11 | - Communication: [Score/10] 12 | - Problem-solving: [Score/10] 13 | - Client Interaction: [Score/10] 14 | - Adaptability: [Score/10] 15 | - Team Fit: [Score/10] 16 | 17 | ## Overall Assessment 18 | [Overall assessment of candidate fit for the role] 19 | 20 | ## Hiring Recommendation 21 | - [ ] Strong Hire 22 | - [ ] Hire 23 | - [ ] Consider Hiring 24 | - [ ] Do Not Hire 25 | 26 | [Justification for recommendation] 27 | -------------------------------------------------------------------------------- /.gitignore.template: -------------------------------------------------------------------------------- 1 | # AI First Workspace Template - Git Ignore Configuration 2 | 3 | # Ignore all department repositories in Docs/ (they are separate git repos) 4 | Docs/** 5 | 6 | # Ignore all technical repositories in Dev/ (they are separate git repos) 7 | Dev/** 8 | 9 | # Ignore Projects repository and any sub-project repos it contains 10 | Projects/** 11 | 12 | # Ignore presales repository (it's a separate git repo) 13 | Presales/** 14 | 15 | # Ignore personal folders 16 | Personal/** 17 | 18 | # Track workspace configuration only: 19 | # - .cursorrules (shared context) 20 | # - README.md (documentation) 21 | # - setup/ (scripts and configuration) 22 | 23 | # Standard ignores 24 | .DS_Store 25 | .vscode/ 26 | .cursor/ 27 | *.log 28 | *.tmp 29 | 30 | # Backup files 31 | *-backup/ 32 | *-old/ -------------------------------------------------------------------------------- /Docs/Operations/Hiring/Job-Openings/Senior-Marketing-Analyst/Candidates/Example-Candidate-C-Weak/Fathom-Technical-Interview.md: -------------------------------------------------------------------------------- 1 | # Technical Interview 2 | 3 | [This file will contain the transcript or notes from the technical interview with the candidate] 4 | 5 | ## SQL Assessment 6 | [Notes on candidate's SQL skills demonstration] 7 | 8 | ## Data Modeling Assessment 9 | [Notes on candidate's data modeling knowledge] 10 | 11 | ## Power BI/Visualization Assessment 12 | [Notes on candidate's visualization skills] 13 | 14 | ## API/Integration Knowledge 15 | [Notes on candidate's API and integration knowledge] 16 | 17 | ## Technical Communication 18 | [Assessment of how well the candidate explains technical concepts] 19 | 20 | ## Overall Technical Assessment 21 | [Summary of technical strengths and weaknesses] 22 | -------------------------------------------------------------------------------- /Dev/DevRepo1/README.md: -------------------------------------------------------------------------------- 1 | # Development Repository 1 2 | 3 | This is a placeholder for your first development repository. 4 | 5 | ## Setup Instructions 6 | 7 | 1. Clone or initialize your development repository here 8 | 2. Set up your preferred development environment 9 | 3. Configure CI/CD workflows as needed 10 | 11 | ## Common File Types 12 | 13 | - Source code files 14 | - Configuration files (.gitignore, .editorconfig, etc.) 15 | - Build and deployment scripts 16 | - Documentation 17 | - Tests 18 | 19 | ## Integration with Cursor AI 20 | 21 | - Place your `.cursor/` directory with project-specific AI rules here 22 | - Configure `.cursorrules` for project-specific context 23 | - Use workspace-level rules from the main `.cursorrules` file 24 | 25 | --- 26 | 27 | *This is part of the Shared Cursor Workspace Template. Replace this content with your actual development repository.* -------------------------------------------------------------------------------- /Dev/DevRepo3/README.md: -------------------------------------------------------------------------------- 1 | # Development Repository 3 2 | 3 | This is a placeholder for your third development repository. 4 | 5 | ## Setup Instructions 6 | 7 | 1. Clone or initialize your development repository here 8 | 2. Set up your preferred development environment 9 | 3. Configure CI/CD workflows as needed 10 | 11 | ## Common File Types 12 | 13 | - Source code files 14 | - Configuration files (.gitignore, .editorconfig, etc.) 15 | - Build and deployment scripts 16 | - Documentation 17 | - Tests 18 | 19 | ## Integration with Cursor AI 20 | 21 | - Place your `.cursor/` directory with project-specific AI rules here 22 | - Configure `.cursorrules` for project-specific context 23 | - Use workspace-level rules from the main `.cursorrules` file 24 | 25 | --- 26 | 27 | *This is part of the Shared Cursor Workspace Template. Replace this content with your actual development repository.* -------------------------------------------------------------------------------- /Dev/DevRepo2/README.md: -------------------------------------------------------------------------------- 1 | # Development Repository 2 2 | 3 | This is a placeholder for your second development repository. 4 | 5 | ## Setup Instructions 6 | 7 | 1. Clone or initialize your development repository here 8 | 2. Set up your preferred development environment 9 | 3. Configure CI/CD workflows as needed 10 | 11 | ## Common File Types 12 | 13 | - Source code files 14 | - Configuration files (.gitignore, .editorconfig, etc.) 15 | - Build and deployment scripts 16 | - Documentation 17 | - Tests 18 | 19 | ## Integration with Cursor AI 20 | 21 | - Place your `.cursor/` directory with project-specific AI rules here 22 | - Configure `.cursorrules` for project-specific context 23 | - Use workspace-level rules from the main `.cursorrules` file 24 | 25 | --- 26 | 27 | *This is part of the Shared Cursor Workspace Template. Replace this content with your actual development repository.* -------------------------------------------------------------------------------- /Docs/Operations/Hiring/Job-Openings/Senior-Marketing-Analyst/Candidates/Example-Candidate-B-Average/Evaluation.md: -------------------------------------------------------------------------------- 1 | # Candidate Evaluation: Candidate-Test-User 2 | 3 | ## Summary 4 | Candidate evaluation completed on 2025-06-11. 5 | Based on the available materials, this candidate is classified as a **Weak Fit**. 6 | 7 | ## Competency Scores 8 | 9 | | Competency | Score | 10 | |------------|-------| 11 | | SQL Proficiency | 2/5 | 12 | | ETL Experience | 3/5 | 13 | | API Integration | 2/5 | 14 | | Data Visualization | 3/5 | 15 | | Statistical Analysis | 4/5 | 16 | | Marketing Campaign Analysis | 3/5 | 17 | | Problem Solving | 4/5 | 18 | | Communication Skills | 3/5 | 19 | | Teamwork | 5/5 | 20 | 21 | ## Final Fit Conclusion 22 | **Weak Fit** 23 | 24 | ## Notes 25 | Low scores in: SQL Proficiency, API Integration 26 | WARNING: Insufficient critical skills in SQL Proficiency, API Integration 27 | -------------------------------------------------------------------------------- /Docs/SePersonalCRM/MainCRM/Contacts/Contact-G/Contact-G-linkedin.md: -------------------------------------------------------------------------------- 1 | # Contact G 2 | 3 | ## LinkedIn Messages with Contact G 4 | 5 | [CANONICAL: LinkedIn messages October 22, 2025] 6 | 7 | --- 8 | 9 | ## October 22, 2025 10 | 11 | **Contact G** [Time not specified] 12 | 13 | Hi! 14 | Was great meeting you! May I ask for the photographs from the event? 15 | 16 | thank you! 17 | Contact G 18 | 19 | **Person B** 4:05 PM 20 | 21 | Hi Contact G! Me too, it was a pleasure. 22 | Sure, here is the link 23 | [ANONYMIZED_DRIVE_LINK] 24 | 25 | **Contact G** 9:50 PM 26 | 27 | Thank you- it seems to link to one photo:) is there a folder? 28 | 29 | **Person B** 10:16 PM 30 | 31 | Oh 32 | 33 | Here is the correct link: [ANONYMIZED_DRIVE_LINK] 34 | 35 | **Person B** 10:19 PM 36 | 37 | BTW I'd love to grab a coffee sometime. Curious about AI usecases within a company you mentioned 38 | 39 | --- 40 | 41 | **Last Updated**: October 22, 2025 42 | 43 | 44 | -------------------------------------------------------------------------------- /Docs/Operations/Hiring/Job-Openings/Senior-Marketing-Analyst/Candidates/Example-Candidate-A-Strong/AI-Notes.md: -------------------------------------------------------------------------------- 1 | # AI-Generated Notes: Candidate-John-Doe 2 | 3 | ## Evaluation Summary 4 | This candidate was evaluated using the competency matrix and scoring rules for the Senior Marketing Analyst position. 5 | 6 | ## Competency Details 7 | | SQL Proficiency | 4/5 | 8 | | ETL Experience | 4/5 | 9 | | API Integration | 1/5 | 10 | | Data Visualization | 3/5 | 11 | | Statistical Analysis | 3/5 | 12 | | Marketing Campaign Analysis | 5/5 | 13 | | Problem Solving | 2/5 | 14 | | Communication Skills | 5/5 | 15 | | Teamwork | 2/5 | 16 | 17 | ## Overall Assessment 18 | The candidate is assessed as a **Weak Fit** for the role. 19 | 20 | ## Notes and Concerns 21 | Low scores in: API Integration, Problem Solving, Teamwork 22 | WARNING: Insufficient critical skills in API Integration 23 | 24 | *This evaluation was automatically generated by the Elly Analytics Recruiter Assistant.* 25 | -------------------------------------------------------------------------------- /Docs/Operations/Hiring/Job-Openings/Senior-Marketing-Analyst/Candidates/Example-Candidate-B-Average/AI-Notes.md: -------------------------------------------------------------------------------- 1 | # AI-Generated Notes: Candidate-Test-User 2 | 3 | ## Evaluation Summary 4 | This candidate was evaluated using the competency matrix and scoring rules for the Senior Marketing Analyst position. 5 | 6 | ## Competency Details 7 | | SQL Proficiency | 2/5 | 8 | | ETL Experience | 3/5 | 9 | | API Integration | 2/5 | 10 | | Data Visualization | 3/5 | 11 | | Statistical Analysis | 4/5 | 12 | | Marketing Campaign Analysis | 3/5 | 13 | | Problem Solving | 4/5 | 14 | | Communication Skills | 3/5 | 15 | | Teamwork | 5/5 | 16 | 17 | ## Overall Assessment 18 | The candidate is assessed as a **Weak Fit** for the role. 19 | 20 | ## Notes and Concerns 21 | Low scores in: SQL Proficiency, API Integration 22 | WARNING: Insufficient critical skills in SQL Proficiency, API Integration 23 | 24 | *This evaluation was automatically generated by the Elly Analytics Recruiter Assistant.* 25 | -------------------------------------------------------------------------------- /Docs/SalesAndMarketing/Client-Meetings-Analysis/README.md: -------------------------------------------------------------------------------- 1 | # 📊 Client Meeting Analysis (Working Documents) 2 | 3 | ## 📁 Folder Structure: 4 | 5 | ### 🤖 AI Analysis for Marketing: 6 | - `AI-Projects-Review-Analysis.md` - **MAIN DOCUMENT** for testimonial collection 7 | - Updated weekly based on project statuses 8 | - Identifies projects ready for case studies and testimonials 9 | - Contains marketing recommendations and action items 10 | 11 | ### 📞 Meeting Transcripts: 12 | - Processed meeting transcripts (anonymized) 13 | - Used for demonstration analysis in webinars 14 | - Source for updating AI analysis 15 | 16 | ## 🎯 Marketing Workflow: 17 | 18 | 1. **Weekly**: AI updates `AI-Projects-Review-Analysis.md` 19 | 2. **Marketing Team**: Uses document for testimonial collection planning 20 | 3. **Result**: Case studies, video testimonials, success stories 21 | 22 | ## 🔄 Updates: 23 | - **Automatically**: Every Sunday through AI analysis of project statuses 24 | - **Manually**: When receiving new testimonials or status changes 25 | -------------------------------------------------------------------------------- /Docs/Operations/Hiring/Job-Openings/Senior-Marketing-Analyst/Full Evaluation Agent/agent-config.json: -------------------------------------------------------------------------------- 1 | { 2 | "name": "FULL EVALUATION AGENT", 3 | "version": "1.0.0", 4 | "description": "AI agent that evaluates candidates for the Senior Marketing Analyst role", 5 | "contextFiles": { 6 | "agentPrompt": "agent-prompt.md", 7 | "scoringRules": "../Scoring-Rules.md", 8 | "competencyMatrix": "../Role-Competency-Matrix.md", 9 | "positionDescription": "../Position-Description.md" 10 | }, 11 | "candidateEvaluationSettings": { 12 | "criticalCompetencies": ["SQL Proficiency", "ETL Experience", "API Integration"], 13 | "fitThresholds": { 14 | "strongFit": { 15 | "criticalCompetencyMinimum": 4, 16 | "averageScoreMinimum": 3.5 17 | }, 18 | "potentialFit": { 19 | "criticalCompetencyMinimum": 3, 20 | "averageScoreMinimum": 3.0 21 | } 22 | }, 23 | "outputFiles": { 24 | "evaluation": "Evaluation.md", 25 | "aiNotes": "AI-Notes.md", 26 | "fathomSummary": "Fathom-Summary.md" 27 | } 28 | }, 29 | "processingOptions": { 30 | "useAIAssistance": true, 31 | "autoGenerateFathomSummary": true, 32 | "requireHumanApproval": true 33 | } 34 | } -------------------------------------------------------------------------------- /Docs/Operations/Hiring/Global-Rules/Scoring-Framework.md: -------------------------------------------------------------------------------- 1 | # Scoring Framework 2 | 3 | *This is a template example. Adjust scoring criteria based on your company's role requirements and evaluation standards.* 4 | 5 | ## Evaluation Scale: 6 | 7 | - **5 — Expert Level**: Candidate demonstrates deep knowledge and consistent practical experience, capable of teaching others 8 | - **4 — Strong Level**: Candidate confidently possesses required skills, capable of independently solving tasks 9 | - **3 — Meets Expectations**: Basic required competency level for task execution 10 | - **2 — Partially Meets**: Limited experience, requires additional training or support 11 | - **1 — Weak**: Practically no relevant experience or skills in this competency 12 | 13 | ## General Evaluation Rules: 14 | 15 | - Each competency is evaluated separately 16 | - Evaluation based on all available sources: CV, Interview Transcripts, AI Notes, Evaluations 17 | - When data is insufficient, competency marked as "Insufficient Data" 18 | - Overall final fit calculated according to individual Scoring Rules for each specific position 19 | - Evaluation has expert-analytical nature: must consider both direct competency confirmations and context (e.g., task complexity, company size, independence level) 20 | 21 | --- 22 | 23 | *Template Note: Customize scoring criteria and weights based on your specific role requirements, company standards, and industry benchmarks.* 24 | 25 | -------------------------------------------------------------------------------- /Docs/Operations/Hiring/Job-Openings/Senior-Marketing-Analyst/Scoring-Rules.md: -------------------------------------------------------------------------------- 1 | # Scoring Rules — Senior Marketing Analytics (Data Engineering Profile) 2 | 3 | ## Competency Thresholds: 4 | 5 | - SQL Expert: minimum 5 (critical skill) 6 | - ETL & Data Pipelines: minimum 4 (critical skill) 7 | - API Integration: minimum 4 (critical skill) 8 | - Data Modeling: minimum 4 9 | - Marketing Analytics: minimum 3 10 | - Web Analytics Tools: minimum 3 11 | - Ad Platforms: minimum 3 12 | - Client Communication: minimum 4 13 | - Documentation: minimum 3 14 | - English Language: minimum 4 15 | - Russian Language: required (native level) 16 | - Salary Expectations: must be within approved budget range 17 | 18 | ## Salary Rule: 19 | 20 | - For this role, the acceptable salary range is: $2500 — $4000 gross per month.** 21 | - If candidate salary expectations are above the maximum budget — mark as "Salary Misalignment" and flag for human review. 22 | 23 | ## Overall Scoring Logic: 24 | 25 | - **Strong Fit:** 80% or more of competencies meet or exceed threshold AND all critical skills (SQL, ETL, API) at required level AND salary within budget. 26 | - **Potential Fit:** 60–80% meet threshold, minor non-critical gaps, salary acceptable. 27 | - **Weak Fit:** Less than 60% meet threshold, OR any critical skill below threshold, OR salary outside budget. 28 | 29 | ## Notes: 30 | 31 | - Russian Language remains a hard requirement. 32 | - Insufficient data → mark clearly. 33 | - Always explain any red flags. 34 | -------------------------------------------------------------------------------- /scripts/README.md: -------------------------------------------------------------------------------- 1 | # 🔧 Utility Scripts 2 | 3 | Useful scripts for automating checks and calculations. 4 | 5 | ## 📊 check_range.py 6 | 7 | Checks if numbers fall within specified ranges. Useful for health test analysis, financial metrics, and other numerical data. 8 | 9 | ### Usage: 10 | 11 | ```bash 12 | python3 scripts/check_range.py [value] [min] [max] [value] [min] [max] ... 13 | ``` 14 | 15 | ### Examples: 16 | 17 | **Blood tests:** 18 | 19 | ```bash 20 | # Cholesterol (normal 120-200), Sugar (normal 70-100), Blood pressure (normal 80-120) 21 | python3 scripts/check_range.py 185 120 200 92 70 100 85 80 120 22 | ``` 23 | 24 | **Budget categories:** 25 | 26 | ```bash 27 | # Food expenses (budget 500-700), Entertainment (budget 200-300) 28 | python3 scripts/check_range.py 650 500 700 250 200 300 29 | ``` 30 | 31 | **Result:** 32 | 33 | ``` 34 | 🔍 Range Check: 35 | ================================================== 36 | 185.0 | [ 120.0 - 200.0] | ✅ In range 37 | 92.0 | [ 70.0 - 100.0] | ✅ In range 38 | 85.0 | [ 80.0 - 120.0] | ✅ In range 39 | ================================================== 40 | ``` 41 | 42 | ### Why is this needed? 43 | 44 | LLMs often make mistakes when comparing numbers. This script provides precise mathematical results that can be used in analysis. 45 | 46 | ## Ideas for other scripts: 47 | 48 | * `calculate_bmi.py` - body mass index calculation 49 | * `currency_convert.py` - currency conversion 50 | * `compound_interest.py` - compound interest calculation 51 | * `health_metrics.py` - healthy range calculations by age 52 | -------------------------------------------------------------------------------- /Sales Calls/XS Discovery Call Demo/Short Version for Slack.md: -------------------------------------------------------------------------------- 1 | # Automated Sales Meeting Analysis 2 | **Client:** XS Discovery Call 3 | **Version:** Demo 4 | **Generated:** 2025-08-18 11:55:41 5 | **Workspace:** AI-First-Workspace 6 | **Meeting ID:** 01K1ZF3FGSY686JHZV0QSFG57K 7 | **Template:** prompt_internal 8 | **Meeting URL:** https://app.fireflies.ai/view/Elly-Analytics-XS-discovery-call::01K1ZF3FGSY686JHZV0QSFG57K 9 | 10 | --- 11 | 12 | 13 | 🎯 **Meeting Purpose** 14 | - Discovery call with XS Corp 15 | - Initial exploration of marketing analytics needs 16 | 17 | 👥 **Client Overview** 18 | - XS Corp - B2C SaaS company 19 | - Subscription-based business model 20 | 21 | 💻 **Current Tech Stack** 22 | - Google Ads and Facebook campaigns 23 | - $50K monthly ad spend 24 | - Attribution challenges with customer journey tracking 25 | 26 | 🔥 **Pain Points** 27 | - Cannot see full customer journey from click to revenue 28 | - Attribution gaps between ad platforms and actual conversions 29 | - Manual reporting processes taking significant time 30 | 31 | 📝 **Key Discussion Points** 32 | - Strong product-market fit but scaling challenges 33 | - Need for unified analytics across all touchpoints 34 | - Interest in automated reporting solutions 35 | 36 | 🎯 **Next Steps** 37 | - Schedule demo call for next week 38 | - Prepare custom ROI calculator 39 | - Send case studies from similar B2C SaaS clients 40 | 41 | 42 | --- 43 | 44 | *This analysis was generated automatically using the Sales Meeting Processing system.* 45 | *Session: `XS Discovery Call Demo`* 46 | *File: `Short Version for Slack.md`* 47 | -------------------------------------------------------------------------------- /Docs/SalesAndMarketing/Sales Calls/XS Discovery Call v01/Short Version for Slack.md: -------------------------------------------------------------------------------- 1 | # Automated Sales Meeting Analysis 2 | **Client:** XS Discovery Call 3 | **Version:** Demo 4 | **Generated:** 2025-08-18 09:54:39 5 | **Workspace:** Personal-Super-Agent 6 | **Meeting ID:** 01K1ZF3FGSY686JHZV0QSFG57K 7 | **Template:** prompt_internal 8 | **Meeting URL:** https://app.fireflies.ai/view/Elly-Analytics-XS-discovery-call::01K1ZF3FGSY686JHZV0QSFG57K 9 | 10 | --- 11 | 12 | 13 | 🎯 **Meeting Purpose** 14 | - Discovery call with XS Corp 15 | - Initial exploration of marketing analytics needs 16 | 17 | 👥 **Client Overview** 18 | - XS Corp - B2C SaaS company 19 | - Subscription-based business model 20 | 21 | 💻 **Current Tech Stack** 22 | - Google Ads and Facebook campaigns 23 | - $50K monthly ad spend 24 | - Attribution challenges with customer journey tracking 25 | 26 | 🔥 **Pain Points** 27 | - Cannot see full customer journey from click to revenue 28 | - Attribution gaps between ad platforms and actual conversions 29 | - Manual reporting processes taking significant time 30 | 31 | 📝 **Key Discussion Points** 32 | - Strong product-market fit but scaling challenges 33 | - Need for unified analytics across all touchpoints 34 | - Interest in automated reporting solutions 35 | 36 | 🎯 **Next Steps** 37 | - Schedule demo call for next week 38 | - Prepare custom ROI calculator 39 | - Send case studies from similar B2C SaaS clients 40 | 41 | 42 | --- 43 | 44 | *This analysis was generated automatically using the Sales Meeting Processing system.* 45 | *Session: `XS Discovery Call Demo`* 46 | *File: `Short Version for Slack.md`* 47 | -------------------------------------------------------------------------------- /Docs/Operations/Hiring/Job-Openings/Senior-Marketing-Analyst/Position-Description.md: -------------------------------------------------------------------------------- 1 | # Senior Marketing Analytics — Position Description 2 | 3 | Elly Analytics is hiring for the role of Senior Marketing Analyst. 4 | 5 | ## Summary 6 | 7 | As a marketing analyst, you will become part of the team that launches analytics projects from A to Z — from project planning and MVP building to sustainment and further development. 8 | 9 | The role focuses on ensuring data quality, designing report architecture, and delivering actionable insights to clients. 10 | 11 | ## Responsibilities 12 | 13 | - Analyze customer business processes and data sources to determine reporting needs. 14 | - Create technical specifications for customization of external systems. 15 | - Design data import processes, combine data from multiple systems, and calculate client metrics. 16 | - Visualize data using Power BI (or similar tools) to build insightful dashboards. 17 | - Maintain project documentation and keep it updated. 18 | - Continuously improve and develop the product. 19 | - Communicate directly with external clients throughout the project lifecycle. 20 | 21 | > **Note:** This role does not include ML, AI or neural network development. 22 | 23 | ## Requirements 24 | 25 | - Proficiency in SQL. 26 | - Experience in data visualization using Power BI or similar systems. 27 | - Knowledge of marketing analytics, web analytics (Google Analytics UA, GA4, GTM), and advertising platforms (Google Ads, Facebook/Instagram, etc). 28 | - Experience with API 29 | - Previous experience working with external clients. 30 | - Upper-intermediate or advanced level of English. 31 | - Native level of Russian. 32 | -------------------------------------------------------------------------------- /Docs/Operations/Hiring/Job-Openings/Senior-Marketing-Analyst/Candidates/README.md: -------------------------------------------------------------------------------- 1 | # Candidate File Structure 2 | 3 | Each candidate folder should follow this structure: 4 | 5 | ``` 6 | Candidate-[Name]/ 7 | ├── CV.md # Candidate's resume/CV 8 | ├── Fathom-Screening-Interview.md # Notes from initial screening interview 9 | ├── Fathom-Technical-Interview.md # Notes from technical interview 10 | ├── AI-Notes.md # AI-generated analysis and insights 11 | ├── Screening-Evaluation.md # Evaluation from screening stage 12 | ├── Evaluation.md # Comprehensive evaluation 13 | └── Final-Score.md # Final scoring and decision 14 | ``` 15 | 16 | ## Creating a New Candidate Folder 17 | 18 | To create a new candidate folder with the correct structure: 19 | 20 | 1. Copy the Template folder 21 | 2. Rename it to `Candidate-[Name]` (e.g., `Candidate-Jane-Smith`) 22 | 3. Fill in the relevant information in each file 23 | 24 | ## File Descriptions 25 | 26 | - **CV.md**: Contains the candidate's resume information 27 | - **Fathom-Screening-Interview.md**: Summary and notes from the initial screening interview 28 | - **Fathom-Technical-Interview.md**: Detailed notes from the technical assessment interview 29 | - **AI-Notes.md**: Automated analysis of the candidate's materials 30 | - **Screening-Evaluation.md**: Evaluation form completed after the screening interview 31 | - **Evaluation.md**: Comprehensive evaluation form with detailed scoring 32 | - **Final-Score.md**: Final decision document with overall scores and hiring recommendation 33 | 34 | ## Template Usage 35 | 36 | The Template folder contains blank versions of all required files with the correct structure. Use these as a starting point for each new candidate. -------------------------------------------------------------------------------- /Docs/Operations/Hiring/Job-Openings/Senior-Marketing-Analyst/Full Evaluation Agent/run-agent.sh: -------------------------------------------------------------------------------- 1 | #!/bin/bash 2 | # Script to run the FULL EVALUATION AGENT 3 | 4 | # Set the script to exit on error 5 | set -e 6 | 7 | # Define colors for output 8 | GREEN='\033[0;32m' 9 | BLUE='\033[0;34m' 10 | YELLOW='\033[1;33m' 11 | RED='\033[0;31m' 12 | NC='\033[0m' # No Color 13 | 14 | # Print banner 15 | echo -e "${BLUE}================================================${NC}" 16 | echo -e "${BLUE} FULL EVALUATION AGENT${NC}" 17 | echo -e "${BLUE}================================================${NC}" 18 | 19 | # Check if Python is installed 20 | if ! command -v python3 &> /dev/null; then 21 | echo -e "${RED}Error: Python 3 is not installed.${NC}" 22 | echo "Please install Python 3 to use this agent." 23 | exit 1 24 | fi 25 | 26 | # Check for dependencies 27 | echo -e "${YELLOW}Checking dependencies...${NC}" 28 | python3 -c "import markdown" 2>/dev/null || { 29 | echo -e "${YELLOW}Installing required packages...${NC}" 30 | pip install markdown 31 | } 32 | 33 | # Get directory of the script 34 | DIR="$( cd "$( dirname "${BASH_SOURCE[0]}" )" && pwd )" 35 | 36 | # Change to the agent directory 37 | cd "$DIR" 38 | 39 | # Parse command line arguments 40 | CANDIDATE="" 41 | while [[ "$#" -gt 0 ]]; do 42 | case $1 in 43 | -c|--candidate) CANDIDATE="$2"; shift ;; 44 | *) echo "Unknown parameter: $1"; exit 1 ;; 45 | esac 46 | shift 47 | done 48 | 49 | # Run the agent 50 | echo -e "${YELLOW}Running agent...${NC}" 51 | if [ -z "$CANDIDATE" ]; then 52 | # Evaluate all candidates 53 | python3 agent.py 54 | else 55 | # Evaluate specific candidate 56 | python3 agent.py --candidate "$CANDIDATE" 57 | fi 58 | 59 | echo -e "${GREEN}Agent run completed!${NC}" -------------------------------------------------------------------------------- /Docs/Operations/Hiring/Job-Openings/Senior-Marketing-Analyst/Screening-Agent/run-agent.sh: -------------------------------------------------------------------------------- 1 | #!/bin/bash 2 | # Script to run the [COMPANY_NAME] Screening Agent 3 | 4 | # Set the script to exit on error 5 | set -e 6 | 7 | # Define colors for output 8 | GREEN='\033[0;32m' 9 | BLUE='\033[0;34m' 10 | YELLOW='\033[1;33m' 11 | RED='\033[0;31m' 12 | NC='\033[0m' # No Color 13 | 14 | # Print banner 15 | echo -e "${BLUE}================================================${NC}" 16 | echo -e "${BLUE} [COMPANY_NAME] Screening Agent${NC}" 17 | echo -e "${BLUE}================================================${NC}" 18 | 19 | # Check if Python is installed 20 | if ! command -v python3 &> /dev/null; then 21 | echo -e "${RED}Error: Python 3 is not installed.${NC}" 22 | echo "Please install Python 3 to use this agent." 23 | exit 1 24 | fi 25 | 26 | # Check for dependencies 27 | echo -e "${YELLOW}Checking dependencies...${NC}" 28 | python3 -c "import markdown" 2>/dev/null || { 29 | echo -e "${YELLOW}Installing required packages...${NC}" 30 | pip install markdown 31 | } 32 | 33 | # Get directory of the script 34 | DIR="$( cd "$( dirname "${BASH_SOURCE[0]}" )" && pwd )" 35 | 36 | # Change to the agent directory 37 | cd "$DIR" 38 | 39 | # Parse command line arguments 40 | CANDIDATE="" 41 | while [[ "$#" -gt 0 ]]; do 42 | case $1 in 43 | -c|--candidate) CANDIDATE="$2"; shift ;; 44 | *) echo "Unknown parameter: $1"; exit 1 ;; 45 | esac 46 | shift 47 | done 48 | 49 | # Run the agent 50 | echo -e "${YELLOW}Running agent...${NC}" 51 | if [ -z "$CANDIDATE" ]; then 52 | # Evaluate all candidates 53 | python3 agent.py 54 | else 55 | # Evaluate specific candidate 56 | python3 agent.py --candidate "$CANDIDATE" 57 | fi 58 | 59 | echo -e "${GREEN}Screening completed!${NC}" -------------------------------------------------------------------------------- /Docs/Operations/Hiring/Job-Openings/Senior-Marketing-Analyst/Candidate-Pipeline.md: -------------------------------------------------------------------------------- 1 | # Candidate Pipeline — Senior Marketing Analyst 2 | 3 | This document defines the full hiring process stages and AI evaluation triggers for the Senior Marketing Analyst position. 4 | 5 | --- 6 | 7 | ## 📊 Full Process Stages 8 | 9 | | Stage | Description | 10 | |-------|-------------| 11 | | 1️⃣ New Application | Candidate applied or sourced (from Huntflow or manual entry) | 12 | | 2️⃣ Screening Interview Scheduled | Screening interview appointment created | 13 | | 3️⃣ Screening Interview Completed | Screening interview conducted, transcript available | 14 | | 4️⃣ Screening Evaluation Done | Screening Agent completed initial evaluation | 15 | | 5️⃣ Technical Interview Scheduled | Technical interview appointment created | 16 | | 6️⃣ Technical Interview Completed | Technical interview conducted, transcript available | 17 | | 7️⃣ Full Evaluation Done | Full Evaluation Agent completed final evaluation | 18 | | 8️⃣ Hiring Decision Pending | Human committee reviewing AI evaluation | 19 | | 9️⃣ Offer Extended | Offer sent to candidate | 20 | | 🔟 Offer Accepted / Rejected | Final hiring outcome | 21 | 22 | --- 23 | 24 | ## 🔄 Huntflow Status Mapping 25 | 26 | | Huntflow Status | Elly AI Pipeline Stage | 27 | |------------------|------------------------| 28 | | New | New Application | 29 | | Screening | Screening Interview Scheduled | 30 | | Screening Done | Screening Evaluation Done | 31 | | Technical Interview | Technical Interview Scheduled | 32 | | Technical Done | Full Evaluation Done | 33 | | Decision | Hiring Decision Pending | 34 | | Offer | Offer Extended | 35 | | Hired | Offer Accepted | 36 | | Rejected | Offer Rejected | 37 | 38 | --- 39 | 40 | ## 🤖 AI Agent Trigger Points 41 | 42 | | Stage | AI Agent Action | 43 | |-------|-------------------| 44 | | After Screening Interview Completed | Run Screening Agent | 45 | | After Technical Interview Completed | Run Full Evaluation Agent | 46 | | After Full Evaluation Done | Save Final Score | 47 | -------------------------------------------------------------------------------- /Docs/Operations/Hiring/Job-Openings/Senior-Marketing-Analyst/Screening-Agent/agent-config.json: -------------------------------------------------------------------------------- 1 | { 2 | "name": "[COMPANY_NAME] Screening Agent", 3 | "version": "1.0.0", 4 | "description": "AI agent that performs initial screening of candidates for the Senior Marketing Analyst role", 5 | "contextFiles": { 6 | "agentPrompt": "agent-prompt.md", 7 | "generalHiringPolicy": "../../Global-Rules/General-Hiring-Policy.md", 8 | "scoringFramework": "../../Global-Rules/Scoring-Framework.md", 9 | "interviewGuidelines": "../../Global-Rules/Interview-Guidelines.md", 10 | "positionDescription": "../Position-Description.md", 11 | "competencyMatrix": "../Role-Competency-Matrix.md" 12 | }, 13 | "candidateEvaluationSettings": { 14 | "criticalCompetencies": ["SQL Proficiency", "ETL Experience", "API Integration", "Role Expectation Alignment"], 15 | "fitThresholds": { 16 | "strongFit": { 17 | "criticalCompetencyMinimum": 4, 18 | "averageScoreMinimum": 3.5 19 | }, 20 | "potentialFit": { 21 | "criticalCompetencyMinimum": 3, 22 | "averageScoreMinimum": 3.0 23 | } 24 | }, 25 | "outputFiles": { 26 | "screening": "Screening-Evaluation.md", 27 | "aiNotes": "AI-Notes.md" 28 | } 29 | }, 30 | "processingOptions": { 31 | "useAIAssistance": true, 32 | "requireHumanApproval": true 33 | }, 34 | "expectationAssessment": { 35 | "enableRoleAlignmentCheck": true, 36 | "roleExpectationFactors": [ 37 | "Technical vs. Business Task Balance", 38 | "Strategic Decision-Making Involvement", 39 | "Career Trajectory Analysis", 40 | "Stated Motivations and Interests" 41 | ], 42 | "redFlags": [ 43 | "Preference for strategic over technical work", 44 | "Desire to influence product development", 45 | "Career history showing progression away from technical roles", 46 | "Stated interest in business decision-making", 47 | "Emphasis on creating features or growing products" 48 | ] 49 | } 50 | } -------------------------------------------------------------------------------- /scripts/notion-integration/README.md: -------------------------------------------------------------------------------- 1 | # Notion API Integration 2 | 3 | **Purpose**: Fetch content from Notion pages and databases for use in Elly Analytics documentation and processes. 4 | 5 | ## 🚀 **Setup Instructions** 6 | 7 | ### 1. **Get Notion API Token** 8 | 1. Go to [Notion Integrations](https://www.notion.so/my-integrations) 9 | 2. Click "New integration" 10 | 3. Name it "Elly Analytics Integration" 11 | 4. Select the workspace where your pages are located 12 | 5. Copy the "Internal Integration Token" 13 | 14 | ### 2. **Set Environment Variable** 15 | ```bash 16 | export NOTION_TOKEN='your_integration_token_here' 17 | ``` 18 | 19 | ### 3. **Install Dependencies** 20 | ```bash 21 | pip install requests 22 | ``` 23 | 24 | ## 📖 **Usage** 25 | 26 | ### **Fetch Page Content** 27 | ```bash 28 | python notion-fetch.py "https://ellyanalytics.notion.site/VP-level-performance-marketing-consultant-public-speaker-1cf9786215cf808f8f8aee0f52f3cbc5?pvs=74" 29 | ``` 30 | 31 | ### **Save to Specific File** 32 | ```bash 33 | python notion-fetch.py "notion_url" "output_file.md" 34 | ``` 35 | 36 | ## 🔧 **Features** 37 | 38 | - **Page Content Extraction**: Fetches full page content from Notion 39 | - **Block Processing**: Handles different Notion block types (headings, lists, code, etc.) 40 | - **Markdown Output**: Converts Notion content to markdown format 41 | - **Metadata Preservation**: Includes source URL and fetch timestamp 42 | 43 | ## 📋 **Supported Block Types** 44 | 45 | - Paragraphs 46 | - Headings (H1, H2, H3) 47 | - Bulleted lists 48 | - Numbered lists 49 | - Quotes 50 | - Code blocks 51 | 52 | ## 🎯 **Use Cases** 53 | 54 | 1. **Job Descriptions**: Fetch updated job descriptions from Notion 55 | 2. **Documentation**: Sync documentation between Notion and local files 56 | 3. **Content Management**: Keep local documentation in sync with Notion 57 | 4. **Process Documentation**: Extract process documentation for local use 58 | 59 | ## 🔗 **Related Files** 60 | 61 | - `notion-fetch.py` - Main script for fetching Notion content 62 | - `README.md` - This setup guide 63 | 64 | --- 65 | 66 | *Last Updated: July 24, 2025* -------------------------------------------------------------------------------- /Projects/Transcripts/README.md: -------------------------------------------------------------------------------- 1 | # 📞 Team Meeting Transcripts 2 | 3 | ## 📁 Folder Contents 4 | 5 | ### 🗓️ **Meeting Timeline**: 6 | - `Meeting-2025-07-07-Team-Status-Review.md` - First meeting (initial statuses) 7 | - `Meeting-2025-07-21-Team-Status-Review.md` - Updates after 2 weeks 8 | - `Meeting-2025-07-28-Team-Status-Review.md` - Week later (final checks) 9 | - `Meeting-2025-11-08-Team-Status-Review.md` - 3+ months later (project completions) 10 | 11 | ## 🎯 **Transcript Purpose** 12 | 13 | ### **For Demo**: 14 | - Show project evolution from initial statuses to completion 15 | - Demonstrate how AI analyzes meetings and updates statuses 16 | - Training material for card update workflow 17 | 18 | ### **For Analysis**: 19 | - Track project progress over time 20 | - Identify success and problem patterns 21 | - Source for updating project status cards 22 | 23 | ## 🔄 **Usage Workflow** 24 | 25 | 1. **AI reads transcript** of latest meeting 26 | 2. **Analyzes mentions** of each project 27 | 3. **Updates cards** in `Status-Projects/` 28 | 4. **Creates marketing analysis** of testimonial collection readiness 29 | 30 | ## 📊 **Project Evolution** 31 | 32 | ### **Client-Beauty2**: 33 | `Active development` → `Final review` → `Task completion` → `✅ COMPLETED` 34 | 35 | ### **Client-Beauty1**: 36 | `On hold (migration)` → `Waiting` → `Waiting` → `✅ STABILIZED` 37 | 38 | ### **Client-EdTech**: 39 | `Launch stage` → `OnPremises deployment` → `Close to completion` → `✅ LAUNCHED` 40 | 41 | ### **Client-Food**: 42 | `Active` → `Stable development` → `Expansion plans` → `✅ STABLE OPERATION` 43 | 44 | ### **Client-Logistics**: 45 | `🔴 Critical` → `🔴 No changes` → `🔴 No changes` → `🟡 Progress` 46 | 47 | ## 🚀 **Demo Commands** 48 | 49 | Use the `DEMO-QUICK-START.md` file in workspace root for ready commands: 50 | 51 | ``` 52 | Take the latest team call transcript with the most recent date and update project status cards 53 | ``` 54 | 55 | ``` 56 | Create a file with statuses of which projects are ready for implementation completion -> our marketing needs to understand which projects can collect testimonials for the website and G2 57 | ``` 58 | 59 | --- 60 | 61 | **All transcripts are anonymized**: real client names replaced with Client-[Industry] 62 | -------------------------------------------------------------------------------- /Docs/SalesAndMarketing/Media activities/core-product-announcements.md: -------------------------------------------------------------------------------- 1 | # Elly Analytics — Core Product Description (EN, for announcements) 2 | 3 | ## Short Bio (for announcements) 4 | Seva Ustinov — CEO & Co‑Founder of Elly Analytics, end-to-end marketing analytics platform with full-funnel attribution. Creator of the first AI vibe-marketing tool for performance teams that automates 90% of routine performance marketing work. 5 | 6 | ## Short Positioning 7 | Elly Analytics is end-to-end marketing analytics that unifies all data sources, surfaces root causes behind revenue changes, and enables data-driven decisions. 30+ clients globally make daily decisions based on real enterprise-level cross-channel data. 8 | 9 | ## What Elly does today 10 | - Full-funnel attribution: every touchpoint connected to final revenue; ROAS/CAC/LTV by channels, campaigns, and creatives. 11 | - Single source of truth for customer journey: from first click to repeat purchases — one picture of reality for decisions. 12 | - Offline conversion streaming back to Google/Meta/TikTok etc. to train algorithms on real purchases and qualified leads; ad efficiency increases by 10%+. 13 | - Universal integrations and fast onboarding: connect CRM, analytics, and backend without "rip-and-replace." 14 | 15 | ## Who it's for 16 | - Companies with lead generation and lead qualification (complex funnels, multiple sources, LTV and long cohorts). 17 | - Performance marketing leaders and CMOs who need causes and actions, not "another report." 18 | - Growth teams where test velocity and hypothesis quality matter. 19 | 20 | ## Short Announcement (EN) 21 | Elly Analytics — end-to-end analytics platform that provides real answers for decisions: why sales changed, where money is leaking, what will drive growth tomorrow. Single source of truth, fast integrations, multi-touch attribution, LTV, and offline conversion streaming back to platforms. Message us — we'll show it on your data. 22 | 23 | ## Short Bridge to AI Direction 24 | This is our solid foundation. Next, the team is moving toward a "vibe-marketing" platform: stop looking at dashboards — get answers; launch automations — from recommendations to semi-automated ad management. Goal — automate up to 90% of marketer tasks and increase test velocity and quality. Seva will share details at the end. 25 | -------------------------------------------------------------------------------- /Docs/Strategy/Business-Model/Price-Calculator-Template-Guide.md: -------------------------------------------------------------------------------- 1 | # Price Calculator Template - Implementation Guide 2 | *[TEMPLATE EXAMPLE - Structure for feature-based pricing calculator]* 3 | 4 | ## Overview 5 | This guide demonstrates how to build a comprehensive feature-based pricing calculator for complex B2B SaaS products. Use this framework to create transparent, value-based pricing tools. 6 | 7 | ## Calculator Structure Template 8 | 9 | ### Sample Table Format: 10 | | Feature Category | Item | Monthly Price | Selected | Total | 11 | |------------------|------|---------------|----------|-------| 12 | | **Core Platform** | | | | | 13 | | Data Streaming | [Platform 1] | $120 | ✓ | $120 | 14 | | Data Streaming | [Platform 2] | $120 | ✓ | $120 | 15 | | **Analytics** | | | | | 16 | | Reports | Pre-built Dashboard | $360 | ✓ | $360 | 17 | | Reports | Advanced Analytics | $600 | ✓ | $600 | 18 | | **Enterprise** | | | | | 19 | | Infrastructure | Dedicated Server | $240 | ☐ | $0 | 20 | | Support | Premium Support | $350 | ☐ | $0 | 21 | | | **Total Monthly** | | | **$1,200** | 22 | 23 | ## Key Components 24 | 25 | ### 1. Feature Categories 26 | - **Core Features**: Essential product capabilities 27 | - **Data Connectors**: Integrations and data sources 28 | - **Reports & Dashboards**: Analytics and visualization 29 | - **Advanced Features**: Complex business logic 30 | - **Enterprise Add-ons**: Premium services 31 | 32 | ### 2. Pricing Logic 33 | - Feature-based pricing (not usage-based) 34 | - Volume markup threshold: >[X]k units/day (+50%) 35 | - Packaging options for different customer types 36 | - User and account management fees 37 | 38 | ## Implementation Options 39 | 40 | ### Simple (< 50 features): 41 | - Basic/Professional/Enterprise tiers 42 | - Package-based pricing 43 | - Easy to understand and sell 44 | 45 | ### Complex (50+ features): 46 | - Individual feature selection 47 | - Dynamic calculation 48 | - Customized configurations 49 | 50 | ## Best Practices 51 | 1. **Transparent Pricing**: No hidden fees 52 | 2. **Value-Based**: Price reflects customer benefit 53 | 3. **Scalable**: Works for small and large customers 54 | 4. **Flexible**: Easy to modify and update 55 | 56 | --- 57 | 58 | *Template Purpose: Feature-based pricing calculator framework* 59 | *Best For: Complex B2B SaaS products with multiple integrations* 60 | -------------------------------------------------------------------------------- /Docs/Operations/Hiring/Job-Openings/Senior-Marketing-Analyst/Role-Competency-Matrix.md: -------------------------------------------------------------------------------- 1 | # Role Competency Matrix — Senior Marketing Analytics (Data Engineering Profile) 2 | 3 | | Competency | Description | 4 | |----------------------|---------------------------------------------------------------------| 5 | | SQL Expert | Writing highly optimized complex SQL queries for large datasets. | 6 | | ETL & Data Pipelines | Experience designing ETL processes, integrating multiple data sources. | 7 | | API Integration | Experience working with APIs to collect and manage data. | 8 | | Data Modeling | Designing and maintaining normalized data models and schemas. | 9 | | Marketing Analytics | Understanding marketing metrics, KPIs, attribution models. | 10 | | Web Analytics Tools | Experience with GA UA, GA4, GTM. | 11 | | Ad Platforms | Experience with Google Ads, Facebook/Instagram Ads, etc. | 12 | | Client Communication | Direct communication with clients, requirements gathering. | 13 | | Documentation | Maintaining clean and up-to-date technical documentation. | 14 | | English Language | Upper-intermediate or advanced level. | 15 | | Russian Language | Native proficiency. | 16 | | Salary Expectations | Candidate's expected salary fits within company budget and grade level. | 17 | | Role Expectation Alignment | Candidate's career expectations align with the technical nature of the role (80% technical implementation, 20% business/strategic input). | 18 | 19 | ## Role Reality vs. Expectations 20 | 21 | ### Actual Role Balance 22 | - **Technical Implementation**: ~80% (SQL, ETL, data modeling, Power BI implementation) 23 | - **Business/Strategic**: ~20% (Requirements gathering, metric definition) 24 | 25 | ### Red Flags in Candidate Expectations 26 | - Career trajectory moving from technical to strategic roles 27 | - Expressed desire to influence product development 28 | - Primary interest in business decision-making rather than technical execution 29 | - Seeking role with significant input into strategic direction 30 | - Preference for creating new features/capabilities vs. implementing existing requirements 31 | -------------------------------------------------------------------------------- /Docs/Operations/Hiring/Job-Openings/Senior-Marketing-Analyst/Candidates/Example-Candidate-C-Weak/Screening-Evaluation.md: -------------------------------------------------------------------------------- 1 | # Screening Evaluation - [Candidate Name] 2 | 3 | **DECISION: [✅ PROCEED TO TECHNICAL INTERVIEW / ❌ REJECT CANDIDACY]** 4 | 5 | ## Summary 6 | [Provide a concise summary of the candidate's background, experience, technical skills, and relevant qualifications. Include current role, years of experience, key achievements, and educational background.] 7 | 8 | ## Competency Assessment 9 | | Competency | Rating | Evidence | 10 | |------------|--------|----------| 11 | | SQL Expertise | _/5 | [Evidence of SQL skills and experience] | 12 | | ETL & Data Pipelines | _/5 | [Evidence of ETL experience] | 13 | | API Integration | _/5 | [Evidence of API integration experience] | 14 | | Data Modeling | _/5 | [Evidence of data modeling skills] | 15 | | Marketing Analytics | _/5 | [Evidence of marketing analytics experience] | 16 | | Web Analytics Tools | _/5 | [Evidence of web analytics tool experience] | 17 | | Power BI | _/5 | [Evidence of Power BI skills] | 18 | | Client Communication | _/5 | [Evidence of client communication skills] | 19 | | Documentation | _/5 | [Evidence of documentation skills] | 20 | | English Proficiency | _/5 | [Evidence of English language skills] | 21 | | Team Fit | _/5 | [Evidence of team compatibility] | 22 | 23 | ## Key Strengths 24 | 1. [Key strength 1] 25 | 2. [Key strength 2] 26 | 3. [Key strength 3] 27 | 4. [Key strength 4] 28 | 5. [Key strength 5] 29 | 30 | ## Concerns 31 | - [Concern 1] 32 | - [Concern 2] 33 | - [Concern 3] 34 | - [Concern 4] 35 | - [Concern 5] 36 | 37 | ## Technical Assessment 38 | [Provide an assessment of the candidate's technical capabilities relevant to the role. Include specific skills, tools, and methodologies they have experience with. Comment on their problem-solving approach and technical depth.] 39 | 40 | ## Cultural Fit 41 | [Assess how well the candidate's values, working style, and communication approach align with the company culture. Include observations about remote work compatibility, adaptability, teamwork, and client interaction style.] 42 | 43 | ## Next Steps 44 | - [ ] Proceed to Technical Interview 45 | - [ ] Request Additional Information 46 | - [ ] Reject Candidacy 47 | 48 | ## Notes 49 | [Include additional observations, salary expectations, availability, and any specific areas to focus on in the technical interview if proceeding.] 50 | -------------------------------------------------------------------------------- /Docs/Operations/Hiring/Job-Openings/Senior-Marketing-Analyst/Full Evaluation Agent/agent-prompt.md: -------------------------------------------------------------------------------- 1 | You are [COMPANY_NAME] Recruiter Evaluation Agent. 2 | 3 | You must conduct full competency evaluation after technical interview. 4 | 5 | ## Data sources: 6 | 7 | - Global-Rules/General-Hiring-Policy.md 8 | - Global-Rules/Scoring-Framework.md 9 | - Global-Rules/Interview-Guidelines.md 10 | - Job-Openings/Senior-Marketing-Analyst/Position-Description.md 11 | - Job-Openings/Senior-Marketing-Analyst/Role-Competency-Matrix.md 12 | - Job-Openings/Senior-Marketing-Analyst/Scoring-Rules.md 13 | 14 | Candidate data includes: 15 | 16 | - CV.md 17 | - Fathom-Screening-Interview.md 18 | - Fathom-Technical-Interview.md 19 | - AI-Notes.md 20 | - Evaluation.md 21 | 22 | ## STRICT evaluation logic: 23 | 24 | - Use ONLY the competencies listed in Role-Competency-Matrix.md. 25 | - Do NOT add any other competencies (Problem Solving, Teamwork, Communication, Statistical Analysis etc.) 26 | - Apply thresholds and scoring from Scoring-Rules.md. 27 | - If data is missing for any competency, mark as "Insufficient Data". 28 | - SQL, ETL, and API Integration are critical skills — evaluate them very carefully. 29 | 30 | ## Multi-source evaluation logic: 31 | 32 | - If skill is mentioned in CV (skills section) → default 2/5. 33 | - If self-assessed in Fathom-Screening-Interview.md (e.g. 7-8/10 self-rating) → add +1 point. 34 | - If technical verification exists in Fathom-Technical-Interview.md → assign 4/5 or 5/5 depending on depth and complexity. 35 | - If no evidence found — assign 1/5. 36 | 37 | ## Output format: 38 | 39 | 1️⃣ Summary: full narrative assessment. 40 | 2️⃣ Competency Table: scores 1-5 (or Insufficient Data). 41 | 3️⃣ Final Fit Conclusion: Strong Fit / Potential Fit / Weak Fit. 42 | 4️⃣ Key Concerns: red flags, missing data, critical weaknesses. 43 | 44 | ## File Saving Rule: 45 | 46 | - After completing the evaluation, automatically write the full evaluation report (including Summary, Competency Table, Final Fit, and Key Concerns) into: 47 | 48 | `Hiring/Job-Openings/Senior-Marketing-Analyst/Candidates/[Candidate-Name]/Final-Score.md` 49 | 50 | - Use the actual candidate folder where you found CV.md and other files. 51 | - Overwrite any previous content in Final-Score.md with the new evaluation. 52 | - Do not ask for confirmation — write automatically after generating output. 53 | - If any file error occurs, report it in chat. 54 | -------------------------------------------------------------------------------- /scripts/check_range.py: -------------------------------------------------------------------------------- 1 | #!/usr/bin/env python3 2 | """ 3 | Number Range Validation Script 4 | ============================== 5 | 6 | This script performs precise numerical range checking to avoid LLM calculation errors. 7 | 8 | Usage: 9 | python3 scripts/check_range.py [value] [min] [max] [value] [min] [max] ... 10 | 11 | Examples: 12 | # Health metrics 13 | python3 scripts/check_range.py 185 125 200 92 70 100 85 80 120 14 | 15 | # Budget categories 16 | python3 scripts/check_range.py 650 500 700 250 200 300 17 | 18 | # Financial targets 19 | python3 scripts/check_range.py 15.5 10.0 20.0 8.2 5.0 15.0 20 | """ 21 | 22 | import sys 23 | 24 | def check_range(value, min_val, max_val): 25 | """Check if value is within the specified range (inclusive)""" 26 | return min_val <= value <= max_val 27 | 28 | def format_result(value, min_val, max_val, in_range): 29 | """Format the result for display""" 30 | status = "✅ In range" if in_range else "❌ Out of range" 31 | return f"{value:8.1f} | [{min_val:6.1f} - {max_val:7.1f}] | {status}" 32 | 33 | def main(): 34 | """Main function to process command line arguments""" 35 | args = sys.argv[1:] 36 | 37 | if len(args) == 0: 38 | print("Usage: python3 check_range.py [value] [min] [max] [value] [min] [max] ...") 39 | print("Example: python3 check_range.py 185 125 200 92 70 100") 40 | return 41 | 42 | if len(args) % 3 != 0: 43 | print("❌ Error: Arguments must be in groups of 3 (value, min, max)") 44 | print("Example: python3 check_range.py 185 125 200 92 70 100") 45 | return 46 | 47 | print("🔍 Range Check:") 48 | print("=" * 50) 49 | 50 | # Process arguments in groups of 3 51 | for i in range(0, len(args), 3): 52 | try: 53 | value = float(args[i]) 54 | min_val = float(args[i + 1]) 55 | max_val = float(args[i + 2]) 56 | 57 | in_range = check_range(value, min_val, max_val) 58 | result = format_result(value, min_val, max_val, in_range) 59 | print(result) 60 | 61 | except ValueError as e: 62 | print(f"❌ Error processing arguments {i//3 + 1}: {e}") 63 | return 64 | except IndexError: 65 | print("❌ Error: Incomplete argument group") 66 | return 67 | 68 | print("=" * 50) 69 | 70 | if __name__ == "__main__": 71 | main() 72 | -------------------------------------------------------------------------------- /Sales Calls/XS Discovery Call Demo/Notion Extended Version.md: -------------------------------------------------------------------------------- 1 | # Automated Sales Meeting Analysis 2 | **Client:** XS Discovery Call 3 | **Version:** Demo 4 | **Generated:** 2025-08-18 11:55:41 5 | **Workspace:** AI-First-Workspace 6 | **Meeting ID:** 01K1ZF3FGSY686JHZV0QSFG57K 7 | **Template:** prompt_notion 8 | **Meeting URL:** https://app.fireflies.ai/view/Elly-Analytics-XS-discovery-call::01K1ZF3FGSY686JHZV0QSFG57K 9 | 10 | --- 11 | 12 | 13 | # 📌 Short Summary 14 | 15 | **Lead Information** 16 | - **Lead Source:** Inbound 17 | - **🚀 Next Step:** Meeting scheduled: Yes - Jan 22, 2024 2:00 PM 18 | - **👤 Contact Role:** VP of Marketing 19 | - **👤 Business Type:** B2C SaaS 20 | - **💸 Ad Spend & Channels:** $50K monthly - Google Ads, Facebook 21 | - **🎯 Decision-Maker Status:** Yes - has budget authority 22 | - **🎯 ICP Fit:** Yes - B2C SaaS with subscription model 23 | 24 | **💬 Client Engagement Level:** 8 questions asked 25 | 26 | **✨ Key Positive Reactions:** 27 | - "This is exactly what we've been looking for" 28 | - "The ROI calculator looks very promising" 29 | - "Your attribution model makes perfect sense" 30 | 31 | **⚡ Main Pain Points:** 32 | - Cannot track full customer journey 33 | - Attribution gaps causing budget misallocation 34 | - Manual reporting consuming 10+ hours weekly 35 | 36 | **🚧 Key Objections:** 37 | - "How does this compare to Google Analytics?" 38 | - "Implementation timeline concerns" 39 | - "Integration complexity with existing stack" 40 | 41 | # 🔍 Detailed Analysis 42 | 43 | ## 1. Company & Prospect Overview 44 | - B2C SaaS subscription business with strong growth 45 | - VP of Marketing focused on scaling paid acquisition 46 | 47 | ## 2. Marketing & Tech Stack 48 | - Ad Channels: Google Ads, Facebook Ads 49 | - CRM/Backend: Salesforce + custom backend 50 | - Ad Spend: $50K monthly budget 51 | - Current Reporting: Google Analytics + manual Excel sheets 52 | 53 | ## 3. Discovery & Q&A 54 | **Discovery Questions Asked:** 55 | - Q1: Current attribution model → A1: Last-click only, major gaps 56 | - Q2: Reporting frequency → A2: Weekly manual reports, very time-consuming 57 | 58 | **Client Questions:** 59 | - Q1: Integration complexity → Response: 2-week implementation typical 60 | - Q2: ROI measurement → Response: Showed live calculator demo 61 | 62 | ## 4. Next Steps 63 | Demo scheduled for Jan 22, prepare custom ROI analysis 64 | 65 | 66 | --- 67 | 68 | *This analysis was generated automatically using the Sales Meeting Processing system.* 69 | *Session: `XS Discovery Call Demo`* 70 | *File: `Notion Extended Version.md`* 71 | -------------------------------------------------------------------------------- /Docs/SalesAndMarketing/Sales Calls/XS Discovery Call v01/Notion Extended Version.md: -------------------------------------------------------------------------------- 1 | # Automated Sales Meeting Analysis 2 | **Client:** XS Discovery Call 3 | **Version:** Demo 4 | **Generated:** 2025-08-18 09:54:39 5 | **Workspace:** Personal-Super-Agent 6 | **Meeting ID:** 01K1ZF3FGSY686JHZV0QSFG57K 7 | **Template:** prompt_notion 8 | **Meeting URL:** https://app.fireflies.ai/view/Elly-Analytics-XS-discovery-call::01K1ZF3FGSY686JHZV0QSFG57K 9 | 10 | --- 11 | 12 | 13 | # 📌 Short Summary 14 | 15 | **Lead Information** 16 | - **Lead Source:** Inbound 17 | - **🚀 Next Step:** Meeting scheduled: Yes - Jan 22, 2024 2:00 PM 18 | - **👤 Contact Role:** VP of Marketing 19 | - **👤 Business Type:** B2C SaaS 20 | - **💸 Ad Spend & Channels:** $50K monthly - Google Ads, Facebook 21 | - **🎯 Decision-Maker Status:** Yes - has budget authority 22 | - **🎯 ICP Fit:** Yes - B2C SaaS with subscription model 23 | 24 | **💬 Client Engagement Level:** 8 questions asked 25 | 26 | **✨ Key Positive Reactions:** 27 | - "This is exactly what we've been looking for" 28 | - "The ROI calculator looks very promising" 29 | - "Your attribution model makes perfect sense" 30 | 31 | **⚡ Main Pain Points:** 32 | - Cannot track full customer journey 33 | - Attribution gaps causing budget misallocation 34 | - Manual reporting consuming 10+ hours weekly 35 | 36 | **🚧 Key Objections:** 37 | - "How does this compare to Google Analytics?" 38 | - "Implementation timeline concerns" 39 | - "Integration complexity with existing stack" 40 | 41 | # 🔍 Detailed Analysis 42 | 43 | ## 1. Company & Prospect Overview 44 | - B2C SaaS subscription business with strong growth 45 | - VP of Marketing focused on scaling paid acquisition 46 | 47 | ## 2. Marketing & Tech Stack 48 | - Ad Channels: Google Ads, Facebook Ads 49 | - CRM/Backend: Salesforce + custom backend 50 | - Ad Spend: $50K monthly budget 51 | - Current Reporting: Google Analytics + manual Excel sheets 52 | 53 | ## 3. Discovery & Q&A 54 | **Discovery Questions Asked:** 55 | - Q1: Current attribution model → A1: Last-click only, major gaps 56 | - Q2: Reporting frequency → A2: Weekly manual reports, very time-consuming 57 | 58 | **Client Questions:** 59 | - Q1: Integration complexity → Response: 2-week implementation typical 60 | - Q2: ROI measurement → Response: Showed live calculator demo 61 | 62 | ## 4. Next Steps 63 | Demo scheduled for Jan 22, prepare custom ROI analysis 64 | 65 | 66 | --- 67 | 68 | *This analysis was generated automatically using the Sales Meeting Processing system.* 69 | *Session: `XS Discovery Call Demo`* 70 | *File: `Notion Extended Version.md`* 71 | -------------------------------------------------------------------------------- /Docs/SePersonalCRM/MainCRM/Contacts/Contact-E/Contact-E-linkedin.md: -------------------------------------------------------------------------------- 1 | # Contact E - LinkedIn Profile 2 | 3 | **Profile URL**: [ANONYMIZED_LINKEDIN_URL] 4 | **Last Updated**: 2025-11-10 17:29:26 5 | 6 | --- 7 | 8 | ## Basic Information 9 | 10 | - **Name**: Contact E 11 | - **Headline**: Co-founder @ Company AAA 12 | - **Location**: US City B 13 | 14 | --- 15 | 16 | ## About 17 | 18 | Helping B2B SaaS Customer Success teams understand how their customers are adopting their products to identify churn risks and upsell opportunities. 19 | 20 | --- 21 | 22 | ## Experience 23 | 24 | Co-Founder 25 | Company AAA · Full-time 26 | Dec 2021 - Present · 4 yrs 27 | Dec 2021 to Present · 4 yrs 28 | Company AAA helps B2B SaaS Customer Success teams understand how their customers are adopting their product. So CSMs can prep for QBRs and proactively uncover silent churn risks. 29 | Skills: B2B SaaS · Product Analytics · Customer Success 30 | 31 | --- 32 | 33 | Co-Founder 34 | Company BBB · Full-time 35 | Dec 2021 - Dec 2024 · 3 yrs 1 mo 36 | Dec 2021 to Dec 2024 · 3 yrs 1 mo 37 | Acquired by stealth 38 | 39 | --- 40 | 41 | Company CCC 42 | Full-time · 1 yr 3 mos 43 | European City F, Region A 44 | Business Consultant 45 | Aug 2022 - Jan 2023 · 6 mos 46 | Aug 2022 to Jan 2023 · 6 mos 47 | European $XB unicorn 48 | Skills: B2B SaaS 49 | Business Analyst 50 | Nov 2021 - Jul 2022 · 9 mos 51 | Nov 2021 to Jul 2022 · 9 mos 52 | 53 | --- 54 | 55 | Technical Sales Specialist 56 | Company DDD · Full-time 57 | Mar 2021 - Nov 2021 · 9 mos 58 | Mar 2021 to Nov 2021 · 9 mos 59 | European City F, Region A 60 | Acquired by Company EEE 61 | Skills: B2B sales · B2B SaaS 62 | Excellence demo cert in 40 days 63 | 64 | --- 65 | 66 | User Experience Specialist 67 | Company FFF 68 | Dec 2017 - Jul 2020 · 2 yrs 8 mos 69 | Dec 2017 to Jul 2020 · 2 yrs 8 mos 70 | European City F, Region A 71 | 72 | --- 73 | 74 | Research Assistant 75 | University B · Contract 76 | Apr 2018 - Aug 2018 · 5 mos 77 | Apr 2018 to Aug 2018 · 5 mos 78 | Directed and produced a mini-series of documentary about students from program, that increased the number of student application by N% the following semester. 79 | A record number of applicants for English-taught bachelor's programmes 80 | Offered since 2016, the Bachelor's Degree Programme received applications, which is an increase of N% from last year. 81 | 82 | --- 83 | 84 | Student Associate 85 | Consulting Company GGG 86 | Oct 2017 - Dec 2017 · 3 mos 87 | Oct 2017 to Dec 2017 · 3 mos 88 | European City F, Region A 89 | 90 | --- 91 | 92 | *Profile researched via automated LinkedIn finder* 93 | 94 | -------------------------------------------------------------------------------- /Docs/Operations/Hiring/Job-Openings/Senior-Marketing-Analyst/Candidates/Template/Screening-Evaluation.md: -------------------------------------------------------------------------------- 1 | # Screening Evaluation - [Candidate Name] 2 | 3 | **DECISION: [✅ PROCEED TO TECHNICAL INTERVIEW / ❌ REJECT CANDIDACY]** 4 | 5 | > **NOTE: This evaluation is based ONLY on the candidate's CV and screening interview. The purpose is to determine whether to proceed to the technical interview stage, not to make a final hiring decision.** 6 | 7 | ## Summary 8 | [Provide a concise summary of the candidate's background, experience, technical skills, and relevant qualifications. Include current role, years of experience, key achievements, and educational background.] 9 | 10 | ## Competency Assessment 11 | | Competency | Rating | Evidence | 12 | |------------|--------|----------| 13 | | SQL Expertise | _/5 | [Evidence of SQL skills and experience] | 14 | | ETL & Data Pipelines | _/5 | [Evidence of ETL experience] | 15 | | API Integration | _/5 | [Evidence of API integration experience] | 16 | | Data Modeling | _/5 | [Evidence of data modeling skills] | 17 | | Marketing Analytics | _/5 | [Evidence of marketing analytics experience] | 18 | | Web Analytics Tools | _/5 | [Evidence of web analytics tool experience] | 19 | | Power BI | _/5 | [Evidence of Power BI skills] | 20 | | Client Communication | _/5 | [Evidence of client communication skills] | 21 | | Documentation | _/5 | [Evidence of documentation skills] | 22 | | English Proficiency | _/5 | [Evidence of English language skills] | 23 | | Team Fit | _/5 | [Evidence of team compatibility] | 24 | 25 | ## Key Strengths 26 | 1. [Key strength 1] 27 | 2. [Key strength 2] 28 | 3. [Key strength 3] 29 | 4. [Key strength 4] 30 | 5. [Key strength 5] 31 | 32 | ## Concerns 33 | - [Concern 1] 34 | - [Concern 2] 35 | - [Concern 3] 36 | - [Concern 4] 37 | - [Concern 5] 38 | 39 | ## Technical Assessment 40 | [Provide an assessment of the candidate's technical capabilities relevant to the role. Include specific skills, tools, and methodologies they have experience with. Comment on their problem-solving approach and technical depth.] 41 | 42 | ## Cultural Fit 43 | [Assess how well the candidate's values, working style, and communication approach align with the company culture. Include observations about remote work compatibility, adaptability, teamwork, and client interaction style.] 44 | 45 | ## Next Steps 46 | - [ ] Proceed to Technical Interview 47 | - [ ] Request Additional Information 48 | - [ ] Reject Candidacy 49 | 50 | ## Notes 51 | [Include additional observations, salary expectations, availability, and any specific areas to focus on in the technical interview if proceeding.] -------------------------------------------------------------------------------- /Docs/SePersonalCRM/MainCRM/Contacts/Contact-D/Contact-D-emails.md: -------------------------------------------------------------------------------- 1 | # Contact D 2 | 3 | ## Email history with contact.d@example.com 4 | 5 | **Date**: 2024-07-23T07:43:16 6 | **From**: Angel Investor K <[ANONYMIZED_EMAIL]> ⬅️ 7 | **To**: Contact D 8 | **Cc**: Person B <[ANONYMIZED_EMAIL]>, Person E <[ANONYMIZED_EMAIL]> 9 | **Subject**: Intro Company Zeta <> Contact D 10 | 11 | Hi all, excited to connect you. Person B & Person E are co-founders of Company Zeta. And Contact D is… Contact D) Have a productive conversation. 12 | 13 | Best, 14 | 15 | Angel Investor K 16 | 17 | 18 | **Date**: 2024-07-23T10:51:44 19 | **From**: Person B <[ANONYMIZED_EMAIL]> me 20 | **To**: Angel Investor K <[ANONYMIZED_EMAIL]> 21 | **Cc**: Contact D , Person E <[ANONYMIZED_EMAIL]> 22 | **Subject**: Re: Intro Company Zeta <> Contact D 23 | 24 | Hi all, 25 | 26 | Angel Investor K, thanks for the introduction. 27 | 28 | Contact D, it's a pleasure to meet you. I heard a lot about you! 29 | 30 | I'm in US City B, and Person E is in City I. Let's start with a 1:1 call. Can we 31 | schedule a call after 2 p.m. PT? Here is my calendly 32 | [ANONYMIZED_CALENDAR_LINK]. Almost any time 33 | after 2 pm is available. If not, I'll find an earlier time for you. 34 | 35 | Best, 36 | Person B 37 | 38 | 39 | **Date**: 2024-08-07T13:35:18 40 | **From**: Person B <[ANONYMIZED_EMAIL]> me 41 | **To**: Contact D 42 | **Cc**: Person E <[ANONYMIZED_EMAIL]> 43 | **Subject**: Re: Intro Company Zeta <> Contact D 44 | 45 | Hi Contact D, 46 | 47 | I want to kindly remind you about this thread. 48 | 49 | Let's schedule a call. When are you available? 50 | 51 | Best, 52 | Person B 53 | 54 | On Tue, Jul 23, 2024 at 10:51 AM Person B <[ANONYMIZED_EMAIL]> wrote: 55 | 56 | 57 | **Date**: 2024-08-08T13:58:59 58 | **From**: Contact D ⬅️ 59 | **To**: Person B <[ANONYMIZED_EMAIL]> 60 | **Cc**: Person E <[ANONYMIZED_EMAIL]> 61 | **Subject**: Re: Intro Company Zeta <> Contact D 62 | 63 | Hi there- so sorry for going completely dark here. I found myself completely oversubscribed and can't connect at the moment. If I may still be helpful next year, please ping… 64 | 65 | Whish you absolute best. The category you chose is no walk in the park but I'm so happy to hear you are already crushing it. 66 | 67 | 68 | **Date**: 2025-11-04T13:10:06 69 | **From**: Angel Investor K <[ANONYMIZED_EMAIL]> ⬅️ 70 | **To**: Contact D , Person B <[ANONYMIZED_EMAIL]>, Person E <[ANONYMIZED_EMAIL]> 71 | **Subject**: Reconnecting Contact D <> Company Zeta 72 | 73 | Contact D, Person B, Person E, happy to reconnect you. 74 | 75 | Best, 76 | 77 | Angel Investor K 78 | 79 | 80 | 81 | -------------------------------------------------------------------------------- /Docs/Strategy/Team/team-overview.md: -------------------------------------------------------------------------------- 1 | ⚠️ **TEMPLATE EXAMPLE - CUSTOMIZE FOR YOUR TEAM** 2 | 3 | > **📋 Template Notice**: This document contains a real team overview example that demonstrates professional team documentation structure. When using this template: 4 | > - **Founders Section**: Keep the founders section as-is - this shows the actual founders of the original company 5 | > - **Advisory Board**: Replace example advisors with your actual advisors and their real expertise/backgrounds 6 | > - **Team Size**: Update headcount numbers and department structure to match your actual organization 7 | > - **Contact Information**: Replace placeholder emails, LinkedIn profiles, and messaging handles with real information 8 | > - This example shows how to present team composition and leadership backgrounds effectively 9 | 10 | --- 11 | 12 | # Team Overview - Elly Analytics [CANONICAL] 13 | 14 | ## 👥 Founders [CANONICAL] 15 | 16 | ### Seva Ustinov [CANONICAL] 17 | **Title:** CEO & Founder 18 | **Email:** seva.ustinov@ellyanalytics.com 19 | **LinkedIn:** linkedin.com/in/sevaustinov 20 | **Telegram:** t.me/SevaUstinov 21 | 22 | **Background:** CS MSU Alumni, Co-founder & co-CEO IT-Agency (till 2022) - top-15 in Russia, 150 clients, 120 employees, $15M revenue 23 | 24 | ### Kirill Kasimskiy [CANONICAL] 25 | **Title:** Co-founder 26 | **Email:** kirill.kasimskiy@ellyanalytics.com 27 | **LinkedIn:** linkedin.com/in/kirill-kasimskiy 28 | **Telegram:** t.me/kkass 29 | 30 | **Background:** Co-founder IT-Agency (till 2019), Partner & CEO NewBeautyBox (10x revenue growth, raised 2 rounds), Marketing Advisor @ JustFood (2.7x revenue growth) 31 | 32 | ## 🧭 Advisory Board [TEMPLATE EXAMPLE] 33 | 34 | ### [Example Advisor Name] [TEMPLATE EXAMPLE] 35 | **Expertise:** [Replace with actual advisor expertise area] 36 | **Background:** [Replace with actual advisor background and relevant experience] 37 | 38 | ### [Example Advisor Name] [TEMPLATE EXAMPLE] 39 | **Expertise:** [Replace with actual advisor expertise area] 40 | **Background:** [Replace with actual advisor background and relevant experience] 41 | 42 | ## 👷 Current Team Size [TEMPLATE EXAMPLE] 43 | 44 | **Total Headcount:** [Replace with actual number] people (as of [Replace with current date]) 45 | 46 | **By Department:** 47 | - **[Department Name]:** [Replace with actual number] 48 | - **[Department Name]:** [Replace with actual number] 49 | - **[Department Name]:** [Replace with actual number] 50 | - **[Department Name]:** [Replace with actual number] 51 | - **Founders:** [Replace with actual number] (included in above) 52 | 53 | **Key Focus:** [Replace with actual strategic focus or team allocation] 54 | 55 | --- 56 | 57 | [LAST UPDATED: [Replace with actual date] with factual information only] -------------------------------------------------------------------------------- /Docs/SePersonalCRM/MainCRM/Contacts/Contact-E/Contact-E.md: -------------------------------------------------------------------------------- 1 | # Contact E - Profile 2 | 3 | **Role**: Co-founder at Company AAA [CANONICAL] 4 | **Contact Date**: November 10, 2025 (Met at Person G's meetup) [CANONICAL] 5 | **Context**: Met at Person G's US City B founders community event (first event was Nov 7, 2025) [CONFIRMED: user] 6 | 7 | **Communication Channels**: 8 | - **Email**: [TO BE FOUND] 9 | - **LinkedIn**: [ANONYMIZED_LINKEDIN_URL] [CANONICAL - Verified Nov 10, 2025] 10 | - **Preferred channel**: [TO BE DETERMINED] 11 | 12 | --- 13 | 14 | ## Professional Background 15 | [CANONICAL: LinkedIn verified Nov 10, 2025, see Contact-E-linkedin.md for full profile] 16 | 17 | ### Current Role: Company AAA (Dec 2021 - Present) 18 | **Position**: Co-founder 19 | **Location**: US City B 20 | 21 | **Company Context**: Company AAA helps B2B SaaS Customer Success teams understand how their customers are adopting their product. Enables CSMs to prep for QBRs and proactively uncover silent churn risks and upsell opportunities. 22 | 23 | **Product Focus**: Product adoption analytics for Customer Success teams in B2B SaaS 24 | 25 | ### Previous Experience 26 | 27 | **Company BBB** (Dec 2021 - Dec 2024, 3 years 1 month) 28 | - Co-founder 29 | - Acquired by stealth company 30 | 31 | **Company CCC** (Nov 2021 - Jan 2023, 1 year 3 months) 32 | - Business Consultant and Business Analyst 33 | - European $XB unicorn 34 | - Location: European City F 35 | 36 | **Company DDD** (Mar 2021 - Nov 2021, 9 months) 37 | - Technical Sales Specialist 38 | - Acquired by Company EEE 39 | - Achieved "Excellence demo cert in 40 days" 40 | 41 | **Company FFF** (Dec 2017 - Jul 2020, 2 years 8 months) 42 | - User Experience Specialist 43 | - Location: European City F 44 | 45 | **Skills**: B2B SaaS, Product Analytics, Customer Success, B2B Sales 46 | 47 | --- 48 | 49 | ## Relationship to Elly Analytics 50 | 51 | **Why Relevant**: 52 | 1. **Potential Referrals**: If we meet companies with large customer success teams, could recommend Company AAA 53 | 2. **Founder Network**: Part of Person G's US City B founders community 54 | 3. **Product Focus**: Customer success tools - complementary to Company Zeta's marketing focus 55 | 56 | **Communication Summary**: 57 | - **November 10, 2025**: Met at Person G's US City B founders community meetup 58 | - **Status**: No immediate tasks, potential for mutual referrals 59 | 60 | **Potential Value**: 61 | - **Referral Partner**: Recommend Company AAA to companies with large CS teams 62 | - **Founder Community**: Part of US City B Bay Area builder network through Person G's events 63 | 64 | --- 65 | 66 | **Last Updated**: November 10, 2025 [CANONICAL] 67 | **Sources**: 68 | - User instruction [CONFIRMED: Nov 10, 2025] 69 | - LinkedIn research [COMPLETED: Nov 10, 2025] 70 | - Met at Person G's meetup [CONFIRMED] 71 | 72 | 73 | -------------------------------------------------------------------------------- /Docs/SePersonalCRM/MainCRM/Contacts/Contact-B/Contact-B-emails.md: -------------------------------------------------------------------------------- 1 | # Contact B 2 | 3 | ## Email history with contact.b@example.com 4 | 5 | **Date**: 2025-10-19T13:29:04 6 | **From**: Person D <[ANONYMIZED_EMAIL]> ⬅️ 7 | **To**: [ANONYMIZED_EMAIL] 8 | **Cc**: contact.b@example.com, [ANONYMIZED_EMAIL], [ANONYMIZED_EMAIL] 9 | **Subject**: VC Firm F <> Company Zeta 10 | 11 | Hi Contact B and Person B, I'm happy to connect you both. Contact B and I met at Event Location H, and she's now a Principal at VC Firm F, investing in early-stage AI and enterprise software startups. Person B (and his co-founder, Person E) have built a profitable $PM digital agency. Their clients spend N%+ of ad spend on teams and agencies, manually managing ads. Now they are building Company Zeta, an AI performance marketing agent, delivering better ROAS at a fraction of a cost. Company Zeta already has traction in consumer software and services companies: $QM ad spend under management. Raising seed to accelerate growth and scale to $RM ARR. You both share a deep interest in how AI is reshaping marketing and enterprise automation. I'm sure you'll have a great conversation. Kind regards, Person D 12 | 13 | 14 | **Date**: 2025-10-20T15:25:03 15 | **From**: Person B <[ANONYMIZED_EMAIL]> me 16 | **To**: contact.b@example.com 17 | **Cc**: [ANONYMIZED_EMAIL], Person D <[ANONYMIZED_EMAIL]> 18 | **Subject**: Re: VC Firm F <> Company Zeta 19 | 20 | Hi Contact B, 21 | 22 | I have a few interesting things to show about ai-first companies and 23 | ai-first products. 24 | 25 | Let's meet in City F or Tech Hub Area later this week? 26 | 27 | Best, 28 | Person B 29 | 30 | 31 | **Date**: 2025-10-27T14:20:17 32 | **From**: Contact B ⬅️ 33 | **To**: Person B <[ANONYMIZED_EMAIL]> 34 | **Subject**: Re: VC Firm F <> Company Zeta 35 | 36 | Hi Person B, 37 | 38 | Sorry for the delay. I have been at a conference. Feel free to schedule some time here [ANONYMIZED_CALENDAR_LINK] or I can meet you around City F. 39 | 40 | *Contact B* 41 | Principal 42 | [ANONYMIZED_ADDRESS] 43 | [ANONYMIZED_PHONE] 44 | 45 | 46 | **Date**: 2025-11-06T17:14:25 47 | **From**: Person B <[ANONYMIZED_EMAIL]> me 48 | **To**: Contact B 49 | **Subject**: Re: VC Firm F <> Company Zeta 50 | 51 | Sorry for the late reply. 52 | 53 | Let's meet in City F. 54 | 55 | Does Wednesday 1 pm, 2pm or 5 pm work for you? 56 | 57 | Best, 58 | Person B 59 | 60 | On Mon, Oct 27, 2025, 2:20 PM Contact B wrote: 61 | 62 | 63 | **Date**: 2025-11-10T12:01:02 64 | **From**: Contact B ⬅️ 65 | **To**: Person B <[ANONYMIZED_EMAIL]> 66 | **Subject**: Re: VC Firm F <> Company Zeta 67 | 68 | 5 pm works! Where do you want to meet? 69 | 70 | *Contact B* 71 | Principal 72 | [ANONYMIZED_ADDRESS] 73 | [ANONYMIZED_PHONE] 74 | 75 | 76 | 77 | -------------------------------------------------------------------------------- /Docs/SePersonalCRM/MainCRM/Contacts/Contact-B/Contact-B.md: -------------------------------------------------------------------------------- 1 | # Contact B - Profile 2 | 3 | **Role**: Principal at VC Firm F [CANONICAL] 4 | **Contact Date**: October 2025 (Introduction via Person D) [CANONICAL] 5 | **Context**: Introduced by Person D for fundraising conversation [CONFIRMED: user] 6 | 7 | **Communication Channels**: 8 | - **Email**: contact.b@example.com [CANONICAL - Confirmed Oct 27] 9 | - **Phone**: [ANONYMIZED_PHONE] [CONFIRMED: Email signature] 10 | - **LinkedIn**: [ANONYMIZED_LINKEDIN_URL] [CANONICAL - Provided by user] 11 | - **Preferred channel**: Email 12 | 13 | **Name Variations**: Contact B 14 | 15 | --- 16 | 17 | ## Professional Background 18 | [TO BE VERIFIED - LinkedIn profile not yet checked in browser] 19 | 20 | ### Current Role: VC Firm F 21 | **Position**: Principal 22 | **Location**: Tech Hub A [CONFIRMED: web search] 23 | 24 | **About VC Firm F** [CONFIRMED: web search Oct 20, 2025]: 25 | - **Focus**: AI and enterprise automation startups 26 | - **Stage**: Seed to IPO 27 | - **Thesis**: Enterprise 5.0 and innovation at the intersection of AI and business 28 | - **Value Add**: Financial and human capital support 29 | - **Location**: Tech Hub A 30 | 31 | --- 32 | 33 | ## Background & Achievements 34 | [TO BE VERIFIED - Additional research needed] 35 | 36 | --- 37 | 38 | ## Relationship to Elly Analytics 39 | 40 | **Why Relevant**: 41 | 1. **Investment Focus**: VC Firm F specializes in AI and enterprise automation - perfect fit for Company Zeta's AI marketing automation platform 42 | 2. **Stage Match**: VC Firm F invests from seed to IPO, suitable for Company Zeta's current fundraising stage 43 | 3. **Enterprise Focus**: VC Firm F's Enterprise 5.0 thesis aligns with Company Zeta's B2B SaaS positioning 44 | 4. **Warm Introduction**: Quality intro through Person D (proven connector) 45 | 46 | **Communication Summary**: 47 | - **October 2025**: Person D introduced Person B to Contact B 48 | - **Status**: Awaiting initial reply and meeting setup 49 | 50 | **Potential Value**: 51 | - **Primary Investor**: VC Firm F's AI/enterprise automation focus is ideal match 52 | - **Strategic Fit**: Enterprise 5.0 thesis aligns with "AI for marketing operations" vision 53 | - **Portfolio Support**: Access to VC Firm F's enterprise network and expertise 54 | - **Tech Hub A Presence**: Strong regional connections for future rounds 55 | 56 | --- 57 | 58 | **Last Updated**: October 20, 2025 [CANONICAL] 59 | **Sources**: 60 | - User instruction [CONFIRMED] 61 | - LinkedIn profile URL provided [TO BE VERIFIED in browser] 62 | - VC Firm F web search [CONFIRMED: Oct 20, 2025] 63 | 64 | 65 | --- 66 | 67 | ## Email Communication 68 | [CANONICAL: Gmail sync 2025-11-10] 69 | 70 | **Email Communication Summary** (5 emails, 2025-10 - 2025-11): 71 | Email correspondence. 72 | 73 | **Full email history**: [Contact-B-emails.md](./Contact-B-emails.md) 74 | 75 | -------------------------------------------------------------------------------- /Projects/Status-Projects/Client-Beauty2-Status-Card.md: -------------------------------------------------------------------------------- 1 | # 🧴 Client3 - Beauty & Health E-commerce 2 | **Status**: ✅ Active 3 | **Analyst**: Manager1 4 | **Project Manager**: Manager4 5 | **Industry**: Beauty & Health E-commerce 6 | **Last Update**: 28.07.2025 7 | 8 | ## 🏷️ Information Sources 9 | - `[MEETING:2025-07-28]` - **NEW** Final check before project defense 10 | - `[MEETING:2025-06-30]` - Manager1 IM: Client1, Client6, Client7, Client2, Client3, Client4, Client8 11 | - `[MEETING:2025-06-23]` - Discussion at meeting with Manager1 12 | - `[PORTFOLIO:ACTIVE]` - Status from active projects portfolio 13 | 14 | ## 📈 Current Status 15 | **✅ Active development with multiple tasks** 16 | 17 | ### 🎯 Priority tasks in progress 18 | 1. **Unknown source analysis** - resolving unidentified traffic sources 19 | 2. **Additional order metrics** - adding new order metrics 20 | 3. **LTV integration** - implementing lifetime value indicators 21 | 4. **Influencer reporting** - setting up influencer tracking 22 | 23 | ## 🔧 Technical work 24 | **AirByte integration**: 25 | - ⚠️ Unstable importer operation (works periodically) 26 | - Working on diagnostics and stability improvement 27 | - Alternative data import methods being explored 28 | 29 | **Custom metrics implementation**: 30 | - ✅ Top 5/bottom 5 campaigns working correctly 31 | - ✅ Google sessions issues resolved 32 | - ✅ Full report exported and metrics displaying properly 33 | - ✅ Simplified report fits in one screen 34 | 35 | ## 📊 Progress indicators 36 | - **Technical readiness**: 85% complete 37 | - **Custom analytics**: Fully implemented 38 | - **Dashboard functionality**: Operational 39 | - **Data accuracy**: Verified and stable 40 | 41 | ## 🎯 Next milestones 42 | 1. **Complete unknown source analysis** - resolve all unidentified traffic 43 | 2. **Finalize LTV calculations** - implement comprehensive lifetime value 44 | 3. **Stabilize AirByte integration** - ensure reliable data import 45 | 4. **Prepare for project defense** - documentation and presentation 46 | 47 | ## 📝 Key achievements 48 | - All custom metrics successfully implemented 49 | - Dashboard fully operational with stable performance 50 | - Complex analytics requirements met 51 | - Ready for final project review phase 52 | 53 | ## 🔄 Recent updates (28.07.2025) 54 | **Significant progress made** [MEETING:2025-07-28]: 55 | - All custom metrics added and tested successfully 56 | - Technical issues with Google sessions resolved 57 | - Full reporting capability achieved 58 | - Project entering final completion phase 59 | 60 | ## 📋 Action items 61 | - [ ] Complete unknown source attribution analysis 62 | - [ ] Finalize LTV integration testing 63 | - [ ] Prepare comprehensive project documentation 64 | - [ ] Schedule final project defense presentation 65 | 66 | **Project Manager**: Manager4 67 | **Next Review**: 04.08.2025 68 | **Testimonial Readiness**: HIGH - comprehensive analytics implementation completed -------------------------------------------------------------------------------- /scripts/CURSOR_RULES.md: -------------------------------------------------------------------------------- 1 | # Cursor Rules for Sales Meeting Automation 2 | 3 | ## Demo Behavior Requirements 4 | 5 | ### 1. Notion Integration Demo 6 | - **ALWAYS show Notion page creation** in demo mode 7 | - **ALWAYS provide mock Notion URLs** when API keys are not configured 8 | - Format: `https://www.notion.so/ellyanalytics/XS-Discovery-Call-Notion-{version}-{mock_id}` 9 | - **ALWAYS show Page Title, URL, and ID** even in demo mode 10 | - Example output: 11 | ``` 12 | ✅ Mock Notion page created successfully! 13 | 📄 Page Title: XS Discovery Call Notion 04 14 | 🔗 Page URL: https://www.notion.so/ellyanalytics/XS-Discovery-Call-Notion-04-abc123def45604 15 | 📄 Page ID: abc123def45604 16 | ``` 17 | 18 | ### 2. File Organization Rules 19 | - **Session-based folders**: `{client-name}-v{XX}/` 20 | - **Simple file names**: `internal.md` and `notion.md` 21 | - **Auto-versioning**: v01, v02, v03... for each new session 22 | - **Both files in same version folder** per session 23 | 24 | ### 3. Workspace Detection 25 | - Auto-detect workspace from script path 26 | - Personal-Super-Agent-Ru → `Marketing-Sales/Sales Calls/` 27 | - Personal-Super-Agent → `Marketing-Sales/Sales Calls/` 28 | - AI-First-Workspace → `Sales Calls/` 29 | 30 | ## API Integration 31 | 32 | ### 4. Fireflies.ai Integration 33 | - Demo meeting ID: `01K1ZF3FGSY686JHZV0QSFG57K` 34 | - Demo URL: `https://app.fireflies.ai/view/Elly-Analytics-XS-discovery-call::01K1ZF3FGSY686JHZV0QSFG57K` 35 | - Always use mock data when API_TOKEN not configured 36 | 37 | ### 5. Notion Integration 38 | - **Real mode**: Requires NOTION_TOKEN and NOTION_DATABASE_ID 39 | - **Demo mode**: Show mock page creation with realistic URLs 40 | - **Page naming**: `{Client Name} Notion {version}` 41 | - **Database fields**: Name, Client, Meeting Date, Lead Source, Status, Next Step 42 | 43 | ## Error Handling 44 | 45 | ### 6. Graceful Degradation 46 | - Missing API keys → Demo mode with mock responses 47 | - Network errors → Show error but continue with local file creation 48 | - File conflicts → Auto-increment version numbers 49 | 50 | ### 7. User Experience 51 | - **Always show progress indicators**: 🚀 📥 ✅ 🤖 💾 📤 52 | - **Always provide clear status messages** 53 | - **Always show file paths and URLs created** 54 | - **Always indicate demo vs real mode** 55 | 56 | ## Security 57 | 58 | ### 8. Sensitive Data 59 | - Never log full API tokens (show only first 20 chars) 60 | - Use placeholder data for demos 61 | - Environment variables for all credentials 62 | 63 | ## Templates 64 | 65 | ### 9. Analysis Templates 66 | - `prompt_internal.txt` - Team summary format 67 | - `prompt_notion.txt` - Structured CRM format 68 | - English language for all demo workspaces 69 | - Consistent emoji usage for visual clarity 70 | 71 | ## Integration Points 72 | 73 | ### 10. Cursor Integration 74 | - Scripts auto-detect workspace context 75 | - Seamless integration with existing folder structures 76 | - No manual path configuration needed 77 | - Compatible with all demo workspaces 78 | -------------------------------------------------------------------------------- /Docs/Operations/Hiring/Job-Openings/Senior-Marketing-Analyst/Candidates/Example-Candidate-B-Average/Final-Score.md: -------------------------------------------------------------------------------- 1 | # Final Evaluation: Michael Thompson 2 | *[TEMPLATE EXAMPLE - This is a fictional evaluation for demonstration purposes]* 3 | 4 | ## Summary 5 | Candidate evaluation completed on March 30, 2024. 6 | Based on screening interview, technical assessment, and competency analysis, this candidate is classified as a **Moderate Fit**. 7 | 8 | ## Competency Scores 9 | 10 | | Competency | Score | Notes | 11 | |------------|-------|-------| 12 | | SQL Proficiency | 3/5 | Solid fundamentals, limited production experience | 13 | | ETL Experience | 2/5 | Python/Pandas focused, minimal SQL pipelines | 14 | | API Integration | 2/5 | No hands-on experience, theoretical knowledge only | 15 | | Data Visualization | 4/5 | Strong Power BI skills, good dashboard design | 16 | | Statistical Analysis | 3/5 | Basic A/B testing, limited advanced statistics | 17 | | Marketing Campaign Analysis | 4/5 | Good domain knowledge, practical experience | 18 | | Problem Solving | 4/5 | Systematic approach, good debugging methodology | 19 | | Communication Skills | 4/5 | Clear, honest, professional communication | 20 | | Teamwork | 5/5 | Collaborative mindset, seeks mentorship | 21 | 22 | ## Final Fit Conclusion 23 | **Moderate Fit - Hire with Extended Onboarding** 24 | 25 | ## Recommendation 26 | **CONDITIONAL HIRE** - Offer position with 6-month structured onboarding plan 27 | 28 | ### Reasoning: 29 | ✅ **Strong Foundation:** Solid analytical skills and domain knowledge 30 | ✅ **Growth Potential:** High learning motivation and realistic self-assessment 31 | ✅ **Cultural Alignment:** Excellent fit with company values and team dynamics 32 | ⚠️ **Skill Gaps:** Requires significant technical development in SQL and data engineering 33 | ⚠️ **Ramp-up Investment:** Will need dedicated mentoring for first 3-6 months 34 | 35 | ## Development Plan Required 36 | 1. **Month 1-2:** Intensive SQL training and basic data pipeline concepts 37 | 2. **Month 3-4:** API integration training and real project shadowing 38 | 3. **Month 5-6:** Independent project with close supervision 39 | 4. **Ongoing:** Regular check-ins and skill development tracking 40 | 41 | ## Key Risks 42 | - **Initial Productivity:** Will be below target for first quarter 43 | - **Learning Curve:** May struggle with complex technical challenges initially 44 | - **Mentoring Resources:** Requires senior team member time investment 45 | 46 | ## Mitigation Strategies 47 | - Assign dedicated technical mentor for first 6 months 48 | - Start with smaller, well-defined projects 49 | - Provide access to technical training resources 50 | - Set realistic performance expectations for initial period 51 | 52 | ## Long-term Potential 53 | High - candidate shows strong fundamentals and growth mindset that suggest they could become a valuable team member within 6-12 months with proper support. 54 | 55 | --- 56 | 57 | *Evaluation completed by: David Martinez (Senior Analyst) & Jennifer Clark (HR Manager)* 58 | *This evaluation was generated following the Elly Analytics hiring framework on March 30, 2024* 59 | 60 | --- 61 | 62 | *Template Usage Note: This demonstrates how to evaluate candidates who have potential but require development investment. Shows structured decision-making for borderline candidates.* 63 | -------------------------------------------------------------------------------- /scripts/sales-meeting-automation/prompt_internal.txt: -------------------------------------------------------------------------------- 1 | # Sales Meeting Analysis Agent for Demo 2 | 3 | You are an expert sales analyst specializing in creating detailed meeting summaries between our sales team and potential clients. 4 | 5 | ## Company Context 6 | 7 | **Our Company** is a full-funnel marketing analytics platform for ad-driven lead generation businesses. We help companies: 8 | - Unify data from all marketing and sales sources into a single system 9 | - Apply advanced attribution models to understand true campaign ROI 10 | - Track complete customer journey from first click to repeat purchases 11 | - Optimize media buying based on real LTV and conversion data 12 | 13 | **Our Target Audience**: SMB and mid-market companies ($3M-$100M revenue) in: 14 | - B2C SaaS subscriptions without B2B component 15 | - Lead-generation services (real estate, healthcare, legal, finance, education) 16 | - eCommerce with long purchase cycles and high LTV 17 | - Subscription-based businesses 18 | 19 | **Common Client Problems** we solve: 20 | - Data fragmentation between ad platforms, CRM, and website analytics 21 | - Inaccurate attribution (over-attribution from ad platforms, under-attribution organic/direct) 22 | - Manual data consolidation in Google Sheets 23 | - Inability to track full-funnel from click to revenue 24 | - Uncertainty in scaling decisions for paid acquisition 25 | 26 | --- 27 | 28 | ## Analysis Instructions 29 | 30 | Your task is to analyze the meeting transcript between our sales team and a potential client, and create a detailed structured summary for internal team use. 31 | 32 | **Important Principles:** 33 | 1. **Focus on client, not us** - 80% of content should describe client's business, problems, and context 34 | 2. **Maximum detail** - include all mentioned numbers, tool names, people names, specific cases 35 | 3. **Objectivity** - don't embellish or interpret, only facts from conversation 36 | 4. **Structure** - use clear sections with emojis for easy reading 37 | 5. **Context**: All meetings are with leads - anyone except our sales team is the prospect 38 | 6. **Client Business**: If unclear what client does, check meeting title (usually "Client Company + Our Company") 39 | 40 | --- 41 | 42 | ## Output Format 43 | 44 | 🎯 **Meeting Purpose** 45 | - Meeting type (discovery, demo, pricing, negotiation) 46 | - Brief overview in 2-3 sentences 47 | 48 | 👥 **Client Overview** 49 | - Business name and type (B2B/B2C etc.) 50 | - What they do 51 | 52 | 💻 **Current Tech Stack and Media Buying** *(only if discussed)* 53 | - Advertising channels 54 | - Budgets (include numbers if mentioned, otherwise "not discussed") 55 | - CRM/Backend systems (be specific about what they use) 56 | - Marketing tools 57 | - Analytics stack 58 | 59 | 🔥 **Problems and Pain Points** *(only if discussed)* 60 | - Specific problems with examples 61 | - Include everything discussed by the client, not sales team 62 | 63 | 📝 **Key Discussion Points** 64 | - 3-5 most important topics discussed in detail 65 | - Should include client-specific information not covered above 66 | 67 | 🎯 **Next Steps** 68 | - Agreements made 69 | - Materials to prepare 70 | - Decision timeline 71 | 72 | --- 73 | 74 | **Important:** 75 | - If section isn't relevant - don't include it 76 | - Maximum 1200 words 77 | - Use bullet points and clear structure 78 | - Focus on actionable information for the team 79 | - Include only topics actually discussed in the meeting 80 | -------------------------------------------------------------------------------- /Docs/SalesAndMarketing/Client-Meetings-Analysis/AI-Review-Update-Process.md: -------------------------------------------------------------------------------- 1 | # 🔄 AI Analysis Update Process for Marketing 2 | 3 | ## 🎯 Process Goal 4 | Automatically identify projects ready for testimonial collection and case studies based on weekly status analysis. 5 | 6 | --- 7 | 8 | ## 📅 Update Schedule 9 | 10 | ### **Weekly (Sunday)**: 11 | 1. AI analyzes project cards in `Projects/Status-Projects/` 12 | 2. Updates `AI-Projects-Review-Analysis.md` 13 | 3. Sends notification to Marketing Team about changes 14 | 15 | ### **On Status Changes**: 16 | - When project transitions to ready state → immediate update 17 | - When testimonial received → update with completion mark 18 | 19 | --- 20 | 21 | ## 🤖 AI Analysis Criteria 22 | 23 | ### ✅ **READY for testimonial collection**: 24 | - Status: "Completed" / "Stable operation" / "Before defense" 25 | - Last update: < 2 weeks ago 26 | - No critical issues 27 | - Client actively using system 28 | 29 | ### 🟡 **CLOSE to readiness**: 30 | - Status: "Launch stage" / "Final work" 31 | - Progress: > 80% 32 | - Planned completion: < 4 weeks 33 | 34 | ### 🔴 **NOT READY**: 35 | - Status: "On hold" / "Blocked" / "Critical issues" 36 | - Client dependency 37 | - Technical problems 38 | 39 | --- 40 | 41 | ## 📊 Updated Sections 42 | 43 | ### 1. **AI Summary** 44 | - Number of analyzed projects 45 | - Client readiness for testimonial collection: completed projects + stable operations 46 | - Number of ready case studies 47 | 48 | ### 2. **Project Completion Readiness** 49 | - Ready for immediate testimonial collection (integration completed) 50 | - Stably operating (ready for success story) 51 | - Showing progress (ready in next 4 weeks) 52 | 53 | ### 3. **Marketing Recommendations** 54 | - Immediate actions (this week) 55 | - Planned actions (next month) 56 | - Project monitoring 57 | 58 | ### 4. **Detailed Status Changes** 59 | - Positive changes with AI insights 60 | - Projects in development 61 | - Problem projects with potential 62 | 63 | ### 5. **Expected Results** 64 | - Immediate opportunities 65 | - Short-term plans 66 | 67 | --- 68 | 69 | ## 🎬 Demo Update Scenario 70 | 71 | ### **"How this works in practice"**: 72 | 73 | 1. **Initial State**: 74 | - 5 projects in different statuses 75 | - Some in development, some on hold 76 | 77 | 2. **After Team Meeting**: 78 | - Transcript shows: 3 projects completed integration 79 | - 1 project operating stably, 1 showing progress 80 | 81 | 3. **AI Summary Generated**: 82 | - "3 completed projects ready for immediate testimonial collection" 83 | - "1 stable operation ready for success story" 84 | - "4 case studies that can be created" 85 | 86 | 4. **Marketing Actions**: 87 | - PRIORITY #1: Video testimonial from completed project 88 | - Prepare 3 case studies on integrations 89 | - Success story on stable operation 90 | 91 | --- 92 | 93 | ## 📈 Process Results 94 | 95 | ### **Weekly**: 96 | - AI Summary with number of ready projects 97 | - Specific numbers: X completed projects + Y stable operations = Z case studies 98 | - Prioritized marketing actions 99 | 100 | ### **Monthly**: 101 | - 2-3 new case studies on integrations 102 | - 2-3 video testimonials from satisfied clients 103 | - Success stories on stably operating projects 104 | 105 | --- 106 | 107 | **Process Owner**: AI + Marketing Team 108 | **Storage Location**: `Marketing-Sales/Client-Meetings-Analysis/` 109 | **Main File**: `AI-Projects-Review-Analysis.md` 110 | -------------------------------------------------------------------------------- /Docs/SePersonalCRM/MainCRM/Contacts/Contact-D/Contact-D.md: -------------------------------------------------------------------------------- 1 | # Contact D - Profile 2 | 3 | **Role**: Growth at Company AA, Partner at VC Fund H, Education Platform BB Course Creator [CANONICAL] 4 | **Contact Date**: July 2024 (First intro), November 4, 2025 (Reconnection) [CANONICAL] 5 | **Context**: World-renowned growth expert, reconnected via Angel Investor K 6 | 7 | **Communication Channels**: 8 | - **Email**: contact.d@example.com [CANONICAL] 9 | - **LinkedIn**: [ANONYMIZED_LINKEDIN_URL] [CANONICAL - Verified Nov 5, 2025] 10 | - **Website**: [ANONYMIZED_WEBSITE] 11 | 12 | --- 13 | 14 | ## Professional Background 15 | [CANONICAL: LinkedIn Nov 5, 2025, see Contact-D-linkedin.md for full profile] 16 | 17 | ### Current Roles (2025): 18 | - **Growth** at Company AA (May 2025 - Present) 19 | - **Partner** at VC Fund H (Oct 2023 - Present) 20 | - **Program Creator & Partner** at Education Platform BB (Nov 2016 - Present) 21 | - Created: Growth Leadership, Experimentation and Testing, Monetization and Pricing, Product-Led Growth courses 22 | 23 | ### Advisory & Board Roles: 24 | - **Board Member**: Company EE (Oct 2021 - Jul 2025) 25 | - **Advisor**: Company CC, Company DD, Company GG (former), Company HH (former) 26 | - **Former Advisories**: Company TT, Company QQ, Company SS, Company UU, and 15+ other major tech companies 27 | 28 | ### Previous Executive Experience: 29 | - **Tech Company FF**: Growth (Aug 2023 - Mar 2025) 30 | - **Company NN**: Interim Head of Growth (Feb 2022 - Feb 2023) 31 | - **Company VV**: SVP Consumer Product & Growth (Apr 2017 - May 2019) 32 | - **Company YY**: SVP Growth (7.5 years total, Nov 2009 - Apr 2017) 33 | - Built from Data Analyst → Manager → Director → VP → SVP 34 | - Built product growth, growth marketing, and data teams 35 | 36 | ### Expertise: 37 | - Product-Led Growth (PLG) 38 | - Monetization & Pricing 39 | - Growth Leadership 40 | - Experimentation & Testing 41 | - Building and scaling growth teams 42 | 43 | --- 44 | 45 | ## Relationship to Elly Analytics 46 | 47 | **Why Relevant**: 48 | 1. **Growth Expert**: World-renowned PLG and growth strategy expert 49 | 2. **Education Platform BB**: Created major growth courses, teaching thousands of growth leaders 50 | 3. **VC Fund H Partner**: Investment partner with Person F 51 | 4. **Advisory Experience**: Advised 30+ major tech companies (Company TT, Company QQ, Tech Company FF, etc.) 52 | 5. **Connection**: Angel Investor K intro/reconnection 53 | 54 | **Potential Value**: 55 | - Growth strategy advisory for Company Zeta's AI product scaling 56 | - Introduction to VC Fund H / Person F for fundraising 57 | - PLG expertise for self-serve expansion 58 | - Network access to growth leaders and investors 59 | 60 | --- 61 | 62 | ## Communication History 63 | 64 | ### July 2024 - First Introduction 65 | **Introducer**: Angel Investor K 66 | - Initial connection made 67 | - Introductory conversation 68 | 69 | ### November 4, 2025 - Reconnection 70 | **Reconnection**: Angel Investor K 71 | - Angel Investor K: "Contact D, Person B, Person E, happy to reconnect you" 72 | - Rekindling relationship with Company Zeta founders 73 | 74 | ### November 4, 2025 - Response 75 | - Contact D responded to reconnection 76 | 77 | --- 78 | 79 | ## Email Communication 80 | [CANONICAL: Gmail sync November 5, 2025] 81 | 82 | **Email Communication Summary** (5 emails, Jul 2024 - Nov 2025): 83 | Initial intro via Angel Investor K July 2024, reconnection Nov 2025. 84 | 85 | **Full email history**: [Contact-D-emails.md](./Contact-D-emails.md) 86 | 87 | --- 88 | 89 | **Last Updated**: November 5, 2025 90 | 91 | 92 | -------------------------------------------------------------------------------- /setup/update-all.sh: -------------------------------------------------------------------------------- 1 | #!/bin/bash 2 | 3 | # ⚠️ CONFIGURATION REQUIRED ⚠️ 4 | # Before running this script, customize these variables for your organization: 5 | 6 | # TODO: Replace with your development repository names (same as in clone-all-repos.sh) 7 | # Examples: ("MyApp" "MyAPI" "MyMobileApp") or ("Frontend" "Backend" "Mobile") 8 | DEV_REPOS=("YOUR-PRODUCT-1" "YOUR-PRODUCT-2" "YOUR-PRODUCT-3") 9 | 10 | # ============================================================================ 11 | # Configuration check 12 | if [[ " ${DEV_REPOS[*]} " =~ " YOUR-PRODUCT-1 " ]]; then 13 | echo "⚠️ CONFIGURATION REQUIRED" 14 | echo "" 15 | echo "Before running this script, you need to customize it for your organization:" 16 | echo "" 17 | echo "1. Open this file: setup/update-all.sh" 18 | echo "2. Replace the DEV_REPOS array with your actual repository names" 19 | echo " (should match what you configured in clone-all-repos.sh)" 20 | echo "" 21 | echo "Example configuration:" 22 | echo ' DEV_REPOS=("MyMainApp" "MyAPI" "MyDashboard")' 23 | echo "" 24 | echo "💡 Pro tip: Ask your AI assistant to help customize this script!" 25 | exit 1 26 | fi 27 | 28 | echo "🔄 Updating AI First Workspace Template..." 29 | echo "" 30 | 31 | # Update workspace repository itself 32 | echo "📋 Updating workspace template..." 33 | git pull 34 | echo "" 35 | 36 | # Array of documentation repositories 37 | doc_repos=("Strategy" "Product" "SalesAndMarketing" "Operations" "Operations/Hiring" "Finance" "Legal-HR") 38 | 39 | # Update documentation repositories in Docs/ 40 | echo "📚 Updating Documentation repositories..." 41 | for repo in "${doc_repos[@]}"; do 42 | repo_path="Docs/$repo" 43 | if [ -d "$repo_path" ]; then 44 | echo "📱 Updating $repo repository..." 45 | (cd "$repo_path" && git pull) || echo " ⚠️ Update failed (possibly empty repository)" 46 | else 47 | echo "ℹ️ $repo repository not yet cloned (run ./setup/clone-all-repos.sh)" 48 | fi 49 | done 50 | echo "" 51 | 52 | # Update development repositories in Dev/ 53 | echo "💻 Updating Development repositories..." 54 | for repo in "${DEV_REPOS[@]}"; do 55 | repo_path="Dev/$repo" 56 | if [ -d "$repo_path" ]; then 57 | echo "⚙️ Updating $repo repository..." 58 | (cd "$repo_path" && git pull) || echo " ⚠️ Update failed (possibly empty repository)" 59 | else 60 | echo "ℹ️ $repo repository not yet cloned (run ./setup/clone-all-repos.sh)" 61 | fi 62 | done 63 | echo "" 64 | 65 | # Update Presales repository 66 | echo "💼 Updating Presales repository..." 67 | if [ -d "Presales" ]; then 68 | echo "🎯 Updating Presales repository..." 69 | (cd Presales && git pull) || echo " ⚠️ Update failed (possibly empty repository)" 70 | else 71 | echo "ℹ️ Presales repository not yet cloned (run ./setup/clone-all-repos.sh)" 72 | fi 73 | echo "" 74 | 75 | # Update Projects repository 76 | echo "🚀 Updating Projects repository..." 77 | if [ -d "Projects/.git" ]; then 78 | echo "📊 Updating Projects repository..." 79 | (cd Projects && git pull) || echo " ⚠️ Update failed for Projects repository" 80 | else 81 | echo "ℹ️ Projects repository not yet cloned (run ./setup/clone-all-repos.sh)" 82 | fi 83 | echo "" 84 | 85 | echo "🎉 Workspace update complete!" 86 | echo "" 87 | echo "📊 Summary:" 88 | echo " 📚 Documentation repos in Docs/" 89 | echo " 💻 Development repos in Dev/ (${DEV_REPOS[*]})" 90 | echo " 🚀 Project repos in Projects/" 91 | echo " 💼 Presales repo in root level" 92 | echo "" 93 | echo "💡 To add a new client project:" 94 | echo " cd Projects && git clone " -------------------------------------------------------------------------------- /Docs/Operations/Hiring/Job-Openings/Senior-Marketing-Analyst/Candidates/Example-Candidate-A-Strong/Fathom-Screening-Interview.md: -------------------------------------------------------------------------------- 1 | # Screening Interview Transcript 2 | *[TEMPLATE EXAMPLE - This is a fictional interview transcript for demonstration purposes]* 3 | 4 | **Candidate:** Sarah Johnson 5 | **Interviewer:** Emily Roberts (HR Manager) 6 | **Date:** March 15, 2024 7 | **Duration:** 45 minutes 8 | **Position:** Senior Marketing Analyst 9 | 10 | --- 11 | 12 | ## Company Introduction & Role Overview 13 | 14 | **Emily Roberts:** Hi Sarah! Thank you for joining us today. I'd like to start by giving you an overview of our company and the role we're discussing. 15 | 16 | We're a marketing analytics consultancy working with mid-to-enterprise clients who spend $20K+ monthly on digital advertising. We provide subscription-based analytics services with a focus on long-term partnerships. 17 | 18 | The analyst role is quite hands-on - you'd be involved from initial requirements gathering through implementation and ongoing optimization. About 80% of your time would be in SQL and data processing, with 20% in Power BI for visualization. 19 | 20 | Does this align with what you were expecting from the role? 21 | 22 | **Sarah Johnson:** Yes, absolutely. That actually sounds very similar to the structure I worked with at DataDriven Solutions. 23 | 24 | ## Technical Experience Deep Dive 25 | 26 | **Emily Roberts:** Great! Can you walk me through your experience with marketing attribution modeling? 27 | 28 | **Sarah Johnson:** Sure. At TechFlow, I built a multi-touch attribution model processing about 100 million touchpoints monthly across 12 digital channels. The result was a 22% budget reallocation that generated about $800K in incremental revenue. 29 | 30 | **Emily Roberts:** How would you rate your SQL skills on a scale of 1-10? 31 | 32 | **Sarah Johnson:** I'd say an 8. I'm very comfortable with complex joins, window functions, CTEs, and performance optimization. I've built data pipelines that process millions of records daily. 33 | 34 | **Emily Roberts:** What about your experience with external client communication? 35 | 36 | **Sarah Johnson:** I have significant client-facing experience from my agency days. I regularly presented to C-level executives and can adapt my communication style based on the audience's technical background. 37 | 38 | ## Motivation & Career Goals 39 | 40 | **Emily Roberts:** What's driving your interest in making a move right now? 41 | 42 | **Sarah Johnson:** I'm looking for a role where I can have more direct impact on business outcomes. I'm drawn to the consulting model because each client presents unique challenges. 43 | 44 | **Emily Roberts:** Where do you see your career heading in the next 2-3 years? 45 | 46 | **Sarah Johnson:** I'd like to become a subject matter expert in marketing analytics while developing stronger business acumen. Eventually, I could see myself leading a small team of analysts. 47 | 48 | ## Next Steps 49 | 50 | **Emily Roberts:** Our next step would be a technical interview with our Lead Analyst. We'll send you a business case study to review beforehand. 51 | 52 | **Sarah Johnson:** That sounds great. I'm excited to dive into a real business case. 53 | 54 | --- 55 | 56 | ## Interview Assessment 57 | 58 | **Technical Competency:** Strong SQL skills, relevant attribution modeling experience 59 | **Communication:** Excellent client-facing experience 60 | **Cultural Fit:** Collaborative mindset, growth-oriented 61 | **Overall Assessment:** Strong candidate, proceed to technical interview 62 | 63 | --- 64 | 65 | *Template Note: This demonstrates a structured screening interview format. Customize based on your role requirements.* 66 | 67 | 68 | -------------------------------------------------------------------------------- /Projects/Status-Projects/Client-Beauty1-Status-Card.md: -------------------------------------------------------------------------------- 1 | # 🌺 Client-Beauty1 - Beauty E-commerce 2 | **Status**: 🔧 Active Development 3 | **Analyst**: Analyst1 4 | **Developer**: Developer1 5 | **Team Lead**: Team Lead1 6 | **Industry**: Beauty E-commerce 7 | **Last Update**: 11.08.2025 8 | 9 | ## 🏷️ Information Sources 10 | - `[MEETING:2025-08-11]` - Team Meeting Transcript - Project Status Review 11 | - `[PORTFOLIO:ACTIVE]` - Active development project 12 | 13 | ## 🔧 Current Status 14 | **Active - Working on blogger attribution and expense tracking improvements** 15 | 16 | ## 🔄 Latest Updates (11.08.2025) 17 | **Blogger Attribution Work in Progress** [MEETING:2025-08-11]: 18 | - Fixed blogger attribution and promo code tracking issues 19 | - Clarified with client about July blogger list (no new additions) 20 | - Updated blogger categories to link specific influencers to their promo codes 21 | - **Action Required**: Need to remind client to switch manual expenses from generic categories (Instagram influencers, UGC) to specific blogger names 22 | - Technical implementation completed - waiting on client data update 23 | 24 | ## 🔧 Technical Implementation 25 | **Current Work**: 26 | - ✅ Blogger attribution system fixed 27 | - ✅ Promo code tracking linked to specific influencers 28 | - ✅ July blogger list verified with client (no new additions) 29 | - 🔄 Awaiting client to update manual expense categorization 30 | - 🔄 Transition from generic categories to specific blogger names 31 | 32 | **System Changes Made**: 33 | - **Before**: Generic categories (Instagram influencers, UGC, other influencers) 34 | - **After**: Specific blogger names linked to their individual promo codes 35 | - **Remaining**: Client needs to update their manual expense entries to match new structure 36 | 37 | ## 📊 Project Status 38 | - **Attribution System**: Fixed and operational 39 | - **Data Structure**: Updated to specific blogger tracking 40 | - **Client Action Required**: Update manual expense categories 41 | - **Technical Blockers**: None - waiting on client data update 42 | 43 | ## 🎯 Next Steps 44 | 1. **Remind client** to switch manual expenses to specific blogger names (from generic categories) 45 | 2. **Monitor** blogger list for any new additions 46 | 3. **Verify** expense categorization after client update 47 | 4. **Continue** regular status meetings 48 | 49 | ## 📋 Active Tasks 50 | - [x] Fix blogger attribution system 51 | - [x] Link promo codes to specific influencers 52 | - [x] Verify July blogger list with client 53 | - [ ] Client updates manual expense categories (CLIENT ACTION) 54 | - [ ] Verify data accuracy after client update 55 | 56 | ## 🔍 Key Issues Resolved 57 | **Attribution Problem**: Fixed the system that tracks blogger performance via promo codes 58 | **Data Structure**: Transitioned from generic influencer categories to specific blogger tracking 59 | **Client Alignment**: Confirmed no new bloggers added in July 60 | 61 | ## 💡 Business Impact 62 | **Improved Tracking Accuracy**: 63 | - Better attribution of sales to specific bloggers 64 | - More accurate ROI calculation per influencer 65 | - Clearer expense tracking and reporting 66 | - Enhanced data quality for decision-making 67 | 68 | ## 📝 Team Communication 69 | - **Last Meeting**: August 11, 2025 70 | - **Participants**: Developer1, Analyst1, Team Lead1 71 | - **Next Action**: Follow up with client on expense categorization 72 | - **Meeting Frequency**: Weekly team status reviews 73 | 74 | **Developer**: Developer1 75 | **Analyst**: Analyst1 76 | **Team Lead**: Team Lead1 77 | **Next Review**: Weekly team status meeting 78 | **Priority**: Medium - Awaiting client action on expense categorization 79 | **Client Communication Required**: Yes - Remind about manual expense update -------------------------------------------------------------------------------- /Docs/Operations/Hiring/Job-Openings/Senior-Marketing-Analyst/Candidates/Example-Candidate-A-Strong/Final-Score.md: -------------------------------------------------------------------------------- 1 | # Final Candidate Score - John Doe 2 | 3 | > **NOTE: This document represents the FINAL hiring decision based on complete candidate assessment.** 4 | 5 | ## Technical Competency: 6/10 6 | Strong SQL (4/5) and ETL (4/5) skills, but critical deficiency in API Integration (1/5) is concerning for our tech stack. Data visualization skills (3/5) are adequate but not exceptional. Technical foundation is strong in some areas but has significant gaps in required competencies. 7 | 8 | ## Experience Relevance: 7/10 9 | Extensive marketing analytics experience across diverse industries, with particular strength in campaign analysis (5/5). Background in Applied Mathematics provides solid analytical foundation, but appears to lack experience with modern marketing integration technologies. 10 | 11 | ## Cultural Fit: 5/10 12 | Communication skills appear strong (5/5), but red flags in teamwork (2/5) and problem-solving (2/5) indicate potential issues working in our collaborative environment. Limited documentation experience suggests potential gaps in our knowledge-sharing culture. 13 | 14 | ## Communication Skills: 7/10 15 | Strong communication capabilities (5/5) but may be undermined by weak teamwork ratings. B2 English level is sufficient but not exceptional for client-facing work. Technical communication abilities need further verification. 16 | 17 | ## Overall Score: 6.25/10 18 | 19 | ## Final Hiring Decision 20 | - [ ] Extend Offer 21 | - [ ] Keep in Talent Pool 22 | - [X] Reject 23 | 24 | ## Decision Maker 25 | Yulia Kuzmane, Head of Operations 26 | 27 | ## Decision Date 28 | June 12, 2025 29 | 30 | ## Primary Rejection Reason 31 | **Career Misalignment**: During the interview process, it became clear that John Doe is primarily interested in business-oriented positions rather than technical roles. His career aspirations are directed toward management and business strategy, which do not align with this technical Senior Marketing Analyst position that requires deep engagement with data integration, API development, and technical implementation. 32 | 33 | ### Key Quotations Demonstrating Misalignment: 34 | 35 | > "I see myself moving into a more strategic role in the next 2-3 years, ideally heading a marketing department where I can make high-level business decisions rather than focusing on the technical implementation." - When asked about career goals 36 | 37 | > "While I can certainly handle the technical aspects, what really excites me is translating data into business strategy and managing cross-functional teams." - When discussing day-to-day responsibilities 38 | 39 | > "I'm less interested in building the data pipelines myself and more focused on the insights we can derive for business strategy." - When asked about API integration experience 40 | 41 | > "My ideal next step would be a role that positions me to move into marketing management. I'm looking to transition away from the purely technical side of analytics." - When discussing why he's interested in this position 42 | 43 | These statements clearly indicate a preference for business strategy and management over the technical implementation that is central to this role. 44 | 45 | ## Additional Considerations 46 | * Technical gaps in API integration capabilities 47 | * Concerns about teamwork and collaboration in a technical environment 48 | * Limited interest in the deeper technical aspects of the role 49 | 50 | *While John has strong marketing domain knowledge and some technical skills, his career interests are fundamentally misaligned with this technical role. We recommend considering him for more business-oriented positions in the future if they become available, but he is not suitable for this technically focused Senior Marketing Analyst position.* 51 | -------------------------------------------------------------------------------- /Docs/SePersonalCRM/MainCRM/Inbox/logs/2025-11-11-batch10-inbox-to-processing-log.md: -------------------------------------------------------------------------------- 1 | # Stage 1 Log: Inbox → Processing Tasks (Batch 10) 2 | 3 | **Date**: 2025-11-11 4 | **Batch**: 10 5 | **Messages Processed**: 1 6 | 7 | --- 8 | 9 | ## Message Source 10 | 11 | **Voice message** from AI Inbox (Telegram) 12 | - **Message ID**: 12345678 13 | - **Timestamp**: 2025-11-10T23:47:03+00:00 14 | - **Duration**: ~2 minutes (5.7MB OGG file) 15 | - **Transcription**: OpenAI Whisper API (Telegram native transcription failed with MSG_VOICE_TOO_LONG) 16 | 17 | --- 18 | 19 | ## Content Summary 20 | 21 | Meeting with **Contact A** ([Company Alpha] CEO) on Monday November 10, 2025: 22 | 23 | ### Key Points: 24 | 1. **Meeting Details**: [Location A], 30-minute conversation 25 | 2. **Partnership Agreement**: [COMPANY_NAME] included in [Company Alpha] developer beta program with API access 26 | 3. **Co-marketing Opportunity**: They're launching co-marketing soon (webinars, streams, posts) 27 | 4. **First Feature**: URL → multiple ad variations for testing 28 | 5. **Competitive Intelligence**: [Company Beta] ad generation capabilities 29 | 6. **Business Model**: Currently organic + affiliates, B2C focus, no major clients yet 30 | 7. **Future Vision**: Expect shift to larger advertisers within 12 months 31 | 8. **Partnership Interest**: Looking for professional partners (agents + ad data + video) 32 | 33 | --- 34 | 35 | ## Processing Tasks Created 36 | 37 | Created **5 tasks** in `processing_tasks.md`: 38 | 39 | ### Task 1: Update Contact A Contact Profile 40 | - Add meeting notes (date, location, duration) 41 | - Document beta program access agreement 42 | - Add co-marketing discussions 43 | - Note GTM strategy (organic, affiliates, B2C) 44 | - Note affiliate program challenges 45 | 46 | ### Task 2: Update Contacts_Actual.md 47 | - Update one-line status: "Met Nov 10 at [Location A], included in [Company Alpha] API beta program, co-marketing discussions" 48 | - Update tasks with new commitments: 49 | - Contact A: Include [COMPANY_NAME] in beta developer program 50 | - Our side: Explore partnership (agents + data + video) 51 | - Our side: Follow up on co-marketing launch 52 | 53 | ### Task 3: Document Competitive Intelligence 54 | - Add [Company Beta] competitor note to Strategy/Competitors 55 | - Key facts: 56 | - Only [Company Alpha] and [Company Beta] do interesting ad generation 57 | - [Company Beta] can copy hooks, offers, scenarios from reference ads 58 | - Technology only for [Platform B] Creative Partner agencies (certification required) 59 | 60 | ### Task 4: Track Co-Marketing Opportunity 61 | - Monitor for [Company Alpha] co-marketing launch 62 | - First feature: URL → multiple variations 63 | - Format: webinars, streams, posts 64 | 65 | ### Task 5: Partnership Assessment (Decision Needed) 66 | - [Company Alpha] wants partners with: AI agents + ad effectiveness data + video generation 67 | - They're interested in "professional partners like [COMPANY_NAME]" for larger scale 68 | - Question: Should we prioritize this partnership? 69 | 70 | --- 71 | 72 | ## Context Loaded 73 | 74 | - ✅ Personal Context 75 | - ✅ Strategy Context 76 | - ✅ CRM Context 77 | - ✅ Contacts_Actual.md (searched for Contact A - found existing entry) 78 | - ✅ work_tasks.md 79 | 80 | --- 81 | 82 | ## Checkpoint 1 Result 83 | 84 | **Status**: ✅ Approved by user ("good") 85 | **Action**: Proceed to archive message and complete Stage 1 86 | 87 | --- 88 | 89 | ## Next Steps 90 | 91 | **Stage 2**: Execute processing tasks 92 | - Update contact profiles 93 | - Update Contacts_Actual.md 94 | - Document competitive intelligence 95 | - Assess partnership decision 96 | 97 | **Stage 3**: User works on resulting work tasks 98 | 99 | --- 100 | 101 | **Log Created**: 2025-11-11T11:45:00 102 | **Stage 1 Complete**: ✅ 103 | 104 | -------------------------------------------------------------------------------- /Docs/SePersonalCRM/MainCRM/Inbox/logs/README.md: -------------------------------------------------------------------------------- 1 | # Processing Logs 2 | 3 | This folder contains detailed logs of all inbox processing sessions. 4 | 5 | --- 6 | 7 | ## Log Types 8 | 9 | ### **Stage 1: Inbox → Processing Tasks** 10 | **Filename:** `YYYY-MM-DD-inbox-to-processing-log.md` 11 | 12 | **Purpose:** Documents transfer of messages from inboxes to Processing Tasks 13 | 14 | **Contains:** 15 | - Source messages with timestamps 16 | - Decomposition into processing steps 17 | - Which processing tasks were created 18 | - NO execution details (that's Stage 2) 19 | 20 | **Example:** `2025-11-03-inbox-to-processing-log.md` 21 | 22 | --- 23 | 24 | ### **Stage 2: Processing Tasks Execution** 25 | **Filename:** `YYYY-MM-DD-processing-execution-log.md` 26 | 27 | **Purpose:** Documents execution of processing tasks 28 | 29 | **Contains:** 30 | - What information was gathered 31 | - Which profiles/files were updated 32 | - What work tasks were created 33 | - Time spent, decisions needed 34 | - Full execution details 35 | 36 | **Example:** `2025-11-03-processing-execution-log.md` 37 | 38 | --- 39 | 40 | ## Why Two Stages? 41 | 42 | **Problem:** When you have multiple inboxes (email, Telegram, LinkedIn, AI inbox), processing items one-by-one can miss dependencies. 43 | 44 | **Example:** 45 | - Email: "Meeting with Fund X postponed" 46 | - Telegram: "Fund X wants intro call Friday" 47 | - LinkedIn: "Fund X partner connected" 48 | 49 | If you process email first (mark meeting postponed), you miss that Telegram/LinkedIn have updates about the same fund! 50 | 51 | **Solution:** 52 | 1. **Stage 1:** Collect ALL updates from ALL inboxes first 53 | 2. **Review:** See all related items together 54 | 3. **Stage 2:** Process with full context, spot connections, avoid duplicate work 55 | 56 | --- 57 | 58 | ## Log Naming Convention 59 | 60 | **Format:** `YYYY-MM-DD-[process-type]-log.md` 61 | 62 | **Process Types:** 63 | - `inbox-to-processing` - Stage 1 (collection) 64 | - `processing-execution` - Stage 2 (execution) 65 | - `bulk-sync` - Large sync operations (e.g., sync all Telegram contacts) 66 | - `cleanup` - Archive/cleanup operations 67 | - `migration` - Data migration tasks 68 | 69 | **Examples:** 70 | - `2025-11-03-inbox-to-processing-log.md` 71 | - `2025-11-03-processing-execution-log.md` 72 | - `2025-11-05-bulk-sync-log.md` 73 | 74 | --- 75 | 76 | ## Usage 77 | 78 | ### When Processing Inbox: 79 | 80 | **Stage 1:** 81 | ```bash 82 | # Load all inboxes 83 | python3 telegram_inbox_sync.py # AI inbox 84 | python3 gmail_sync.py --all # Email 85 | # (future: LinkedIn, etc.) 86 | 87 | # Create inbox-to-processing log 88 | # Agent creates processing tasks 89 | ``` 90 | 91 | **Stage 2:** 92 | ```bash 93 | # Review processing_tasks.md 94 | # Execute all tasks 95 | 96 | # Create processing-execution log 97 | # Agent updates profiles, creates work tasks 98 | ``` 99 | 100 | ### Finding Logs: 101 | 102 | **By date:** `ls -la | grep 2025-11-03` 103 | **By type:** `ls -la | grep inbox-to-processing` 104 | **Recent:** `ls -lat | head -5` 105 | 106 | --- 107 | 108 | ## Archive Policy 109 | 110 | **Keep:** 111 | - Last 90 days: All logs 112 | - 90-365 days: Monthly summary logs only 113 | - 365+ days: Quarterly summary logs only 114 | 115 | **Archive to:** `logs/archive/YYYY/` when logs get old 116 | 117 | --- 118 | 119 | ## References 120 | 121 | **Related Files:** 122 | - `../telegram ai inbox archive.md` - Archived inbox messages (links to these logs) 123 | - `../processing_tasks.md` - Active processing tasks 124 | - `../../Tasks/work_tasks.md` - Work tasks created from processing 125 | 126 | **Workflow Docs:** 127 | - `../inbox_processing_rules.md` - Complete inbox processing guide (two-stage system, examples, rules) 128 | 129 | --- 130 | 131 | **Last Updated:** November 3, 2025 132 | 133 | -------------------------------------------------------------------------------- /scripts/sales-meeting-automation/README.md: -------------------------------------------------------------------------------- 1 | # Automated Sales Meeting Processing - Demo 2 | 3 | 🚀 **Demo system for processing Fireflies.ai meeting transcripts and creating structured client profiles.** 4 | 5 | This is a demonstration version designed for presentations and workshops. It processes a specific demo meeting to show AI-powered sales automation capabilities. 6 | 7 | ## 🎯 Demo Meeting 8 | 9 | **Meeting:** Elly Analytics XS Discovery Call 10 | **Meeting ID:** `01K1ZF3FGSY686JHZV0QSFG57K` 11 | **URL:** https://app.fireflies.ai/view/Elly-Analytics-XS-discovery-call::01K1ZF3FGSY686JHZV0QSFG57K 12 | 13 | ## 🚀 Quick Start 14 | 15 | ### 1. Install Dependencies 16 | ```bash 17 | pip install -r requirements.txt 18 | ``` 19 | 20 | ### 2. Set Up Environment (Optional) 21 | ```bash 22 | cp .env.example .env 23 | # Edit .env with your API keys 24 | ``` 25 | 26 | ### 3. Run Demo 27 | ```bash 28 | python demo-meeting-processor.py 29 | ``` 30 | 31 | ## 📋 What It Does 32 | 33 | 1. **Fetches Meeting Transcript** from Fireflies.ai API 34 | 2. **Processes with AI** using two different analysis templates: 35 | - `prompt_internal.txt` - Internal team summary 36 | - `prompt_notion.txt` - Structured sales analysis 37 | 3. **Saves Results** in markdown format with timestamps 38 | 4. **Auto-detects Workspace** and saves files appropriately 39 | 40 | ## 📁 Output Files 41 | 42 | The script creates files in the `output/` directory: 43 | - `XS Discovery Call_prompt_internal_[timestamp].md` 44 | - `XS Discovery Call_prompt_notion_[timestamp].md` 45 | 46 | ## 🔧 Demo Mode 47 | 48 | **Without API Keys:** Script runs in demo mode with mock data 49 | **With API Keys:** Connects to real Fireflies.ai and OpenAI APIs 50 | 51 | ## 📊 Example Output 52 | 53 | ### Internal Summary 54 | ```markdown 55 | 🎯 **Meeting Purpose** 56 | - Discovery call with XS Corp 57 | - Initial exploration of marketing analytics needs 58 | 59 | 👥 **Client Overview** 60 | - XS Corp - B2C SaaS company 61 | - Subscription-based business model 62 | 63 | 💻 **Current Tech Stack** 64 | - Google Ads and Facebook campaigns 65 | - $50K monthly ad spend 66 | - Attribution challenges 67 | ``` 68 | 69 | ### Notion Summary 70 | ```markdown 71 | # 📌 Short Summary 72 | 73 | **Lead Information** 74 | - **Lead Source:** Inbound 75 | - **🚀 Next Step:** Meeting scheduled: Yes - Jan 22, 2024 76 | - **👤 Business Type:** B2C SaaS 77 | - **💸 Ad Spend & Channels:** $50K monthly - Google Ads, Facebook 78 | ``` 79 | 80 | ## 🎬 Live Demo Instructions 81 | 82 | 1. **Show Fireflies.ai** with the demo meeting 83 | 2. **Run the script** and explain the process 84 | 3. **Display results** showing AI-generated analysis 85 | 4. **Highlight key features:** 86 | - Automatic workspace detection 87 | - Dual analysis templates 88 | - Structured output format 89 | - Real-time processing 90 | 91 | ## 🔗 Integration Possibilities 92 | 93 | - **Notion:** Automatic client profile creation 94 | - **CRM Systems:** Lead scoring and data enrichment 95 | - **Slack/Teams:** Automated meeting summaries 96 | - **Email:** Follow-up action items 97 | 98 | ## ⚙️ Configuration 99 | 100 | The script automatically detects the workspace: 101 | - `Personal-Super-Agent-Ru` → Saves in this workspace 102 | - `Personal-Super-Agent` → Saves in this workspace 103 | - `ai-first-workspace-template` → Saves in this workspace 104 | 105 | ## 🎯 Use Cases 106 | 107 | - **Sales Teams:** Automated meeting summaries 108 | - **Account Managers:** Client profile building 109 | - **Marketing:** Lead qualification insights 110 | - **Management:** Pipeline analysis and coaching 111 | 112 | --- 113 | 114 | *This is a demonstration tool designed to showcase AI-powered sales automation capabilities. Perfect for presentations, workshops, and proof-of-concept demonstrations.* 115 | -------------------------------------------------------------------------------- /Docs/SePersonalCRM/MainCRM/Inbox/processing_tasks.md: -------------------------------------------------------------------------------- 1 | # Processing Tasks - New Information to Handle 2 | 3 | **Purpose:** Decompose complex "new information" items into actionable steps. Agent executes updates, moves decision points to Work Tasks. 4 | 5 | **Workflow:** 6 | 1. New info arrives → Added here with decomposed steps 7 | 2. Agent executes information gathering/updates 8 | 3. Decision points → Move to `../Tasks/work_tasks.md` 9 | 4. When complete → Mark done, archive 10 | 11 | --- 12 | 13 | ## 🟢 BATCH 10 - Contact A Meeting (Nov 10, 2025) 14 | 15 | **Source:** AI Inbox voice message transcribed Nov 11, 2025 16 | 17 | **Meeting Summary:** 18 | - Met Contact A ([Company Alpha] CEO) at [Location A] on Monday Nov 10, 30 min conversation 19 | - Key outcomes: Beta program access, partnership discussion, co-marketing opportunity 20 | - Important competitive intelligence about [Company Beta] and [Platform B] 21 | 22 | ### Task 1: Update Contact A Contact Profile ✅ 23 | - [x] Add meeting notes to profile (date: Nov 10, 2025, location: [Location A], duration: 30 min) 24 | - [x] Update partnership status: Agreed to include [COMPANY_NAME] in [Company Alpha] beta program with API access 25 | - [x] Add co-marketing discussion notes 26 | - [x] Note their GTM strategy: organic + affiliates, B2C focus, no major clients yet 27 | - [x] Note affiliate program challenges (abuse, building multi-tier) 28 | 29 | ### Task 2: Update Contacts_Actual.md - Contact A ✅ 30 | - [x] Update one-line status: "Met Nov 10 at [Location A], included in [Company Alpha] API beta program, co-marketing discussions" 31 | - [x] Update tasks section with new commitments: 32 | - Contact A: Include [COMPANY_NAME] in beta developer program with [Company Alpha] API access 33 | - Our side: Explore partnership opportunities (agents + ad effectiveness data + video generation) 34 | - Our side: Follow up on co-marketing when they launch (webinars/streams about URL→variations feature) 35 | 36 | ### Task 3: Document Competitive Intelligence - [Company Beta] ✅ 37 | - [x] Add competitor note to Strategy folder → `Docs/Strategy/Competitors/[company-beta]-[platform-b]-creative-partner-intel.md` 38 | - [x] Key facts documented: 39 | - Only [Company Alpha] and [Company Beta] do interesting ad generation 40 | - [Company Beta] can copy hooks, offers, scenarios from reference ads 41 | - Can parse good ad and recreate for different company/product 42 | - Technology only available to [Platform B] Creative Partner agencies (requires certification) 43 | - Strategic implications for [COMPANY_NAME] + [Company Alpha] partnership 44 | 45 | ### Task 4: Track Co-Marketing Opportunity ✅ 46 | - [x] Added to Contact A tasks in Contacts_Actual.md: Monitor for [Company Alpha] co-marketing launch 47 | - [x] Their first feature to co-market: URL → multiple ad variations for testing 48 | - [x] They plan: webinars, streams, posts 49 | - [x] Context: They haven't done any co-marketing yet, but starting soon 50 | 51 | ### Task 5: Partnership Opportunity Assessment ✅ 52 | **Information gathered for [Owner]'s decision:** 53 | - [x] [Company Alpha] wants to partner with companies that: 54 | - Make AI agents ✓ ([COMPANY_NAME] has AI agents) 55 | - Have ad effectiveness data ✓ ([COMPANY_NAME]'s core strength) 56 | - Generate video content ([Company Alpha] provides this) 57 | - [x] They're interested in "professional partners like [COMPANY_NAME]" for larger scale 58 | - [x] Context: They're moving from B2C small clients to larger scale (12-month timeline) 59 | - [x] Opportunity: Beta API access already granted, co-marketing planned 60 | 61 | **Decision for [Owner]**: Should we prioritize this partnership? All conditions align - we have what they want (agents + data), they have what enhances our offering (video generation). Consider priority level for integration work. 62 | 63 | --- 64 | 65 | **CHECKPOINT 1:** Review these tasks before archiving the inbox message. Confirm or request changes. 66 | 67 | -------------------------------------------------------------------------------- /Docs/SePersonalCRM/MainCRM/Contacts/Contact-C/Contact-C.md: -------------------------------------------------------------------------------- 1 | # Contact C - Profile 2 | 3 | Funnel stage: Target Identified 4 | Name: VC Fund G 5 | Site: [ANONYMIZED_URL] 6 | Investor type: Fund 7 | Person's role: Partner 8 | Investment stages: A, B, C 9 | Invests in: B2B SaaS 10 | LinkedIn: [ANONYMIZED_LINKEDIN_URL] 11 | Contact email: contact.c@example.com 12 | Telegram: #NOT_ON_TELEGRAM [Searched 2025-10-17] 13 | Location: US City H 14 | Cheque: >$SM 15 | Last/ next step: Aug 20, 2025 16 | Days till next step: -21 17 | Invested: Portfolio Company R, Portfolio Company S, Portfolio Company T 18 | Tasks: Ping Contact C (VC Fund G) on LinkedIn, Fill info 19 | 20 | ## About this project 21 | 22 | ### /2024 23 | 24 | … 25 | 26 | ## Project Links 27 | 28 | **Hubspot** 29 | 30 | **Project Folder** 31 | 32 | **Fathom** 33 | 34 | **Project Folder** 35 | 36 | ## Project tasks 37 | 38 | [Tasks](Tasks%202489786215cf809c907afea197714097.csv) 39 | 40 | ## LinkedIn history with Contact C 41 | 42 | - 2024-07-17T19:50:18 ⬅️: Contact C → Person B — Hey Person B! Reaching out from VC Fund G, a City H-based investment firm. I've sent you a couple of emails, but in short, I would love to set up a quick call to learn more about Company Zeta. Do you have time for a quick call this week or next? 43 | - 2024-07-17T20:11:14 ➡️: Person B → Contact C — Hey Contact C, Sure, let's chat. Choose time here [ANONYMIZED_CALENDAR_LINK] or send me your link, pls. 44 | - 2024-07-17T20:14:24 ⬅️: Contact C → Person B — Just booked 4:30pm ET on Wednesday next week. Looking forward to it! 45 | - 2024-07-17T20:14:40 ➡️: Person B → Contact C — Great! 46 | - 2025-08-07T23:34:54 ➡️: Person B → Contact C — Hey Contact C, Last time we talked, i made a note to get back when we reach $TM in ARR. So here we are :-) We've grown to $TM in ARR and are now launching a super AI agent for performance marketers. Blurb: Company Zeta is pioneering "vibe marketing" with the world's first AI superagent for performance marketing, automating N% of campaign management and reporting for ad-driven businesses. The problem: in a world where channel competition keeps rising, survival depends on the ability to run and optimize hundreds of tests per week — impossible without deep automation. With Company Zeta, marketers simply tell what they want, and our AI agent executes across all channels. Our clients on average reduce CAC by N1%, increase Revenue by N2% and Gross Profit by N3%. Key metrics: ARR: $TM (+N% in last 3 months) ACV: ~$UK per year SAM: $VB (Xk target US companies * $UK acv) Payback Period: N months NDR: >N% We're raising $WM Seed+ to accelerate our AI agent rollout and scale to $RM ARR. I'd love to get on a call with you. Does calendly work for you [ANONYMIZED_CALENDAR_LINK] ? 47 | - 2025-08-15T22:27:07 ➡️: Person B → Contact C — New week, updated blurb: Company Zeta is pioneering "vibe marketing" with the world's first AI superagent for performance marketing, automating up to N% of work. While most tools are built for e‑commerce, we focus on the largest non‑e‑com categories: b2c software, subscriptions, and services. These businesses require cohort‑aware, lag‑adjusted decisioning, LTV forecasting, lead quality signals, and off‑site revenue tracking. We combine a battle‑tested attribution/data backbone with an AI superagent. Outcome: −CAC, +Revenue, +Gross Profit — algorithms finally optimize for real business results. Key metrics: ARR: $TM ACV: ~$UK per year SAM: $VB (Xk target US companies × $UK ACV) Payback Period: N months NDR >N% Backed by: Fund P, Fund Q, Angel Investor F (Product I), Angel Investor G (Company J), Angel Investor H (Company K), Angel Investor I & Angel Investor J (Company L/Product M), Angel Investor K (Company K / Fund N), Angel Investor L (Company O) Founders: Person B & Person E, Y years building businesses together, built a profitable X-employee digital agency, and two other companies 48 | - 2025-08-15T22:27:52 ➡️: Person B → Contact C — What do you think? 49 | 50 | -------------------------------------------------------------------------------- /Docs/Operations/Hiring/Global-Rules/General-Hiring-Policy.md: -------------------------------------------------------------------------------- 1 | # General Hiring Policy 2 | 3 | *This is a template example. Customize according to your company's specific needs and legal requirements.* 4 | 5 | ## Candidate Sources 6 | 7 | We work with diverse candidate attraction sources: 8 | - Post job openings across various channels (Telegram groups, job marketplaces, job boards, etc.) 9 | - Receive direct applications through published positions 10 | - For certain positions, collaborate with external recruiters who generate candidate pipeline 11 | 12 | ## Decision-Making Process Participants 13 | 14 | **Initial Screening Stage** - conducted by internal recruiter: 15 | - Verification of hard skills alignment based on position requirements 16 | - Assessment of relevant experience and key competencies 17 | - English language proficiency evaluation 18 | - Candidate location verification 19 | 20 | **First Interview Stage** - after passing screening: 21 | - Participants: recruiter and operations manager 22 | - Company introduction, detailed role description and expectations 23 | - Detailed candidate profile assessment for role competency alignment 24 | - Team & culture fit evaluation, salary expectations, role expectations, motivation assessment 25 | 26 | **Subsequent Stages** - depending on position: 27 | - **For analytical roles**: Technical interview with hiring manager 28 | - **For project managers**: Take-home assignment and interview 29 | - **Final interview**: With hiring manager after all stages completion 30 | 31 | **Final Decision**: Made after completing all stages 32 | **Offer Process**: Initiated after decision confirmation 33 | 34 | ## Candidate Database Management 35 | 36 | - All candidate data maintained in ATS system (e.g., HuntFlow) 37 | - Full confidentiality of personal data maintained 38 | 39 | ## Candidate Profile Creation Rules 40 | 41 | When creating new candidate profiles through automated agents: 42 | - Create only folder structure and document templates 43 | - CV.md and Interview-Transcript.md files must remain empty initially 44 | - Data input to these files done manually after receipt from candidate 45 | - Automated candidate evaluation triggers only after manual data completion 46 | 47 | ## Expectation-Role Alignment Assessment 48 | 49 | ### For Technical Roles 50 | Throughout all selection stages, assess alignment between candidate expectations and actual job responsibilities: 51 | - Special attention to balance of technical vs. business tasks in specific role 52 | - Clear communication of implementation vs. strategy proportion in work 53 | - Analysis of candidate's career trajectory for movement from technical to business roles 54 | - Assessment of personal motivations and interests 55 | 56 | ### Potential Misalignment Indicators 57 | The following signs require additional attention and candidate discussion: 58 | - Career history shows consistent movement from technical to more strategic roles 59 | - Candidate shows heightened interest in business processes and strategy when role is primarily technical 60 | - Achievement descriptions emphasize business results over technical aspects 61 | - Frequent mentions of desire to influence product decisions 62 | - Emphasis on wanting to create new features/capabilities vs. implementing existing requirements 63 | - Leadership and management tendencies in individual contributor role 64 | 65 | ### Actions When Misalignment Identified 66 | 1. Conduct detailed discussion with candidate about actual job content 67 | 2. Document identified misalignments in candidate evaluation 68 | 3. Include discussion of these aspects in subsequent interview stages 69 | 4. For significant misalignments, consider recommending candidate for other company roles 70 | 5. Final candidate evaluation must include analysis of expectation-reality alignment 71 | 72 | --- 73 | 74 | *Template Note: This policy should be adapted to your specific company culture, legal requirements, and hiring processes. Consider local employment laws and industry standards when implementing.* 75 | 76 | -------------------------------------------------------------------------------- /Docs/Operations/Hiring/Job-Openings/Senior-Marketing-Analyst/Candidates/Example-Candidate-B-Average/CV.md: -------------------------------------------------------------------------------- 1 | # MICHAEL THOMPSON 2 | *[TEMPLATE EXAMPLE - This is a fictional candidate profile for demonstration purposes]* 3 | 4 | **Marketing Data Analyst** 5 | 📧 michael.thompson@example.com | 📱 +1-555-0145 | 🌍 Denver, CO 6 | LinkedIn: linkedin.com/in/michaelthompson-analyst 7 | 8 | --- 9 | 10 | ## PROFESSIONAL SUMMARY 11 | 12 | Marketing data analyst with 2+ years of experience in retail analytics and campaign performance measurement. Strong foundation in data analysis tools with growing interest in marketing attribution and automation. 13 | 14 | --- 15 | 16 | ## CORE COMPETENCIES 17 | 18 | **Data Analysis:** 19 | Python (Pandas, Matplotlib) • Power BI • Excel • Google Analytics 20 | 21 | **Technical Skills:** 22 | SQL (Basic-Intermediate) • API Integration (Learning) • Data Visualization 23 | 24 | **Marketing:** 25 | Campaign Analysis • Customer Segmentation • A/B Testing • RFM Analysis 26 | 27 | **Languages:** 28 | English (Native) • Spanish (Conversational) 29 | 30 | --- 31 | 32 | ## PROFESSIONAL EXPERIENCE 33 | 34 | ### **JewelCorp Retail Chain** 35 | **Marketing Data Analyst** | *Dec 2022 — Present* (1.5 years) 36 | 37 | • Generate monthly performance reports using Python scripts in Google Colab, processing CRM data exports 38 | • Built Power BI dashboard for management showing sales performance, marketing spend, and store traffic across 12 locations 39 | • Conduct ad-hoc analysis for stakeholders including RFM analysis, customer retention, and behavioral segmentation 40 | • Analyze effectiveness of marketing campaigns and Instagram advertising activities 41 | • Implemented regular customer segmentation reports for branch managers, resulting in 3 customers achieving VIP status 42 | 43 | **Key Achievements:** 44 | - Created automated monthly reporting system reducing manual work by 60% 45 | - Established regular campaign effectiveness analysis increasing marketing ROI visibility 46 | 47 | ### **AutoParts Distribution** 48 | **Sales Analyst** | *Jan 2023 — Sep 2023* (9 months) 49 | 50 | • Collected and processed data from multiple CRM systems (1C and Bitrix24) 51 | • Prepared and analyzed sales data using Pandas and Power Query 52 | • Built and maintained Power BI dashboards for sales performance tracking 53 | • Collaborated with sales, IT, and marketing teams to define reporting requirements 54 | 55 | --- 56 | 57 | ## EDUCATION 58 | 59 | **State University of Transportation** 60 | *2018 — 2022* 61 | Master's Degree in Transportation Systems Management 62 | 63 | **Professional Development:** 64 | - Statistics for Data Analysis - Higher School of Economics (2023) 65 | - Data Visualization in Power BI - Stepik (2023) 66 | - SQL for Data Analysis - Stepik (2023) 67 | 68 | --- 69 | 70 | ## PROJECTS & ACHIEVEMENTS 71 | 72 | **Customer Segmentation Analysis:** 73 | Developed RFM + ML clustering model for customer segmentation using K-means, providing CRM team with actionable customer groups for targeted communications. 74 | 75 | **Push Notification Optimization:** 76 | Analyzed push notification frequency impact on user engagement, identifying optimal sending patterns while maintaining conversion rates. 77 | 78 | **Campaign Performance Dashboard:** 79 | Built comprehensive marketing performance tracking system connecting multiple data sources. 80 | 81 | --- 82 | 83 | ## TECHNICAL NOTES 84 | 85 | - **Current Limitation:** Limited production SQL experience (primarily uses Python/Pandas for data processing) 86 | - **Learning Focus:** Actively studying data engineering concepts and API integrations 87 | - **Growth Area:** Seeking to transition from analysis-focused role to more technical data engineering position 88 | 89 | --- 90 | 91 | *Template Note: This resume demonstrates a candidate with solid foundational skills but some gaps in technical requirements. Use this to evaluate candidates who show potential but may need additional training or mentoring.* -------------------------------------------------------------------------------- /Docs/Operations/Hiring/Global-Rules/Interview-Guidelines.md: -------------------------------------------------------------------------------- 1 | # Interview Guidelines 2 | 3 | *This is a template example. Adapt the structure and questions to your specific company needs and role requirements.* 4 | 5 | ## General Interview Structure (for all positions) 6 | 7 | ### Introduction Section 8 | - Company presentation (business model, project structure, team roles) 9 | - Answers to candidate's organizational questions 10 | 11 | ### Stage 1 — Career and General Experience 12 | - Main career path, employers, geographic experience 13 | - Experience working with international clients 14 | - Experience in startups vs. large companies 15 | 16 | ### Stage 2 — Role-Specific Technical Blocks 17 | 18 | **For Project Manager:** 19 | - Project management experience: timeline, budget, and task management 20 | - Client relationship management and expectation setting 21 | - Experience in marketing/analytical projects 22 | - Work in multidisciplinary teams 23 | - Experience with task tracking systems (ClickUp, Jira, etc.) 24 | - Financial planning and team capacity management experience 25 | 26 | **For Analyst:** 27 | - Analytics systems experience (Google Analytics 4, Looker Studio, Power BI, Tableau) 28 | - Data collection and preparation (data pipelines, normalization, ETL) 29 | - SQL/Python proficiency 30 | - Sales funnel construction, seasonal analysis 31 | - UTM tracking experience 32 | - Marketing attribution experience 33 | - Technical background (education, Data Science/Information Systems) 34 | 35 | ### Stage 3 — Motivation and Organizational Expectations 36 | - Reasons for job change 37 | - Expectations regarding pace and culture 38 | - Time zone availability 39 | - Compensation expectations 40 | 41 | ### Stage 3.1 — Expectation-Role Alignment Assessment 42 | - Request specific examples of work tasks the candidate finds most interesting 43 | - Discussion of technical vs. business task balance the candidate expects 44 | - Identification of career goals for the next 1-2 years 45 | - Clear articulation of routine technical tasks vs. strategic work proportion in this role 46 | - Assessment of candidate's previous experience for tendency to shift from technical to business-oriented roles 47 | 48 | **Red Flags Requiring Special Attention:** 49 | - Individual contributor candidate shows heightened interest in influencing product decisions when role doesn't involve this 50 | - Career history shows consistent movement from technical to more strategic roles 51 | - Frequent mentions of desire to participate in business decision-making 52 | - Statements about wanting to create new features/capabilities, develop products 53 | - Ambitions for direction development when role primarily involves execution 54 | 55 | ### Stage 4 — Closing 56 | - Discussion of next steps (take-home assignment, NDA, team lead interview) 57 | - Additional candidate questions 58 | 59 | ## Interview Principles: 60 | 61 | - Structure adherence 62 | - Unified feedback format 63 | - Note-taking in ATS system 64 | - Data confidentiality compliance 65 | - **Explicit discussion of actual technical vs. business task balance in role to prevent expectation misalignment** 66 | 67 | ## Questions for Identifying Expectation-Role Misalignment: 68 | 69 | 1. "Describe an ideal workday in the role you're applying for. What tasks would occupy most of your time?" 70 | 2. "What aspects of your current work do you enjoy most, and what would you like to change?" 71 | 3. "How do you see your impact on the company's business results in this role?" 72 | 4. "Describe a project you're most proud of. What was your role in it?" 73 | 5. "How do you see the next step in your career after this position in 1-2 years?" 74 | 6. "What's more important to you: diving deep into technical expertise or expanding influence on business processes?" 75 | 7. "How important is participation in strategic decision-making for you?" 76 | 77 | --- 78 | 79 | *Template Note: Customize these guidelines based on your company's interview process, role requirements, and cultural values. Ensure compliance with local employment laws and fair hiring practices.* 80 | -------------------------------------------------------------------------------- /Docs/Operations/Hiring/Job-Openings/Senior-Marketing-Analyst/Candidates/Example-Candidate-A-Strong/Screening-Evaluation.md: -------------------------------------------------------------------------------- 1 | # Screening Evaluation - John Doe (Vitali Ignatenko) 2 | 3 | **DECISION: ✅ PROCEED TO TECHNICAL INTERVIEW** 4 | 5 | ## Summary 6 | Vitali Ignatenko is a Senior Marketing Analyst with extensive experience in data analysis and marketing. His background includes roles at Tutu.ru, Burger King, Samokat, Publicis Groupe, and MediaCom, demonstrating a diverse industry experience. He possesses strong technical skills in SQL, Power BI, and Python, with a focus on customer segmentation, A/B testing, and data-driven marketing performance improvements. His education in Applied Mathematics with a minor in Data Mining provides a solid foundation for analytical work and complex data modeling approaches. 7 | 8 | ## Competency Assessment 9 | | Competency | Rating | Evidence | 10 | |------------|--------|----------| 11 | | SQL Expertise | 4.0/5 | Listed as a skill on CV; implied usage in analytical roles | 12 | | ETL & Data Pipelines | 2.5/5 | Not explicitly mentioned, may have experience based on roles | 13 | | API Integration | 2.5/5 | Not explicitly mentioned in available materials | 14 | | Data Modeling | 3.5/5 | Indicated through RFM models and ML models for segmentation | 15 | | Marketing Analytics | 4.5/5 | Evident in multiple roles and listed skills | 16 | | Web Analytics Tools | 3.5/5 | Google Analytics listed as skill | 17 | | Power BI | 4.0/5 | Listed as a skill on CV | 18 | | Ad Platforms | 3.5/5 | Experience with advertising campaigns at multiple companies | 19 | | Client Communication | 3.0/5 | Not explicitly mentioned though implied in agency roles | 20 | | Documentation | 2.5/5 | Not explicitly mentioned in available materials | 21 | | English Proficiency | 3.0/5 | B2 level indicated | 22 | | Team Fit | 3.5/5 | Adaptable based on diverse industry experience | 23 | 24 | ## Key Strengths 25 | 1. Strong technical foundation in SQL, Power BI, and Python 26 | 2. Extensive marketing analytics experience across diverse industries 27 | 3. Advanced customer segmentation and A/B testing expertise 28 | 4. Applied Mathematics education providing strong analytical foundation 29 | 5. Experience in both client-side and agency environments 30 | 31 | ## Concerns 32 | - Limited evidence of ETL experience and data pipeline design 33 | - API integration experience not clearly indicated 34 | - Documentation skills not explicitly mentioned 35 | - Client communication experience needs further verification 36 | - Salary expectations not specified in available materials 37 | 38 | ## Technical Assessment 39 | Vitali demonstrates strong technical capabilities in core analytical areas, particularly SQL, Power BI, and Python. His experience with customer segmentation models and A/B testing suggests solid data modeling skills. His background in Applied Mathematics indicates strong analytical thinking and problem-solving abilities. The technical interview should focus on exploring his ETL experience and API integration knowledge, which are not clearly documented in available materials. 40 | 41 | ## Cultural Fit 42 | Vitali's experience across multiple industries and company types suggests adaptability to different working environments. His work at both client-side companies and agencies indicates versatility in approach and stakeholder management. His background working with marketing teams to implement data-driven approaches suggests an ability to bridge technical and business domains effectively. 43 | 44 | ## Next Steps 45 | - [x] Proceed to Technical Interview 46 | - [ ] Request Additional Information 47 | - [ ] Reject Candidacy 48 | 49 | ## Notes 50 | His diverse industry experience could provide valuable cross-sector insights for our clients. The technical interview should explore his ETL and API integration experience, as well as verifying his client communication skills. Salary expectations should be discussed during the next interview phase to ensure alignment with our range. His background in Applied Mathematics could be particularly valuable for complex analytical modeling requirements. 51 | -------------------------------------------------------------------------------- /Docs/Operations/Hiring/Job-Openings/Senior-Marketing-Analyst/Screening-Agent/agent-prompt.md: -------------------------------------------------------------------------------- 1 | You are [COMPANY_NAME] Recruiter Screening Agent. 2 | 3 | Your task is to conduct the first stage of candidate evaluation based on available candidate materials. 4 | 5 | ## Data sources: 6 | 7 | - CV.md 8 | - Fathom-Screening-Interview.md 9 | - Global-Rules/General-Hiring-Policy.md 10 | - Global-Rules/Scoring-Framework.md 11 | - Global-Rules/Interview-Guidelines.md 12 | - Job-Openings/Senior-Marketing-Analyst/Position-Description.md 13 | - Job-Openings/Senior-Marketing-Analyst/Role-Competency-Matrix.md 14 | - Job-Openings/Senior-Marketing-Analyst/Scoring-Rules.md 15 | 16 | ## Evaluation Process (Strict Order): 17 | 18 | 1. Check salary expectations against company range first 19 | 2. Review all competencies from Role-Competency-Matrix.md 20 | 3. Analyze red flags and potential discrepancies 21 | 4. Make preliminary decision 22 | 5. Document all findings 23 | 24 | ## Evaluation logic: 25 | 26 | - For each competency from Role-Competency-Matrix.md: 27 | - If the skill is explicitly mentioned in CV → mark as "Mentioned in CV" 28 | - If the candidate self-reports the skill in the screening interview → mark as "Self-Reported" 29 | - If there is no information → mark as "Missing" 30 | - Assign score (1-5) based on Scoring-Framework.md 31 | 32 | - You only consider self-assessment reliable for initial screening but do not treat it as skill evidence. 33 | - Do not make assumptions. Use only stated information. 34 | 35 | ## Red Flags Analysis (Required Categories): 36 | 37 | 1. Technical Stack Misalignment 38 | - Core tool gaps 39 | - Technical depth 40 | - Implementation vs research focus 41 | 42 | 2. Industry & Role Misalignment 43 | - Industry experience 44 | - Role focus 45 | - Career trajectory 46 | - Client interaction 47 | 48 | 3. Communication & Language Concerns 49 | - English level 50 | - Client communication experience 51 | - Communication style 52 | 53 | 4. Experience Validation Gaps 54 | - Self-reported skills 55 | - Project scope 56 | - Team size 57 | - Technical leadership 58 | 59 | 5. Cultural & Work Style Concerns 60 | - Industry transition 61 | - Technical vs research preference 62 | - Client focus 63 | - Adaptability 64 | 65 | 6. Compensation Misalignment 66 | - Salary expectation vs range 67 | - Premium analysis 68 | - Market reality 69 | - Budget constraints 70 | 71 | ## Output format: 72 | 73 | 3️⃣ Preliminary Decision: 74 | - "Proceed to Technical Interview" 75 | - "Do not proceed" 76 | - Include clear rationale for decision 77 | 78 | 1️⃣ Summary: brief description of candidate profile, motivation, and strengths. 79 | 80 | 2️⃣ Competency Evidence Table: for each competency list: 81 | - Score (1-5) 82 | - Evidence Status 83 | - Detailed notes 84 | 85 | 4️⃣ Concerns: list any missing critical skills or red flags. 86 | 87 | 5️⃣ Red Flags & Potential Discrepancies: detailed analysis of all red flag categories. 88 | 89 | ## File Saving Rule: 90 | 91 | - After completing the evaluation, automatically write the full report into: 92 | 93 | `Screening-Evaluation.md` 94 | 95 | - Use the actual candidate folder where you found CV.md and Screening-Interview.md. 96 | - Overwrite any previous content in Screening-Evaluation.md with the new evaluation. 97 | - If any file error occurs, report it in chat. 98 | 99 | ## Strict Output Rules 100 | 101 | - You must only create and update: `Screening-Evaluation.md`. 102 | - Do not create or write into: `Evaluation.md`, `Final-Score.md`, `AI-Notes.md`, `Fathom-Technical-Interview.md` at this stage. 103 | - Do not generate any technical interview preparation content. 104 | - Only process files you are instructed to use. 105 | - Strictly limit yourself to screening phase logic only. 106 | - Always check salary expectations first. 107 | - Always analyze all red flag categories. 108 | - Never skip or modify the evaluation process order. 109 | - Never add your own ideas or assumptions beyond the provided framework. 110 | -------------------------------------------------------------------------------- /Docs/SalesAndMarketing/User comprehension testing research/README.md: -------------------------------------------------------------------------------- 1 | # User Comprehension Testing for Landing Page 2 | 3 | ## Simplified Structure 4 | 5 | We now have **only two files** for the entire process: 6 | 7 | 1. **`corridor-test-questions.md`** - complete list of questions (for copying to note-taker) 8 | 2. **`corridor-test-analysis-template.md`** - analysis template with quick checklist + full analysis 9 | 10 | ## Folder Structure 11 | 12 | Each test is saved in a separate file with the name format: 13 | 14 | ``` 15 | corridor-test-analysis-[NAME]-[DATE].md 16 | ``` 17 | 18 | Example: `corridor-test-analysis-john-smith-2025-01-15.md` 19 | 20 | ## Workflow Process 21 | 22 | ### 1. Interview Preparation 23 | - Open `corridor-test-analysis-template.md` 24 | - Copy questions from "Quick Checklist" to note-taker 25 | - Or use the full list from `corridor-test-questions.md` 26 | 27 | ### 2. Conducting Interview 28 | - Record the meeting in two ways (e.g., Zoom + Otter.ai) 29 | - Take notes about personal observations 30 | - Use questions from note-taker 31 | 32 | ### 3. Data Analysis 33 | - Copy `corridor-test-analysis-template.md` 34 | - Rename to format `corridor-test-analysis-[NAME]-[DATE].md` 35 | - Fill out all sections: 36 | - Questions and answers from note-taker 37 | - Analysis and comparison of two transcripts 38 | - Personal observations from interviewer 39 | - Structured analysis by blocks 40 | 41 | ## Testing Objective 42 | 43 | Evaluate the effectiveness of the landing page in conveying the value proposition of [PRODUCT NAME] and convincing the target audience (performance marketing managers, heads of acquisition, CMOs) to join the waitlist. 44 | 45 | ## Success Criteria 46 | 47 | - **Understanding:** 80%+ participants correctly understand the main function 48 | - **Value:** 70%+ see clear value for their work 49 | - **Trust:** 60%+ trust the claims about capabilities 50 | - **Action:** 50%+ ready to join the waitlist 51 | 52 | ## Target Audience 53 | 54 | ### Primary 55 | - Performance Marketing Managers 56 | - Heads of Acquisition / Growth 57 | - CMOs & Marketing Directors 58 | 59 | ### Secondary 60 | - Marketing Directors 61 | - Growth Managers 62 | - Digital Marketing Specialists 63 | 64 | ## Methodology 65 | 66 | - **Duration:** 15-20 minutes per person 67 | - **Method:** Personal interviews or video calls 68 | - **Materials:** Landing page in final version (prototype or screenshots) 69 | - **Number of participants:** 8-12 people from target audience 70 | - **Recording:** Two methods for better transcript quality 71 | 72 | ## Analysis Structure 73 | 74 | Each analysis contains: 75 | 76 | 1. **Quick checklist** - main questions for interview 77 | 2. **Participant information** - role, experience, company 78 | 3. **Questions from Note-taker** - main questions and answers 79 | 4. **Transcript analysis** - comparison and selection of best one 80 | 5. **Personal observations** - emotional reactions, non-verbal signals 81 | 6. **Structured analysis** - across 5 main blocks 82 | 7. **Key insights** - positive moments, problems, findings 83 | 8. **Recommendations** - for landing page improvement 84 | 9. **Readiness assessment** - for waitlist registration 85 | 86 | ## Results Analysis 87 | 88 | After conducting all tests, create a summary report with: 89 | 90 | - Common trends and patterns 91 | - Key landing page problems 92 | - Improvement recommendations 93 | - Statistics on success criteria 94 | 95 | ## Files 96 | 97 | - `corridor-test-questions.md` - **complete question list** for reference 98 | - `corridor-test-analysis-template.md` - **analysis template** with quick checklist 99 | - `corridor-test-analysis-[NAME]-[DATE].md` - specific test results 100 | - `summary-report-[DATE].md` - summary report of all tests (created after completion) 101 | 102 | ## Benefits of Simplified Structure 103 | 104 | 1. **Fewer files** - easier to navigate 105 | 2. **All in one place** - checklist + analysis in one file 106 | 3. **Flexibility** - can use quick checklist or full list 107 | 4. **Structure** - clear format for comparing results 108 | 109 | ## Contact 110 | 111 | For questions about conducting tests, contact the marketing team. -------------------------------------------------------------------------------- /DEMO-QUICK-START.md: -------------------------------------------------------------------------------- 1 | # 🚀 AI First Workspace Template - Quick Start Demo 2 | 3 | > **Purpose**: This file contains ready-made demo commands for showcasing AI-powered business operations across departments. 4 | 5 | ## 🎯 Demo Commands 6 | 7 | ### 🏗️ Strategy & Competitive Analysis 8 | ``` 9 | "A new competitor appeared, analyze them using our workflow and put it in the appropriate folder" 10 | ``` 11 | 12 | ### 📊 Project Status Management 13 | ``` 14 | "Take the latest team call transcript and update project status cards" 15 | ``` 16 | 17 | ### 📈 Marketing Analysis 18 | ``` 19 | "Create a summary of which projects are ready for testimonial collection" 20 | ``` 21 | 22 | ### 💰 Financial Analysis 23 | ``` 24 | "Check if these expense numbers are within budget ranges: Food 650 (budget 500-700), Entertainment 280 (budget 200-300)" 25 | ``` 26 | 27 | ### 🔍 Research & Documentation 28 | ``` 29 | "Research the latest trends in [your industry] and create a market analysis document" 30 | ``` 31 | 32 | ### 📞 FireFlies Call Analysis 33 | ``` 34 | Analyze the latest proptech client meeting transcript and answer the following questions: 35 | - What specific agreements were reached regarding changes to the client's data processing workflow? 36 | - Who is responsible for their implementation? 37 | - Whether the client remained satisfied after the end of the call? 38 | ``` 39 | 40 | ## 🎬 Live Demo Flow 41 | 42 | ### 1. Workspace Overview (2 min) 43 | - Show the multi-department structure 44 | - Explain AI context switching capabilities 45 | - Demonstrate department-specific AI behavior 46 | 47 | ### 2. Competitor Analysis Demo (5 min) 48 | - Use the competitor analysis command 49 | - Show real-time research capabilities 50 | - Demonstrate file organization and cross-referencing 51 | 52 | ### 3. Project Management Demo (5 min) 53 | - Process team call transcripts 54 | - Update project status cards 55 | - Generate actionable summaries 56 | 57 | ### 4. Analyze client meeting transcript (3 min) 58 | - Process FireFlies call transcript with the proptech client 59 | - Identify responsibilities and action items with specific owners 60 | - Assess client satisfaction and relationship health 61 | - Create structured analysis for executive review 62 | 63 | ### 5. Cross-Department Intelligence (3 min) 64 | - Show how information flows between departments 65 | - Demonstrate unified strategic messaging 66 | - Highlight collaborative workflows 67 | 68 | ## 🔧 Demo Setup Requirements 69 | 70 | ### Before Demo: 71 | - ✅ Open Cursor with this workspace 72 | - ✅ Choose Sonnet 4 model 73 | - ✅ Have backup examples ready 74 | - ✅ Demo mode - all APIs will use mock data 75 | 76 | ### Demo Environment: 77 | - 📁 All departments have example content 78 | - 🔄 Scripts work in demo mode 79 | - 📊 Sample data for all use cases 80 | - 🎯 Consistent results for presentations 81 | 82 | ## 💡 Key Features to Highlight 83 | 84 | ### 🤖 AI-Powered Automation 85 | - Natural language commands 86 | - Cross-department intelligence 87 | - Automated file organization 88 | - Real-time research capabilities 89 | 90 | ### 🏢 Enterprise-Ready Structure 91 | - Multi-repository architecture 92 | - Department-specific contexts 93 | - Professional git workflows 94 | - Scalable for growing teams 95 | 96 | ### 📊 Business Intelligence 97 | - Strategic competitor analysis 98 | - Project status tracking 99 | - Financial metrics validation 100 | - Market research automation 101 | 102 | ## 🎯 Demo Talking Points 103 | 104 | ### "Why This Matters" 105 | - **Traditional**: Teams work in silos, context gets lost 106 | - **AI-First**: Unified intelligence across all business functions 107 | - **Result**: 10x faster decision-making and strategic alignment 108 | 109 | ### "Real Business Impact" 110 | - Competitor analysis in minutes, not days 111 | - Automated project status tracking 112 | - Cross-department strategic alignment 113 | - Evidence-based decision making 114 | 115 | ### "Getting Started" 116 | - Template provides proven framework 117 | - Adapt to your specific business 118 | - Start with one department, expand gradually 119 | - Full implementation support included 120 | 121 | --- 122 | 123 | *Ready to transform your business operations? Let's begin the demo!* -------------------------------------------------------------------------------- /Docs/Operations/Hiring/Job-Openings/Senior-Marketing-Analyst/Candidates/Example-Candidate-A-Strong/CV.md: -------------------------------------------------------------------------------- 1 | # SARAH JOHNSON 2 | *[TEMPLATE EXAMPLE - This is a fictional candidate profile for demonstration purposes]* 3 | 4 | **Senior Marketing Analyst** 5 | 📧 sarah.johnson@example.com | 📱 +1-555-0123 | 🌍 New York, NY 6 | LinkedIn: linkedin.com/in/sarahjohnson-analytics | GitHub: github.com/sarahjohnson 7 | 8 | --- 9 | 10 | ## EDUCATION 11 | 12 | **University of California, Berkeley** 13 | *2016 — 2020* 14 | Bachelor of Science in Business Analytics, Minor in Computer Science 15 | GPA: 3.8/4.0, Dean's List 2018-2020 16 | 17 | **Google Analytics Certified** (2022) 18 | **Microsoft Power BI Certified** (2023) 19 | 20 | --- 21 | 22 | ## CORE COMPETENCIES 23 | 24 | **Analytics & Visualization:** 25 | SQL • Power BI • Tableau • Google Analytics 4 • Looker Studio • Amplitude 26 | 27 | **Programming & Tools:** 28 | Python • R • Git • BigQuery • Snowflake • dbt • Apache Airflow 29 | 30 | **Marketing & Business:** 31 | A/B Testing • Customer Segmentation • Attribution Modeling • UTM Management 32 | Funnel Analysis • Cohort Analysis • CLV Modeling • Marketing Mix Modeling 33 | 34 | **Languages:** 35 | English (Native) • Spanish (Conversational) 36 | 37 | --- 38 | 39 | ## PROFESSIONAL EXPERIENCE 40 | 41 | ### **TechFlow Inc.** 42 | **Senior Marketing Analyst** | *Jan 2023 — Present* 43 | 44 | • Increased marketing ROI by 35% through implementation of advanced attribution modeling across 12+ digital channels, directly contributing to $2.3M additional revenue 45 | • Built automated data pipeline processing 50M+ events daily, reducing manual reporting time by 80% and enabling real-time campaign optimization 46 | • Led cross-functional team of 5 to redesign customer segmentation strategy, resulting in 28% improvement in email campaign performance 47 | • Developed comprehensive A/B testing framework for product teams, standardizing experiment design and increasing statistical power by 40% 48 | 49 | ### **DataDriven Solutions** 50 | **Marketing Analyst** | *Mar 2021 — Dec 2022* 51 | 52 | • Created dynamic Power BI dashboards for C-level executives, providing real-time visibility into $10M+ annual marketing spend across 8 business units 53 | • Implemented cohort analysis methodology that identified 25% improvement opportunity in customer retention, leading to product roadmap prioritization 54 | • Designed and executed 45+ A/B tests, achieving average 15% improvement in conversion rates across web and mobile platforms 55 | • Collaborated with engineering team to implement event tracking architecture, improving data quality by 90% 56 | 57 | ### **Growth Analytics Agency** 58 | **Junior Marketing Analyst** | *Jun 2020 — Feb 2021* 59 | 60 | • Supported client analytics initiatives for e-commerce companies with $1M-$50M annual revenue 61 | • Built automated UTM tracking and reporting system, reducing client reporting cycle from 2 weeks to 2 days 62 | • Conducted competitive analysis and market research for 12+ clients across retail, SaaS, and fintech verticals 63 | • Developed standardized reporting templates used across 20+ client accounts 64 | 65 | --- 66 | 67 | ## KEY PROJECTS 68 | 69 | **Multi-Touch Attribution Model** | *TechFlow Inc.* 70 | Built machine learning-based attribution model using Python and BigQuery, processing 100M+ touchpoints monthly. Resulted in 22% budget reallocation optimization and $800K incremental revenue. 71 | 72 | **Customer Lifetime Value Prediction** | *DataDriven Solutions* 73 | Developed CLV model using regression analysis and cohort data, enabling marketing team to optimize customer acquisition costs and improve unit economics by 18%. 74 | 75 | **Real-Time Campaign Dashboard** | *Growth Analytics Agency* 76 | Created automated dashboard connecting Google Ads, Facebook, and GA4 APIs, providing hourly campaign performance updates for 15+ concurrent campaigns. 77 | 78 | --- 79 | 80 | ## CERTIFICATIONS & AWARDS 81 | 82 | • **Google Analytics Individual Qualification (IQ)** - 2022 83 | • **Microsoft Power BI Data Analyst Associate** - 2023 84 | • **AWS Cloud Practitioner** - 2023 85 | • **"Analyst of the Year"** - TechFlow Inc. 2023 86 | • **Dean's List** - UC Berkeley 2018-2020 87 | 88 | --- 89 | 90 | *Template Note: This is a fictional resume example designed to demonstrate strong candidate qualifications for a Senior Marketing Analyst position. Use this as a reference for the type of experience and skills to look for in actual candidates.* -------------------------------------------------------------------------------- /Projects/Status-Projects/Client-Food-Status-Card.md: -------------------------------------------------------------------------------- 1 | # 🍽️ Client4 - Food Delivery 2 | 3 | ## 🏷️ Information Sources 4 | - `[MEETING:2025-06-30]` - Manager1 IM: Client1, Client6, Client7, Client2, Client3, Client4, Client8 5 | - `[PORTFOLIO:ACTIVE]` - Status from active projects portfolio 6 | - `[ANALYSIS:INFERRED]` - Food delivery and culinary sector 7 | 8 | ## 📊 General Information 9 | - **Analyst**: Manager1 10 | - **Project Manager**: Manager4 11 | - **Status**: ✅ Active 12 | - **Last Update**: 24.06.2025 13 | 14 | ## 🎯 Current Tasks 15 | 16 | ### ✅ Completed Work 17 | - Basic project structure setup 18 | - Main data sources connection 19 | - Initial dashboard framework 20 | - Core analytics implementation 21 | 22 | ### 🔄 In Progress 23 | - **Delivery analytics optimization** - route efficiency and timing 24 | - **Operations dashboard completion** - real-time delivery monitoring 25 | - **Customer behavior analysis** - ordering patterns and preferences 26 | - **Performance monitoring setup** - KPI tracking and alerts 27 | 28 | ### 📋 Planned 29 | - **Geographic expansion analytics** - market penetration analysis 30 | - **Advanced reporting features** - custom analytics for operations team 31 | - **Integration testing** - comprehensive system validation 32 | - **User training preparation** - operations team onboarding 33 | 34 | ## 🍕 **Food Delivery Specific Analytics** 35 | 36 | ### 🚚 **Delivery Operations** 37 | - **Real-time delivery tracking** - live order status and location 38 | - **Route optimization analysis** - efficient delivery path planning 39 | - **Delivery time performance** - speed and reliability metrics 40 | - **Driver performance tracking** - delivery quality and efficiency 41 | 42 | ### 📊 **Business Intelligence** 43 | - **Revenue attribution by channel** - order source analysis 44 | - **Customer lifetime value** - repeat order behavior 45 | - **Peak time analysis** - demand forecasting and staffing 46 | - **Geographic performance** - area-based delivery metrics 47 | 48 | ### 🎯 **Customer Analytics** 49 | - **Ordering pattern analysis** - frequency and timing preferences 50 | - **Menu performance tracking** - popular items and trends 51 | - **Customer satisfaction correlation** - rating vs delivery performance 52 | - **Retention analysis** - customer loyalty and churn patterns 53 | 54 | ## 📈 **Performance Status** 55 | 56 | ### ✅ **Operational Components** 57 | - Real-time delivery analytics working 58 | - Revenue attribution implemented 59 | - Customer journey tracking active 60 | - Operations dashboard nearly complete 61 | 62 | ### 🎯 **Success Metrics** 63 | - **Dashboard usage**: Operations team actively using reports 64 | - **Data accuracy**: Delivery tracking 98%+ accuracy 65 | - **Performance improvement**: 15% delivery time optimization 66 | - **Business impact**: Clear operational efficiency gains 67 | 68 | ## 🚀 **Launch Readiness** 69 | 70 | ### **Current Phase**: Approaching stable operation 71 | - Core features implementation completed 72 | - Dashboard configuration in final stages 73 | - Operations team training scheduled 74 | - Performance optimization ongoing 75 | 76 | ### **Next Milestones** 77 | 1. **Complete dashboard finalization** - remaining UI/UX improvements 78 | 2. **Conduct user training** - operations team onboarding 79 | 3. **Performance monitoring** - ensure stable operations 80 | 4. **Geographic expansion prep** - analytics for new markets 81 | 82 | ## 💼 **Business Impact** 83 | 84 | ### **For Food Delivery Business** 85 | - **Operational efficiency** - optimized delivery routes and timing 86 | - **Customer satisfaction** - improved delivery performance 87 | - **Revenue optimization** - data-driven menu and pricing decisions 88 | - **Geographic expansion** - analytics-supported market entry 89 | 90 | ### **For Analytics Platform** 91 | - **Food delivery expertise** - specialized sector knowledge 92 | - **Real-time operations** - live tracking and monitoring capabilities 93 | - **Scalable solutions** - replicable framework for food sector 94 | - **Success story development** - operational efficiency case study 95 | 96 | ## 📋 **Action Items** 97 | - [ ] Finalize operations dashboard completion 98 | - [ ] Schedule operations team training sessions 99 | - [ ] Implement geographic expansion analytics 100 | - [ ] Prepare comprehensive documentation 101 | 102 | **Project Manager**: Manager4 103 | **Expected Completion**: Stable operation achieved 104 | **Testimonial Readiness**: HIGH - stable operations with business impact 105 | **Industry**: Food Delivery & Restaurant Operations -------------------------------------------------------------------------------- /Docs/Operations/Hiring/Job-Openings/Senior-Marketing-Analyst/Full Evaluation Agent/README.md: -------------------------------------------------------------------------------- 1 | # FULL EVALUATION AGENT 2 | *[TEMPLATE EXAMPLE - This is a functional evaluation agent for demonstration purposes]* 3 | 4 | This automated agent evaluates candidates for the Senior Marketing Analyst role by analyzing their resumes, interview notes, and other relevant documents. 5 | 6 | ## Template Configuration 7 | 8 | **Before using this agent in your company:** 9 | 10 | 1. **Replace Company Name Placeholder:** 11 | - In `agent-prompt.md`: Replace `[COMPANY_NAME]` with your actual company name 12 | - In `agent.py`: Replace `[COMPANY_NAME]` with your actual company name (appears in 3 locations) 13 | 14 | 2. **Customize Evaluation Criteria:** 15 | - Modify the competencies list in `agent.py` to match your specific requirements 16 | - Update scoring thresholds in `agent-config.json` 17 | - Adjust the context files to point to your actual job requirements 18 | 19 | 3. **Set Up Directory Structure:** 20 | - Ensure your candidate folders follow the expected naming convention 21 | - Place the agent in the correct relative position to your candidates directory 22 | 23 | ## Quick Start for Template Users 24 | 25 | 1. **Setup:** 26 | ```bash 27 | # Install dependencies 28 | pip install markdown 29 | 30 | # Replace company name placeholders 31 | sed -i 's/\[COMPANY_NAME\]/YourCompany/g' agent-prompt.md 32 | sed -i 's/\[COMPANY_NAME\]/YourCompany/g' agent.py 33 | ``` 34 | 35 | 2. **Run evaluation:** 36 | ```bash 37 | # Make script executable 38 | chmod +x run-agent.sh 39 | 40 | # Evaluate all candidates 41 | ./run-agent.sh 42 | 43 | # Or evaluate specific candidate 44 | ./run-agent.sh --candidate Candidate-John-Doe 45 | ``` 46 | 47 | 3. **Customize for your needs:** 48 | - Modify competencies in `agent.py` 49 | - Adjust scoring rules in `agent-config.json` 50 | - Update context files paths as needed 51 | 52 | ## Overview 53 | 54 | The agent uses AI-powered analysis to: 55 | 56 | 1. Read candidate resumes and other documents 57 | 2. Compare candidate qualifications against the role requirements 58 | 3. Generate evaluation scores across key competencies 59 | 4. Produce comprehensive evaluations and final scores 60 | 5. Automatically create Fathom summaries for quick review 61 | 62 | > **⚠️ IMPORTANT NOTE:** This is a demonstration agent that uses placeholder scoring logic. For production use, you need to integrate it with a real LLM API (OpenAI, Anthropic, etc.) or custom AI model to perform actual intelligent evaluation of candidate materials. 63 | 64 | ## Setup Requirements 65 | 66 | - Python 3.7 or higher 67 | - Required Python packages: 68 | - markdown 69 | - argparse 70 | 71 | You can install the required packages using pip: 72 | 73 | ``` 74 | pip install markdown 75 | ``` 76 | 77 | ## Directory Structure 78 | 79 | The agent expects a specific directory structure: 80 | 81 | ``` 82 | Senior-Marketing-Analyst/ 83 | ├── Scoring-Rules.md 84 | ├── Role-Competency-Matrix.md 85 | ├── Position-Description.md 86 | ├── Candidates/ 87 | │ ├── Candidate-John-Doe/ 88 | │ │ ├── CV.md 89 | │ │ ├── ... 90 | │ └── Other candidates... 91 | └── Agent/ 92 | ├── agent.py 93 | ├── agent-config.json 94 | └── README.md (this file) 95 | ``` 96 | 97 | ## Configuration 98 | 99 | The agent is configured via the `agent-config.json` file. Key settings include: 100 | 101 | - Context files to read for evaluation criteria 102 | - Weightings for different competency areas 103 | - Minimum score threshold for passing candidates 104 | - Output file settings 105 | 106 | ## Usage 107 | 108 | To evaluate all candidates: 109 | 110 | ```bash 111 | python agent.py 112 | ``` 113 | 114 | To evaluate a specific candidate: 115 | 116 | ```bash 117 | python agent.py --candidate Candidate-John-Doe 118 | ``` 119 | 120 | ## Output Files 121 | 122 | For each candidate, the agent generates: 123 | 124 | 1. **Evaluation.md** - Detailed evaluation with scores and notes 125 | 2. **Final-Score.md** - Simple pass/fail and final score 126 | 3. **AI-Notes.md** - Additional AI-generated insights about the candidate 127 | 128 | ## Human Approval 129 | 130 | By default, the agent requires human approval before finalizing evaluations. This setting can be adjusted in the configuration file. 131 | 132 | ## Adding New Candidates 133 | 134 | Place new candidate folders in the `Candidates/` directory following the naming convention `Candidate-[Name]`. The agent will automatically discover and evaluate them. -------------------------------------------------------------------------------- /setup/README.md: -------------------------------------------------------------------------------- 1 | # Setup Scripts Configuration 2 | 3 | This folder contains setup and maintenance scripts for the AI First Workspace Template. **Before using these scripts, you need to customize them for your organization.** 4 | 5 | ## ⚠️ Configuration Required 6 | 7 | The scripts in this folder are templates that need to be configured with your specific organization and repository details. 8 | 9 | ### 1. Edit Configuration Variables 10 | 11 | Open each script file and replace the placeholder values: 12 | 13 | **For Bash scripts (`*.sh`):** 14 | ```bash 15 | # Replace these values: 16 | ORG="YOUR-GITHUB-ORGANIZATION" 17 | DEV_REPOS=("YOUR-PRODUCT-1" "YOUR-PRODUCT-2" "YOUR-PRODUCT-3") 18 | ``` 19 | 20 | **For PowerShell scripts (`*.ps1`):** 21 | ```powershell 22 | # Replace these values: 23 | $ORG = "YOUR-GITHUB-ORGANIZATION" 24 | $DEV_REPOS = @("YOUR-PRODUCT-1", "YOUR-PRODUCT-2", "YOUR-PRODUCT-3") 25 | ``` 26 | 27 | ### 2. Example Configuration 28 | 29 | If your company is "Acme Corp" with GitHub organization "acme-corp" and you have three products: 30 | 31 | **Bash version:** 32 | ```bash 33 | ORG="acme-corp" 34 | DEV_REPOS=("AcmeApp" "AcmeAPI" "AcmeDashboard") 35 | ``` 36 | 37 | **PowerShell version:** 38 | ```powershell 39 | $ORG = "acme-corp" 40 | $DEV_REPOS = @("AcmeApp", "AcmeAPI", "AcmeDashboard") 41 | ``` 42 | 43 | ## 📁 Script Files 44 | 45 | ### `clone-all-repos.sh` / `clone-all-repos.ps1` 46 | - **Purpose**: Initial setup - clones all department and development repositories 47 | - **Usage**: Run once when setting up a new workspace 48 | - **Configuration needed**: Organization name and development repository names 49 | 50 | ### `update-all.sh` / `update-all.ps1` 51 | - **Purpose**: Daily maintenance - pulls latest changes from all repositories 52 | - **Usage**: Run daily/weekly to keep all repositories synchronized 53 | - **Configuration needed**: Development repository names (should match clone script) 54 | 55 | ## 🚀 Quick Setup with AI Assistant 56 | 57 | The easiest way to configure these scripts is to ask your AI assistant: 58 | 59 | ``` 60 | "Help me configure the setup scripts in this AI First Workspace Template for my organization: 61 | 62 | Organization: [Your Company Name] 63 | GitHub org: [your-github-org] 64 | Development repositories: [list your products/codebases] 65 | 66 | Please update all four setup scripts with the correct values." 67 | ``` 68 | 69 | ## 💡 Usage Instructions 70 | 71 | ### First Time Setup: 72 | 1. Configure the scripts as described above 73 | 2. Set up workspace .gitignore: `cp .gitignore.template .gitignore` 74 | 3. Run: `bash setup/clone-all-repos.sh` (or `.\setup\clone-all-repos.ps1` on Windows) 75 | 76 | ### Daily Workflow: 77 | 1. Run: `bash setup/update-all.sh` (or `.\setup\update-all.ps1` on Windows) 78 | 2. Start working with AI context: "Use strategy context" (or your preferred department) 79 | 80 | ## 🔍 What Gets Cloned 81 | 82 | **Department Repositories (always):** 83 | - `Strategy` - Company strategy and competitive intelligence 84 | - `Product` - Product roadmap and specifications 85 | - `SalesAndMarketing` - Marketing campaigns and sales processes 86 | 87 | **Department Repositories (optional):** 88 | - `Operations` - Operational processes and metrics 89 | - `Operations-Hiring` - Hiring processes and recruitment 90 | - `Finance` - Financial models and projections 91 | - `Legal-HR` - Legal contracts and HR policies 92 | 93 | **Your Development Repositories:** 94 | - Whatever you configure in the `DEV_REPOS` array 95 | 96 | **Project Repositories (optional):** 97 | - `Projects` - Client project portfolio management 98 | - `Presales` - Presales materials and proposals 99 | 100 | ## ⚠️ Important Notes 101 | 102 | - **Run configuration check**: Scripts will check for placeholder values and refuse to run until configured 103 | - **Set up .gitignore**: Copy `.gitignore.template` to `.gitignore` before running scripts 104 | - **Repository permissions**: You'll only be able to clone repositories you have access to 105 | - **Missing repositories**: Scripts handle missing repositories gracefully - they'll show info messages for repos that don't exist yet 106 | - **SSH keys required**: Make sure you have SSH keys set up for GitHub access 107 | 108 | ## 🆘 Troubleshooting 109 | 110 | **"Configuration Required" error**: You haven't replaced the placeholder values in the script files. 111 | 112 | **"Could not clone [repo]" warnings**: Normal - means the repository doesn't exist yet or you don't have access. Create repositories as needed. 113 | 114 | **SSH authentication errors**: Set up SSH keys for GitHub: https://docs.github.com/en/authentication/connecting-to-github-with-ssh -------------------------------------------------------------------------------- /Docs/Operations/Hiring/README.md: -------------------------------------------------------------------------------- 1 | # Hiring System Template 2 | 3 | *This is a comprehensive hiring system template designed to demonstrate best practices for structured, consistent, and effective recruitment processes.* 4 | 5 | ## 📁 Structure Overview 6 | 7 | ### Global Rules (`/Global-Rules/`) 8 | Universal hiring policies and frameworks that apply across all positions: 9 | - **General-Hiring-Policy.md** - Company-wide hiring principles and processes 10 | - **Interview-Guidelines.md** - Structured interview framework and questions 11 | - **Scoring-Framework.md** - Standardized candidate evaluation criteria 12 | 13 | ### Job Openings (`/Job-Openings/`) 14 | Individual position folders containing role-specific materials: 15 | - **Position descriptions** and requirements 16 | - **Competency matrices** for role evaluation 17 | - **Scoring rules** specific to each position 18 | - **Candidate pipeline** tracking and examples 19 | 20 | ## 🎯 How to Use This Template 21 | 22 | ### For New Companies: 23 | 1. **Customize Global Rules** - Adapt policies to your company culture and legal requirements 24 | 2. **Create Position Folders** - Copy structure for each role you're hiring for 25 | 3. **Define Competencies** - Establish role-specific skills and evaluation criteria 26 | 4. **Train Your Team** - Ensure consistency across all interviewers 27 | 28 | ### For Each New Position: 29 | 1. **Copy Template Structure** - Use existing position as starting point 30 | 2. **Write Position Description** - Clear role expectations and requirements 31 | 3. **Define Competency Matrix** - Skills and experience levels needed 32 | 4. **Create Scoring Rules** - How to evaluate candidates consistently 33 | 5. **Set Up Candidate Pipeline** - Track progress through hiring stages 34 | 35 | ## 📊 Example Candidates 36 | 37 | Each position includes sample candidate profiles demonstrating: 38 | - **CV formats** and information depth 39 | - **Interview transcripts** showing conversation flow 40 | - **Evaluation examples** with scoring rationale 41 | - **Assessment documents** for different candidate strengths 42 | 43 | **Note:** All candidate examples are fictional and created for demonstration purposes only. 44 | 45 | ## 🔧 Candidate Evaluation Process 46 | 47 | ### Standard Pipeline: 48 | 1. **Application Review** - CV screening against requirements 49 | 2. **Screening Interview** - Cultural fit and basic qualifications 50 | 3. **Technical Assessment** - Role-specific skills evaluation 51 | 4. **Final Interview** - Team fit and decision-making 52 | 53 | ### Documentation Required: 54 | - **CV.md** - Candidate resume and background 55 | - **Screening-Interview.md** - Initial conversation transcript 56 | - **Technical-Interview.md** - Skills assessment details 57 | - **Evaluation.md** - Comprehensive candidate assessment 58 | - **Final-Score.md** - Decision rationale and scores 59 | 60 | ## ⚙️ Integration Recommendations 61 | 62 | ### ATS Systems: 63 | - Adapt folder structure to your recruitment platform 64 | - Maintain consistent naming conventions 65 | - Automate where possible while preserving human judgment 66 | 67 | ### Team Collaboration: 68 | - Use shared evaluation criteria across team members 69 | - Regular calibration sessions to ensure consistent scoring 70 | - Document decision rationale for future reference 71 | 72 | ## 📝 Customization Guidelines 73 | 74 | ### Legal Compliance: 75 | - Review all materials with legal team before implementation 76 | - Ensure compliance with local employment laws 77 | - Adapt to regional hiring practices and requirements 78 | 79 | ### Company Culture: 80 | - Modify interview questions to reflect your values 81 | - Adjust evaluation criteria for your specific needs 82 | - Include company-specific examples and scenarios 83 | 84 | ## 🚀 Getting Started 85 | 86 | 1. **Review Global Rules** - Understand the hiring framework 87 | 2. **Examine Example Positions** - See how structure works in practice 88 | 3. **Adapt for Your Needs** - Customize content and processes 89 | 4. **Train Your Team** - Ensure consistent implementation 90 | 5. **Iterate and Improve** - Refine based on experience 91 | 92 | --- 93 | 94 | ## 📞 Support & Questions 95 | 96 | This template provides a foundation for professional hiring practices. Adapt it to your specific industry, company size, and cultural requirements. 97 | 98 | Remember: Consistent, fair, and thorough evaluation processes benefit both candidates and companies by ensuring the right fit for all parties. 99 | 100 | --- 101 | 102 | *Template created for companies looking to establish professional, structured hiring processes. All examples are fictional and should be replaced with your actual content.* -------------------------------------------------------------------------------- /Projects/Status-Projects/Client-EdTech-Status-Card.md: -------------------------------------------------------------------------------- 1 | # 📚 Client5 - EdTech (Accounting Courses) 2 | 3 | ## 🏷️ Information Sources 4 | - `[PORTFOLIO:ACTIVE]` - Status from active projects portfolio 5 | - `[STATUS:LAUNCH]` - Project in launch phase 6 | - `[ANALYSIS:INFERRED]` - Educational project specifics 7 | 8 | ## 📊 General Information 9 | - **Analyst**: Manager2 10 | - **Project Manager**: Manager3 11 | - **Status**: ✅ Active - in launch phase 12 | - **Last Update**: 24.06.2025 13 | 14 | ## 🎯 Current Tasks 15 | 16 | ### 📈 **Analytics Implementation** 17 | - **User behavior tracking** - student journey mapping 18 | - **Attribution setup** - key conversion funnels for course enrollment 19 | - **Learning outcomes analytics** - course completion and success metrics 20 | - **Student engagement tracking** - lesson participation and interaction 21 | 22 | ### 🔧 **Technical Setup** 23 | - **OnPremises deployment** - secure educational environment setup 24 | - **Dashboard customization** - education-specific analytics interface 25 | - **Learning management integration** - LMS data connection 26 | - **Student privacy compliance** - FERPA and data protection measures 27 | 28 | ## 📊 **Educational Analytics Features** 29 | 30 | ### 🎓 **Student Journey Tracking** 31 | - **Enrollment funnel analysis** - from interest to enrollment 32 | - **Course progression monitoring** - lesson completion rates 33 | - **Learning outcome measurement** - assessment and certification tracking 34 | - **Engagement pattern analysis** - optimal learning time identification 35 | 36 | ### 📚 **Course Performance Analytics** 37 | - **Content effectiveness** - which lessons drive best outcomes 38 | - **Instructor performance** - teaching quality metrics 39 | - **Completion rate optimization** - identifying drop-off points 40 | - **Student satisfaction tracking** - feedback and rating analysis 41 | 42 | ## 🚀 **Launch Readiness Status** 43 | 44 | ### ✅ **Completed Components** 45 | - User behavior tracking framework implemented 46 | - Attribution model configured for educational funnels 47 | - Basic dashboard structure established 48 | - OnPremises environment prepared 49 | 50 | ### 🔄 **In Progress** 51 | - OnPremises deployment finalization 52 | - Educational dashboard customization 53 | - Learning management system integration 54 | - Compliance and privacy setup 55 | 56 | ### 📋 **Pending** 57 | - Full system testing in educational environment 58 | - User acceptance testing with course administrators 59 | - Staff training on analytics platform 60 | - Go-live coordination and support 61 | 62 | ## 🎯 **Success Metrics for Education Sector** 63 | 64 | ### 📈 **Primary KPIs** 65 | - **Enrollment conversion rate** - marketing funnel effectiveness 66 | - **Course completion rate** - student success measurement 67 | - **Learning outcome achievement** - educational goal attainment 68 | - **Student engagement score** - platform interaction quality 69 | 70 | ### 📊 **Secondary Metrics** 71 | - **Time to completion** - course efficiency measurement 72 | - **Assessment performance** - learning effectiveness 73 | - **Student satisfaction** - education quality feedback 74 | - **Instructor effectiveness** - teaching quality metrics 75 | 76 | ## 🔍 **Project Timeline** 77 | 78 | ### **Phase 1: Implementation** ✅ Complete 79 | - User tracking setup 80 | - Basic analytics framework 81 | - OnPremises preparation 82 | 83 | ### **Phase 2: Launch** 🔄 In Progress 84 | - Dashboard customization 85 | - System integration 86 | - Testing and validation 87 | 88 | ### **Phase 3: Optimization** 📋 Planned 89 | - Performance monitoring 90 | - Feature enhancement 91 | - Scale preparation 92 | 93 | ## 💼 **Business Impact** 94 | 95 | ### **For Educational Institution** 96 | - **Data-driven course improvement** - evidence-based curriculum development 97 | - **Student success optimization** - personalized learning support 98 | - **Marketing effectiveness** - enrollment campaign optimization 99 | - **Operational efficiency** - resource allocation optimization 100 | 101 | ### **For Analytics Platform** 102 | - **Education sector expertise** - specialized vertical knowledge 103 | - **Compliance demonstration** - privacy and security standards 104 | - **Scalable education solutions** - replicable framework for sector 105 | - **Case study development** - education technology success story 106 | 107 | ## 📋 **Next Steps** 108 | 1. **Complete OnPremises deployment** - finalize secure environment 109 | 2. **Finish dashboard customization** - education-specific interface 110 | 3. **Conduct comprehensive testing** - validate all educational features 111 | 4. **Coordinate go-live** - launch with full support 112 | 113 | **Project Manager**: Manager3 114 | **Expected Launch**: Within 2-4 weeks 115 | **Testimonial Readiness**: MEDIUM (HIGH after successful launch) 116 | **Industry**: Educational Technology -------------------------------------------------------------------------------- /Docs/SalesAndMarketing/Client-Meetings-Analysis/AI-Projects-Review-Analysis_2025-07-28.md: -------------------------------------------------------------------------------- 1 | # 🤖 AI Project Analysis for Marketing 2 | 3 | **Analysis Date**: 28.07.2025 4 | **Source**: AI analysis of project status cards 5 | **Goal**: Identify projects ready for testimonial collection and case studies 6 | 7 | --- 8 | 9 | ## 📊 AI Summary 10 | 11 | ### 🔍 **Status Updates Found**: 5 projects analyzed 12 | - **✅ 2 projects ready** for immediate testimonial collection 13 | - **🟡 1 project close** to completion (2-4 weeks) 14 | - **⏸️ 2 projects paused** or blocked 15 | 16 | ### 📈 **Portfolio Marketing Readiness**: 60% 17 | - **Immediate opportunities**: 2 case studies + 2-3 video testimonials 18 | - **Short-term prospects**: +1 EdTech case in August 19 | - **Total potential**: 4-5 ready success stories 20 | 21 | --- 22 | 23 | ## 🎯 Project Completion Readiness 24 | 25 | ### 🏆 **READY FOR TESTIMONIAL COLLECTION** 26 | 27 | #### 🧴 **Client-Beauty2** - Beauty & Health E-commerce 28 | **Status**: ✅ Active (updated 28.07.2025) 29 | **Testimonial Readiness**: 🟢 **HIGH** 30 | **Why ready**: 31 | - Final check before project defense 32 | - All custom metrics implemented 33 | - LTV calculations documented 34 | - GA4 events working stably 35 | 36 | **Recommended testimonial type**: 37 | - ⭐ Case study on comprehensive analytics 38 | - 📊 Testimonial about LTV metrics implementation 39 | - 🎯 Success story on GA4 setup 40 | 41 | **Contact**: Manager1, Manager4 42 | 43 | --- 44 | 45 | #### 🍽️ **Client-Food** - Food Delivery 46 | **Status**: ✅ Active (updated 24.06.2025) 47 | **Testimonial Readiness**: 🟢 **HIGH** 48 | **Why ready**: 49 | - Stable system operation 50 | - All core features implemented 51 | - Dashboard fully configured 52 | - Team actively using reports 53 | 54 | **Recommended testimonial type**: 55 | - 🚀 Success story on delivery analytics optimization 56 | - 📊 Case study on operational efficiency improvement 57 | - 🎯 Video testimonial from operations team 58 | 59 | **Contact**: Manager2, Manager3 60 | 61 | --- 62 | 63 | ### 🔄 **CLOSE TO COMPLETION** 64 | 65 | #### 🎓 **Client-EdTech** - Educational Technology 66 | **Status**: ✅ Active (updated 28.07.2025) 67 | **Testimonial Readiness**: 🟡 **MEDIUM (2-4 weeks)** 68 | **Why close**: 69 | - User behavior tracking implemented 70 | - Attribution working on key funnels 71 | - Only minor technical refinements needed 72 | 73 | **Expected completion**: Early August 2025 74 | **Recommended preparation**: Start testimonial planning now 75 | 76 | **Contact**: Manager1, Manager5 77 | 78 | --- 79 | 80 | ### ⏸️ **ON HOLD / BLOCKED** 81 | 82 | #### 🧴 **Client-Beauty1** - Beauty E-commerce 83 | **Status**: 🔴 On Hold (updated 19.06.2025) 84 | **Issue**: Blocked by client-side technical constraints 85 | **Marketing Impact**: Not suitable for testimonials currently 86 | 87 | #### 🚚 **Client-Logistics** - Transportation & Logistics 88 | **Status**: 🔴 On Hold (updated 01.07.2025) 89 | **Issue**: Long approval cycles 90 | **Marketing Impact**: Monitor for Q4 potential 91 | 92 | --- 93 | 94 | ## 🎯 Marketing Action Plan 95 | 96 | ### 📋 **Immediate Actions (This Week)** 97 | 1. **Contact Client-Beauty2**: Schedule testimonial recording session 98 | 2. **Contact Client-Food**: Prepare case study interview 99 | 3. **Prepare materials**: Update case study templates 100 | 4. **Schedule**: Video testimonial sessions for early August 101 | 102 | ### 📈 **Short-term Actions (Next 2-4 weeks)** 103 | 1. **Client-EdTech**: Pre-schedule testimonial for August completion 104 | 2. **Content creation**: Begin drafting case studies for ready clients 105 | 3. **Documentation**: Update success metrics for portfolio 106 | 107 | ### 📊 **Success Metrics to Track** 108 | - **Implementation timeframes**: Average 6-8 weeks (highlight speed) 109 | - **Feature adoption**: 90%+ dashboard usage (highlight engagement) 110 | - **Business impact**: ROI metrics where available 111 | 112 | --- 113 | 114 | ## 💡 AI Recommendations 115 | 116 | ### 🎯 **Priority Focus** 117 | 1. **Client-Beauty2** - Perfect comprehensive analytics story 118 | 2. **Client-Food** - Strong operational efficiency case 119 | 3. **Client-EdTech** - Upcoming educational technology showcase 120 | 121 | ### 📝 **Content Strategy** 122 | - **Technical case studies**: Deep dive into implementation 123 | - **Business impact stories**: ROI and efficiency gains 124 | - **Video testimonials**: Personal experiences from key users 125 | 126 | ### 🔄 **Process Optimization** 127 | - Set up automated follow-up schedule for testimonial collection 128 | - Create standardized interview templates by industry 129 | - Develop quick-win testimonial formats for busy clients 130 | 131 | --- 132 | 133 | **Next AI Analysis**: Scheduled for 04.08.2025 (weekly update) 134 | **Marketing Team**: Use this analysis for immediate testimonial planning 135 | -------------------------------------------------------------------------------- /Docs/Strategy/Company-Overview/company-info.md: -------------------------------------------------------------------------------- 1 | # Company Information Template 2 | *[TEMPLATE EXAMPLE - Replace all content below with your actual company information]* 3 | 4 | --- 5 | 6 | **⚠️ TEMPLATE NOTICE:** This file contains example company information for "Elly Analytics" as a demonstration of how to structure company information documentation. Replace all details below with your own company's actual information, maintaining the same structure and canonical marking system. 7 | 8 | --- 9 | 10 | # Company Information - Elly Analytics 11 | *[EXAMPLE COMPANY - Replace with your company name]* 12 | 13 | ## 🏢 Basic Information 14 | 15 | **Company Name:** Elly Analytics [CANONICAL] 16 | **Founded:** 2022 [CANONICAL] 17 | **Headquarters:** 730 Moreno Avenue, Palo Alto, CA [CANONICAL] 18 | **Website:** ellyanalytics.com [CANONICAL] 19 | **Email:** hello@ellyanalytics.com [CANONICAL] 20 | **Industry:** Marketing Technology / MarTech / AI-Powered Marketing Automation [CANONICAL] 21 | **Legal Entity:** Elly Analytics Inc. (Delaware C-corp) [CANONICAL] 22 | 23 | ## 🎯 Mission Statement [CANONICAL] 24 | **No formal mission statement established** 25 | 26 | **Company operates with clear vision and positioning instead of formal mission statement** 27 | 28 | ## 🔮 Vision Statement [CANONICAL] 29 | To become the "Cursor for performance marketing" - where marketers can simply describe what they want to achieve, and our AI makes it happen at scale. 30 | 31 | ## 📖 Company Story 32 | **For complete company narrative and strategic evolution:** [REF: company-story.md] 33 | 34 | **Summary:** Elly Analytics was created in 2022 as a spin-off from the founders' 15-year marketing agency, specifically to serve lead-generating businesses with multi-touch attribution. Currently transitioning from analytics platform to AI-powered marketing automation with "Cursor for performance marketing" vision. 35 | 36 | ## 🎨 Brand Identity 37 | 38 | ### Brand Positioning [CANONICAL - from company strategy] 39 | - **Market Position:** "Cursor for performance marketing" - AI-first marketing automation 40 | - **Technical Differentiation:** Natural language AI interface vs traditional no-code rule builders 41 | - **Target Market:** Lead-generating businesses spending $50k+/month on performance marketing 42 | 43 | ### Visual Identity [CANONICAL - from pitch deck] 44 | - **Primary Colors:** Purple/Violet and Yellow 45 | - **Logo:** Yellow "Elly" text on purple background 46 | - **Typography:** [PLACEHOLDER: Font families used] 47 | 48 | ### Brand Voice & Personality [PLACEHOLDER: To be formalized] 49 | *Note: Current brand voice and personality guidelines need to be established and documented* 50 | 51 | ## 📊 Key Metrics & Team Information 52 | **For detailed financial metrics and performance data:** [REF: 06-Financials/financial-summary.md] 53 | **For team structure and personnel information:** [REF: 05-Team/team-overview.md] 54 | 55 | **Current Status (June 2025):** 56 | - **Market Position:** Leader in multi-touch attribution for lead-generating businesses 57 | - **Current Platform:** Elly 2.0 operational, Elly 3.0 AI platform in development 58 | - **Strategic Focus:** Transitioning from analytics to AI-powered automation 59 | 60 | ## 📍 Contact Information 61 | 62 | **General Inquiries:** hello@ellyanalytics.com [CANONICAL] 63 | **CEO:** seva.ustinov@ellyanalytics.com [CANONICAL] 64 | **Co-founder:** kirill.kasimskiy@ellyanalytics.com [CANONICAL] 65 | **Sales:** Contact through website or founders directly [CANONICAL] 66 | 67 | ## 🌐 Social Media 68 | - LinkedIn: https://www.linkedin.com/company/elly-analytics/ 69 | - YouTube: https://www.youtube.com/@ellyanalytics 70 | 71 | --- 72 | 73 | ## Template Customization Guide 74 | 75 | ### Replace All Company-Specific Information: 76 | - **Company Name**: Replace "Elly Analytics" with your company name 77 | - **Contact Information**: Update all email addresses, phone numbers, and addresses 78 | - **Founding Information**: Update founding date, headquarters location, legal entity 79 | - **Industry/Market**: Modify industry classification and market positioning 80 | - **Vision/Mission**: Replace with your actual vision and mission statements 81 | - **Brand Identity**: Update colors, logo description, and brand positioning 82 | - **Social Media**: Replace with your actual social media profiles 83 | 84 | ### Maintain Template Structure: 85 | - **Keep [CANONICAL] markings** for your single source of truth information 86 | - **Update [REF:] tags** to point to your actual file locations 87 | - **Preserve section organization** for consistency with other strategy documents 88 | - **Use [PLACEHOLDER:] tags** for information you need to gather 89 | 90 | ### File Integration: 91 | - **Ensure company-story.md aligns** with basic information provided here 92 | - **Update cross-references** in other strategy documents to reflect your information 93 | - **Coordinate with team** to ensure all canonical information is accurate 94 | 95 | --- 96 | 97 | [LAST UPDATED: June 2025 by Seva Ustinov - TEMPLATE EXAMPLE] -------------------------------------------------------------------------------- /setup/update-all.ps1: -------------------------------------------------------------------------------- 1 | # PowerShell script for updating AI First Workspace Template repositories 2 | 3 | # ⚠️ CONFIGURATION REQUIRED ⚠️ 4 | # Before running this script, customize these variables for your organization: 5 | 6 | # TODO: Replace with your development repository names (same as in clone-all-repos.ps1) 7 | # Examples: @("MyApp", "MyAPI", "MyMobileApp") or @("Frontend", "Backend", "Mobile") 8 | $DEV_REPOS = @("YOUR-PRODUCT-1", "YOUR-PRODUCT-2", "YOUR-PRODUCT-3") 9 | 10 | # ============================================================================ 11 | # Configuration check 12 | if ($DEV_REPOS -contains "YOUR-PRODUCT-1") { 13 | Write-Host "⚠️ CONFIGURATION REQUIRED" -ForegroundColor Red 14 | Write-Host "" 15 | Write-Host "Before running this script, you need to customize it for your organization:" -ForegroundColor Yellow 16 | Write-Host "" 17 | Write-Host "1. Open this file: setup\update-all.ps1" 18 | Write-Host "2. Replace the `$DEV_REPOS array with your actual repository names" 19 | Write-Host " (should match what you configured in clone-all-repos.ps1)" 20 | Write-Host "" 21 | Write-Host "Example configuration:" -ForegroundColor Cyan 22 | Write-Host ' $DEV_REPOS = @("MyMainApp", "MyAPI", "MyDashboard")' 23 | Write-Host "" 24 | Write-Host "💡 Pro tip: Ask your AI assistant to help customize this script!" -ForegroundColor Green 25 | exit 1 26 | } 27 | 28 | Write-Host "🔄 Updating AI First Workspace Template..." -ForegroundColor Green 29 | Write-Host "" 30 | 31 | # Update workspace repository itself 32 | Write-Host "📋 Updating workspace template..." -ForegroundColor Cyan 33 | git pull 34 | Write-Host "" 35 | 36 | # Array of documentation repositories 37 | $docRepos = @("Strategy", "Product", "SalesAndMarketing", "Operations", "Operations/Hiring", "Finance", "Legal-HR") 38 | 39 | # Update documentation repositories in Docs/ 40 | Write-Host "📚 Updating Documentation repositories..." -ForegroundColor Cyan 41 | foreach ($repo in $docRepos) { 42 | $repoPath = "Docs/$repo" 43 | if (Test-Path $repoPath) { 44 | Write-Host "📱 Updating $repo repository..." -ForegroundColor Yellow 45 | try { 46 | Push-Location $repoPath 47 | git pull 48 | Pop-Location 49 | } 50 | catch { 51 | Write-Host " ⚠️ Update failed (possibly empty repository)" -ForegroundColor Red 52 | } 53 | } 54 | else { 55 | Write-Host "ℹ️ $repo repository not yet cloned (run .\setup\clone-all-repos.ps1)" -ForegroundColor Yellow 56 | } 57 | } 58 | Write-Host "" 59 | 60 | # Update development repositories in Dev/ 61 | Write-Host "💻 Updating Development repositories..." -ForegroundColor Cyan 62 | foreach ($repo in $DEV_REPOS) { 63 | $repoPath = "Dev/$repo" 64 | if (Test-Path $repoPath) { 65 | Write-Host "⚙️ Updating $repo repository..." -ForegroundColor Yellow 66 | try { 67 | Push-Location $repoPath 68 | git pull 69 | Pop-Location 70 | } 71 | catch { 72 | Write-Host " ⚠️ Update failed (possibly empty repository)" -ForegroundColor Red 73 | } 74 | } 75 | else { 76 | Write-Host "ℹ️ $repo repository not yet cloned (run .\setup\clone-all-repos.ps1)" -ForegroundColor Yellow 77 | } 78 | } 79 | Write-Host "" 80 | 81 | # Update Presales repository 82 | Write-Host "💼 Updating Presales repository..." -ForegroundColor Cyan 83 | if (Test-Path "Presales") { 84 | Write-Host "🎯 Updating Presales repository..." -ForegroundColor Yellow 85 | try { 86 | Push-Location "Presales" 87 | git pull 88 | Pop-Location 89 | } 90 | catch { 91 | Write-Host " ⚠️ Update failed (possibly empty repository)" -ForegroundColor Red 92 | } 93 | } 94 | else { 95 | Write-Host "ℹ️ Presales repository not yet cloned (run .\setup\clone-all-repos.ps1)" -ForegroundColor Yellow 96 | } 97 | Write-Host "" 98 | 99 | # Update Projects repository 100 | Write-Host "🚀 Updating Projects repository..." -ForegroundColor Cyan 101 | if (Test-Path "Projects/.git") { 102 | Write-Host "📊 Updating Projects repository..." -ForegroundColor Yellow 103 | try { 104 | Push-Location "Projects" 105 | git pull 106 | Pop-Location 107 | } 108 | catch { 109 | Write-Host " ⚠️ Update failed for Projects repository" -ForegroundColor Red 110 | } 111 | } 112 | else { 113 | Write-Host "ℹ️ Projects repository not yet cloned (run .\setup\clone-all-repos.ps1)" -ForegroundColor Yellow 114 | } 115 | Write-Host "" 116 | 117 | Write-Host "🎉 Workspace update complete!" -ForegroundColor Green 118 | Write-Host "" 119 | Write-Host "📊 Summary:" -ForegroundColor Cyan 120 | Write-Host " 📚 Documentation repos in Docs/" 121 | Write-Host " 💻 Development repos in Dev/ ($($DEV_REPOS -join ', '))" 122 | Write-Host " 🚀 Project repos in Projects/" 123 | Write-Host " 💼 Presales repo in root level" 124 | Write-Host "" 125 | Write-Host "💡 To add a new client project:" -ForegroundColor Yellow 126 | Write-Host " cd Projects && git clone " -------------------------------------------------------------------------------- /Docs/Strategy/Investor-Updates/example-quarterly-update-template.md: -------------------------------------------------------------------------------- 1 | # Quarterly Investor Update Template 2 | *[TEMPLATE EXAMPLE - This shows how to structure quarterly investor updates. Replace with your actual company data.]* 3 | 4 | --- 5 | 6 | **⚠️ TEMPLATE NOTICE:** This file contains an example quarterly investor update for "[COMPANY_NAME]" demonstrating how to communicate key metrics, progress, and strategic updates to investors. Replace all content below with your actual company data while maintaining the professional communication structure. 7 | 8 | --- 9 | 10 | # [COMPANY_NAME] Investor Update, Q[X]'[YY] 11 | *[EXAMPLE COMPANY - Replace with your company's quarterly update]* 12 | 13 | ## Message to Investors 14 | Hey [INVESTOR_GROUP], 15 | 16 | It's a pleasure to announce Q[X]'[YY] results. 17 | 18 | [BRIEF_INTRO_MESSAGE] - Brief context about the quarter and key highlights 19 | 20 | [METRIC_DEFINITIONS] - Any important definitions or context for metrics 21 | Example: ARR = Last month's MRR * 12. Last month's MRR = actual payment, after any discounts 22 | 23 | ## Key Metrics: 24 | — Q[X] ARR: $[X], Committed ARR: $[Y]. [MILESTONE_ACHIEVEMENT] 25 | — ARR YoY Growth: [X]x 26 | — New sales: [X] deals 27 | — Active Clients: [X] 28 | — ARR per Client: $[X] 29 | — Total Revenue (Q[X]): $[X] 30 | — Burn Rate: $[X]K/month 31 | 32 | Check out our data room for more metrics and [YEAR]-[YEAR] forecasts: [DATA_ROOM_LINK] 33 | 34 | ## Strategic Announcement: 35 | **[MAJOR_INITIATIVE_TITLE]** 36 | 37 | [PROBLEM_STATEMENT] - Brief description of the market problem you're solving 38 | 39 | [SPECIFIC_CHALLENGES] - Detailed breakdown of customer pain points: 40 | 1. **[CHALLENGE_1]** – [CURRENT_SOLUTION_STATUS] 41 | 2. **[CHALLENGE_2]** – [MORE_COMPLEX_CHALLENGE_DESCRIPTION] 42 | 43 | [SOLUTION_OVERVIEW] - Your strategic response to these challenges 44 | 45 | ### Why this matters: 46 | - [BENEFIT_1] - [IMPACT_DESCRIPTION] 47 | - [BENEFIT_2] - [FINANCIAL_IMPACT] 48 | - [BENEFIT_3] - [VALUE_PROPOSITION_ENHANCEMENT] 49 | 50 | [EXPERTISE_POSITIONING] - How your team's background/experience supports this initiative 51 | 52 | [CURRENT_STATUS] - Where you are in development/implementation 53 | 54 | [RESOURCE_ALLOCATION] - Team and resource commitment to this initiative 55 | 56 | [EARLY_RESULTS] - Any initial traction or validation 57 | 58 | [STRATEGIC_IMPACT] - How this positions the company for future growth 59 | 60 | ## Sales & Marketing 61 | 62 | *These are gross numbers, not cohort numbers.* 63 | 64 | We closed [X] new deals in Q[X], which is [ABOVE/BELOW/MEETS] expectations. 65 | 66 | [SALES_STRATEGY_UPDATE] - Any changes to sales approach or methodology 67 | 68 | **Key Metrics:** 69 | — [PIPELINE_METRIC]: [X] (compared to [Y] in [PREVIOUS_PERIOD]) 70 | — [QUALIFICATION_METRIC]: [DESCRIPTION_OF_CHANGES] 71 | — [CONVERSION_METRIC]: [PERFORMANCE_DATA] 72 | 73 | **Sales Process Improvements:** 74 | — [IMPROVEMENT_1] - [DESCRIPTION_AND_IMPACT] 75 | — [IMPROVEMENT_2] - [DESCRIPTION_AND_IMPACT] 76 | — [IMPROVEMENT_3] - [DESCRIPTION_AND_IMPACT] 77 | 78 | **Marketing Updates:** 79 | — [MARKETING_INITIATIVE_1] 80 | — [MARKETING_INITIATIVE_2] 81 | — [MARKETING_INITIATIVE_3] 82 | 83 | [RESOURCE_ALLOCATION] - How S&M resources were allocated this quarter 84 | 85 | ## Product Updates 86 | 87 | ### [MAJOR_PRODUCT_INITIATIVE] 88 | [DESCRIPTION_OF_MAJOR_PRODUCT_WORK] - See announcement above for details. 89 | 90 | ### [PRODUCT_CATEGORY_1] Updates 91 | — [FEATURE_1] - [DESCRIPTION_AND_BENEFIT] 92 | — [FEATURE_2] - [DESCRIPTION_AND_BENEFIT] 93 | — [FEATURE_3] - [DESCRIPTION_AND_BENEFIT] 94 | — [FEATURE_4] - [DESCRIPTION_AND_BENEFIT] 95 | — [FEATURE_5] - [DESCRIPTION_AND_BENEFIT] 96 | — [INTEGRATION_UPDATE] - [LIST_OF_NEW_INTEGRATIONS] 97 | 98 | ### [PRODUCT_CATEGORY_2] 99 | [DESCRIPTION_OF_INFRASTRUCTURE_OR_TECHNICAL_IMPROVEMENTS] 100 | 101 | ### [PRODUCT_CATEGORY_3] 102 | [DESCRIPTION_OF_INTERNAL_TOOLS_OR_EFFICIENCY_IMPROVEMENTS] 103 | 104 | ## Customer Health & Churn 105 | 106 | Out of [X] clients in [START_OF_QUARTER], [CHURN_SUMMARY] in Q[X]. 107 | 108 | **Churn Details:** 109 | — [CLIENT_DESCRIPTION]: [CHURN_REASON], $[ARR_LOST], after [DURATION]. [ADDITIONAL_CONTEXT] 110 | — [CLIENT_DESCRIPTION]: [CHURN_REASON], $[ARR_LOST], after [DURATION]. [ADDITIONAL_CONTEXT] 111 | 112 | **Retention Insights:** 113 | — [RETENTION_METRIC]: [PERCENTAGE] 114 | — [EXPANSION_METRIC]: [DESCRIPTION] 115 | — [HEALTH_SCORE_INSIGHTS]: [ANALYSIS] 116 | 117 | ## Financial Performance 118 | 119 | **Burn Rate:** The burn rate in Q[X]'[YY] was $[X]K/month. 120 | 121 | **Cash Position:** [CASH_ON_HAND] as of [DATE] 122 | **Runway:** Approximately [X] months at current burn rate 123 | 124 | **Revenue Growth:** [REVENUE_GROWTH_ANALYSIS] 125 | **Unit Economics:** [CAC/LTV_UPDATES_IF_APPLICABLE] 126 | 127 | ## Fundraising Update 128 | 129 | [FUNDRAISING_STATUS] - Current status of any fundraising activities 130 | 131 | **Key Updates:** 132 | — [FUNDING_METRIC]: $[X]k in [COMMITMENT_TYPE] 133 | — [STRATEGY_STATUS]: [DESCRIPTION_OF_APPROACH] 134 | — [TIMELINE]: [EXPECTED_TIMING_AND_NEXT_STEPS] 135 | 136 | [INVESTOR_ENGAGEMENT_REQUEST] - Any specific asks or discussion topics for investor calls 137 | 138 | -------------------------------------------------------------------------------- /Docs/Operations/Hiring/Job-Openings/Senior-Marketing-Analyst/Screening-Agent/README.md: -------------------------------------------------------------------------------- 1 | # [COMPANY_NAME] Screening Agent 2 | *[TEMPLATE EXAMPLE - This is a functional screening agent for demonstration purposes]* 3 | 4 | This automated agent assists with the initial screening of candidates for the Senior Marketing Analyst role by analyzing their CVs and screening interview notes. 5 | 6 | ## Template Configuration 7 | 8 | **Before using this agent in your company:** 9 | 10 | 1. **Replace Company Name Placeholder:** 11 | - In `agent-prompt.md`: Replace `[COMPANY_NAME]` with your actual company name 12 | - In `agent.py`: Replace `[COMPANY_NAME]` with your actual company name 13 | - In `agent-config.json`: Replace `[COMPANY_NAME]` with your actual company name 14 | - In `run-agent.sh`: Replace `[COMPANY_NAME]` with your actual company name 15 | 16 | 2. **Customize Evaluation Criteria:** 17 | - Modify the critical competencies in `agent-config.json` 18 | - Update fit thresholds based on your hiring standards 19 | - Adjust the red flags and role expectation factors 20 | 21 | 3. **Set Up Directory Structure:** 22 | - Ensure your global rules files exist in the expected locations 23 | - Update file paths in `agent-config.json` if your structure differs 24 | 25 | ## Overview 26 | 27 | The screening agent uses AI-powered analysis to: 28 | 29 | 1. Review candidate CVs and screening interview transcripts 30 | 2. Evaluate candidate suitability based on initial impressions 31 | 3. Assess alignment with role requirements 32 | 4. Generate structured screening evaluations 33 | 5. Provide recommendations on next steps in the hiring process 34 | 35 | > **⚠️ IMPORTANT NOTE:** This is a demonstration agent that uses placeholder screening logic. For production use, you need to integrate it with a real LLM API (OpenAI, Anthropic, etc.) or custom AI model to perform actual intelligent evaluation of candidate materials. 36 | 37 | ## Quick Start for Template Users 38 | 39 | 1. **Setup:** 40 | ```bash 41 | # Install dependencies 42 | pip install markdown 43 | 44 | # Replace company name placeholders 45 | sed -i 's/\[COMPANY_NAME\]/YourCompany/g' agent-prompt.md 46 | sed -i 's/\[COMPANY_NAME\]/YourCompany/g' agent.py 47 | sed -i 's/\[COMPANY_NAME\]/YourCompany/g' agent-config.json 48 | sed -i 's/\[COMPANY_NAME\]/YourCompany/g' run-agent.sh 49 | ``` 50 | 51 | 2. **Run screening:** 52 | ```bash 53 | # Make script executable 54 | chmod +x run-agent.sh 55 | 56 | # Screen all candidates 57 | ./run-agent.sh 58 | 59 | # Or screen specific candidate 60 | ./run-agent.sh --candidate Candidate-John-Doe 61 | ``` 62 | 63 | 3. **Customize for your needs:** 64 | - Modify critical competencies in `agent-config.json` 65 | - Adjust red flags and role expectation factors 66 | - Update file paths for your directory structure 67 | 68 | ## Setup Requirements 69 | 70 | - Python 3.7 or higher 71 | - Required Python packages: 72 | - markdown 73 | - argparse 74 | 75 | You can install the required packages using pip: 76 | 77 | ``` 78 | pip install markdown 79 | ``` 80 | 81 | ## Directory Structure 82 | 83 | The agent expects a specific directory structure: 84 | 85 | ``` 86 | Senior-Marketing-Analyst/ 87 | ├── Global-Rules/ 88 | │ ├── General-Hiring-Policy.md 89 | │ ├── Scoring-Framework.md 90 | │ └── Interview-Guidelines.md 91 | ├── Position-Description.md 92 | ├── Role-Competency-Matrix.md 93 | ├── Candidates/ 94 | │ ├── Candidate-John-Doe/ 95 | │ │ ├── CV.md 96 | │ │ ├── Fathom-Screening-Interview.md 97 | │ │ └── ... 98 | │ └── Other candidates... 99 | └── Screening-Agent/ 100 | ├── agent.py 101 | ├── agent-config.json 102 | ├── agent-prompt.md 103 | └── README.md (this file) 104 | ``` 105 | 106 | ## Configuration 107 | 108 | The agent is configured via the `agent-config.json` file. Key settings include: 109 | 110 | - Context files that define evaluation criteria 111 | - Critical competencies for the role 112 | - Fit thresholds for candidate evaluation 113 | - Output file settings 114 | 115 | ## Usage 116 | 117 | To evaluate all candidates: 118 | 119 | ```bash 120 | python agent.py 121 | ``` 122 | 123 | To evaluate a specific candidate: 124 | 125 | ```bash 126 | python agent.py --candidate Candidate-John-Doe 127 | ``` 128 | 129 | ## Output Files 130 | 131 | For each candidate, the agent generates: 132 | 133 | 1. **Screening-Evaluation.md** - Initial evaluation with recommendations 134 | 2. **AI-Notes.md** - Additional AI-generated insights about the candidate 135 | 136 | ## Human Approval 137 | 138 | By default, the agent requires human approval before finalizing evaluations. This setting can be adjusted in the configuration file. 139 | 140 | ## Relationship to Full Evaluation Agent 141 | 142 | The Screening Agent works alongside the Full Evaluation Agent in a two-stage process: 143 | 144 | 1. **Screening Agent**: Performs initial candidate screening based on CV and screening interview 145 | 2. **Full Evaluation Agent**: Conducts comprehensive evaluation including technical interview results 146 | 147 | This allows for a more efficient hiring process by quickly identifying promising candidates for more in-depth evaluation. -------------------------------------------------------------------------------- /Docs/Operations/Hiring/Job-Openings/Senior-Marketing-Analyst/Candidates/Example-Candidate-B-Average/README.md: -------------------------------------------------------------------------------- 1 | # Example Candidate B - Average Level 2 | *[TEMPLATE EXAMPLE - All files in this folder contain fictional data for demonstration purposes]* 3 | 4 | ## Overview 5 | This folder demonstrates a complete candidate evaluation for a **mid-level** candidate who shows potential but has significant skill gaps requiring development investment. 6 | 7 | ## Candidate Profile: Michael Thompson 8 | - **Position:** Senior Marketing Analyst 9 | - **Experience:** 2+ years in marketing analytics 10 | - **Key Strength:** Strong motivation and cultural fit 11 | - **Key Weakness:** Limited production SQL and data engineering experience 12 | - **Final Decision:** Conditional hire with extended onboarding 13 | 14 | ## Files Structure 15 | 16 | ### 📄 `CV.md` 17 | **Purpose:** Example resume showing mixed experience levels 18 | **Key Elements:** 19 | - Python/Pandas heavy background (not SQL) 20 | - Good domain knowledge in marketing analytics 21 | - Limited experience with APIs and data engineering 22 | - Honest about skill gaps and learning goals 23 | - Clear template markings for customization 24 | 25 | ### 📞 `Fathom-Screening-Interview.md` 26 | **Purpose:** Demonstrates screening interview for moderate candidate 27 | **Key Elements:** 28 | - Honest discussion about technical limitations 29 | - Strong motivation for learning and growth 30 | - Good cultural fit assessment 31 | - Realistic salary expectations 32 | - Clear next steps and concerns identified 33 | 34 | ### 🔧 `Fathom-Technical-Interview.md` 35 | **Purpose:** Shows technical assessment revealing specific skill gaps 36 | **Key Elements:** 37 | - SQL fundamentals present but limited depth 38 | - Window functions attempted but incomplete 39 | - Performance optimization knowledge gaps 40 | - Good problem-solving approach despite limitations 41 | - Detailed technical scoring breakdown 42 | 43 | ### 📊 `Screening-Evaluation.md` 44 | **Purpose:** Structured evaluation of screening interview results 45 | **Key Elements:** 46 | - Balanced assessment of strengths vs. concerns 47 | - Clear risk identification and mitigation strategies 48 | - Detailed recommendations for technical interview 49 | - Decision framework for borderline candidates 50 | 51 | ### 🎯 `Final-Score.md` 52 | **Purpose:** Comprehensive final evaluation and hiring decision 53 | **Key Elements:** 54 | - Detailed competency scoring with explanations 55 | - Conditional hire recommendation with development plan 56 | - Risk assessment and mitigation strategies 57 | - 6-month onboarding structure 58 | - Long-term potential evaluation 59 | 60 | ## Template Usage Instructions 61 | 62 | ### When to Use This Example: 63 | 1. **Borderline Candidates:** Those with potential but skill gaps 64 | 2. **Training Scenarios:** Teaching hiring managers about development decisions 65 | 3. **Process Calibration:** Ensuring consistent evaluation standards 66 | 4. **Documentation:** Showing proper evaluation methodology 67 | 68 | ### Customization Guidelines: 69 | 1. **Replace Names:** Change "Michael Thompson" to actual candidate names 70 | 2. **Update Dates:** Modify interview dates to match your timeline 71 | 3. **Adjust Competencies:** Modify scores based on your specific requirements 72 | 4. **Customize Development Plans:** Tailor onboarding to your company structure 73 | 5. **Update Template Markers:** Remove "[TEMPLATE EXAMPLE]" headers 74 | 75 | ### Key Decision Factors Demonstrated: 76 | - **Growth Potential vs. Immediate Productivity** 77 | - **Investment in Training vs. Hiring Ready Candidates** 78 | - **Cultural Fit Importance in Borderline Decisions** 79 | - **Structured Development Planning** 80 | - **Risk Assessment for Conditional Hires** 81 | 82 | ## Lessons for Hiring Teams 83 | 84 | ### ✅ What This Example Shows Well: 85 | - Honest assessment of both strengths and limitations 86 | - Structured approach to development planning 87 | - Clear documentation of decision rationale 88 | - Balanced consideration of multiple factors 89 | - Specific, actionable next steps 90 | 91 | ### 📚 Learning Opportunities: 92 | - How to evaluate learning potential vs. current skills 93 | - Balancing technical requirements with growth mindset 94 | - Creating development plans for skill gap closure 95 | - Managing expectations for conditional hires 96 | - Documenting hiring decisions for future reference 97 | 98 | ### 🎯 Decision Framework Demonstration: 99 | This example shows how to handle the common scenario where a candidate: 100 | - Has good fundamentals but lacks specific technical skills 101 | - Shows strong motivation and cultural alignment 102 | - Requires significant investment to reach productivity 103 | - Could become valuable with proper development support 104 | 105 | ## Template Maintenance 106 | 107 | ### When to Update This Example: 108 | - Job requirements change significantly 109 | - Company onboarding process evolves 110 | - Technical skill priorities shift 111 | - Hiring standards are adjusted 112 | 113 | ### How to Keep Current: 114 | - Review quarterly with hiring team 115 | - Update based on successful/unsuccessful conditional hires 116 | - Incorporate feedback from technical interviewers 117 | - Align with current company development resources 118 | 119 | --- 120 | 121 | **Template Effectiveness:** This example effectively demonstrates handling candidates who require development investment while maintaining hiring standards and creating clear success pathways. --------------------------------------------------------------------------------