ZedQueue

Join public clinic queues from home and get notified when it's your turn

Score: 7.9/10ZMMedium BuildReady to Spawn
Brand Colors

The Opportunity

Problem

Zambia's public healthcare system is critically understaffed, forcing patients to endure long waits, reduced care quality, and higher health risks.

Solution

ZedQueue allows Zambian patients to view live crowd-sourced wait times at public facilities, join virtual queues remotely, and receive SMS or push notifications when their turn approaches. Patients avoid spending entire days at overcrowded clinics, reducing exposure to infections and lost wages, especially critical for rural users who travel long distances.

Target Audience

Zambian citizens relying on public hospitals and clinics, especially in rural and low-income areas

Differentiator

First app built exclusively for Zambia's public sector with SMS-first fallback for feature phones and crowd-sourced data weighted by verified patient check-ins, creating unmatched accuracy in rural districts where official systems don't exist.

Brand Voice

supportive

Features

Clinic Locator & Live Wait Times

must-have45h

Shows nearby public clinics with current crowd-sourced wait times and busyness level

Virtual Queue Joining

must-have65h

Reserve your place in line for specific services (OPD, antenatal, ART) without physical presence

SMS & Push Notifications

must-have50h

Alerts when you are within 5 spots or when it's your turn, with offline SMS fallback

Wait Time Reporting

must-have35h

Patients report actual wait after visit to improve community data accuracy

Personal Queue Dashboard

must-have40h

Track all active and past queues with estimated vs actual times

Basic Health Profile

must-have30h

Store age, chronic conditions and preferred facilities for faster queue joining

Family Queue Management

nice-to-have45h

Add children or elderly relatives to queues under one account

Historical Wait Analytics

nice-to-have55h

See typical wait times by day of week and service type per clinic

Clinic Feedback System

future80h

Anonymous rating of care quality after visit

Total Build Time: 445 hours

Database Schema

users

ColumnTypeNullable
iduuidNo
phonetextNo
full_nametextYes
districttextNo
chronic_conditionstextYes
created_attimestampNo

Relationships:

  • queue_entries.user_id → users.id

clinics

ColumnTypeNullable
iduuidNo
nametextNo
districttextNo
latitudefloatYes
longitudefloatYes
average_wait_minutesintYes
last_updatedtimestampYes

Relationships:

  • queue_entries.clinic_id → clinics.id
  • wait_reports.clinic_id → clinics.id

queue_entries

ColumnTypeNullable
iduuidNo
user_iduuidNo
clinic_iduuidNo
service_typetextNo
statustextNo
positionintYes
joined_attimestampNo
estimated_ready_attimestampYes

Relationships:

  • references users and clinics

wait_reports

ColumnTypeNullable
iduuidNo
clinic_iduuidNo
user_iduuidNo
reported_wait_minutesintNo
crowd_leveltextYes
created_attimestampNo

Relationships:

  • references clinics and users

API Endpoints

GET
/api/clinics/nearby

Return clinics in user's district with latest wait times

🔒 Auth Required
POST
/api/queues/join

Create new queue entry and return position

🔒 Auth Required
GET
/api/queues/my

Get user's active and recent queue entries

🔒 Auth Required
POST
/api/reports/submit

Submit post-visit wait time report

🔒 Auth Required
POST
/api/notifications/trigger

Internal endpoint for queue position updates

Tech Stack

Frontend
Flutter 3.19 + Riverpod + dio
Backend
Node.js + Express
Database
PostgreSQL
Auth
Firebase Auth (phone-based)
Payments
Flutterwave
Hosting
Railway (backend + Postgres), Google Play + App Store
Additional Tools
Twilio for SMSOneSignal for push

Build Timeline

Week 1: Foundation and auth

55h
  • Project setup
  • Firebase phone auth
  • Basic navigation and clinic locator UI

Week 2: Core queue engine

65h
  • Queue joining logic
  • Position calculation algorithm
  • Database schema implementation

Week 3: Real-time notifications

60h
  • SMS integration with Twilio
  • OneSignal push setup
  • Background queue monitoring

Week 4: Reporting and dashboard

50h
  • Wait time reporting flow
  • Personal dashboard
  • Data aggregation for averages

Week 5: Polish and payments

45h
  • Flutterwave subscription integration
  • Family management
  • Offline support with Hive

Week 6: Testing and launch prep

35h
  • Beta testing with 50 users in Lusaka
  • App store assets
  • Landing page
Total Timeline: 6 weeks • 310 hours

Pricing Tiers

Free

$0/mo

Limited to 4 queues per month

  • View live wait times
  • Join up to 4 queues/month
  • Basic notifications

Pro

$9/mo

None

  • Unlimited queues
  • Family accounts (up to 3)
  • Priority SMS alerts

Premium

$35/mo

None

  • All Pro features
  • Historical analytics
  • Priority queue weighting at partner clinics
  • Exportable health reports

Revenue Projections

MonthUsersConversionMRRARR
Month 18504%$1,190$14,280
Month 66,2009%$19,530$234,360

Unit Economics

$6.5
CAC
$185
LTV
11%
Churn
78%
Margin
LTV:CAC Ratio: 28.5xExcellent!

Landing Page Copy

Stop Waiting Hours at Zambian Clinics

Join the queue from your village, get notified when it's your turn, and spend time on what matters.

Feature Highlights

Live crowd-sourced wait times
Virtual queue tickets
SMS alerts for any phone
Built for rural Zambia

Social Proof (Placeholders)

"'I joined the queue while cooking nsima and arrived just in time.' — Agnes M., Chipata"
"'This saved me 6 hours last month for my child's vaccinations.' — John B., Kitwe"

First Three Customers

Visit two district hospitals in Lusaka and Southern Province to offer free Premium access to their health promotion officers in exchange for promoting the app during community outreach. Run targeted Facebook ads in Bemba and Nyanja in rural districts offering free queue joins for the first 200 users. Partner with three large WhatsApp groups for new mothers and TB patients.

Launch Channels

ProductHuntr/SaaSZambian Facebook health groupsWhatsApp health communitiesLocal radio partnerships in Lusaka and Ndola

SEO Keywords

zambia clinic queue apppublic hospital wait times zambiavirtual queue public health zambiaskip hospital lines zambiazambia hospital appointment app

Competitive Analysis

Per consultation
Strength

Broad telemedicine offering

Weakness

No focus on physical public clinic queuing or rural crowd-sourcing

Our Advantage

Specifically built for public sector queues with SMS-first design

🏰 Moat Strategy

Strong network effects: the more patients report wait times, the more accurate the data becomes, creating a data moat difficult for newcomers to replicate in Zambia's specific context.

⏰ Why Now?

Smartphone penetration in Zambia crossed 45% in 2023 while public healthcare staffing ratios continue to worsen. Post-COVID digital health acceptance and government eHealth strategy create perfect timing.

Risks & Mitigation

marketmedium severity

Low smartphone penetration in deepest rural areas

Mitigation

Heavy SMS fallback and partnerships with community health workers who have smartphones

executionhigh severity

Clinics may not recognize virtual tickets

Mitigation

Start with pilot clinics that agree to honor virtual positions and expand from proven success

technicalmedium severity

Accurate position calculation with incomplete data

Mitigation

Use statistical modeling based on historical reports and continuously refine algorithm

Validation Roadmap

pre-build12 days

Interview 40 patients and 12 clinic staff in 3 districts about current wait pain

Success: 80% of patients say they would use virtual queuing at least monthly

mvp35 days

Closed beta with 150 users in Lusaka and Southern Province

Success: At least 65% return rate for second queue join within 3 weeks

launch45 days

Public launch with marketing in 4 provinces

Success: 3000 downloads and 12% conversion to paid in first 45 days

Pivot Options

  • Become B2B SaaS for private hospitals
  • Expand into full appointment booking with clinic integration
  • Add medicine stock visibility layer

Quick Stats

Build Time
310h
Target MRR (6 mo)
$18,500
Market Size
$18.5M
Features
9
Database Tables
4
API Endpoints
5