SaaS vs Custom

24/7 emergency trades: plumbing (burst pipes, blocked drains, hot water failure at 2am), electrical (power outage, electrical fire risk, safety shutdown at midnight), locksmith (lock-out, lost keys, security breach after-hours). Picture: Brisbane emergency services fleet "NightCall Trades" operates 8 technicians, 24/7 rotating on-call roster (each tech on-call 2 nights/week average). Current annual revenue: $400k (2 trucks × $200k = baseline day-work revenue, evening/weekend emergencies undermonetized). Breakdown: 60% standard business hours work ($240k, Mon–Fri 7am–5pm, residential + commercial scheduled jobs), 30% evening work ($120k, 5pm–10pm weekdays + Sat mornings, higher demand but chaotic dispatch), 10% overnight emergencies ($40k, 10pm–7am + full weekend, premium pricing (3× day rate) but low volume, friction-heavy booking). Chaos: on-call rotation (5 techs share on-call rotation, 2-night stints, communication via WhatsApp group "NightCall OnCall", tech doesn't always check group, dispatch fails, customer waits 45 mins for unknown ETA, angry), manual GPS routing (customer calls "Burst pipe at 42 York St, Brisbane CBD", dispatcher Mark opens Google Maps, manually calculates: "Tech 1 is 8km away, ETA 22 mins. Tech 2 is 12km, ETA 34 mins. Send Tech 1."), GPS doesn't account for traffic (22 mins ETA, actual 35 mins after traffic, customer angry "You said 22 mins, tech arrived 35 mins late, water damage worsened, bill you for extra damage!"), payment chaos (tech Dave finishes job 1:30am, customer Jessica "I don't have cash on me, invoice me", Dave sends invoice via WhatsApp photo (handwritten, illegible), Jessica loses photo, unpaid invoice, Dave chases Jessica 2 weeks later "That $850 invoice still due?", customer unhappy, relationship sours), after-hours premium not enforced (day rate $150 per hour is standard, after-hours should be $300–450 (2–3× multiplier per Fair Work), but Mark hasn't set up dynamic pricing, techs sometimes negotiate down "It's 2am, give me $200 for 1.5hr job instead of $450", revenue leakage $80–150 per job × 15 emergencies/week = $2k–3k/week lost premium, $100k–150k/yr revenue loss), compliance risk (Fair Work Australia: after-hours work must attract penalty rates, if audited Mark hasn't documented rates/paid penalty correctly, potential fine $5k–20k, back-pay claim from tech if underpaid), corporate contracts loose (hospital "St Vincent's Brisbane" has emergency generator backup but sometimes needs 24/7 plumber on-retainer, standing contract could be $50k/yr recurring, Mark hasn't formalized it, hospital calls whoever answers fastest, sometimes competitor gets the call).

Six Features Custom 24/7 Emergency Dispatch Platform Delivers

1. On-Call Roster + Auto-Dispatch — Rotation Tracking, Real-Time Location, Nearest-Tech Algorithm, SMS Alerts

Custom system: [On-Call Manager]. NightCall Trades manages 8 technicians (Dave, Tom, Sarah, Mike, Emma, Chris, Lisa, James). 2-week roster cycle: each tech on-call 2 nights/week. Week starting Mon 15 Jun 2026: on-call schedule (Monday night: Dave + Tom, Tuesday: Sarah + Mike, Wednesday: Emma + Chris, Thursday: Lisa + James, Friday: Dave + Sarah, Saturday: Tom + Mike, Sunday: Emma + Chris). System displays: calendar view (all 8 techs, color-coded per night, schedule locked, visible to all). Each tech sees: "You're on-call Mon 15 Jun, Tue 22 Jun, Fri 25 Jun" (personal calendar reminder, no missed shifts). Emergency call (Friday 16 Jun, 11:47pm): customer Jessica calls "Burst pipe, 42 York St Brisbane CBD, water pouring, need emergency help now!" System receives: call routed to NightCall's emergency line, SMS auto-triggered to on-call tech for Fri 16 Jun (Dave + Sarah). SMS: "EMERGENCY: Burst pipe, 42 York St CBD. Accept job? Reply Y or N." Dave replies (seconds): "Y" (app notification, GPS location auto-captured). System calculates: Dave's location (currently at home, Mt Graveside, 12km from job), Sarah's location (commercial job closure, Fortitude Valley, 8km from job). Algorithm: "Sarah closer (8km, ETA 14 mins), assign Sarah." SMS auto-sent to Sarah: "Job assigned, burst pipe 42 York St, customer Jessica +61401234567, GPS navigation: https://maps.link/job123, click to navigate." Sarah taps link, GPS opens (real-time traffic, ETA updated 14 mins, shows live traffic on route). Sarah replies "On way." System updates: Jessica receives SMS "Help on way, Sarah arriving 14 mins, vehicle rego ABC123, +61487654321." Jessica: "Great, thanks." Sarah drives (GPS real-time tracking), hits traffic (ETA now 18 mins), system auto-updates Jessica: "ETA now 18 mins due to traffic, still on way." Sarah arrives (app confirms on-site), immediately: SMS to Jessica "Sarah arrived, assessing pipe." Sarah works (30 mins), fixes burst, tests water. Completion: "Job complete, invoice $850 (after-hours premium rate, 1:15am, 3× multiplier on $283 base). Payment: https://pay.link/job123 (card/bank)." Jessica pays (Afterpay $212.50 × 4 fortnightly), system confirms receipt. Revenue captured: $850, correct premium rate applied. Next emergency (Sat 17 Jun, 2:15am): electrical outage at residential complex. On-call: Tom + Mike (Sat night roster). System sends SMS to both. Tom in bed (ignores), Mike replies "Y" immediately. Mike assigned, GPS ETA 11 mins. Customer receives: "Mike arriving 11 mins, vehicle rego XYZ789." Mike navigates (traffic-aware), arrives 11 mins (accurate ETA = customer satisfied, no complaints). System value: on-call roster eliminated WhatsApp chaos (SMS is reliable, push notifications alert even if phone silent), GPS auto-dispatch (nearest tech assigned algorithm = fastest response, 14–11 mins, no guessing), customer visibility (ETA + tech photo + vehicle rego = trust built, reduced complaint calls), after-hours premium enforced (all emergencies after 8pm automatically flagged as premium tier 3×, rate locked in system, no negotiation). Revenue: 15 emergencies/week × 52 weeks = 780 emergencies/yr. Day rate $150/hr × 1.5 hrs average = $225 base. Premium 3× = $675. Year 1 capture: 780 × ($675 - $225) = 780 × $450 = $351k extra revenue (premium recovery). Value: dispatch speed improved (ETA accuracy reduced wait-time complaints 80%), revenue premium enforced (eliminated $100k–150k/yr negotiation leakage), on-call management automated (zero admin for Mark managing roster).

2. Customer SMS Gateway + ETA Tracking + Tech Photos — Real-Time Comms, Proof of Arrival, Visual Reassurance

Custom system: [SMS Comms]. Emergency call (Mon 18 Jun, 3:47am): customer Robert "Water leak in ceiling, don't know where it's coming from, need help ASAP, I'm panicking." System (on-call Dave received alert): SMS to Robert: "Help on way. Dave assigned, ETA 12 mins. Vehicle rego ABC123. You'll receive live updates." Robert: calm (immediate response, knows who's coming, when). Dave navigates (hits traffic, ETA updates): SMS to Robert "Traffic delay, now 16 mins ETA." Robert: "Thanks for update, much better knowing." Dave arrives (16 mins), starts assessment. System: [Live Photos]. Dave points phone camera at ceiling leak, taps "send photo to customer." Photo auto-captures (timestamp, geolocation off for privacy, shows water stain, ceiling damage extent). System compresses, sends SMS + app notification to Robert: photo + caption "Found leak source, kitchen ceiling, cracked plumbing joint. Easy fix, 20 mins repair." Robert sees photo (relief, problem visualized, trust in Dave). Dave works (20 mins), repair complete. System: [After Photos]. Dave taps "before-after," system shows side-by-side: before (water stain, damage), after (repair applied, water stopped, ceiling dry). SMS to Robert: "Repair complete, before-after photos attached. Invoice $520 (3:47am emergency, after-hours premium)." Robert: "Perfect, thanks for the visual proof and quick response." Payment: link, Robert pays. System value: SMS comms eliminated "Where's my tech?" calls (ETA updates pro-active, customer never needs to call), photo proof built confidence (visual proof of problem = customer comfortable paying premium, less dispute risk), live-location transparency (customer can see vehicle approaching on map if app enabled, zero "tech's not coming" anxiety). Revenue: premium pricing ($520 vs $280 standard) accepted because customer saw before-after (justified premium in their eyes). Volume: 15 emergencies/week, average +$150 extra per job from reduced disputes/premium acceptance = $10.5k/yr revenue. Value: comms automation reduced call-back volume (Mark -3 hrs/week admin managing "where's my tech" calls = $1.5k labour saved), photo proof reduced warranty claims/disputes (no "tech didn't actually fix it" comebacks), customer experience (5-star reviews, word-of-mouth referral +20% new customers = +$80k/yr revenue).

3. Dynamic After-Hours Premium Pricing — Time-Based Rate Multiplier, Penalty Rates Compliant, Revenue Elasticity

Custom system: [Dynamic Pricing]. Base rate: $150/hr plumbing work (standard 7am–5pm). Multipliers: evening 5–8pm (1.25×, $187.50/hr), night 8pm–10pm (1.5×, $225/hr), late-night 10pm–6am (2.5×, $375/hr), overnight 6am–7am (1.25×, $187.50/hr—transition zone). Weekends: Sat 7am–5pm (1.5×, $225/hr), Sat 5pm–10pm (2×, $300/hr), Sat 10pm–6am (3×, $450/hr), Sun same as Sat. Rationale (Fair Work Australia): after-hours work commands penalty rates to compensate risk (tech away from family, fatigue, hazard exposure, emergency pressure). Insurance + compliance: penalty rates documented in system (tech salary + penalty multiplier visible on timesheet, compliance auditable). Example job 1: Burst pipe Mon 10am (standard rate). Job duration 1.5 hrs. Rate: $150/hr. Invoice: $225. Example job 2: Burst pipe Mon 11:47pm (late-night rate). Job duration 1.5 hrs. Rate: $375/hr. Invoice: $562.50. Same job, same duration, 2.5× price elasticity = $337.50 extra revenue per job. Volume: 15 emergencies/week, assume 40% after 8pm (6 jobs/week, 312 jobs/yr). Premium jobs: 312 × $375/hr × 1.5 avg duration = $175.5k potential. Standard jobs: 312 × $150/hr × 1.5 = $70.2k. Difference: +$105.3k extra from after-hours premium (if all priced correctly). Current baseline: Mark underprices after-hours (negotiation pressure, customer resistance), achieves only 60% of premium = $63.2k actual. Custom system auto-enforces premium (no negotiation, locked in at dispatch time), achieves 90% of premium = $94.8k extra captured. Year 1 impact: +$94.8k revenue. Compliance: Fair Work auditor asks "How do you ensure penalty rate compliance?" Mark shows: system documentation (each job tagged with time-of-day multiplier, timesheet shows multiplier applied to tech salary). Tech Dave (1.5 hrs late-night work, $375/hr rate, system shows: "Dave earned $562.50 gross (including 2.5× penalty multiplier) for this job." Dave's fortnightly payslip auto-calculated (system multiplies hours by multiplier, pays penalty component separately for audit clarity). Auditor: "Compliant, documented, no fine risk." Insurance negotiation: insurer reviews system (penalty rates documented, Fair Work compliant). Insurer: "Lower risk profile, reduce workers-comp premium by $500–1k/yr." Value: premium pricing captured +$94.8k revenue, Fair Work compliance prevented $5k–20k fine risk, penalty rates paid fairly (tech retention improved, better morale knowing after-hours work compensated properly).

4. Corporate Emergency Contracts + Auto-Renewal — Retainer Revenue, SLA Lock-In, Volume Guarantees, Billing Automation

Custom system: [Contract Manager]. NightCall Trades targets corporate customers: hospitals, shopping centres, office parks, data centres. Prospect: St Vincent's Hospital Brisbane (1000-bed hospital, emergency operations 24/7, generator backup, but occasional plumbing / electrical emergency outside working hours). Current: hospital calls random plumber (Google search, 3-star reviews), tech arrives 30 mins later, problem unresolved, hospital loses trust, calls different plumber next time (no loyalty). NightCall pitch: "24/7 emergency contract, guaranteed response under 15 mins, dedicated plumber on on-call retainer, $4k/month ($48k/yr)." Hospital agrees (peace of mind, guaranteed response, premium service justified for critical infrastructure). System: [Contract Setup]. Contract: "St Vincent's Hospital, 24/7 emergency plumbing on-call retainer, $4k/month, response SLA 15 mins, minimum 2 calls/month guarantee, availability 365 days/yr." System auto-schedules: retainer tech assigned (Sarah dedicated to St Vincent's calls, on-call 50% of nights, other nights covered by secondary backup tech Tom). Monthly invoice auto-generated (1st of month, $4k, sent to hospital accounts). Hospital pays net-30 (7-day average, reliable payment). Year 1: 8 calls to hospital (average 1.3 calls/month, minimum 2 guaranteed, hospital is light caller, but minimum clause ensures revenue stability if low-volume month). Revenue: $48k/yr guaranteed (12 months × $4k, recurring cash flow, no customer acquisition cost after initial close). Secondary revenue: hospital occasionally requests weekend urgent job (not emergencies, but scheduled work, preventative maintenance). System flags: "St Vincent's customer + contract holder = premium service tier, use contract tech Sarah if available, lock in customer loyalty." Sarah's weekend job: backup generator maintenance, $800 (upsell, not included in contract). Hospital: "Great, need this quarterly," system auto-schedules Q2/Q3/Q4 gigs. Revenue: $800 × 4 = $3.2k/yr extra (upsell capture). Total hospital: $48k retainer + $3.2k upsell = $51.2k/yr. Growth: NightCall lands 3 corporate contracts (hospital, shopping centre, data centre) = $48k × 3 = $144k/yr guaranteed recurring revenue. Scale: Day-work (residential, commercial calls) = variable. Contracts = predictable. Mix: 36% contract revenue ($144k), 64% variable ($256k) on $400k baseline → revenue mix becomes 40% + 60% = better stability. Upsell wave: annual contract renewal (Dec 2026). System alerts: "St Vincent's contract renews 31 Dec 2026, 60 days out. Send renewal proposal." Renewal proposal: "Upgraded to 20-min SLA (higher-touch service) + 4 preventative maintenance visits/yr (included). New price: $5.5k/month ($66k/yr)." Hospital: "Worth it for better SLA, renew upgraded." Revenue growth: $48k → $66k (37.5% increase per contract, applied to 3 contracts = +$54k/yr). Year 2 total: $400k baseline + $144k contracts + $54k upsell growth = $598k revenue (49.5% growth, same 8 techs). Billing: automated invoicing (contract manager sees: "St Vincent's Q2 invoice due 1 Jul, $4k, hospital account email, auto-send." Invoice auto-sent, payment tracked, if 10 days overdue system alerts Mark "St Vincent's payment due, follow up.") Value: contract revenue locked in ($144k/yr guaranteed, zero churn if service is reliable), upsell captured (+$54k/yr growth from renewals, no new customer acquisition cost), cash flow stabilized (predictable monthly revenue, easier budgeting, can hire staff confidently knowing revenue floor).

5. Fair Work Compliance + Penalty Rate Tracking — Rostering Documentation, After-Hours Audit Trail, Fatigue Management

Custom system: [Compliance Manager]. Fair Work Australia rules (emergency trades specific): after-hours work triggers penalty rates (already covered in feature #3), but also "break-in-service" penalties (if tech called from home to job, loses evening time with family = Fair Work considers this "break" in service, tech entitled to penalty loading even if job 30 mins only; some contracts specify "call-out fee" separate from labour rate). NightCall's compliance gap: no documentation of call-out practices, potential fine $10k+ if audited and found non-compliant. Custom system tracks: [Call-Out Fee]. Tech Sarah on-call Mon 10pm. Emergency call 11:47pm (burst pipe customer). Sarah leaves home, drives 14 mins, works 1.5 hrs, drives back 14 mins = total 1 hr 59 mins on-task. Sarah's compensation: base rate $375/hr late-night (2.5× multiplier already applies), plus call-out fee $80 (documented in system: "Call-out fee, 23:47 call timestamp, job acceptance 23:49, 2-min response time"). Sarah's invoice total: (1.5 hrs × $375) + $80 call-out = $562.50 + $80 = $642.50. System: audit trail (call-out timestamp logged, fee amount logged, compliance documented). SafeWork Queensland inspector reviews: "Call-out fee documented, Fair Work compliant, penalty rates calculated correctly." No fine. Tech fatigue management: system tracks hours worked (each tech, rolling 7-day tally). Sarah's week: Mon 1:59 am work, Tue 0 (rest), Wed 3:15 am work (pipe job + valve repair), Thu 0, Fri 1:45 am work (electrical outlet emergency), Sat 0, Sun 2:30 am work (burst main). Total after-hours: 9:29 hrs in 7 days. System alert: "Sarah accumulated 9.5 hrs after-hours work this week, approaching fatigue threshold (10 hrs/week recommendation). Consider: day-shift only next week or light on-call duty." Mark sees alert, decides: Sarah day-shift only next week (prevent burnout, reduce safety risk at 3am while fatigued). System rostering auto-adjusts: Tue on-call = Tom instead of Sarah. Compliance documentation: "Sarah fatigue monitoring implemented, hours tracked, schedule adjusted per guidelines, audit-ready." Insurance question: "How do you manage tech fatigue (safety hazard)?" Mark: "System tracking, weekly review, schedule adjustment per Fair Work guidelines, risk mitigation documented." Insurance: "Excellent, reduce premium $200–300/yr (safety-conscious operator)." Value: Fair Work compliance prevented $5k–10k fine risk, fatigue management reduced accident risk (emergency work at 3am while exhausted = liability), insurance premium negotiation saved $200–300/yr, tech retention improved (management proactively manages fatigue = morale up, retention up 85% vs 75% baseline).

6. Payment Recovery + Corporate Invoicing — On-Site Payment Link, Afterpay + Bank Transfer, Delinquency Tracking

Custom system: [Payment Manager]. After-hours emergency work: high default risk (customers panicked, cash not on-hand, invoicing delayed = payment recovery rate 60–70% vs daytime 95%+). Tech Dave finishes job (1:30am, customer Jessica "I don't have cash, send invoice"). Dave system sends invoice-link SMS: "Invoice $850, pay now: https://pay.link/job456." Jessica has 3 options: (1) Credit/debit card (instant, 2.2% fee system absorbs), (2) Afterpay (4 fortnightly payments, $212.50 each, Jessica prefers for cash-flow), (3) Bank transfer (email invoice with BSB/account, Jessica pays next morning). Jessica chooses Afterpay: system processes $212.50 × 4 (auto-scheduled, payment guaranteed by Afterpay, Dave's $850 captured). Success: 24 hrs later, $850 received. Recovery rate: 95% (vs manual 60%). Corporate invoicing (hospital): St Vincent's $4k monthly contract + emergency jobs on top. System generates 2 invoices monthly: (1) Contract invoice $4k (net-30, standard business invoice), (2) Emergency jobs invoice (variable, bundled, net-30). Hospital's accounts team logs into portal: sees invoices, payment history (paid on-time for 12 months = hospital delinquency rate 0%). System tracks: "St Vincent's, payment record: 100% on-time, trusted customer, payment risk: zero." Mark negotiates: "Can we extend net-30 to net-60 (60-day payment terms)?" Hospital: unlikely (standard net-30), but system shows Mark the risk: "If extended to net-60, capital tied up (St Vincent's $4k contract rolling 2 months out = $8k outstanding). Not recommended unless customer is long-term strategic (5+ years)." Mark declines (keep net-30, working capital healthy). Delinquency management: system tracks invoices due. Residential customer Sam, emergency job Mon 2am, invoice $680, due 7 days. Day 8: unpaid. System alert to Mark: "Sam invoice $680 overdue 1 day, send reminder." Mark SMS to Sam: "Invoice $680 still due, payment link: https://pay.link/job789." Sam replies: "Forgot, paying now," pays Afterpay. Captured. Day 15: another customer (Robert) still owes $520 from weekend job. Overdue 8 days. System escalates: "Robert $520 overdue 8 days, recommend follow-up call." Mark calls Robert: "Hey, your invoice $520 due from weekend job, still good?" Robert: "Yeah, can you do Afterpay?" System offers, Robert approves, payment scheduled. Value: payment recovery improved (95% vs 60% = +$28k/yr on $400k baseline captured recovered), Afterpay + bank transfer options increased acceptance (multiple payment paths reduce friction), corporate payment risk managed (zero delinquency on repeat customers, cash-flow predictable). Corporate contracts: net-30 or better terms on predictable repeat customers = working capital healthy (cash available for payroll, fuel, equipment, growth investment).

24/7 Emergency Dispatch Business ROI: 8-Tech Fleet, Year 1 Break-Even + $200k Net Profit, Year 2+ $300k/yr Growth

Build cost: $85k (on-call roster + GPS dispatch + SMS gateway + dynamic pricing + contract manager + payment recovery + compliance tracking + mobile app). Year 1 ops: $6k/yr (SMS gateway $2k, app hosting $2k, payment processing 2.2% built into customer payments, support $2k). Total Year 1 investment: $91k. Value captured: (1) After-hours premium recovery (15 emergencies/week, 40% after 8pm = 6 jobs/week, 312/yr, premium $450/job average, Year 1 capture conservative $94.8k). (2) Corporate contract revenue (3 contracts × $48k base + $4.2k upsells = $156k locked recurring, Year 1 capture full year $156k). (3) Payment recovery (emergency work 95% vs manual 60%, $400k baseline × 35% extra recovery = $140k, Year 1 capture $28k conservative from recovery improvement). (4) Labour elimination (Mark admin scheduling + dispatch + invoicing + payment chasing = 8 hrs/week manual, system reduces to 1 hr/week = 7 hrs saved/week × $30/hr = $10.5k/yr labour). (5) Premium pricing acceptance (customer sees before-after photos + real-time ETA = willing to pay premium, day-rate jobs uplift average $50 per job, 400 day-jobs/yr × $50 = $20k extra). (6) Compliance insurance reduction (Fair Work + fatigue documented, insurance premium reduce $500–1k/yr, conservatively $750). Year 1 total value: $94.8k + $156k + $28k + $10.5k + $20k + $0.75k = $310.05k. Year 1 net: $310k - $91k = +$219k profit. Break-even: 2–3 months (fast). Year 2: contract value grows ($156k → $210k with renewals + upsells), after-hours volume grows (word-of-mouth, brand, +15% = $109k), labour savings repeat ($10.5k), premium upsells repeat ($20k), compliance insurance repeats ($0.75k). Year 2 total value: $109k + $210k + $10.5k + $20k + $0.75k = $350.25k. Year 2 net: $350k - $6k ops = $344k profit. Year 3+: scale to 12 technicians (additional 4 hires, same platform, zero new software cost), revenue scales 1.5× ($400k → $600k baseline day-work, + corporate contracts now 6 customers = $312k contract revenue = $912k/yr). Scale without software rebuild = pure operational leverage. Conservative scenario (8 techs, organic growth): Year 2+ net $300k+/yr profit on $500k–600k revenue = 50–60% margin (very healthy for service business, typical is 20–30%). Growth upside: Year 3–4, target 15–20 corporate contracts ($240k–$320k contract revenue) + 12 techs ($800k day-work baseline) = $1.2m revenue with 60%+ margin = $700k+ annual profit potential. Need custom platform for your emergency dispatch fleet? Check platform pricing or book a call—we'll handle on-call rostering, GPS dispatch, SMS comms, dynamic after-hours pricing, corporate contract lock-in, Fair Work compliance, and payment recovery so you can scale emergency revenue 3–4× without hiring overhead.

Six FAQs

Why do emergency trades (plumbing, electrical, locksmith) need different software than standard business software?

Standard SaaS (e.g., ServiceTitan, Housecall Pro): designed for scheduled work (customer books appointment, tech arrives at scheduled time, payment at completion). Features: online booking, job scheduling, invoicing, payment collection. Emergency trades have different dynamics: (1) On-call rotation (tech can't be "booked" in advance, roster is internal scheduling, external customer can't pick a tech or time—they call, system auto-assigns nearest available). (2) Real-time dispatch (customer calls at 2am with emergency, tech needs assignment within 60 seconds, not scheduled 3 days in advance). (3) Dynamic pricing (3× multiplier at 2am, 1.25× at 6:30pm—time-of-day critical, standard SaaS has fixed pricing). (4) After-hours premium compliance (Fair Work penalty rates must be documented + paid correctly, standard SaaS doesn't track multipliers). (5) Corporate retainers (hospital pays $4k/month for "right of call", not per-job pricing, standard SaaS assumes transactional pricing). (6) GPS dispatch (nearest-tech algorithm, real-time location tracking, traffic-aware ETA updates—standard SaaS has basic routing). Standard SaaS gap: built for appointment-based work, not emergency response. Emergency trades need: real-time dispatch, dynamic pricing, on-call management, contract revenue, compliance tracking. Custom build accounts for these unique dynamics.

How does GPS dispatch actually determine "nearest technician" when traffic varies?

Nearest-tech algorithm: system tracks real-time GPS location of all on-call technicians. Emergency call arrives (customer address). System calculates: (1) Distance from each on-call tech to customer (crow-flies straight-line distance, then Google Maps API distance-matrix query for driving distance). (2) ETA calculation (distance + traffic data from Google Maps real-time, returns ETA 14 mins for tech 1, 20 mins for tech 2, even if tech 1 is closer by straight-line). (3) Capability filter (some jobs are specialist, e.g., "data-centre critical electrical work", system only assigns techs with "data-centre certification" tag). (4) Availability filter (some techs already on-site at another job, system marks "unavailable", skips). (5) Ranking (all available + certified techs ranked by ETA, fastest ETA assigned). Example: 3 on-call techs (Dave, Sarah, Tom). Customer emergency at CBD address. System calculates: Dave (12km away, traffic medium, ETA 18 mins), Sarah (8km, traffic light, ETA 11 mins), Tom (15km, traffic heavy, ETA 26 mins). Ranking: Sarah first (11 mins). Sarah assigned. SMS to Sarah + customer. Sarah navigates (live traffic updates ETA), if traffic worsens (11 mins → 15 mins), system auto-updates customer (real-time ETA refresh every 2 minutes). Accuracy: Google Maps traffic is 95%+ accurate (real-time Waze + Google Maps crowd-sourced data). Edge case: Sarah's GPS signal lost (tunnel, dead zone). System detects (signal off 5+ mins), escalates to Tom (next nearest). Tom gets assignment, SMS sent, takes over. Fallback: if all on-call techs > 30 mins ETA, system can flag "call customer, offer callback at later time" or "escalate to partner company if available". ROI: ETA accuracy (11 mins vs manual "20–30 mins" guesswork) = customer satisfaction (predictability, trust), response time (nearest tech = fastest arrival = premium pricing justifiable).

What happens to on-call staff if they don't respond to emergency SMS within 60 seconds?

Escalation protocol: emergency SMS sent to tech (on-call Dave). 60-second timer starts. If no response: (1) System sends SMS reminder (urgent, 2nd alert) at 30-second mark. (2) If still no response at 60 seconds: system auto-escalates to 2nd on-call tech (Sarah assigned as backup). SMS to Sarah: "Dave didn't respond, emergency assigned to you." Sarah confirms, system cancels Dave's alert. Dave wakes up 90 seconds later, sees missed alerts, knows he lost the job (routine, expected, no penalty but miss revenue-opportunity). (3) If 2nd tech (Sarah) also doesn't respond: system escalates to 3rd on-call tech (Tom). (4) If all on-call techs don't respond within 5 mins: system triggers override (calls dispatch centre or business owner directly, human takes over). Fairness: on-call staff are paid retention fee (standby payment) for being on-call (e.g., $50/night to carry phone, be available). Non-response 3+ times per week = disciplinary (verbal warning, then loss of on-call privilege if pattern continues). Incentive: fast response = first access to jobs = earn more (on-call fee + job revenue), so techs stay alert. System fairness: response tracking (visible to tech, management sees "Dave responded in 40 secs, Sarah 12 secs, Tom 85 secs", over time patterns emerge). Competitive: techs see who responds fastest (informal competition), fast-responders get reputation, potential for bonus or priority scheduling benefits. Value: zero missed emergencies (escalation protocol ensures job always assigned), tech accountability (response time tracked, performance visible).

How does after-hours premium pricing comply with Fair Work Australia rules?

Fair Work Australia framework: minimum wages + penalty rates (award rates differ by industry, emergency trades typically under General Construction or Building Services awards). Penalty rates: after-hours work (before 6am, after 10pm, weekends) attracts multipliers (1.25–3× base rate depending on time + day). Plumbing example: base rate $150/hr (standard 7am–5pm). Fair Work award specifies (emergency services): after 8pm weekday = +50% penalty ($225/hr), after 10pm = +100% penalty ($300/hr), weekend nights = +150% penalty ($375/hr). Custom system enforcement: every job tagged with time-of-call timestamp. System calculates: "Job logged 23:47 (11:47pm), after-hours tier applies, multiplier 2.5× ($375/hr applies)." System auto-calculates tech compensation (1.5 hrs × $375 = $562.50 gross). Payslip breakdown (audit-clear): "Base hours 1.5 × $150 = $225 ordinary rate, Penalty component 1.5 × $225 (50% uplift for after-hours, per Fair Work award XYZ) = $337.50, Total = $562.50." Tech receives: $562.50. Auditor review: "Penalty correctly calculated, award-compliant, multiplier applied correctly." Employer (NightCall) shows: system documentation (algorithm transparent, calculation visible). No dispute. Customer invoice: "Job 23:47–01:22, 1.5 hrs after-hours emergency plumbing, rate $375/hr per emergency premium pricing, total $562.50." Customer charged, tech paid correctly, Fair Work compliant. Insurance + compliance: no fine risk (documentation proves compliance), tech morale (clear pay structure, tech knows after-hours work is compensated fairly), customer satisfaction (premium justified, customer sees explanation, willing to pay). Risk if non-compliant: audit finds employer underpaid techs (should be $562.50, paid $350), employee complaint filed, Fair Work investigates, back-pay owed to tech + penalty fine to employer ($5k–20k). Custom system eliminates this risk through transparency + automation.

Can the platform integrate with insurance companies or become a "preferred emergency vendor" network?

Yes, two pathways: (1) Insurer integration. Insurance company (e.g., QBE, AAMI, Westpac) receives emergency claim (customer: "Burst pipe, $5k water damage, covered under home insurance"). Insurer approves claim, needs licensed plumber to assess + repair (within insurer network). Custom platform: insurer's system sends emergency alert to NightCall system (API integration, insurer-approved vendor). Alert: "Customer Sarah, burst pipe, claim approved, authorize repair up to $5k, insurer reference XYZ123." System auto-creates job (zero manual entry), system calculates: nearest tech (Tom, ETA 12 mins). Tom assigned. Tom arrives, assesses, repairs (1.5 hrs), system generates invoice ($562.50), system sends to insurer (claim reference XYZ123 attached, for reimbursement). Insurer receives, pays NightCall directly (zero customer involvement). NightCall revenue: $562.50. Customer has zero out-of-pocket (insurer covers). Repeat insurer referrals: insurer sends 10 emergency claims/month to NightCall (customer base large, high referral volume). Revenue: 10 × $562.50 × 12 months = $67.5k/yr insurer-sourced revenue. Insurer benefit: preferred vendor (fast response, professional documentation, claim processed 2 days vs manual 10 days). NightCall becomes insurer's sole plumber in Brisbane region (volume lock-in, contract 3-year). (2) Marketplace network. NightCall operates Brisbane. Sister company operates Sydney. Custom platform: both companies share on-call roster (inter-state roaming). Customer emergency in Sydney (customer calls national 24/7 emergency number), Sydney operator receives, system routes to nearest tech (Sydney company's roster), Sydney tech responds. Revenue: Sydney company pays NightCall referral fee ($50–100 per job) for matching algorithm + infrastructure access. NightCall scales revenue (passive, cross-company network) without hiring new staff. Ecosystem: 5 regional emergency trades companies, all integrated on 1 platform, customers call national number, nearest company's tech assigned. Platform provider (Aiden's company) takes 10% of transaction volume (SaaS revenue). Competitive: traditional insurer-vendor lists are fragmented (insurer has 20+ plumbers per region, customer calls, insurer gives them 3 options, customer picks, tech may be 30+ mins away). Integrated platform: customer emergency auto-routed to nearest certified vendor (across network), ETA 12–15 mins (faster, better customer satisfaction, insurer claims processed quicker). Value: insurer partnership = volume lock-in (15% of Brisbane plumbing emergencies) + recurring referral revenue, marketplace = scaled network (zero new hiring, passive revenue from cross-company integrations).

What's the business case for offering 24/7 dispatch to a competitive market (e.g., Brisbane has dozens of plumbers)?

Competitive advantage: 24/7 emergency dispatch at after-hours premium rates is capital-intensive (requires on-call roster + GPS tech + SMS infrastructure + customer trust). Competitors (typical plumber): day-only hours (7am–5pm), weekend ad-hoc (no structured availability), after-hours (irregular, no premium, customer frustration). NightCall: 24/7 structured + premium pricing ($3× at night) + guaranteed response (15-min SLA corporate contracts). Customer choice: 2am burst pipe, homeowner calls: (1) Generic plumber (Google search, 3-star reviews, 40-min ETA, no premium visible), vs (2) NightCall (app + SMS + 11-min ETA, before-after photos, professional, pay Afterpay). Homeowner picks NightCall (speed, visibility, trust). Revenue: homeowner pays $562.50 (premium justified by visibility + speed). Competitor gets $280 (standard rate, slower response, no premium). NightCall premium: $282.50 extra per job. Volume: 15 emergencies/week × 52 weeks = 780/yr. Revenue advantage: 780 × $282.50 = $220k/yr premium capture (vs competitor zero). Corporate contracts: hospital retainer ($48k/yr). Competitors don't offer retainers (transactional only). NightCall locks in $48k/yr guaranteed (12 corporate contracts = $576k/yr stable recurring, zero churn if service reliable). Competitors chase one-off calls (revenue unpredictable, customer churn high). Market research: Brisbane metro (1 million people, ~200k households, 15% experience emergency plumbing/electrical/locksmith per year = 30k annual emergency jobs). Current market: spread across 200 plumbers (150 jobs each average, low premium, chaos). NightCall model: capture 2% of market (600 jobs/yr × $500 average premium-inclusive = $300k/yr), scale to 5% (1500 jobs/yr = $750k/yr) within 3 years through brand + reputation. Winner-take-most: first-mover 24/7 premium model builds trust + retention, scales faster than competitors trying to copy. Barrier: platform tech (easy to copy), but customer base + corporate contracts (hard to copy, relationship-locked). Year 1: establish brand (24/7 reliable), year 2: lock in corporate contracts, year 3: defensible market position (network effects, customer inertia). ROI: $91k platform investment in year 1 pays for itself via year 1 profit ($219k), then becomes strategic asset (enables 3–4× revenue scaling in years 2–3 without proportional cost growth = leverage). Competitors without platform: hire more staff to scale (cost multiplier), margin compressed. NightCall with platform: scale without proportional cost, margin expands 20–30% points (from 30% to 50–60%), premium defensible. Value: first-mover advantage is time-limited (12–18 months before competitors copy), move fast to lock in customers + contracts before market matures.