On the Idea Wall · ▲ 0 votes
BayStock — the spec
BayStock is a healthcare surplus marketplace where Bayshore Healthcare posts excess medical inventory and sells it to Long Term Care Facilities, Hospice Care providers, Doctor Clinics, and individual patients. It operates as a dual-channel platform: a B2B procurement layer with bulk pricing and logistics, and a B2C retail storefront for individual buyers — both drawing from the same live supplier inventory.
---
Decisions locked
| Question | Answer |
|---|---|
| Shape | Marketplace |
| Audience | B2B (facilities, clinics, hospice) and B2C (individual patients) |
| Core loop | Supplier posts excess stock, sets price tiers, receives bulk orders from facilities on a weekly cadence |
| Success metric at 30 days | 10+ weekly active users and 10 paying customers, fully automated |
---
The core loop
- Bayshore posts an excess stock item — quantity, unit price, bulk tier pricing, and delivery window.
- A facility buyer browses, compares prices across active suppliers, selects quantities that trigger their applicable bulk tier, and places an order.
- An individual patient lands on the retail storefront, sees retail-priced listings drawn from the same inventory pool, and checks out as a consumer.
- Payment is captured; the logistics module assigns a delivery method and begins tracking the shipment.
- Buyer receives SMS or email status updates through to confirmed delivery.
- The supplier's analytics dashboard updates: units sold, remaining stock, revenue, and demand trend signals.
---
v1 scope
Bulk Pricing Tiers for Facilities and Clinics
Suppliers define quantity brackets (e.g., 1–9 units / 10–49 / 50+) with corresponding unit prices at listing time. The order screen auto-applies the correct tier as a buyer adjusts quantity.
Integrated Logistics and Delivery Tracking
At order confirmation, the platform calls an external logistics API to generate a shipment, assigns a tracking number, and surfaces live status to both buyer and supplier on their respective dashboards.
Price Comparison Across Active Suppliers
A comparison view on the browse and product-detail screens shows the same item or category listed by multiple suppliers side-by-side — price, quantity available, and estimated delivery date.
Analytics Dashboard: Sell-Through Rates and Demand Trends
A supplier-side dashboard displays units listed vs. units sold per SKU, revenue over selectable time ranges, and which buyer segments (facility type, region) are driving volume — feeding restocking decisions.
Individual Patient Storefront with Retail Pricing
A separate, consumer-facing storefront pulls from the same inventory with retail pricing rules applied. It presents a simplified checkout without bulk-tier logic, appropriate for single-unit purchases.
---
Deliberately later
- Real-time inventory posting with expiration tracking — expiration-date logic adds regulatory and UI complexity; establish the baseline listing flow first, then layer compliance controls once supplier onboarding patterns are understood.
- One-click reorder templates for facilities — requires sufficient order history to be useful; build after buyers have completed at least a few cycles.
- Supplier verification and compliance documentation — critical long-term, but initial operation with Bayshore as the known anchor supplier makes full multi-supplier credentialing a v2 governance project.
---
Data model sketch
users— id, role (supplier / facility\_buyer / patient / admin), org\_id, contact, auth credentialsorganizations— id, type (LTC / hospice / clinic / individual), billing address, verified flaglistings— id, supplier\_id, product\_name, sku, quantity\_available, expiration\_date, bulk\_tier\_json, retail\_price, statusorders— id, buyer\_id, listing\_id, quantity, tier\_applied, unit\_price, total, payment\_status, created\_atshipments— id, order\_id, logistics\_provider, tracking\_number, status, estimated\_delivery, last\_updatedpayments— id, order\_id, amount, processor\_reference, status, paid\_atanalytics\_events— id, listing\_id, event\_type (view / add\_to\_cart / purchase), buyer\_segment, timestampnotifications— id, user\_id, channel (email / SMS), template, payload, sent\_at
---
Screens
- Supplier Dashboard — post listings, view sell-through analytics, manage active stock
- Browse / Search — facility buyers filter by product category, supplier, and price tier
- Price Comparison View — side-by-side supplier offers for a given product
- Product Detail + Order Form — listing detail with dynamic bulk-tier pricing and quantity selector
- Patient Storefront — consumer-facing catalog with retail pricing and single-unit checkout
- Order Tracking — buyer view of shipment status from dispatch to delivery
- Admin Panel — user management, order oversight, logistics configuration
---
How to use this document
- Bring it into Mind Palace, where the guided platform and its AI coach pick up from exactly this document and build the working product with you step by step.
- Hand it to a developer as the complete v1 brief — every scope decision, data relationship, and screen is already resolved.
- Keep it as the single source of truth during build to prevent scope drift and evaluate every new feature request against what is listed here.
This is Shelley's. Build yours.
A spec like this is step 3 of Mind Palace's nine — the other six take a weekend: working software, a real offer, first customers.
Want to build this with Shelley?
Tell us who you are and we'll broker the introduction — their contact details stay private until they say yes.