# 🚨 DECATUR SCHOOLS - 7-DAY EMERGENCY SPRINT PLAN
**Demo Date:** Week of April 7, 2026 (NEXT WEEK!)  
**Today:** Sunday, March 30, 2026  
**Days Until Demo:** 7 DAYS

---

## ⚡ REALITY CHECK

**Original Plan:** 4 weeks (28 days)  
**Actual Time:** 7 days  
**Strategy:** **DEMO-FIRST, NOT PRODUCTION-READY**

### **New Approach: Smoke & Mirrors + Solid Foundation**

We CANNOT build everything. We must:
1. ✅ Make it LOOK complete
2. ✅ Make KEY scenarios work flawlessly
3. ✅ UI transformation (highest impact)
4. ✅ Budget module (their #1 pain)
5. ❌ Skip anything not visible in demo

---

## 🎯 RUTHLESS PRIORITIZATION

### **MUST HAVE (Days 1-5)**
Focus on what they'll SEE in the demo:

1. **UI/Navigation** (Day 1-2) - 🔴 CRITICAL
2. **Budget Module** (Day 2-4) - 🔴 CRITICAL  
3. **Workflow Inbox** (Day 3-4) - 🔴 HIGH
4. **Demo Data** (Day 5-6) - 🔴 CRITICAL

### **SKIP (NOT ENOUGH TIME)**
- ❌ Full procurement workflow (use mockups)
- ❌ Payroll integration (UI mockup only)
- ❌ GL enhancement (use existing)
- ❌ 3-way matching (mention in demo)
- ❌ Advanced MIRA features (basic only)
- ❌ Mobile views
- ❌ Demo control panel

---

## 📅 7-DAY SPRINT BREAKDOWN

### **DAY 1 (Monday, March 31) - UI TRANSFORMATION** 
**Goal:** Hide non-ERP, create school navigation  
**Team:** Frontend + Ekam

#### Morning (4 hours):
- [ ] Create backup of current menu
- [ ] Hide these modules via CSS/blade conditions:
  - Donor CRM
  - Events & Fundraising  
  - Store (keep link in backend)
  - Marketing
  - Membership
  - Forums
  
#### Afternoon (4 hours):
- [ ] Create new navigation structure:
  ```
  Dashboard
  Finance
    - Invoices (existing)
    - Payments (existing)
    - Expenses (existing)
    - Budget (new - placeholder)
    - Bank Accounts (existing)
  Procurement (rename from Products)
    - Products (existing)
    - Orders (existing)
    - Vendors (existing)
  HR (rename from HRIQ)
    - Employees (existing)
    - Leaves (existing)
    - Attendance (existing)
  Grants (existing)
  Reports (existing)
  Workflow Inbox (new - placeholder)
  ```

#### End of Day:
- [ ] Clean school-focused navigation visible
- [ ] School theme colors applied
- [ ] Non-ERP items hidden

**Deliverable:** Missio looks like school ERP, not generic SaaS  
**Owner:** Ekam + Frontend Dev  
**Success Metric:** Show Ria at EOD - she says "This looks professional"

---

### **DAY 2 (Tuesday, April 1) - BUDGET MODULE FOUNDATION**
**Goal:** Budget allocation & display working  
**Team:** Ekam + Backend Dev

#### Morning (4 hours):
- [ ] Create database migrations:
  - `budgets` table (basic)
  - `budget_allocations` table
  - `budget_transfers` table (simplified)
  
- [ ] Create models:
  - `Budget.php`
  - `BudgetAllocation.php`
  - `BudgetTransfer.php`

- [ ] Seed demo data:
  - FY 2025-26 budget
  - 5-6 departments
  - Basic fund structure
  - Allocated amounts
  - Some spent amounts

#### Afternoon (4 hours):
- [ ] Create Budget controller with:
  - `index()` - Overview page
  - `allocations()` - Department view
  - `available()` - Calculate available balance
  
- [ ] Create Budget views:
  - Budget overview dashboard
  - Allocation table (fund/dept/allocated/spent/available)
  - Simple visual charts

#### End of Day:
- [ ] Budget page showing allocations
- [ ] Available balance calculations working
- [ ] Visual pie charts by department

**Deliverable:** Can show "Department X has $Y available"  
**Owner:** Ekam (lead) + Backend Dev  
**Success Metric:** Budget overview page loads with realistic data

---

### **DAY 3 (Wednesday, April 2) - BUDGET CONTROLS + WORKFLOW**
**Goal:** Budget checking & transfer workflow  
**Team:** Ekam + Backend Dev

#### Morning (4 hours):
- [ ] Budget checking function:
  ```php
  function checkBudgetAvailable($allocationId, $amount) {
      // Return true/false + available balance
  }
  ```
  
- [ ] Add to expense/invoice creation:
  - Select budget allocation dropdown
  - Check budget on save
  - Show warning if exceeded
  - Block if no budget (can disable for demo)

- [ ] Budget transfer request:
  - Simple form (from/to/amount/reason)
  - Save to `budget_transfers` table
  - Status = 'pending'

#### Afternoon (4 hours):
- [ ] Workflow inbox page:
  - List pending approvals by type
  - Budget transfers
  - Expenses (existing)
  - Invoices (existing)
  
- [ ] Approval actions:
  - Approve button
  - Reject button  
  - Comment field
  - Update budget allocations on approve

#### End of Day:
- [ ] Budget checking works on expense entry
- [ ] Transfer request can be created
- [ ] Workflow inbox shows pending items
- [ ] Can approve/reject transfers

**Deliverable:** Budget Scenario 2 functional  
**Owner:** Ekam + Backend Dev  
**Success Metric:** Complete budget transfer demo flow

---

### **DAY 4 (Thursday, April 3) - PROCUREMENT MOCKUP + POLISH**
**Goal:** Procurement UI + Budget polish  
**Team:** Full team

#### Morning (4 hours):
- [ ] Requisition mockup:
  - Create simple form (looks like order form)
  - Select items from products
  - Show total
  - "Check Budget" button
  - Shows allocation and available
  - Submit for approval
  
- [ ] Convert existing Orders to look like POs:
  - Rename "Orders" to "Purchase Orders"
  - Add "PO Number" display
  - Add "Requisition #" field (fake for demo)
  - Add status badges

#### Afternoon (4 hours):
- [ ] Polish budget module:
  - Better charts
  - Drill-down (click dept → see line items)
  - Position control mockup (just table view)
  - Budget vs. actual chart
  
- [ ] Polish workflow inbox:
  - Better styling
  - Tabs for different types
  - Priority indicators
  - Due dates

#### End of Day:
- [ ] Procurement looks professional
- [ ] Budget module polished
- [ ] Workflow inbox looks complete

**Deliverable:** Professional UI for all demo areas  
**Owner:** Full team  
**Success Metric:** Looks production-ready

---

### **DAY 5 (Friday, April 4) - DEMO DATA + SCENARIOS**
**Goal:** Realistic data, test scenarios  
**Team:** Ekam + QA

#### Morning (4 hours):
- [ ] Create realistic demo data:
  - **Users:**
    - Finance Director (Jane Williams)
    - Department Chair - Science (Bob Martinez)
    - AP Clerk (Sarah Johnson)
    - Principal (Dr. Davis)
    
  - **Budget data:**
    - General Fund: $5.2M
    - Science Dept: $125K allocated
    - Supplies: $2,500 remaining
    - Professional Dev: $8,000 remaining
    - Salaries: $95K (for position control demo)
    
  - **Expenses/Invoices:**
    - Hotel invoice: $450
    - Dinner expense: $75 (over limit)
    - Lab equipment quote: $500
    
  - **Products:**
    - Science lab equipment
    - Microscopes
    - Lab supplies

#### Afternoon (4 hours):
- [ ] Test Scenario 1: AP + Travel
  - Create hotel invoice
  - Submit expense over limit
  - Workflow to manager
  - Manager rejects
  - Resubmit corrected
  - Approve & process
  
- [ ] Test Scenario 2: Budget + Procurement
  - Check supplies budget ($2,500)
  - Try to order $500 items (succeeds)
  - Try to order $3,000 items (blocked)
  - Create transfer request
  - Approve transfer
  - Budget updated
  - Create requisition
  - Convert to PO

#### End of Day:
- [ ] Both core scenarios work end-to-end
- [ ] Demo data is realistic
- [ ] No errors in workflows

**Deliverable:** Demo scenarios rehearsable  
**Owner:** Ekam + QA  
**Success Metric:** Run both scenarios without errors

---

### **DAY 6 (Saturday, April 5) - MIRA AI + FINAL POLISH**
**Goal:** AI features + bug fixes  
**Team:** AI dev + Ekam

#### Morning (4 hours):
- [ ] MIRA duplicate detection:
  - Simple check: same vendor + similar amount + recent date
  - Show alert on invoice entry
  - "Possible duplicate found" message
  - Show comparison panel
  
- [ ] MIRA policy assistant:
  - When expense rejected, show MIRA button
  - Click → MIRA explains policy
  - Hardcode for dinner expense scenario
  - "Policy limit is $50 for in-state travel (Section 3.2)"

- [ ] MIRA budget insights:
  - "Ask MIRA" button on budget page
  - Pre-scripted responses for common questions:
    - "Which budget lines are at risk?"
    - "Why did supplies increase this month?"
  - Use GPT API with budget data context

#### Afternoon (4 hours):
- [ ] Bug fixing:
  - Test all navigation
  - Fix broken links
  - Check calculations
  - Mobile responsive (basic)
  
- [ ] Final polish:
  - Consistent styling
  - Loading indicators
  - Success/error messages
  - Professional look

#### End of Day:
- [ ] MIRA features working for demo
- [ ] All major bugs fixed
- [ ] System stable

**Deliverable:** Demo-ready system with AI  
**Owner:** AI dev + Ekam  
**Success Metric:** MIRA impresses in demo

---

### **DAY 7 (Sunday, April 6) - REHEARSAL & PREP**
**Goal:** Team ready, backups prepared  
**Team:** All hands

#### Morning (4 hours):
- [ ] Full demo run-through #1:
  - Ria presents full demo
  - Ekam runs system
  - Note all issues
  - Note timing
  
- [ ] Fix critical issues:
  - Anything that broke
  - Timing adjustments
  - Script refinements

#### Afternoon (4 hours):
- [ ] Full demo run-through #2:
  - Clean execution
  - Perfect timing
  - Smooth transitions
  
- [ ] Backup preparation:
  - Database backup of demo data
  - Screenshots of key screens (backup)
  - Video recording of working demo (insurance)
  
- [ ] Q&A preparation:
  - List likely questions
  - Prepare answers
  - Assign who answers what

#### Evening:
- [ ] Team dinner/celebration
- [ ] Final review of demo script
- [ ] Get good rest!

**Deliverable:** Confident, prepared team  
**Owner:** Ria + All  
**Success Metric:** Flawless demo execution

---

## 🎯 SIMPLIFIED DEMO STRATEGY

### **What We'll Actually Demo:**

#### **Scenario 1: Budget Control (8 minutes)** ⭐ FOCUS HERE
The one scenario that MUST be perfect.

**Story:** Science department needs lab supplies but only has $2,500. They need $3,000 worth.

**Steps:**
1. Show budget dashboard
   - General fund overview
   - Department allocations
   - Science dept detail: $2,500 available in supplies
   
2. Try to create expense/order for $3,000
   - System calculates available balance
   - Shows warning: "Insufficient budget"
   - Can't proceed (or shows override option)
   
3. Create budget transfer request
   - From: Professional Development ($8,000 available)
   - To: Supplies
   - Amount: $1,000
   - Reason: "Science fair lab equipment needed"
   - Submits to workflow
   
4. Principal receives in workflow inbox
   - Reviews request
   - Sees both budget lines
   - Checks that PD has funds
   - Approves with comment
   
5. Budget automatically updates
   - Supplies now shows $3,500
   - PD now shows $7,000
   - Show audit trail of transfer
   
6. Create requisition/order for $3,000
   - Now succeeds because budget available
   - Order created
   - Budget shows encumbered

**Key Message:** "This is the budget control you told us you need. No more overspending."

---

#### **Scenario 2: Workflow & Approvals (6 minutes)**
Show the approval infrastructure.

**Story:** AP clerk processes invoices, approvals route automatically.

**Steps:**
1. Login as AP clerk
   - Upload hotel invoice
   - MIRA scans and extracts data (or manual entry)
   - Assign to budget line
   - Budget checked automatically ✓
   - Submit for approval
   
2. Switch to department manager workflow inbox
   - Shows pending invoice
   - Open invoice
   - See attachments
   - See budget status
   - Approve
   
3. Goes to finance for payment
   - Finance director sees in workflow
   - Reviews
   - Approves for payment
   
4. Shows in payment queue
   - Check will be printed (or show ACH)
   
5. Budget automatically updated
   - Show department budget decreased
   - Show GL posting (if time)

**Key Message:** "Complete approval automation with budget checking built in."

---

#### **Scenario 3: MIRA AI (5 minutes)** ⭐ DIFFERENTIATOR
Show the AI capability.

**Story:** Demonstrate AI features competitors don't have.

**Steps:**
1. Duplicate detection
   - Enter invoice
   - MIRA flags: "Possible duplicate"
   - Shows similar invoice
   - Explain how MIRA caught it
   
2. Policy assistant
   - Show rejected expense (dinner $75)
   - Click "Ask MIRA why"
   - MIRA explains policy and limit
   - Employee understands and corrects
   
3. Budget insights
   - On budget page, click "Ask MIRA"
   - Type: "Which departments are at risk of running out?"
   - MIRA analyzes and responds
   - Shows proactive monitoring

**Key Message:** "AI that helps prevent errors and provides insights."

---

#### **Scenario 4: Dashboard & Reporting (3 minutes)**
Quick overview of reporting.

**Steps:**
1. Executive dashboard
   - All funds overview
   - Budget vs. actual charts
   - Key metrics
   
2. Drill-down
   - Click department
   - See line items
   - Click line item
   - See transactions
   - Click transaction
   - See voucher detail
   
3. Grant compliance view
   - Show grant spending status
   - Compliance indicators

**Key Message:** "Real-time insights, drill down to the receipt."

---

## 🎬 DEMO SCRIPT (25 minutes total)

**0:00-2:00** - Introduction
- "Thank you for the opportunity"
- "We understand your pain points"
- "Single integrated platform"
- "Live demo, not slides"

**2:00-10:00** - Budget Control Scenario
- THE SHOWCASE
- Walk through budget transfer completely
- Show every approval step
- Highlight budget checking

**10:00-16:00** - Workflow & Approvals
- Show how all approvals work
- Audit trail
- Budget integration

**16:00-21:00** - MIRA AI Features
- Duplicate detection
- Policy assistant
- Budget insights
- "Competitors don't have this"

**21:00-24:00** - Reporting & Dashboards
- Quick tour
- Drill-down capability
- Real-time updates

**24:00-25:00** - Closing
- "Questions?"
- "We can configure to your exact needs"
- "Faster implementation than legacy systems"

---

## ⚠️ RISKS & MITIGATION (7-Day Version)

| Risk | Mitigation |
|---|---|
| **Budget module not done** | Day 1-4 focused entirely on this. Non-negotiable. |
| **Demo crashes** | Database backup, screenshot backup, video backup |
| **Feature not working** | Don't show it. Stick to script. |
| **Question about missing feature** | "That's on our roadmap, we'd configure that for you" |
| **Team exhausted** | Focus on critical path only. Cut ruthlessly. |
| **Not enough time to test** | Day 5-6 is ONLY testing and polish |

---

## 🚀 WHAT TO CUT (NO TIME)

These are OUT for this demo:

❌ **Full procurement workflow** - Use existing orders, rename to POs  
❌ **Payroll integration** - Just mention "integrates with your payroll provider"  
❌ **GL enhancement** - Use what exists  
❌ **3-way matching** - Mention it, don't show it  
❌ **Position control detail** - Mock table view only  
❌ **Advanced MIRA** - Basic features only  
❌ **Mobile demo** - Focus on desktop  
❌ **Report builder** - Use existing reports  
❌ **Multiple demo scenarios** - Focus on 2-3 only  

**If they ask:** "We can add that during implementation based on your workflows."

---

## 📋 DAILY CHECKLIST FORMAT

### **Each Day:**
- [ ] **9:00 AM** - Stand-up: Yesterday, Today, Blockers
- [ ] **12:00 PM** - Quick sync: On track?
- [ ] **5:00 PM** - Demo to Ria: Show progress
- [ ] **6:00 PM** - Tomorrow prep: Assign next day tasks

### **Each Evening:**
- [ ] Commit code
- [ ] Update progress doc
- [ ] Note tomorrow's priorities
- [ ] Get rest (CRITICAL)

---

## 💪 TEAM ASSIGNMENTS (7-DAY SPRINT)

| Person | Primary Focus | Backup | Days |
|---|---|---|---|
| **Ekam** | Budget module lead, Demo coord | UI, Testing | 7 |
| **Frontend Dev** | UI/Navigation, Workflow inbox | Budget UI | 7 |
| **Backend Dev 1** | Budget engine, Calculations | Workflow logic | 7 |
| **Backend Dev 2** | Database, APIs | Budget backend | 5 |
| **AI Dev** | MIRA features | - | 2 (Day 6-7) |
| **Ravi** | School theme, UI polish | - | 3 (Day 1,4,6) |
| **QA (Ashutosh)** | Demo data, Testing | - | 3 (Day 5-7) |

**Everyone must be available Day 7 for rehearsal!**

---

## 🎯 SUCCESS CRITERIA (REALISTIC)

### **Minimum Viable Demo:**
- ✅ Looks like school ERP (not generic SaaS)
- ✅ Budget scenario works perfectly
- ✅ Workflow inbox functional
- ✅ One MIRA feature working
- ✅ Team confident in presentation

### **Stretch Goals (If Time):**
- ⚪ Second scenario polished
- ⚪ Multiple MIRA features
- ⚪ Advanced reporting
- ⚪ Full procurement flow

**Focus on MINIMUM VIABLE. Perfection is the enemy of done.**

---

## 🚨 EMERGENCY PROTOCOLS

### **If Behind Schedule:**

**By Wednesday EOD:**
- Budget module 80% complete
- Navigation restructured
- Demo data exists

**NOT THERE?**

**Emergency Cut List:**
1. Cut MIRA to bare minimum
2. Cut second demo scenario
3. Simplify budget module (remove transfers, just show allocations)
4. Use existing features only
5. Slide deck backup (screen recording of working parts)

### **If Someone Gets Sick:**

**Ekam backup:** Ria can present using script  
**Frontend backup:** Use existing UI, minimal changes  
**Backend backup:** Simplify to data display only  

### **If Demo Environment Fails:**

**Plan B:** Screen recording of working demo  
**Plan C:** Screenshots with narration  
**Plan D:** Existing Missio features + verbal description of planned enhancements

**Database backup before demo: CRITICAL**

---

## 📞 COMMUNICATION PLAN

### **Daily Standups (9 AM):**
- 15 minutes max
- What I did, What I'm doing, Blockers
- Ekam runs

### **Evening Demo to Ria (5 PM):**
- Show progress
- Get feedback
- Adjust tomorrow's plan

### **Slack Channel: #decatur-sprint**
- Real-time updates
- Quick questions
- Screenshots of progress

### **Emergency Contact:**
- If blocker can't be resolved in 30 minutes
- Escalate to Ria immediately
- Pivot or cut feature

---

## 🎓 WHAT TO TELL COMPETITORS

**They will ask:** "Can you do [feature]?"

**Response framework:**
- "Yes, that's built into our platform. Let me show you [existing similar feature]"
- "Yes, we'd configure that specifically for Decatur during implementation"
- "That's a great point. Our API allows us to integrate with any system you use"

**Never say:** "We don't have that" or "We'd need to build that"

**Always say:** "Our platform is configurable" or "That's part of implementation"

---

## 💰 REALISTIC EXPECTATIONS

### **What This Demo Will Be:**
- ✅ Budget module working (their #1 concern)
- ✅ Professional school ERP appearance
- ✅ Core workflows functional
- ✅ AI differentiation visible
- ✅ Confident presentation

### **What This Demo Won't Be:**
- ❌ Production-ready
- ❌ Feature-complete
- ❌ Fully integrated
- ❌ Perfect

### **But That's OK Because:**
- ✅ This is a demo, not delivery
- ✅ They know implementation takes months
- ✅ They're evaluating direction, not completion
- ✅ Competitors also demo aspirational features

**Goal: Show we understand their needs and have a credible path to solve them.**

---

## ✅ END OF WEEK SUCCESS LOOKS LIKE:

**Sunday night (April 6), you should have:**

1. ✅ Clean school ERP interface
2. ✅ Budget module working (allocations, transfers, checking)
3. ✅ Workflow inbox with approvals
4. ✅ At least one MIRA feature
5. ✅ Realistic demo data
6. ✅ 2-3 scenarios rehearsed
7. ✅ Confident team
8. ✅ Backup plans ready
9. ✅ Good night's sleep before demo!

**That's enough to win.**

---

## 🚀 LET'S GO! KICK-OFF ACTIONS

### **RIGHT NOW (Sunday Night):**

1. **Ekam: Send to team**
   - This document
   - Schedule Monday 9 AM kickoff
   - Set up daily standups
   - Create #decatur-sprint Slack channel

2. **Everyone: Read tonight**
   - This plan
   - Understand your role
   - Clear your calendar
   - Prepare for intensity

3. **Ria: Confirm**
   - Demo date/time
   - Location (in-person/virtual)
   - Who will attend from their side
   - How long we have (45 min?)

### **Monday 9:00 AM Sharp:**

- Team kickoff meeting
- Review this plan
- Confirm assignments
- Start Day 1 tasks
- No time to waste!

---

## 💪 CLOSING THOUGHTS

**This is tight. Really tight.**

But here's the truth:
- ✅ You have 60-70% already built
- ✅ Budget module is ~4 days focused work
- ✅ UI transformation is ~2 days
- ✅ You have the team
- ✅ You have the capability

**What you need:**
- 🔥 Intense focus
- 🔥 Ruthless prioritization  
- 🔥 Team commitment
- 🔥 Smart shortcuts

**We're not building production software. We're building a compelling demo.**

**Remember:**
- Tyler/Skyward will demo aspirational features too
- This is about showing vision and capability
- Implementation takes 12+ months anyway
- They're evaluating potential, not completion

**You can do this!**

**Let's win this $1.6M deal!** 🚀🔥

---

**Document Owner:** Ekam (Simranjeet Singh)  
**Status:** EMERGENCY SPRINT MODE ACTIVATED  
**Timeline:** 7 DAYS TO DEMO  
**Start Date:** Monday, March 31, 2026  
**Demo Date:** Week of April 7, 2026  

**Last Updated:** March 30, 2026 - 11:45 PM  
**Next Update:** Daily standup summaries

---

## 📱 QUICK REFERENCE CARD (Print This!)

```
DAY 1 (Mon): UI Transformation → School ERP look
DAY 2 (Tue): Budget module foundation → Show allocations
DAY 3 (Wed): Budget controls → Transfers work
DAY 4 (Thu): Procurement mockup → Polish everything
DAY 5 (Fri): Demo data → Test scenarios
DAY 6 (Sat): MIRA AI → Bug fixes
DAY 7 (Sun): REHEARSE → Get ready!

FOCUS: Budget module + UI = 80% of impact
CUT: Anything not in demo script
BACKUP: Screenshots + screen recording
MINDSET: Demo credibility, not production perfection
```

**Let's GO! 🚀**