PARamedic Ops Sales Demo Guide

Purpose and demo story

Use this guide for a repeatable 30-minute demonstration in the development environment. The fictional service operates three ALS ambulances from one supply room and answers about 3,000 calls per year. Its six-month history contains 1,500 calls: 450 BLS, 825 ALS 1, and 225 ALS 2. This provides a realistic 70% ALS mix, including 15% ALS 2.

The sample agency has 16 inventory items, four vendors, six monthly purchasing cycles, tracked lots, readiness PAR levels, equipment checks, vehicle checklists, support records, and three narcotic kits. No record contains patient information.

Reset and verify the demonstration

1. Confirm the DEVELOPMENT ENVIRONMENT banner is visible.
2. Use Data Reset and select the complete development dataset when a clean demonstration is needed.
3. Use the Development Administrator for configuration, ordering, receiving, and reporting. Use the Demo Provider for operational workflows.
4. Confirm Development Supply Room and Development Ambulance 1, 2, and 3 appear.
5. Confirm Development Medical Supply, Metro EMS Catalog, Regional Pharmaceutical, and Emergency Care Wholesale appear.
6. Never substitute production data during a sales demonstration.

30-minute demonstration route

1. Establish the operational problem — 2 minutes

Explain that a provider records supply use once and that the same event drives restocking, readiness, ordering, and reporting. Introduce the three ambulances and supply room as the operating model.

2. Show the provider workflow — 5 minutes

1. Open Transactions and start Complete a Call for Development Ambulance 1.
2. Use seeded items such as Alcohol Prep Pads - 10 pack, 10 mL Syringe, IV Catheter 18 gauge, and Normal Saline 1000 mL.
3. Show the difference between simple and lot-tracked items. Saline and IV catheters carry seeded lots; alcohol prep pads do not require one.
4. Review before completing. Explain that posted movements become permanent history and corrections remain traceable.
5. Open the replacement workflow and connect the vehicle need to stock in Development Supply Room.

Expected result: one operational entry updates inventory history and readiness without a separate spreadsheet.

3. Demonstrate readiness — 4 minutes

1. Open Inventory Health for Development Ambulance 1.
2. Find Development shortage requiring review, tied to Abdominal Pad 5x9.
3. Show PAR placement in Airway Cabinet, Driver Side IV Drawer, Passenger Side Medication Drawer, and PPE and Trauma Cabinet.
4. Point out Epinephrine 1 mg/mL as the nearest seeded expiration. Its date moves forward when the dataset is reset.
5. Explain how authorized staff resolve the shortage while preserving the report and correction history.

4. Run a truck count — 4 minutes

1. Open Cycle Counts and create or open a full-location count for Development Ambulance 1.
2. Select a storage area and show its configured item order.
3. Enter a quantity before scanning a recognized non-lot item, then demonstrate a lot-tracked item.
4. Show how differences enter research or reconciliation.
5. Explain that loose readiness supplies can be verified during the count while bulk replacement stock remains in the supply room.

5. Show purchasing across four vendors — 6 minutes

1. Open Ordering and show six months of history. The seed creates four orders per month.
2. In the newest cycle, identify two completed orders, one submitted Regional Pharmaceutical order, and one draft Emergency Care Wholesale order. Numbers use DEV-PO-YYYYMM-1 through -4, so the month changes after reset.
3. Open Compare vendor prices and explain package conversions, receipt-backed pricing, preferred entries, and normalized unit cost.
4. Open Smart Recommendations to show how shortages, supply-room targets, usable stock, expiration loss, open orders, lead time, and package rounding form a plan.
5. Open the newest draft and use Alcohol Prep Pads - 10 pack, ChloraPrep Applicator, CAT Tourniquet, or i-gel Supraglottic Airway Size 4 as examples.

Expected result: purchasing recommendations use operational evidence while the administrator controls the final order.

6. Show six months of evidence — 5 minutes

1. Open Reporting Center and select the prior six months.
2. Show 1,500 calls and explain the 30% BLS, 55% ALS 1, and 15% ALS 2 mix.
3. Highlight higher seeded consumption of alcohol pads, syringes, IV catheters, saline, aspirin, albuterol, electrodes, and airway supplies on ALS calls.
4. Show purchasing and vendor reports across four vendors and 24 monthly orders.
5. Show expiration, shortage, correction, and readiness evidence.

7. Show narcotics separation — 2 minutes

1. Open Narcotics Transactions with an authorized demonstration role.
2. Show DEV-KIT-001 and DEV-KIT-002 green on Ambulances 1 and 2.
3. Show DEV-KIT-003 red on Ambulance 3 as the exception.
4. Explain that narcotics custody and seals remain separate from general inventory.

8. Close with support and rollout — 2 minutes

1. Open Help & Learning and show the User Manual, training, Release Guide, and support tickets.
2. Open Application Configuration and explain modules and release stages. Voice Count is the seeded alpha example for beta-enabled users.
3. Summarize the workflows that answer the prospect's stated problems.

Discovery prompts

• How many vehicles, stations, supply rooms, and annual calls does the agency manage?
• How are loose readiness items verified during truck checks?
• Who investigates shortages, expirations, and count differences?
• How many vendors and purchasing records are maintained?
• Which reports require manual reconstruction?
• Which users need provider, inventory, administrator, narcotics, or reporting access?

Demonstration safeguards

• Keep the development banner visible and use only DEV- records.
• Do not enter patient names, incident narratives, credentials, or real narcotics details.
• Identify alpha and beta capabilities by their displayed release stage.
• Reset the dataset after demonstrations that materially change the seeded story.