@ema.co/mcp-toolkit 2026.1.24 → 2026.1.25

package/dist/mcp/handlers/reference/index.js

@@ -276,13 +276,113 @@ export async function handleReference(args, context) {
         const result = validateWorkflowPrompt(args.validate_prompt);
         return result;
     }
+    // ─────────────────────────────────────────────────────────────────────────
+    // type="demo_kits" or demo_kits=true - List demo kits
+    // ─────────────────────────────────────────────────────────────────────────
+    if (type === "demo_kits" || args.demo_kits) {
+        return {
+            demo_kits: [
+                {
+                    id: "finance-ap",
+                    name: "Finance - Accounts Payable Automation",
+                    domain: "finance",
+                    personas: 2,
+                    tags: ["finance", "invoice", "automation", "coupa"],
+                    description: "End-to-end AP invoice processing and generation",
+                },
+                {
+                    id: "sales-sdr",
+                    name: "Sales Development",
+                    domain: "sales",
+                    personas: 2,
+                    tags: ["sales", "outbound", "prospecting"],
+                    description: "SDR workflow automation for prospecting and outreach",
+                },
+                {
+                    id: "support-tier1",
+                    name: "Customer Support T1",
+                    domain: "support",
+                    personas: 2,
+                    tags: ["support", "voice", "chat"],
+                    description: "Tier 1 customer support automation",
+                },
+            ],
+            count: 3,
+            _tip: "Use reference(demo_kit=\"finance-ap\") to get full kit details",
+        };
+    }
+    // ─────────────────────────────────────────────────────────────────────────
+    // demo_kit="{id}" - Get specific demo kit
+    // ─────────────────────────────────────────────────────────────────────────
+    if (args.demo_kit) {
+        const kitId = args.demo_kit;
+        // Return finance-ap kit (the one we created)
+        if (kitId === "finance-ap") {
+            return {
+                id: "finance-ap",
+                name: "Finance - Accounts Payable Automation",
+                version: "1.0.0",
+                domain: "finance",
+                tags: ["finance", "invoice", "automation", "ap-automation", "ar-automation", "coupa", "usage-billing"],
+                personas: [
+                    {
+                        id: "fa91cb51-58fe-4255-b2d2-0b3e3a72cf7e",
+                        name: "AP Invoice Processing",
+                        role: "primary",
+                        description: "Processes inbound invoices: extract, validate, create in Coupa, notify supplier",
+                        workflow_nodes: 5,
+                    },
+                    {
+                        id: "d73c8dca-d340-4541-a7ff-ae69f2810906",
+                        name: "AP Invoice Generation",
+                        role: "primary",
+                        description: "Generates outbound invoices: validate customer/usage/contract, generate document",
+                        workflow_nodes: 12,
+                    },
+                ],
+                target_audience: {
+                    primary: "AP Manager / Controller",
+                    secondary: ["CFO", "RevOps Manager", "IT Director"],
+                    company_size: "mid-market to enterprise",
+                    industries: ["manufacturing", "retail", "saas", "distribution"],
+                },
+                roi_summary: {
+                    ap_processing_savings: "$105K/month at 10K invoices",
+                    invoice_generation_savings: "$73K/month at 500 invoices",
+                    revenue_protection: "$450K/month at $10M billings",
+                },
+                demo_script: "docs/demos/ap-invoice-processing.md",
+                _tip: "Use persona(method=\"analyze\", id=\"...\") to analyze each persona's workflow",
+            };
+        }
+        return { error: `Demo kit not found: ${kitId}`, available: ["finance-ap", "sales-sdr", "support-tier1"] };
+    }
+    // ─────────────────────────────────────────────────────────────────────────
+    // tags=true - Get tagging taxonomy
+    // ─────────────────────────────────────────────────────────────────────────
+    if (args.tags) {
+        return {
+            categories: {
+                domain: ["finance", "sales", "support", "hr", "it", "legal", "marketing", "operations", "procurement"],
+                capability: ["voice", "chat", "dashboard", "document", "automation", "analysis", "extraction", "validation"],
+                use_case: ["invoice", "billing", "onboarding", "compliance", "reporting", "routing", "scheduling", "order", "claims"],
+                integration: ["coupa", "salesforce", "servicenow", "workday", "sap", "oracle", "netsuite", "hubspot", "zendesk", "jira"],
+                complexity: ["simple", "moderate", "complex"],
+                bundle: ["demo-kit", "bundle", "template", "example"],
+            },
+            _tip: "Use tags to filter personas and demo kits. Tags help organize and discover related content.",
+        };
+    }
     return {
-        error: "Specify type (envs|actions|templates|patterns|widgets|concepts), or use concept, guidance, questions, mistakes, checklist, execution, check_types, validate_prompt",
+        error: "Specify type (envs|actions|templates|patterns|widgets|concepts|demo_kits), or use concept, guidance, questions, mistakes, checklist, execution, check_types, validate_prompt, demo_kit, tags",
         examples: [
             'reference(type="envs")',
             'reference(type="actions")',
             'reference(type="actions", id="send_email")',
             'reference(type="patterns")',
+            'reference(type="demo_kits")',
+            'reference(demo_kit="finance-ap")',
+            'reference(tags=true)',
             'reference(concept="HITL")',
             'reference(guidance="categorizer-routing")',
             'reference(questions=true)',

package/dist/mcp/tools-consolidated.js

@@ -513,6 +513,11 @@ This tool still works but shows a deprecation warning.`,
   reference(guidance="categorizer-routing")
   reference(questions=true)  # Qualifying questions
 
+**Demo Kits & Tags**:
+  reference(type="demo_kits")              # List all demo kits
+  reference(demo_kit="finance-ap")         # Get specific kit
+  reference(tags=true)                     # Get tagging taxonomy
+
 **Debugging**:
   reference(mistakes=true)
   reference(checklist=true)
@@ -524,7 +529,7 @@ This tool still works but shows a deprecation warning.`,
                 // Type selector (v2)
                 type: {
                     type: "string",
-                    enum: ["envs", "actions", "templates", "patterns", "widgets", "concepts"],
+                    enum: ["envs", "actions", "templates", "patterns", "widgets", "concepts", "demo_kits"],
                     description: "What type of reference information"
                 },
                 // Actions
@@ -576,6 +581,10 @@ This tool still works but shows a deprecation warning.`,
                     description: "Check type compatibility"
                 },
                 validate_prompt: { type: "string", description: "Validate workflow prompt" },
+                // Demo Kits & Tags
+                demo_kits: { type: "boolean", description: "List available demo kits" },
+                demo_kit: { type: "string", description: "Get specific demo kit by ID (e.g., 'finance-ap')" },
+                tags: { type: "boolean", description: "Get tagging taxonomy for personas and kits" },
             }),
         },
         // ═══════════════════════════════════════════════════════════════════════

package/docs/demos/ap-invoice-generation.md

@@ -0,0 +1,347 @@
+# AP Invoice Generation - Demo Script
+
+**Persona ID**: `d73c8dca-d340-4541-a7ff-ae69f2810906`  
+**Type**: Chat  
+**Complexity**: High (12 nodes, multi-stage validation)  
+**Generated**: 2026-01-24
+
+---
+
+## Target Persona
+
+| Role | Profile |
+|------|---------|
+| **Primary** | Revenue Operations Manager / Billing Manager |
+| **Secondary** | CFO, Finance Director, Deal Desk Manager |
+| **Company Size** | Mid-market to Enterprise (SaaS, usage-based billing) |
+| **Industry** | Software/SaaS, Telecom, Utilities, Cloud Services |
+| **Business Model** | Usage-based, subscription, hybrid pricing |
+
+**Buyer Characteristics:**
+- Managing complex B2B contracts with tiered pricing
+- Handling usage-based billing across multiple products
+- Consolidating invoices across subsidiary accounts
+- Dealing with contract amendments and credits mid-cycle
+- Under pressure for accurate, timely invoicing
+- Managing DSO (Days Sales Outstanding) targets
+
+---
+
+## Pain Points Addressed
+
+| Pain Point | Impact | How Ema Solves It |
+|------------|--------|-------------------|
+| **Manual invoice creation** | 2-4 hours per enterprise invoice | Automated in minutes |
+| **Usage data aggregation** | Scattered across 5+ systems | Single unified view |
+| **Contract compliance errors** | Revenue leakage 3-5% | Automated validation |
+| **Pricing mistakes** | Credits, disputes, churn | Contract-accurate pricing |
+| **Parent/child billing** | Complex consolidation | Automatic hierarchy handling |
+| **Audit trail gaps** | SOX compliance risk | Full generation history |
+| **Late invoices** | DSO impact, cash flow | Same-day generation |
+| **Format inconsistency** | Unprofessional, customer complaints | Standardized templates |
+
+---
+
+## Workflow Overview
+
+```
+Data Sources → Validate Customer → Validate Usage → Validate Contract → Generate Invoice → Publish Document
+     ↓              ↓                    ↓                 ↓                   ↓              ↓
+  (6 sources)   (Salesforce,        (Usage metrics,   (Contract terms,   (Markdown       (DOCX
+                 Contracts,          API logs,         payment terms,     template)       download)
+                 Compliance)         Proration)        discounts)
+```
+
+### Nodes (12 total)
+
+| Node | Type | Purpose |
+|------|------|---------|
+| **Convert to Text** | `convert_to_text` | Normalizes inputs |
+| **SFDC API Placeholder** | `fixed_response` | Salesforce account data |
+| **Contract Placeholder** | `fixed_response` | Contract terms & billing |
+| **Reference File Placeholder** | `fixed_response` | Customer master data |
+| **Product Offering Placeholder** | `fixed_response` | Product catalog & pricing |
+| **Usage Placeholder** | `fixed_response` | Usage metrics |
+| **Payment Records Placeholder** | `fixed_response` | Payment history |
+| **Validate Customer** | `call_llm` | Verifies customer, credit, compliance |
+| **Validate Usage** | `call_llm` | Aggregates & validates usage data |
+| **Validate Contract** | `call_llm` | Validates contract terms & pricing |
+| **Generate Invoice** | `call_llm` | Creates professional markdown invoice |
+| **Publish Document** | `generate_document` | Converts to downloadable DOCX |
+
+---
+
+## Key Talking Points
+
+### 1. **Multi-Source Data Orchestration**
+> "Ema pulls from Salesforce, your contract management system, usage databases, and payment history - then orchestrates it all into a single validated invoice. No more copy-pasting between systems."
+
+### 2. **Triple Validation Pipeline**
+> "Before generating anything, Ema runs three validation stages:
+> 1. **Customer Validation** - Account hierarchy, credit status, compliance
+> 2. **Usage Validation** - Aggregate, prorate, convert units
+> 3. **Contract Validation** - Terms, discounts, commitments
+>
+> Only if all three pass does the invoice get generated."
+
+### 3. **Complex Billing Scenarios**
+> "Usage-based? Tiered pricing? Volume discounts? Minimum commitments? Mid-cycle amendments? Ema handles them all - the same logic your best billing analyst would use, but consistent every time."
+
+### 4. **Professional Document Output**
+> "The invoice isn't just data - it's a professional document with your branding, proper formatting, payment instructions, and compliance information. Download as DOCX or PDF."
+
+### 5. **Consolidated Billing**
+> "For enterprise customers with subsidiaries, Ema automatically identifies the billing hierarchy, consolidates across accounts, and applies parent-level discounts."
+
+### 6. **Audit-Ready**
+> "Every invoice generation is logged with: what data was used, what validations ran, what calculations were applied. Perfect for revenue recognition and SOX compliance."
+
+---
+
+## Demo Script
+
+### **Setup (Before Demo)**
+- [ ] Sample order/usage data ready
+- [ ] Mock Salesforce account data
+- [ ] Sample contract with tiered pricing
+- [ ] Ema workspace with this persona loaded
+
+---
+
+### **Act 1: The Problem (2 min)**
+
+**[Show current state]**
+
+> "Let me show you what enterprise invoice generation looks like today."
+
+**Talking points:**
+- "Customer places an order or usage period closes"
+- "Billing analyst opens Salesforce, finds the account"
+- "Opens contract management system, finds the contract"
+- "Opens usage database, runs reports, exports to Excel"
+- "Manually calculates: included quantities, overages, discounts"
+- "Opens Word, copies a template, types everything in"
+- "Checks, double-checks, maybe misses something"
+- "2-4 hours later, maybe the invoice is ready"
+
+**Ask:** "How many enterprise invoices does your team generate per month? What's your error rate?"
+
+---
+
+### **Act 2: The Validation Pipeline (5 min)**
+
+**[Show Ema interface]**
+
+> "Now let me show you Ema's approach - validate everything BEFORE generating."
+
+**Step 1: Data Sources**
+> "Ema connects to your systems - Salesforce, contract database, usage metrics, payment history. In production, these are live API connections. For this demo, we're using sample data."
+
+*[Show data source placeholders]*
+
+**Step 2: Customer Validation**
+> "First, Ema validates the customer. Watch what it checks:"
+
+*[Trigger workflow, show Validate Customer output]*
+
+> "It verified:
+> - Account exists in Salesforce
+> - Parent/child relationships (for consolidated billing)
+> - Credit terms and payment history
+> - Contract compliance status
+> - No open disputes
+> - Authorized billing contacts
+>
+> If ANY red flag exists, it stops and alerts. No invoice generated for a customer on credit hold."
+
+**Step 3: Usage Validation**
+> "Next, Ema aggregates and validates usage:"
+
+*[Show Validate Usage output]*
+
+> "It:
+> - Pulls from all usage sources (API logs, storage, support tickets)
+> - Aggregates by product/SKU
+> - Handles unit conversions
+> - Prorates partial periods
+> - Handles multi-tenant consolidation
+>
+> Your billing team would spend hours on this. Ema does it in seconds."
+
+**Step 4: Contract Validation**
+> "Finally, contract terms are validated against usage:"
+
+*[Show Validate Contract output]*
+
+> "It checks:
+> - Correct pricing tiers
+> - Volume discount qualifications  
+> - Minimum commitments
+> - Promotional credits still valid
+> - Contract amendments in effect
+>
+> This is where revenue leakage happens. Ema catches it."
+
+---
+
+### **Act 3: Invoice Generation (3 min)**
+
+> "With all validations passed, now Ema generates the invoice."
+
+*[Show Generate Invoice output]*
+
+**Invoice Components Generated:**
+> "The invoice includes:
+> - **Header**: Invoice number, dates, terms, contract references
+> - **Bill To / Remit To**: Full address blocks with tax IDs
+> - **Line Items**: Products, included vs actual usage, overage pricing
+> - **Adjustments**: Discounts, credits, penalties
+> - **Tax Calculations**: Jurisdiction-specific rates
+> - **Totals**: Subtotal, adjustments, tax, amount due
+> - **Compliance**: Usage metrics, contract status, milestones
+> - **Payment Info**: Wire/ACH instructions
+> - **Audit Trail**: Generation ID, timestamp"
+
+**Document Output:**
+> "And finally, it's converted to a professional document."
+
+*[Show Publish Document - DOCX download link]*
+
+> "One click to download. Ready to send to the customer."
+
+---
+
+### **Act 4: The Differentiators (3 min)**
+
+**Complex Pricing Scenarios**
+> "Let me show you how Ema handles tiered pricing."
+
+*[Walk through a tiered pricing example in the output]*
+
+> "
+> - 0-1,000 units: included in base
+> - 1,001-5,000: $0.10 each
+> - 5,001+: $0.05 each
+>
+> Ema calculated each tier correctly, showed the breakdown, and applied the right total."
+
+**Consolidated Billing**
+> "For enterprise customers with subsidiaries:"
+
+> "Ema:
+> - Identifies the ultimate parent account
+> - Finds all child accounts with billing enabled
+> - Aggregates usage across the hierarchy
+> - Applies parent-level discounts
+> - Generates one consolidated invoice"
+
+**Mid-Cycle Amendments**
+> "Contract changed mid-period? Ema handles proration automatically - you don't need to manually calculate partial months."
+
+**Audit Trail**
+> "Every invoice includes a generation ID. You can trace exactly what data was used, what validations ran, what decisions were made. Perfect for revenue recognition audits."
+
+---
+
+### **Act 5: ROI Discussion (2 min)**
+
+**Build the business case:**
+
+| Metric | Before | After | Impact |
+|--------|--------|-------|--------|
+| Time per invoice | 2-4 hours | 5 minutes | 95% reduction |
+| Pricing errors | 3-5% | <0.5% | Revenue protected |
+| DSO impact | Invoices delayed 3-5 days | Same-day | Cash flow improved |
+| Audit prep time | 40 hours/quarter | 4 hours | 90% reduction |
+| Billing headcount | 1 FTE per 200 invoices | 1 FTE per 2,000 invoices | 10x efficiency |
+
+> "If you're generating 500 enterprise invoices per month at 3 hours each, that's 1,500 hours. At $50/hour loaded cost, that's $75,000/month in labor alone.
+>
+> With Ema: 500 invoices × 5 minutes = 42 hours. That's $73,000 monthly savings."
+
+**Revenue Protection:**
+> "More importantly - if your error rate drops from 5% to 0.5% on $10M monthly billings, you've protected $450,000 in revenue per month."
+
+---
+
+### **Act 6: Next Steps (1 min)**
+
+> "Here's how we typically get started:"
+
+1. **Discovery (1 week)** - Map your data sources, pricing models, invoice formats
+2. **Pilot (2-4 weeks)** - Run Ema on one customer segment or product line
+3. **Validate** - Compare output to manual invoices, measure accuracy
+4. **Expand** - Roll out to full invoice generation
+5. **Optimize** - Add more data sources, approval workflows, integrations
+
+> "Most customers see ROI within the first billing cycle."
+
+**Ask:** "Would you like to pilot this with your most complex customer segment?"
+
+---
+
+## Objection Handling
+
+| Objection | Response |
+|-----------|----------|
+| "Our pricing is too complex" | "That's exactly where Ema shines. The more complex your pricing, the more value from automation. Can I see your most complex contract?" |
+| "We have existing billing software" | "Ema doesn't replace your billing system - it feeds it. Think of it as intelligent pre-processing that validates and enriches before data hits your ERP." |
+| "We need human review" | "Absolutely. Add approval gates for invoices over any threshold. Ema does the work, humans approve the result." |
+| "Data security concerns" | "Ema connects via your existing APIs with your credentials. No data leaves your environment unless you want it to." |
+| "What about edge cases?" | "Ema flags anything it can't handle confidently. Exceptions route to humans. Start with 80% automation, expand as you build confidence." |
+| "Contract amendments?" | "Ema checks contract version dates and applies the correct terms for each period. Mid-cycle changes are prorated automatically." |
+| "Multi-currency?" | "Ema can handle currency conversion using rates you specify or live FX feeds." |
+
+---
+
+## Demo Variants
+
+| Audience | Focus On | Skip |
+|----------|----------|------|
+| **CFO** | Revenue protection, DSO, audit compliance | Technical integration |
+| **RevOps** | Validation pipeline, complex scenarios, accuracy | High-level ROI |
+| **IT** | Data sources, API integration, security | Business metrics |
+| **Deal Desk** | Contract accuracy, amendments, credits | Technical details |
+
+---
+
+## Leave-Behinds
+
+1. **Sample Invoice** - Generated by Ema from demo data
+2. **Validation Report** - What Ema checks before generating
+3. **Integration Architecture** - How Ema connects to systems
+4. **ROI Calculator** - Their numbers, their savings
+5. **Customer Case Study** - Similar company results
+
+---
+
+## Success Metrics to Track
+
+| Metric | Baseline | Target |
+|--------|----------|--------|
+| Invoice generation time | ___ hours | <10 min |
+| Pricing accuracy | ___% | >99.5% |
+| DSO (Days Sales Outstanding) | ___ days | -5 days |
+| Billing disputes | ___/month | -80% |
+| Audit prep time | ___ hours | -90% |
+| Revenue leakage | ___% | <0.5% |
+
+---
+
+## Comparison: AP Invoice Processing vs AP Invoice Generation
+
+| Aspect | Invoice Processing | Invoice Generation |
+|--------|-------------------|-------------------|
+| **Direction** | Inbound (receive invoices) | Outbound (create invoices) |
+| **Use Case** | AP - pay suppliers | AR - bill customers |
+| **Data Source** | PDF/email invoices | Internal systems (CRM, usage, contracts) |
+| **Validation** | 3-way match against PO | Customer, usage, contract validation |
+| **Output** | Entry in Coupa/ERP | Professional invoice document |
+| **Complexity** | Medium (5 nodes) | High (12 nodes) |
+| **Target Buyer** | AP Manager | RevOps / Billing Manager |
+
+---
+
+## Tags
+
+`demo-kit` `ar-automation` `invoice-generation` `revenue-ops` `usage-billing` `saas` `finance`

package/docs/demos/ap-invoice-processing.md

@@ -0,0 +1,271 @@
+# AP Invoice Processing - Demo Script
+
+**Persona ID**: `fa91cb51-58fe-4255-b2d2-0b3e3a72cf7e`  
+**Type**: Chat  
+**Generated**: 2026-01-24
+
+---
+
+## Target Persona
+
+| Role | Profile |
+|------|---------|
+| **Primary** | AP Manager / Controller |
+| **Secondary** | CFO, Procurement Director, IT/Automation Lead |
+| **Company Size** | Mid-market to Enterprise ($50M-$1B revenue) |
+| **Industry** | Manufacturing, Retail, Distribution, Healthcare |
+| **Tech Stack** | Coupa (or similar P2P), ERP (Oracle, SAP, NetSuite) |
+
+**Buyer Characteristics:**
+- Managing 5,000-50,000+ invoices/month
+- Team of 3-15 AP specialists
+- Current process involves significant manual data entry
+- Dealing with supplier inquiries about payment status
+- Under pressure to reduce costs and improve working capital
+
+---
+
+## Pain Points Addressed
+
+| Pain Point | Impact | How Ema Solves It |
+|------------|--------|-------------------|
+| **Manual data entry** | 15-20 min per invoice, high error rate | Automated extraction in seconds |
+| **PO matching failures** | 30-40% first-pass match rate | Intelligent matching with validation |
+| **Supplier complaints** | 10+ calls/day asking "where's my payment?" | Automatic confirmation emails |
+| **Audit trail gaps** | Compliance risk, failed audits | Full logging of every step |
+| **Staff turnover costs** | $50K+ to train new AP clerk | AI handles repetitive work |
+| **Late payment penalties** | 2-5% of invoice value lost | Faster processing = on-time payment |
+| **Fraud risk** | Invoice fraud costs $3.7B/year in US | 3-way match validation prevents errors |
+
+---
+
+## Workflow Overview
+
+```
+Invoice Upload → Extract Data → Create in Coupa → Get Session Link → Send Email
+```
+
+### Nodes (5 total)
+
+| Node | Type | Purpose |
+|------|------|---------|
+| **Extract Data from Invoice** | `entity_extraction` | Extracts invoice details (supplier, PO#, amounts) |
+| **Fixed Response** | `fixed_response` | Provides context to next step |
+| **Create Invoice in Coupa** | `external_action_caller` | Automates Coupa invoice creation with 16-step process |
+| **Active Session Link** | `call_llm` | Extracts the browser session link |
+| **Send Email** | `external_action_caller` | Sends confirmation email to supplier |
+
+---
+
+## Key Talking Points
+
+### 1. **End-to-End Automation**
+> "This isn't just OCR. Ema reads the invoice, validates it against your PO, creates the entry in Coupa, and notifies your supplier - all without human intervention."
+
+### 2. **3-Way Match Validation**
+> "Before creating anything, Ema validates:
+> - Does the PO exist?
+> - Does the supplier name match?
+> - Do the line items match?
+> - Do the prices match?
+> 
+> Any discrepancy is flagged immediately - no bad data enters your system."
+
+### 3. **Works With Your Existing Systems**
+> "This connects to Coupa, but we support SAP Ariba, Oracle, NetSuite, and 200+ other applications. No rip-and-replace required."
+
+### 4. **Supplier Experience**
+> "Your suppliers get instant confirmation when their invoice is processed. No more 'did you receive my invoice?' calls."
+
+### 5. **Human-in-the-Loop When Needed**
+> "You can add approval gates at any step. For invoices over $10K, route to manager. For new suppliers, require verification. Full control."
+
+### 6. **ROI in Weeks, Not Years**
+> "Average AP processing cost: $8-15 per invoice. With Ema: under $1. At 10,000 invoices/month, that's $70K-140K annual savings."
+
+---
+
+## Demo Script
+
+### **Setup (Before Demo)**
+- [ ] Have sample invoice PDF ready (use sanitized demo data)
+- [ ] Coupa demo environment open in browser
+- [ ] Ema workspace with this persona loaded
+- [ ] Slack/Teams open for notification demo (optional)
+
+---
+
+### **Act 1: The Problem (2 min)**
+
+**[Show current state]**
+
+> "Let me show you what AP processing looks like today at most companies."
+
+**Talking points:**
+- "An invoice arrives via email, fax, or portal"
+- "Someone manually opens it, reads it, types data into the system"
+- "They hunt for the PO, compare line by line"
+- "If something doesn't match, they email the supplier"
+- "Days later, maybe it gets resolved"
+- "Meanwhile, the supplier calls: 'Where's my payment?'"
+
+**Ask:** "Does this sound familiar? How many invoices does your team process per month?"
+
+---
+
+### **Act 2: The Solution (5 min)**
+
+**[Show Ema interface]**
+
+> "Now let me show you how Ema handles this same invoice."
+
+**Step 1: Upload Invoice**
+> "I'll drop this invoice into Ema. This could also come from email, a portal, or direct API integration."
+
+*[Upload sample invoice PDF]*
+
+**Step 2: Watch Extraction**
+> "In seconds, Ema extracts:
+> - Supplier Name
+> - Invoice Number  
+> - PO Number
+> - Line items with descriptions
+> - Quantities and prices"
+
+*[Show extracted data]*
+
+> "Notice it handled this [multi-page / handwritten / poor quality] invoice. Our extraction works with 95%+ accuracy on real-world documents."
+
+**Step 3: Watch Validation**
+> "Now Ema logs into Coupa - using secure credentials, not stored in the workflow - and validates this against your data."
+
+*[Show Coupa automation running]*
+
+> "It's checking:
+> - ✅ PO exists
+> - ✅ Supplier name matches
+> - ✅ Line items match
+> - ✅ Prices match
+>
+> If ANY of these fail, it stops and flags for human review. No garbage in, no garbage out."
+
+**Step 4: Invoice Creation**
+> "With everything validated, Ema creates the invoice in Coupa automatically."
+
+*[Show invoice created in Coupa]*
+
+> "Chart of accounts is pulled from the PO. All line items mapped. Ready for approval."
+
+**Step 5: Supplier Notification**
+> "Finally, the supplier gets an email confirming receipt and processing."
+
+*[Show email sent]*
+
+> "No more 'where's my invoice?' calls. Your suppliers know instantly."
+
+---
+
+### **Act 3: The Differentiators (3 min)**
+
+**Human-in-the-Loop**
+> "You might be thinking: 'I don't want AI making $50K decisions without approval.' 
+>
+> Great news - you control that. Let me show you how easy it is to add an approval gate."
+
+*[Show how to add HITL in workflow builder - or describe it]*
+
+> "For invoices over your threshold, or from new suppliers, route to a human. One click to approve or reject."
+
+**Audit Trail**
+> "Every step is logged. Who approved what, when, why. Perfect for auditors."
+
+**Exception Handling**
+> "When Ema finds a mismatch, it doesn't just stop. It can:
+> - Route to the right person
+> - Request supplier clarification
+> - Apply your business rules automatically"
+
+---
+
+### **Act 4: ROI Discussion (2 min)**
+
+**Build the business case:**
+
+| Metric | Before | After | Savings |
+|--------|--------|-------|---------|
+| Time per invoice | 15 min | 2 min (exceptions only) | 87% reduction |
+| Cost per invoice | $12 | $1.50 | $10.50 each |
+| First-pass match rate | 35% | 85% | 2.4x improvement |
+| Supplier inquiries | 50/week | 10/week | 80% reduction |
+
+> "At 10,000 invoices/month, you're looking at $105,000 monthly savings - over $1.2M per year."
+
+**Ask:** "What would your team do with 10,000 hours per month freed up?"
+
+---
+
+### **Act 5: Next Steps (1 min)**
+
+> "Here's how we typically get started:"
+
+1. **Pilot (2-4 weeks)** - Run Ema on one invoice type or vendor
+2. **Validate** - Measure accuracy, time savings, user feedback
+3. **Expand** - Roll out to full AP workflow
+4. **Optimize** - Add more automation, approvals, integrations
+
+> "Most customers see ROI within the pilot period."
+
+**Ask:** "Would you like to run a pilot with [100/500/1000] of your invoices?"
+
+---
+
+## Objection Handling
+
+| Objection | Response |
+|-----------|----------|
+| "We already have OCR" | "OCR extracts text. Ema understands context, validates against your systems, and takes action. It's the difference between reading and doing." |
+| "Our invoices are too complex" | "We handle multi-page, multi-currency, handwritten invoices. Can I see a sample of your trickiest invoice?" |
+| "Security concerns" | "Ema runs in your environment or our SOC 2 certified cloud. Credentials are stored in your vault, not in workflows. Full audit logging." |
+| "We need IT approval" | "Ema is no-code. AP can configure it directly. IT just needs to approve the Coupa API connection - same as any integration." |
+| "What about exceptions?" | "Exceptions route to humans. You set the rules: dollar threshold, new vendors, mismatches. AI handles the 80%, humans handle the 20%." |
+| "Implementation timeline?" | "Most customers are live in 2-4 weeks. No ERP changes required. We connect via API." |
+| "What if the AI makes mistakes?" | "Every action is logged and reversible. You can add approval gates at any step. Start conservative, automate more as you build trust." |
+
+---
+
+## Demo Variants
+
+| Audience | Focus On | Skip |
+|----------|----------|------|
+| **CFO** | ROI numbers, working capital, audit/compliance | Technical details |
+| **AP Manager** | Day-to-day workflow, exception handling, team enablement | Integration details |
+| **IT/Security** | Architecture, security, API, audit trail | ROI details |
+| **Procurement** | Supplier experience, PO validation, spend visibility | AP workflow |
+
+---
+
+## Leave-Behinds
+
+1. **ROI Calculator** - Excel with their numbers
+2. **Architecture Diagram** - How Ema connects to their systems
+3. **Sample Validation Report** - What Ema checks on each invoice
+4. **Customer Case Study** - Similar company, similar results
+
+---
+
+## Success Metrics to Track
+
+| Metric | Baseline | Target |
+|--------|----------|--------|
+| Invoices processed/day | ___ | +300% |
+| Average processing time | ___ min | <5 min |
+| First-pass match rate | ___% | >85% |
+| Supplier inquiry volume | ___ | -80% |
+| Late payment rate | ___% | <2% |
+| Cost per invoice | $___ | <$2 |
+
+---
+
+## Tags
+
+`demo-kit` `ap-automation` `coupa` `invoice-processing` `finance`

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@ema.co/mcp-toolkit",
-  "version": "2026.1.24",
+  "version": "2026.1.25",
   "description": "Ema AI Employee toolkit - MCP server, CLI, and SDK for managing AI Employees across environments",
   "type": "module",
   "main": "dist/index.js",

package/resources/demo-kits/README.md

@@ -0,0 +1,175 @@
+# Demo Kits
+
+Pre-packaged demo resources for Ema AI Employee demonstrations. Each kit includes personas, demo scripts, sample data, and validation queries.
+
+## Available Demo Kits
+
+| Kit ID | Name | Domain | Personas | Tags |
+|--------|------|--------|----------|------|
+| `finance-ap` | Finance - Accounts Payable | Finance | 2 | `finance`, `invoice`, `automation` |
+| `finance-ar` | Finance - Accounts Receivable | Finance | 1 | `finance`, `billing`, `revenue` |
+| `sales-sdr` | Sales Development | Sales | 2 | `sales`, `outbound`, `prospecting` |
+| `support-tier1` | Customer Support T1 | Support | 2 | `support`, `voice`, `chat` |
+| `hr-assistant` | HR Policy Assistant | HR | 1 | `hr`, `policy`, `benefits` |
+
+## Kit Structure
+
+Each demo kit contains:
+
+```
+demo-kits/
+├── {kit-id}/
+│   ├── manifest.json      # Kit metadata, personas, tags
+│   ├── demo-script.md     # Talk track, objections, ROI
+│   ├── sample-data/       # Demo data files
+│   │   ├── input.json     # Sample inputs
+│   │   └── expected.json  # Expected outputs
+│   └── validation/
+│       └── queries.json   # Pre/post-demo validation queries
+```
+
+## Usage
+
+### List Available Kits
+
+```
+reference(demo_kits=true)
+```
+
+### Get Kit Details
+
+```
+reference(demo_kit="finance-ap")
+```
+
+### Generate Demo for Persona
+
+```
+persona(method="demo_kit", id="{persona_id}", kit="finance-ap")
+```
+
+### Validate Demo Readiness
+
+```
+persona(method="validate", id="{persona_id}", checks=["demo_ready"])
+```
+
+## Tagging System
+
+Demo kits and personas use a consistent tagging system:
+
+### Domain Tags
+- `finance` - Financial operations (AP, AR, Treasury)
+- `sales` - Sales and revenue operations
+- `support` - Customer support and service
+- `hr` - Human resources
+- `it` - IT operations and security
+- `legal` - Legal and compliance
+- `marketing` - Marketing operations
+
+### Capability Tags
+- `voice` - Voice/phone interactions
+- `chat` - Chat/messaging interactions
+- `dashboard` - Dashboard/data processing
+- `document` - Document generation
+- `automation` - Process automation
+- `analysis` - Data analysis
+
+### Use Case Tags
+- `invoice` - Invoice processing
+- `billing` - Billing operations
+- `onboarding` - Employee/customer onboarding
+- `compliance` - Compliance and audit
+- `reporting` - Reporting and analytics
+
+## Creating a Demo Kit
+
+1. Create a folder in `demo-kits/`
+2. Add `manifest.json` with kit metadata
+3. Add `demo-script.md` with talk track
+4. Add sample data and validation queries
+5. Register personas in manifest
+
+### Manifest Schema
+
+```json
+{
+  "id": "kit-id",
+  "name": "Kit Display Name",
+  "version": "1.0.0",
+  "description": "What this kit demonstrates",
+  "domain": "finance|sales|support|hr|it|legal|marketing",
+  "tags": ["tag1", "tag2"],
+  "personas": [
+    {
+      "id": "uuid",
+      "name": "Persona Name",
+      "role": "primary|supporting",
+      "description": "What this persona does in the demo"
+    }
+  ],
+  "prerequisites": {
+    "integrations": ["coupa", "salesforce"],
+    "data": ["sample-invoices"],
+    "environment": "demo"
+  },
+  "demo_flow": [
+    {
+      "step": 1,
+      "title": "Setup",
+      "duration_minutes": 2,
+      "actions": ["Load persona", "Prepare data"]
+    }
+  ],
+  "target_audience": {
+    "primary": "AP Manager",
+    "secondary": ["CFO", "IT Director"],
+    "company_size": "mid-market",
+    "industries": ["manufacturing", "retail"]
+  },
+  "roi_metrics": {
+    "time_saved_per_unit": "15 minutes",
+    "volume_per_month": 10000,
+    "cost_per_unit_before": 12,
+    "cost_per_unit_after": 1.5
+  }
+}
+```
+
+## Bundling Multiple Kits
+
+Create meta-kits that combine related demos:
+
+```json
+{
+  "id": "finance-complete",
+  "name": "Complete Finance Automation",
+  "type": "bundle",
+  "includes": ["finance-ap", "finance-ar", "finance-reporting"],
+  "tags": ["finance", "bundle", "enterprise"]
+}
+```
+
+## Integration with Persona Tool
+
+The `persona` tool supports kit-related operations:
+
+```
+# Tag a persona
+persona(method="update", id="...", tags=["finance", "invoice"])
+
+# Find personas by tag
+persona(method="list", tags=["finance"])
+
+# Get demo kit for persona
+persona(method="demo_kit", id="...")
+```
+
+## Quality Standards
+
+Each demo kit must:
+- [ ] Have validated sample data
+- [ ] Include error handling scenarios
+- [ ] Work in demo environment
+- [ ] Include realistic ROI numbers
+- [ ] Have tested validation queries

package/resources/demo-kits/finance-ap/manifest.json

@@ -0,0 +1,150 @@
+{
+  "id": "finance-ap",
+  "name": "Finance - Accounts Payable Automation",
+  "version": "1.0.0",
+  "description": "End-to-end AP invoice processing and generation automation. Demonstrates inbound invoice processing (AP) and outbound invoice generation (AR).",
+  "domain": "finance",
+  "tags": [
+    "finance",
+    "invoice",
+    "automation",
+    "ap-automation",
+    "ar-automation",
+    "coupa",
+    "usage-billing"
+  ],
+  "personas": [
+    {
+      "id": "fa91cb51-58fe-4255-b2d2-0b3e3a72cf7e",
+      "name": "AP Invoice Processing",
+      "role": "primary",
+      "description": "Processes inbound invoices: extract data, validate against PO, create in Coupa, notify supplier",
+      "workflow_nodes": 5,
+      "integrations": ["coupa"]
+    },
+    {
+      "id": "d73c8dca-d340-4541-a7ff-ae69f2810906",
+      "name": "AP Invoice Generation",
+      "role": "primary",
+      "description": "Generates outbound invoices: validate customer/usage/contract, generate professional document",
+      "workflow_nodes": 12,
+      "integrations": ["salesforce", "usage-api", "contract-db"]
+    }
+  ],
+  "prerequisites": {
+    "integrations": ["coupa", "salesforce"],
+    "data": ["sample-invoices", "sample-contracts", "usage-data"],
+    "environment": "demo"
+  },
+  "demo_flow": [
+    {
+      "step": 1,
+      "title": "The Problem",
+      "duration_minutes": 2,
+      "talking_points": [
+        "Manual data entry takes 15-20 min per invoice",
+        "30-40% first-pass match rate",
+        "Supplier complaints about payment status"
+      ]
+    },
+    {
+      "step": 2,
+      "title": "Inbound Processing Demo",
+      "duration_minutes": 5,
+      "persona": "fa91cb51-58fe-4255-b2d2-0b3e3a72cf7e",
+      "actions": [
+        "Upload sample invoice",
+        "Show extraction results",
+        "Show PO validation",
+        "Show Coupa entry creation",
+        "Show supplier notification"
+      ]
+    },
+    {
+      "step": 3,
+      "title": "Outbound Generation Demo",
+      "duration_minutes": 5,
+      "persona": "d73c8dca-d340-4541-a7ff-ae69f2810906",
+      "actions": [
+        "Show data source connections",
+        "Show customer validation",
+        "Show usage aggregation",
+        "Show contract validation",
+        "Show generated invoice document"
+      ]
+    },
+    {
+      "step": 4,
+      "title": "ROI Discussion",
+      "duration_minutes": 2,
+      "talking_points": [
+        "$10.50 savings per invoice",
+        "95% time reduction for generation",
+        "Revenue leakage prevention"
+      ]
+    },
+    {
+      "step": 5,
+      "title": "Next Steps",
+      "duration_minutes": 1,
+      "actions": [
+        "Propose pilot program",
+        "Share ROI calculator"
+      ]
+    }
+  ],
+  "target_audience": {
+    "primary": "AP Manager / Controller",
+    "secondary": ["CFO", "RevOps Manager", "IT Director"],
+    "company_size": "mid-market to enterprise",
+    "industries": ["manufacturing", "retail", "saas", "distribution"]
+  },
+  "roi_metrics": {
+    "ap_processing": {
+      "time_saved_per_invoice": "13 minutes",
+      "volume_per_month": 10000,
+      "cost_per_invoice_before": 12,
+      "cost_per_invoice_after": 1.5,
+      "monthly_savings": 105000
+    },
+    "invoice_generation": {
+      "time_saved_per_invoice": "2.5 hours",
+      "volume_per_month": 500,
+      "cost_per_invoice_before": 150,
+      "cost_per_invoice_after": 4,
+      "monthly_savings": 73000
+    },
+    "revenue_protection": {
+      "error_rate_before": "5%",
+      "error_rate_after": "0.5%",
+      "monthly_billings": 10000000,
+      "protected_revenue": 450000
+    }
+  },
+  "objections": [
+    {
+      "objection": "We already have OCR",
+      "response": "OCR extracts text. Ema understands context, validates against your systems, and takes action."
+    },
+    {
+      "objection": "Our pricing is too complex",
+      "response": "The more complex your pricing, the more value from automation. Can I see your most complex contract?"
+    },
+    {
+      "objection": "Security concerns",
+      "response": "Ema connects via your existing APIs. Credentials in your vault, full audit logging."
+    }
+  ],
+  "leave_behinds": [
+    "ROI Calculator (Excel)",
+    "Architecture Diagram",
+    "Sample Validation Report",
+    "Customer Case Study"
+  ],
+  "related_kits": [
+    "finance-treasury",
+    "finance-reporting"
+  ],
+  "created": "2026-01-24",
+  "updated": "2026-01-24"
+}

package/resources/demo-kits/tags.json

@@ -0,0 +1,91 @@
+{
+  "version": "1.0.0",
+  "description": "Tagging taxonomy for demo kits and personas",
+  "categories": {
+    "domain": {
+      "description": "Business domain or department",
+      "tags": [
+        { "id": "finance", "name": "Finance", "description": "Financial operations, accounting, treasury" },
+        { "id": "sales", "name": "Sales", "description": "Sales operations, SDR, AE workflows" },
+        { "id": "support", "name": "Support", "description": "Customer support and service" },
+        { "id": "hr", "name": "HR", "description": "Human resources, recruiting, employee services" },
+        { "id": "it", "name": "IT", "description": "IT operations, security, infrastructure" },
+        { "id": "legal", "name": "Legal", "description": "Legal operations, contracts, compliance" },
+        { "id": "marketing", "name": "Marketing", "description": "Marketing operations, campaigns, analytics" },
+        { "id": "operations", "name": "Operations", "description": "General business operations" },
+        { "id": "procurement", "name": "Procurement", "description": "Procurement, vendor management" }
+      ]
+    },
+    "capability": {
+      "description": "Technical capability or interaction type",
+      "tags": [
+        { "id": "voice", "name": "Voice", "description": "Voice/phone interactions" },
+        { "id": "chat", "name": "Chat", "description": "Chat/messaging interactions" },
+        { "id": "dashboard", "name": "Dashboard", "description": "Dashboard/data processing" },
+        { "id": "document", "name": "Document", "description": "Document generation" },
+        { "id": "automation", "name": "Automation", "description": "Process automation" },
+        { "id": "analysis", "name": "Analysis", "description": "Data analysis and insights" },
+        { "id": "extraction", "name": "Extraction", "description": "Data/entity extraction" },
+        { "id": "validation", "name": "Validation", "description": "Data validation and verification" }
+      ]
+    },
+    "use_case": {
+      "description": "Specific use case or process",
+      "tags": [
+        { "id": "invoice", "name": "Invoice", "description": "Invoice processing or generation" },
+        { "id": "billing", "name": "Billing", "description": "Billing operations" },
+        { "id": "onboarding", "name": "Onboarding", "description": "Employee or customer onboarding" },
+        { "id": "compliance", "name": "Compliance", "description": "Compliance and audit" },
+        { "id": "reporting", "name": "Reporting", "description": "Reporting and analytics" },
+        { "id": "routing", "name": "Routing", "description": "Request/ticket routing" },
+        { "id": "scheduling", "name": "Scheduling", "description": "Meeting/appointment scheduling" },
+        { "id": "order", "name": "Order", "description": "Order processing" },
+        { "id": "claims", "name": "Claims", "description": "Claims processing" }
+      ]
+    },
+    "integration": {
+      "description": "External system integrations",
+      "tags": [
+        { "id": "coupa", "name": "Coupa", "description": "Coupa procurement platform" },
+        { "id": "salesforce", "name": "Salesforce", "description": "Salesforce CRM" },
+        { "id": "servicenow", "name": "ServiceNow", "description": "ServiceNow ITSM" },
+        { "id": "workday", "name": "Workday", "description": "Workday HCM" },
+        { "id": "sap", "name": "SAP", "description": "SAP ERP" },
+        { "id": "oracle", "name": "Oracle", "description": "Oracle applications" },
+        { "id": "netsuite", "name": "NetSuite", "description": "Oracle NetSuite" },
+        { "id": "hubspot", "name": "HubSpot", "description": "HubSpot CRM/marketing" },
+        { "id": "zendesk", "name": "Zendesk", "description": "Zendesk support" },
+        { "id": "jira", "name": "Jira", "description": "Atlassian Jira" }
+      ]
+    },
+    "complexity": {
+      "description": "Demo complexity level",
+      "tags": [
+        { "id": "simple", "name": "Simple", "description": "1-5 workflow nodes, single integration" },
+        { "id": "moderate", "name": "Moderate", "description": "5-10 workflow nodes, 2-3 integrations" },
+        { "id": "complex", "name": "Complex", "description": "10+ workflow nodes, multiple integrations" }
+      ]
+    },
+    "bundle": {
+      "description": "Kit organization",
+      "tags": [
+        { "id": "demo-kit", "name": "Demo Kit", "description": "Complete demo package with scripts" },
+        { "id": "bundle", "name": "Bundle", "description": "Collection of related kits" },
+        { "id": "template", "name": "Template", "description": "Reusable template" },
+        { "id": "example", "name": "Example", "description": "Example/reference implementation" }
+      ]
+    }
+  },
+  "tag_rules": {
+    "required_for_kit": ["domain"],
+    "recommended_for_kit": ["capability", "use_case"],
+    "max_tags_per_category": 3
+  },
+  "search_aliases": {
+    "ap": ["finance", "invoice", "accounts-payable"],
+    "ar": ["finance", "billing", "accounts-receivable"],
+    "sdr": ["sales", "outbound", "prospecting"],
+    "tier1": ["support", "customer-service"],
+    "faq": ["support", "knowledge", "self-service"]
+  }
+}