Investment Thesis
Building the product infrastructure
for specialty healthcare.
iPothecary connects product data, inventory, retail, safety, and traceability across eye-care practices — creating the foundation for a connected product lifecycle from manufacturer to patient.
Connected infrastructure
Lifecycle visibility
The Problem
Specialty practices manage products with fragmented infrastructure.
Specialty practices increasingly recommend and sell products directly to patients — but the operational infrastructure surrounding those products is poorly connected. A practice may use one system for purchasing, another for checkout, spreadsheets for inventory, email for recalls, and vendor portals for product information.
That fragmentation is fundamentally a data and infrastructure problem — not simply a workflow inconvenience.
pieces of the story.
No single source of truth across locations
Overstock, expiration, and write-off exposure
Manual recall matching without traceability
No structured transaction-to-product data
Different products, prices, and policies by site
No link between recommendation and purchase
The Platform
One lifecycle instead of disconnected transactions.
iPothecary is not replacing a POS. It is connecting the entities that surround a transaction — from source to safety.
Current Platform
What exists today.
The current foundation centers on connected product, inventory, safety, and practice operations. Expansion items are separated clearly below.
Product Catalog
- Structured product catalog
- Manufacturer and vendor records
- Product documentation
- Identifiers and package information
Inventory Operations
- Multi-location inventory
- Receiving and stock movement
- Lot and batch tracking
- Expiration monitoring
- Cycle counts and discrepancy resolution
Safety & Recall
- Recall and safety information
- Product-to-lot matching
- Affected inventory identification
- Hold and response workflows
- Safety document management
Retail & Commerce
- Practice-selected products
- In-office kiosk retail
- Staff-assisted checkout
- Transaction history
- Location-aware retail activity
Practice Operations
- Multi-location organization support
- Roles and permissions
- Operational reporting
- Device and label management
- Practice administration
- Audit history
Expansion Path
Start with operations. Expand across the lifecycle.
Product Operations
- Structured product catalog
- Multi-location inventory
- Vendor management
- In-office retail
- Safety and recall workflows
Product Intelligence
- Deeper manufacturer integrations
- Product documentation
- Advanced ordering workflows
- Vendor relationship management
- Product availability intelligence
Patient Continuity
- Practice-branded online purchasing
- Repeat ordering
- Home delivery
- Autoship / replenishment
- Patient purchase history
Network Infrastructure
- Manufacturer connectivity
- Distribution partnerships
- Product launch infrastructure
- Practice-vendor network effects
- Product performance intelligence
Vertical Selection
Why eye care.
Start where clinical recommendation and product purchasing already overlap naturally. Eye care is characterized by chronic conditions, high rates of physician-recommended product usage, and multi-location specialty practice organizations — all within an existing vendor and manufacturer ecosystem that currently lacks connected infrastructure.
- Chronic conditions driving repeat product demand
- Physician-recommended OTC and specialty categories
- Significant multi-location practice organizations
- Fragmented retail and inventory operations
- High patient trust and clinical recommendation authority
- Active vendor and manufacturer relationships
Eye care is the initial wedge — not necessarily the ceiling.
Market Timing
Why now.
Larger multi-location organizations require centralized systems with local execution capability.
Patients increasingly expect convenient access to products recommended by their providers.
Practices manage more manufacturers, vendors, lots, documentation, and safety events than ever before.
Ancillary revenue and operational efficiency are increasingly important to practice economics.
APIs, payment platforms, and healthcare interoperability make connectivity increasingly possible.
Strategic Infrastructure
The transaction is only one moment in the product lifecycle.
Recall and traceability create a reason for the underlying data model to exist independently of commerce. A manufacturer issues a recall. Without lifecycle connectivity, a practice must manually determine: whether they carry the product, which locations have it, which lots are present, what has been sold, and which patient transactions may need review.
With iPothecary, product, lot, location, inventory, transaction, and customer relationships can exist within one operational system. Safety creates the infrastructure reason — retail is one monetization layer on top of it.
- Which locations carry it?
- Which lots are on-hand?
- What has already sold?
- Which patient transactions need review?
- Is affected stock removed?
Answered manually, inconsistently, or not at all.
- Product → location relationship exists
- Lot → inventory link is recorded
- Transactions are connected to lots
- Relevant transactions can be reviewed
- Quarantine can be triggered systematically
Answered from the operational record.
Business Model
How iPothecary can make money.
Revenue streams reflect the natural progression of platform depth.
SaaS Platform
Practice subscriptions based on organization size, locations, and capability tier. The primary recurring revenue mechanism.
Transaction Revenue
A platform fee associated with eligible retail transactions processed through iPothecary-connected payment workflows.
Manufacturer & Vendor
Commercial relationships involving product onboarding, practice access, integrations, and data products where legally appropriate.
Fulfillment & Recurring Commerce
Revenue associated with direct-to-patient transactions, repeat ordering, autoship, and fulfillment partnerships as the platform expands.
Implementation & Services
Onboarding, hardware, integration, and professional services revenue associated with practice deployment and setup.
Competitive Position
Defensibility emerges from the connected data model.
The software is not the moat. The depth of the connected record is.
Product graph
Relationships between product, manufacturer, vendor, package, lot, location, inventory, transaction, and safety event — held together in one operational record.
Workflow depth
iPothecary becomes embedded in receiving, inventory, retail, recall, and daily operations — not serving as a dashboard over existing workflows.
Historical lifecycle data
Operational history accumulates value over time. A practice that has managed three years of inventory, recalls, and transactions has something that cannot easily be transferred.
Multi-location standardization
Once organizations build standardized product operations around a platform, switching costs increase significantly — particularly for organizations with centralized purchasing.
Network potential
As practices, manufacturers, vendors, and product data become more connected, each side benefits from participation by the others. iPothecary can develop a two-sided ecosystem.
Safety and compliance requirement
Traceability and recall workflows are not optional features — they are operational requirements. Infrastructure that addresses them becomes structurally necessary.
Economic Engine
The business compounds with each connected entity.
Create demand and transaction activity
Expand the operational footprint
Deepen the product graph
Increase lifecycle data density
Increase manufacturer and vendor value
Deepen product integrations and partnerships
Attract more practices
Traction
Early validation in a real clinical environment.
Development is grounded in live specialty practice operations — real staff workflows, multi-location inventory, vendor relationships, and safety requirements — rather than hypothetical design.
Detailed metrics including active locations, products managed, GMV, ARR, and pipeline are available to qualified investors in a controlled conversation.
Market Opportunity
A bottom-up framework.
Rather than citing a top-down market figure, the relevant question is how many specialty practices can benefit from connected product lifecycle infrastructure, and what that is worth per organization.
Expansion Path
Eye care as a wedge.
Eye care is an attractive initial vertical — but it is a wedge, not necessarily a ceiling. The product lifecycle problem exists across specialty medicine wherever clinical recommendation and product purchasing naturally overlap.
Expansion into additional specialties is not an immediate commitment. Eye care provides the operational foundation first.
Team
Built from inside the workflow.
iPothecary is being built by people with direct experience inside multi-location specialty eye-care organizations — not by an engineering team that studied the industry from the outside.
"Built from inside the workflow rather than from outside healthcare looking in."
Detailed team biographies are available in the investor conversation.
Long-Term Vision
The infrastructure connecting products,
practices, and patients.
The company does not need to own every part of the supply chain. The opportunity is to become the software layer connecting it.
Investor Relations
Interested in the future of product infrastructure
in specialty healthcare?
We're interested in speaking with investors and strategic partners who understand healthcare operations, vertical software, commerce infrastructure, or specialty medicine.
Detailed information — financial statements, cap table, forecasts, customer contracts, and pipeline — is available in a controlled investor conversation, not on this page.
Contact
Start a controlled investor conversation.
Use the contact form and select investor relations so your request reaches the right conversation.
Go to the contact form