3. Feature-by-Feature Scrutiny (The Stated Features)
Date: 30 Sept 2026 · Back to WHAT-TO-DO-AND-AVOID.md
The idea named five feature areas: inventory and availability, bookings, delivery and pickup, damage and maintenance records, and compliance tracking. Each is classified below for the chosen sub-vertical (small DME/HME suppliers).
Categories:
- Table stakes (TS): customers expect it. It earns nothing, but its absence costs you.
- Differentiator (D): a real reason to choose you over the alternatives.
- Distraction (X): built, but unlikely to move revenue or retention.
- Liability (L): creates support, compliance, legal or trust risk.
3.1 Classification table
| # | Stated feature | Category | Reasoning |
|---|---|---|---|
| 1 | Inventory and availability | TS, and D only at serial level | Counting "12 beds in stock" is table stakes, and every suite does it. What surveyors check is per-serial history: which unit went to which patient, when it was cleaned, and by whom. Build that. |
| 2 | Bookings (customer-facing reservations, calendars) | X | DME rentals start from a physician order that arrives through intake and billing, not from a booking page. Import the order reference. Don't build a storefront. |
| 3 | Delivery and pickup | TS / D | Bonafide, NikoHealth, Serious ERP and WellSky all have driver apps. Yours differentiates only if it's faster for drivers, works offline, and writes clean/dirty status and setup-education sign-off straight into the unit's history. |
| 4 | Damage records | TS | Damage photos at pickup are expected. Deposits and damage charges are rare in Medicare rentals. Keep it a photo and a note. |
| 5 | Maintenance records (preventive maintenance, repairs) | D | The DMEPOS quality standards require documented failures, repairs and preventive maintenance. Schedules by manufacturer interval, due lists, and repair history per serial are the core. |
| 6 | Compliance tracking | D as evidence, L as a promise | A one-click export of cleaning, PM, recall and delivery records for a surveyor is the product's reason to exist. Calling it "compliance" or implying a pass is a liability. Call it "survey evidence". |
| 7 | Rental billing and capped-rental logic (implied by "rental management") | L | Medicare rental billing lives in the billing suite. NikoHealth already flags caps at months 10 and 13. Show an informational rental-month counter only. |
| 8 | Being a full rental-management system (implied positioning) | L | It puts you head-on against suites that own billing. Position as "the equipment log that sits beside your billing system". |
3.2 Scoreboard
| Category | Count | Features |
|---|---|---|
| Table stakes | 3 | Inventory counts, delivery and pickup basics, damage photos |
| Differentiator | 3 | Per-serial state history, preventive maintenance and repair log, survey evidence export |
| Distraction | 1 | Customer bookings and storefront |
| Liability | 2 | Rental billing and capped-rental logic, full-system positioning (plus "compliance" wording) |
About a third of the stated scope is a reason to buy. The rest is either already in the supplier's billing suite or a trap.
3.3 "Building to avoid selling": explicit call-outs
- A general rental engine with sub-vertical templates. It feels like leverage ("serve party, bike and DME with one codebase"), but Booqable and EZRentOut have done it for a decade.
- Billing "because the log is right there." It's the fastest way to spend a year and still lose to Brightree.
- Route optimisation and live truck tracking. It demos well, but suppliers with 1–3 drivers don't need it, and WellSky already sells it.
- An online booking storefront. Wrong buyer flow for Medicare rentals.
3.4 What a disciplined v1 looks like
- Keep: serial register with CSV import, the clean → out → dirty → cleaned → PM → repair → quarantine state machine, a driver app (scan, photo, signature, offline), PM schedules, and the survey evidence export (PDF plus CSV).
- Defer: recall matching (month 4–6), consultant multi-client view, integrations with billing exports.
- Cut: bookings and storefront, billing, deposits, dynamic pricing, route optimisation, sub-vertical templates.