NURO

Enter password to continue

NURO

The AI-Native PharmacyOS for Independent Pharmacy

Board-Ready Business Plan • Confidential

April 2026

🎯 Executive Summary

18,960
Independent Pharmacies
$103B
Market Size
1,200+
Annual Closures
80.3%
Declining Financially
NURO is the AI-native PharmacyOS for entrepreneurial independent pharmacies. It replaces fragmented legacy systems with a single cloud-native operating layer that embeds clinical programs into workflow, returns data control to pharmacies, and enables independents to operate as a coordinated network.

The Opportunity

Why this market, why now

Independent pharmacies are individually strong but collectively fragmented. Chains execute as one coordinated network while independents run on software built before the internet. NURO provides the operating layer that closes this gap — unified workflow, owned data, network execution.

The Plan

Phased, milestone-driven

Founder-led sales to 8–12 design partners. Validate the wedge, capture 3 public case studies, prove migration and onboarding. Scale hiring and paid GTM only after repeatable proof. Milestone-based profitability tied to adoption density, not calendar dates.

Independent pharmacy runs on software built before the internet. Every transaction generates data. Control flows upstream. Pharmacies create value. Others capture it. NURO is not a vendor. It is an operating layer.

Messaging Stack

LayerRole
Modern + reliable web appTrust Layer Credibility & reliability signal
AI-native workflow improvementHero Story Queue triage, patient follow-up, reporting, exception handling
Creator studio / owner automationsPhase Two Upside for power users
Data ownership / sovereigntyDifferentiator Strategic moat
NCPA alignmentDistribution Channel + mission alignment

Board Process Timeline

MilestoneDate
Investor sign-off targetApril 29, 2026
Board-related windowApril 27 – May 1, 2026
Business plan dueMay 10, 2026
Financial due diligence & valuationWeek of May 15, 2026
Alignment on plan, pricing, governance, KPIsWeek of June 12, 2026
Definitive agreement targetWeek of July 10, 2026
NCPA trade show (Kansas City)October 2026

📉 Market Problem

3–5%
Gross Margins (10yr Low)
$45–75K
DIR Revenue Lost / Pharmacy / Year
30–40%
Pharmacist Time on Manual Entry
$85–120K
Annual Labor Waste / Pharmacy

Four Connected Problems

Fragmented Software

5+ systems, manual reconciliation, no unified view. Legacy PMS systems are 30–40 years old.

Workflow Burden

Pharmacist time wasted on data entry, unnecessary alerts, and rework instead of patient care.

Data Extraction

Pharmacies create data, intermediaries capture value. Top 3 PBMs process ~80% of the 6.6B annual prescriptions.

No Network Execution

Independents cannot reliably execute payer, manufacturer, or clinical programs at scale.

Independent pharmacy is individually strong but collectively fragmented. Chains can execute as one coordinated network. Independents cannot — yet.

Market Data

MetricValue
Independent community pharmacy locations18,960
Independent pharmacy market size$103B
Annual closures1,200+ stores per year
Financial health declined (2024)80.3%
Interested in digital pharmacy tools63%
Legacy software age30–40 years old
Clinical program adoption delay6+ months to first patient engagement
CPESN network participants3,500+ pharmacies

⚡ Why Now

Margin Crisis

Existential pressure creates urgency

Gross margins at 3–5% (10-year low). DIR fees extract $45K–$75K per pharmacy per year. 1,200+ closures annually. Pharmacies need operational leverage, not incremental tools.

Legacy Lock-in Breaking

30–40 year old systems hitting end-of-life

Pioneer, Rx30, Computer-Rx, QS/1, Liberty, BestRx — these systems were built before the internet. Migration friction is real, but the pain of staying is growing faster than the pain of switching.

AI Window

Cloud-native + AI creates timing advantage

AI-enabled workflow assistance (queue triage, DUR optimization, patient follow-up) is achievable now. A new entrant building on modern infrastructure can embed AI natively, not bolt it on.

NCPA Alignment

Distribution channel + mission partner

NCPA has relationships with 18,960 pharmacies, advocacy infrastructure, and trade show presence. Strategic alignment lowers CAC, accelerates trust, and supports credibility.

🧩 Platform

One platform. Four layers. One data model. One workflow engine. NURO is a cloud-native, AI-powered operating system that eliminates fragmented systems, returns data control to pharmacies, embeds clinical programs into workflow, and enables independents to operate as a coordinated network.
NURO Rx — Dispensing
E-Prescribing & EPCS
Surescripts certified
Rx Processing
All sources
Claims Billing
NCPDP D.0
POS & Payments
Integrated checkout
Workflow Queues
≤3 clicks any action
↕
NURO Bridge — Connectivity
Cloud + Edge
Offline-first resilience
Standards
NCPDP, HL7/FHIR, Surescripts
Integrations
Wholesaler EDI, PMP, IIS
↕
NURO Intelligence — Analytics
Real-time P&L
By Rx, payer, patient, contract
AI Workflow Assist
Queue triage, DUR optimization
Operational Dashboards
Staff productivity, KPIs
↕
NURO Clinical — Patient Care
Immunizations
Admin, billing, IIS
MTM & Clinical Docs
CPT coding
Patient Engagement
Follow-up, notifications
340B Lite
Program support

Core Differentiators

DifferentiatorWhat It Means
Unified WorkflowSingle workflow engine replacing 5+ fragmented systems
Data OwnershipPharmacy owns and controls data with transparent consent
Network ExecutionMany independents act as one coordinated network
Clinical EmbeddingClinical programs live in dispensing workflow, not separate tools
Offline-FirstNURO Bridge supports continuity during connectivity issues
Real-Time ProfitabilityVisibility into margins by Rx, payer, patient, contract
Standards-FirstNCPDP, HL7/FHIR, Surescripts orientation built-in
Governance-ProtectedDesigned to prevent conflicted control by PBMs, PE, or wholesalers

Early Clinical Impact Data

Note: These are referenced metrics from early clinical deployments. The business plan treats these as directional, not guaranteed outcomes at scale.
>70%
DUR Alert Reduction
97%
Clinically Actionable Alerts
+20 pts
Patient NPS Lift
18–25%
Staff Productivity Gain
241 → <50
Alerts per 250 Rx
40%+
Clinical Adoption (vs 10% baseline)

🗺 Product Roadmap

VersionThemeTimelineStatusFocus
v1 — MVP Foundation Jan–Aug 2026 In Dev Core dispensing: e-prescribing, EPCS, billing, patient mgmt, POS, workflow queues
v2 — Ops Automate Q4 2026 – Q1 2027 Planned Inventory, med sync, automated refills, patient notifications, dashboards
v3 — Clinical Revenue Q2–Q3 2027 Planned Immunizations, MTM, clinical docs, compound billing, 340B lite, enhanced DUR
v4 — Expand Segments Q4 2027 – Q1 2028 Planned LTC, specialty, workers' comp, central fill, mail order, PMP queries
v5 — Intel AI/Data Q2–Q3 2028 Planned Analytics/BI, patient portal, predictive AI, telehealth, API marketplace
AI clarification: The GTM story leads with AI-native workflows. The roadmap places full predictive AI in v5 (2028). This is reconciled by distinguishing: AI-assisted workflow at launch (queue triage, DUR optimization) vs. predictive intelligence & data products later.

v1 MVP Feature Areas

Feature AreaTargetStatusEffort (hrs)
Electronic Prescribing & EPCSQ1–Q3 2026In Dev960
Insurance Claim BillingQ2–Q3 2026In Dev960
Patient ManagementQ2–Q3 2026In Dev560
Prescription ProcessingQ2 2026In Dev480
Drug Information / FDBQ1 2026In Dev440
Plans & Pricing / CouponsQ3 2026Planned400
Prescriber ManagementQ2 2026In Dev360
Prescription ImagesQ3 2026Planned280
POS & PaymentsQ3 2026Planned~240
Regulatory Reporting / PMPQ3 2026Planned240
Eligibility VerificationQ3 2026Planned200
Platform & SecurityQ1 2026In Dev176
Shared UI ComponentsQ1 2026In Dev160

Key Dependencies

v1 Dependencies

Surescripts certification, FDB API, claims switch partner

v2 Dependencies

v1 complete, wholesaler EDI partner, SMS/IVR provider

v3 Dependencies

v2 complete, medical billing clearinghouse, IIS registry access

📅 Product Timeline

Visual timeline of NURO product releases from MVP through Intelligence platform.

Q1 '26Q2 '26Q3 '26Q4 '26 Q1 '27Q2 '27Q3 '27Q4 '27 Q1 '28Q2 '28Q3 '28
v1 — MVP
Foundation
v2 — Ops
Automate
v3 — Clinical
Revenue
v4 — Expand
Segments
v5 — Intel
AI/Data

Key Milestones

Q1 2026

Development Kickoff

Platform & security, shared UI, drug information (FDB), e-prescribing begins

Active
Q2 2026

Core Rx Processing

Prescription processing, prescriber management, insurance claims billing, patient management

In Progress
Q3 2026

MVP Complete

POS & payments, eligibility verification, PMP reporting, prescription images, plans & coupons

Target
October 2026

NCPA Trade Show — Kansas City

Target moment to showcase product publicly. Design partners should be live by this point.

Milestone
Q4 2026 – Q1 2027

v2: Operational Efficiency

Inventory management, med sync, automated refills, patient notifications, operational dashboards

Q2 – Q3 2027

v3: Clinical Services

Immunizations, MTM, clinical documentation, compound billing, 340B lite, enhanced DUR

Q4 2027 – Q1 2028

v4: Market Expansion

LTC, specialty pharmacy, workers' comp, central fill, mail order, PMP gateway

Q2 – Q3 2028

v5: Intelligence Platform

Analytics/BI, patient portal, predictive AI, telehealth, API marketplace, compliance tools

🏥 Initial Customer Profile

Target: Owner-operated independent / community pharmacies with 1–10 locations, service-heavy operations (immunizations, MTM, delivery, med sync, compounding), motivated by growth, control, leverage, and margin pressure relief.
Best Fit

The Growth-Minded Owner

1–3 locations, adding services, frustrated by legacy system limitations. Wants one platform to run everything.

  • Immunizations + MTM active
  • Delivery program in place
  • Open to technology change
Strong Fit

The Multi-Store Operator

4–10 locations, needs unified view across stores. Current systems don't talk to each other.

  • Multi-location complexity
  • Staff coordination challenges
  • Margin visibility critical
Not First Buyer

The Compliance-Only Pharmacy

Low appetite for change. Runs minimum services. Not the early adopter — may convert later through network proof.

  • Minimal services offered
  • Risk-averse
  • Later-stage conversion

Buyer Motivation

💰
Margin Pressure

3–5% margins, $45K–$75K DIR loss

🔧
Operational Leverage

$85K–$120K annual labor waste

🔒
Data Control

Own data, don't feed intermediaries

📈
Growth

Add services without adding headcount

🚀 Go-to-Market Plan

Founder-led sales first. Prove the wedge with 8–12 design partners before investing in paid GTM. Three public case studies with before/after outcomes are the exit criteria for founder-led phase.

GTM Phases

1

Foundation — 0–3 Months

Lock descriptor ("Nuro PharmacyOS"), sharpen story, build demo, recruit advisors. Modern web app as credibility, AI-native workflows as hero story.

2

Founder-Led Design Partner Sales — 3–9 Months

Weekly demos. Close 8–12 design partners. Map every objection. Document migration friction. Capture 3 public stories with before/after outcomes.

3

Repeatability + First Hires — 9–15 Months

Codify onboarding and pricing. Build competitor pages, webinars. Hire implementation lead, then GTM generalist. Prove the motion is repeatable.

4

Selective Paid Scale — 15–24 Months

Competitor search, retargeting, trade media, referral programs. Only after 8–12 design partners, 3 public proofs, 1 repeatable demo + migration story, and 2 targeted paid channels validated.

Exit Criteria Before Paid GTM

Must Have

  • ✓ 8–12 signed design partners
  • ✓ 3 public case studies with before/after outcomes
  • ✓ 1 repeatable demo + migration story
  • ✓ Documented objection map

Then Unlock

  • → 2 targeted paid channels (max to start)
  • → Competitor search ads
  • → Retargeting campaigns
  • → Trade media + referral programs

NCPA Channel Strategy

Distribution Advantage

NCPA as trust accelerator, not just a channel

NCPA has relationships with 18,960 member pharmacies. Membership can be embedded in NURO contracts (structural alignment). NCPA gains data for advocacy while NURO gains distribution efficiency far beyond pure vendor selling. The October 2026 trade show in Kansas City is the target showcase moment.

💲 Pricing Strategy

Pricing is a market-learning process. The current model is a disciplined starting point, not a fixed conclusion. Willingness-to-pay must be validated through real buyer reaction with design partners.
Founder Member

First 100 Customers

$600–800/mo
$7,200–$9,600 ARR • 20% discount vs. standard
  • Full NURO Rx platform
  • AI workflow assistance
  • NURO Bridge connectivity
  • Operational dashboards
  • Priority onboarding
  • Locked-in founder rate
Standard

Post-Founder Pricing

$720–960/mo
20% increase after first 100 customers
  • Full NURO Rx platform
  • AI workflow assistance
  • NURO Bridge connectivity
  • Operational dashboards
  • Standard onboarding
  • NCPA membership benefit option
Multi-Store

Volume Operators

Custom
Volume discounts for 4+ locations
  • Everything in Standard
  • Multi-location dashboard
  • Centralized management
  • Dedicated support
  • Custom onboarding plan
  • Discount ladder: 20%, 15%, 10%

Pricing Signal from Market

Prior experiment: Willingness to pay was higher than expected. Some buyers preferred $25,000 upfront over $7,000 upfront + monthly. Higher upfront payment was more preferred by some customers. This suggests the market may tolerate higher pricing than the conservative starting point.

ARR Reconciliation

Gap to resolve: The CIM's old model assumed ~$15,000 ARR per pharmacy. The new pricing of $600–$800/month implies $7,200–$9,600 ARR before add-ons. The gap can be closed through:

Implementation Fees

Upfront onboarding & migration charges

Premium Modules

Clinical workflow, advanced analytics add-ons

Founder Step-Up

20% increase after first 100 customers

Multi-Location Pricing

Higher per-account revenue from operators

Claims / Transaction Fees

Usage-based revenue at scale

Clinical Add-Ons

Immunization billing, MTM documentation

External Reference

Key Centrics (Competitor)

Reported pricing of $1,000–$5,000/month with add-ons. NURO's $600–$800 entry point is well below competitor ceiling, with room to grow.

📊 Profitability Framework

Profitability is milestone-based, not calendar-based. Adoption density matters more than calendar timing. The plan does not promise "year 3 profitability" — it ties economics to verifiable adoption milestones.
~$130K
Current Monthly Burn
80%
Target Gross Margin
45%
Target EBITDA Margin
<5%
Churn Benchmark

Milestone-Based Profitability

8
Design Partners
Product wedge + migration story
50
Early Scale
Onboarding economics visible
100
Repeatability
Support load + basic unit economics
250
Data Threshold
Evaluate data infrastructure
500
Network Effects
Repeatable implementation
1K+
SaaS Profitability
Credible expansion economics

Financial Model Assumptions

AssumptionValueNotes
Current monthly burn~$130K/monthPre-revenue
ARR per pharmacy (base)$7,200–$9,600Founder pricing, before add-ons
ARR per pharmacy (blended target)~$15,000With implementation + modules
Gross margin target80%SaaS benchmark
EBITDA margin target45%At management-model scale
Customer churn target<5%Annual
Payback period36–48 monthsAt scale
Year 2 store target~100 storesPlanning assumption
Deployment capacity~1,100/yearAt full operating model
Cash runway note: Meaningful revenue is unlikely before burning through ~$3M. At $130K/month, that is roughly 23 months. This needs to be reconciled with hiring, founder-led GTM timing, and adoption trajectory.

Profitability Drivers

Active Pharmacy Count

Primary revenue driver

Subscription Pricing

Base + add-on modules

Implementation Efficiency

Onboarding cost per store

Customer Retention

<5% annual churn target

Sales Cycle Length

Demo to signed to live

NCPA Channel Efficiency

CAC reduction via trust

💾 Data Monetization

Future option value only. Data monetization is a second business line. NURO should not build the infrastructure until the pharmacy base and claims volume justify it. Not a near-term revenue source.

Trigger-Based Investment Model

StageTriggerAction
Today – 100 storesProduct / workflow validationUse data internally for product improvement only
~100 storesEarly scale signalBegin data architecture planning only
~250 stores / 10M claimsScale thresholdEvaluate dedicated data infrastructure investment
Post-thresholdValidated demand + governance clarityHire data infrastructure / data science resources
Later stageStrong scale + compliant data productsExplore commercial data products

Required Infrastructure (When Triggered)

Data Warehouse

Ingestion, normalization, cleaning

Governance & Consent

Transparent opt-in, compliance controls

Analytics Products

De-identified benchmarking, market intel

Data Science Team

Dedicated commercial leadership

Extraction & Scraping

Claims data pipeline at scale

FHIR Infrastructure

Standards-based interoperability

👥 Leadership Team

👨‍💼

Alex Graber

CEO
👨‍💼

Noah Chapman

COO
👨‍💻

Taylor Miller

CTO
👨‍💼

Travis Kliewer

CFO

📋 Hiring Plan

Hiring philosophy: Implementation capacity should lag adoption slightly, not lead too aggressively. Founder-led sales first. Engineering focused on MVP refinement. Add one-quarter timing buffer to avoid overhiring early.

Milestone-Triggered Hiring

MilestoneHiring TriggerRole(s)
8–12 design partners Proven wedge + active accounts Implementation Lead
Repeatable onboarding Codified process, clear capacity need Customer Success / Onboarding
Proven demo + objection map Repeatable sales motion exists GTM Generalist / Seller
100 stores Support load + process maturity Support Ops + Implementation
250 stores / 10M claims Data infrastructure justified Data Infrastructure Planning
Post-data threshold Validated data demand Data Engineer / Analytics / Data Science

Earlier CIM Hiring Plan (Reference)

Note: This earlier plan from the CIM may be adjusted based on milestone-triggered hiring approach above.
RoleTimingPriority
Senior Backend Engineers x2Q1 2026Critical
Frontend EngineerQ1 2026Critical
QA EngineerQ2 2026High
DevOps / InfrastructureQ2 2026High
Customer Success ManagerQ3 2026High
Enterprise Sales RepQ3 2026Medium
Clinical Program ManagerQ4 2026Medium

📅 Hiring Timeline

Hiring aligned to adoption milestones, not calendar dates. Each role unlocks at a specific proof point.

Q1 '26Q2 '26Q3 '26Q4 '26 Q1 '27Q2 '27Q3 '27Q4 '27 Q1 '28Q2 '28Q3 '28
Backend Eng x2
Q1
Frontend Eng
Q1
QA Engineer
Q2
DevOps / Infra
Q2
Implementation Lead
After 8-12 partners
Customer Success
Repeatable onboarding
GTM Generalist
Proven demo
Clinical Prog Mgr
v3 clinical
Support Ops
100 stores
Data Engineer
250 stores / 10M claims

Hiring Philosophy

Do First

  • ✓ Founder-led sales — learn before hiring sellers
  • ✓ Engineering focused on MVP refinement
  • ✓ Marketing builds waitlist & educates market
  • ✓ Implementation lead after proof, not before

Avoid

  • ✗ Hiring GTM aggressively before product-market proof
  • ✗ Data science hiring before scale justifies it
  • ✗ Overhiring without one-quarter timing buffer
  • ✗ Leading with implementation capacity before demand

🏛 Operating Cadence & Governance

Structured oversight without operational paralysis. The board pre-approves major spending categories and draw capacity, then allows management to execute within those boundaries.

Financial Controls

ControlDetail
Monthly financial reportingDue by 17th of each month
Quarterly risk reviewsFormal board-level review
Budget vs. forecastMonthly discipline maintained
Major spending bucketsBoard pre-approval of categories and draw capacity
Cash bufferMaintain minimum cash reserve
Approval processPredictable, not ad hoc

Board vs. Management Authority

Board Controls

  • Annual budget / major budget buckets
  • Cash buffer requirement
  • Quarterly risk review
  • Major pivots
  • Draw capacity / spending thresholds
  • Data monetization approval

Management Controls

  • Day-to-day execution
  • Hiring within approved plan
  • Customer onboarding decisions
  • Product sequencing inside approved roadmap
  • Vendor selection inside budget
  • Workflow / product iteration

Capital Deployment Model

52%
Implementation Pods
15%
Platform & Infra
15%
Working Capital
12%
Sales & Marketing
6%
Compliance

❓ Board Questions & Discussion Points

Central tension: The board wants to keep pricing low and attractive while also showing a credible path to profitability. This is the primary business-plan issue to resolve.

Top 10 Board Questions

  1. 1. Does profitability happen in year 3 or year 5?
  2. 2. What drives profitability? (Active stores, pricing, retention, implementation efficiency)
  3. 3. Which assumptions matter most? What kills the model if wrong?
  4. 4. What adoption milestones unlock better economics?
  5. 5. How much pricing flexibility is needed? What happens if $600–$800 is too low?
  6. 6. When does NURO know pricing is too low? What are the trigger signals?
  7. 7. When should hiring accelerate? What milestones justify it?
  8. 8. When should data monetization become a real investment? What scale justifies it?
  9. 9. How can the board oversee cash without blocking execution speed?
  10. 10. What is the minimum proof package before scaling paid GTM?

Known Weak Spots to Resolve

Pricing vs. Profitability

Tension between keeping pricing attractive and showing a credible profitability path. Fix: Present pricing as a tested range with milestone-based review gates.

ARR Mismatch

$600–$800/month doesn't match the older $15K ARR assumption. Fix: Build a pricing waterfall showing base + implementation + modules + step-ups.

AI Story vs. Roadmap

GTM leads with AI-native while full AI is v5 (2028). Fix: Clearly separate AI-assisted workflow at launch from predictive intelligence later.

Data Monetization Risk

Older CIM includes data licensing as revenue. Fix: Remove from near-term forecasts. Treat as triggered future option only.

Revenue Timing

May burn through ~$3M before meaningful revenue. Fix: Show cash runway model with adoption triggers, not broad revenue forecast.

Design Partner Definition

No clear definition of success. Fix: Define precisely: signed? live? active workflow? paid? referenceable case study?

🧭 Key Assumptions & Open Questions

Key Assumptions

CategoryAssumption
BuyerOwner-operated pharmacies will buy for leverage, control, and growth
PricingWillingness-to-pay must be tested in-market; current model is starting point
AdoptionFirst 8–12 design partners will reveal the actual product wedge
ProductMVP must prioritize certifiable core workflow before broad feature expansion
GTMFounder-led sales is required before meaningful paid marketing
NCPANCPA can lower CAC, accelerate trust, and support credibility
ProfitabilityAdoption density matters more than calendar timing
DataData monetization requires scale; not a near-term revenue source
HiringImplementation capacity should lag adoption slightly, not lead aggressively
GovernancePre-approved spending bands reduce friction between board and management

Open Questions

  • PricingIs $600–$800/month too low relative to ROI and legacy pricing comps?
  • ARR ModelDoes the plan assume $7.2K–$9.6K ARR, $15K ARR, or a blended model with add-ons?
  • PricingShould NURO charge an implementation / onboarding fee?
  • PricingHow long do early founder discounts last?
  • NCPAIs the first-year membership benefit funded by NURO, NCPA, or baked into pricing?
  • AdoptionWhat is the realistic store count by end of year 1 and year 2?
  • SalesHow long does it take to move from demo to signed to live?
  • MigrationWhich PMS systems create the most friction: Pioneer, Rx30, Computer-Rx, QS/1, Liberty, BestRx?
  • SupportHow many stores can one implementation / customer success person handle?
  • MarginIs 80% gross margin realistic before scale?
  • BurnHow long does $3M cover at $130K/month plus hiring?
  • DataWhat is the compliance/governance process for future de-identified data products?
  • AIWhat AI functionality exists at launch vs. later roadmap?
NURO Business Plan • Confidential • April 2026