MULTI-TENANT ARCHITECTURE — 3-LAYER MODEL
===============================================================

  LAYER 1: ISOLATION (Data Separation)
  ├── Each client's data NEVER touches another client's
  ├── A bug in Client A's workflow does NOT affect Client B
  ├── Separate Google Sheets per client (not shared tabs)
  ├── Separate credential sets per client
  └── Client cannot see other clients' execution history

  LAYER 2: ACCESS CONTROL (Who Sees What)
  ├── Clients can VIEW their workflow executions
  │   (for transparency — "show me it's working")
  ├── Clients CANNOT modify your core workflow logic
  ├── Clients CANNOT see other clients' data or workflows
  ├── You (admin) have full access to everything
  └── Optional: read-only dashboard per client

  LAYER 3: BILLING & REPORTING (Track and Charge)
  ├── Execution counts per client per month
  ├── Success/failure rates per client
  ├── Monthly report generation (automated)
  ├── Invoice generation based on execution volume
  └── Value demonstration = retention

===============================================================

n8n FOLDER STRUCTURE FOR 4-CLIENT AGENCY
===============================================================

  /clients/
  ├── /FST_fashionstore/
  │   ├── FST_order-processor_v2
  │   ├── FST_customer-notifier_v1
  │   ├── FST_inventory-updater_v1
  │   └── FST_daily-summary_v1
  │
  ├── /KRC_karachi-restaurant/
  │   ├── KRC_reservation-handler_v1
  │   ├── KRC_menu-updater_v1
  │   ├── KRC_review-collector_v1
  │   └── KRC_whatsapp-broadcast_v1
  │
  ├── /ALI_ali-agency/
  │   ├── ALI_lead-gen-pipeline_v1
  │   ├── ALI_content-poster_v1
  │   └── ALI_competitor-monitor_v1
  │
  └── /DMK_daraz-malik/
      ├── DMK_order-processor-daraz_v1
      └── DMK_cod-tracker_v1

  /shared/ (Your infrastructure — never client-facing)
  ├── _error_handler_v2
  ├── _daily_report_v1
  ├── _health_check_v1
  └── _credential_monitor_v1

===============================================================

  NAMING CONVENTION:
  [ClientCode]_[workflow-name]_v[version]

  ClientCode = 3-letter uppercase abbreviation
  workflow-name = kebab-case description
  version = increment on every major change

  Why this matters:
  - At 3 AM when a WhatsApp alert says "FST_order-processor_v2 failed"
    you instantly know: Fashion Store client, order processing, version 2
  - Without naming: "Workflow 47 failed" tells you nothing

===============================================================

CREDENTIAL ISOLATION — THE GOLDEN RULE
===============================================================

  NEVER mix credentials between clients.

  PER CLIENT, CREATE SEPARATE:
  ├── Google Sheets credential (their Google account)
  ├── Gmail credential (their business email OR yours per client)
  ├── WhatsApp/WATI credential (their WATI account)
  ├── Shopify/Daraz credential (their store)
  └── Any API keys (Hunter.io, etc.)

  NAMING IN n8n CREDENTIALS:
  ├── "FST — Google Sheets" (Fashion Store)
  ├── "KRC — WATI WhatsApp" (Karachi Restaurant)
  ├── "ALI — Hunter.io" (Ali Agency)
  └── "SHARED — UptimeRobot" (Your monitoring)

  WHEN A CLIENT CANCELS:
  1. Deactivate their workflows (don't delete yet)
  2. Revoke their credential access in n8n
  3. After 30 days, archive workflows as JSON exports
  4. Delete from n8n to free resources

  WHEN YOU USE YOUR OWN API KEYS FOR CLIENTS:
  ├── Track usage per client meticulously
  ├── Bill API costs as pass-through + 20% markup
  ├── Example: Hunter.io 500 lookups/month
  │   Client A uses 200, Client B uses 150, Client C uses 100
  │   You have 50 buffer for testing
  └── If a client exceeds allocation, upgrade or bill overage

===============================================================

TAG-BASED BILLING SYSTEM
===============================================================

  WORKFLOW TAGS:
  ├── client:fashionstore
  ├── client:karachi-restaurant
  ├── client:ali-agency
  └── client:daraz-malik

  MONTHLY BILLING WORKFLOW:
  1. Schedule Trigger: 1st of every month at 9 AM PKT
  2. HTTP Request: GET n8n API /api/v1/executions
     ?filter={"status":"success","startedAfter":"2026-03-01"}
  3. Code Node: Group executions by workflow tag
  4. Calculate: total executions per client
  5. Format invoice data
  6. Google Sheets: Append to "Monthly Billing" sheet
  7. Gmail: Send invoice summary to each client

  EXECUTION COST BREAKDOWN:
  ├── Your VPS cost: PKR 1,960/month (fixed)
  ├── Per-execution cost to you: ~PKR 0.05
  │   (PKR 1,960 / 40,000 avg executions)
  ├── Per-execution price to client: PKR 0.50-1.00
  │   (markup of 10-20x — industry standard)
  └── This is why execution-based billing is so profitable

===============================================================

NEW CLIENT ONBOARDING — STEP BY STEP
===============================================================

  DAY 1: SETUP (2-3 hours)
  ├── [ ] Create client folder in n8n
  ├── [ ] Assign 3-letter client code
  ├── [ ] Create all credential sets (Google, WATI, etc.)
  ├── [ ] Clone template workflows into client folder
  ├── [ ] Rename workflows with client code prefix
  └── [ ] Configure client-specific variables:
      ├── Google Sheet ID
      ├── WhatsApp Business number
      ├── Email addresses
      ├── Business name / city
      └── Pricing (PKR amounts, COD threshold, VIP threshold)

  DAY 2: TESTING (1-2 hours)
  ├── [ ] Run 3 test executions per workflow
  ├── [ ] Verify all data reaches correct Google Sheet
  ├── [ ] Verify WhatsApp notifications arrive
  ├── [ ] Verify email drafts/sends work
  ├── [ ] Test error handler catches failures
  └── [ ] Screenshot test results for client report

  DAY 3: GO-LIVE (30 minutes)
  ├── [ ] Activate all workflows
  ├── [ ] Send client "LIVE" confirmation via WhatsApp
  │   "Assalam o Alaikum! Aapki automation live hai.
  │    Pehla test order abhi process ho raha hai..."
  ├── [ ] Include first execution screenshot
  └── [ ] Schedule Week 1 check-in call

  WEEK 1: MONITORING (15 min/day)
  ├── [ ] Check execution logs daily
  ├── [ ] Fix any edge cases (missing fields, format issues)
  ├── [ ] Send client mid-week status update
  └── [ ] Prepare Week 1 mini-report

  MONTH 1: FIRST REPORT (1 hour)
  ├── [ ] Generate execution summary
  ├── [ ] Calculate value delivered (time saved, leads found, etc.)
  ├── [ ] Format as professional PDF or WhatsApp message
  ├── [ ] Include: "Next month, we recommend adding [upgrade]..."
  └── [ ] Send invoice for Month 2

===============================================================

BILLING MODEL COMPARISON
===============================================================

  MODEL 1: FLAT MONTHLY RETAINER (Recommended for starters)
  ├── PKR 15,000-75,000/month depending on tier
  ├── Includes: monitoring, maintenance, updates
  ├── Pro: Predictable revenue, simple invoicing
  ├── Con: High-volume clients may be undercharged
  └── Best for: First 5 clients (keep it simple)

  MODEL 2: EXECUTION-BASED BILLING
  ├── Base fee + per-execution charge above threshold
  ├── Example: PKR 15,000 base + PKR 0.50 per execution > 500
  ├── Pro: Revenue scales with client growth
  ├── Con: Harder to explain, client fears "surprise bills"
  └── Best for: Clients with variable volume (seasonal businesses)

  MODEL 3: VALUE-BASED BILLING
  ├── Price based on value delivered, not work done
  ├── Example: "This saves you PKR 60,000/month in labor.
  │   I charge PKR 25,000/month — you keep PKR 35,000."
  ├── Pro: Highest margins, strongest retention
  ├── Con: Requires proving value with data
  └── Best for: Clients who understand ROI

  RECOMMENDED FOR PAKISTAN (2026):
  ├── Start with Model 1 (flat retainer)
  ├── Move to Model 3 (value-based) after 3 months
  │   when you have execution data to prove savings
  └── Never use Model 2 unless client specifically asks

===============================================================