Feature	V1 (Fabbi builds)	Future
Auth & Multi-tenant	Passkeys, WebAuthn, biometric, JWT RS256	SSO/OAuth2 (V1.5)
KYC & QES	Manual KYC + D-Trust registration & signing	AI KYC (V1.5), SwissSign (V1.5)
Presence Check	Geofence GPS + rotating QR + liveness selfie	—
Patients & Appointments	Search, create, consent, booking, calendar	Full history (V1.5)
Prescriptions	ICD-10, product select, dosage, QES-sign	Templates (V1.5)
Pharmacy Routing	Cannaleo + HiGreen auto-routing	Fallback rules (V1.5)
Cannametrics	Collect + store: catalog, prices, availability, outcomes	Analytics UI (V3)
Doctor & Admin Portals	Web (React, responsive) + Mobile (React Native, iOS+Android)	—
Audit Trail	Hash-chained, tamper-evident, 10-year retention	Regulatory export (V1.5)
Notifications	Push (iOS/Android) + Web Push + Email	SMS (V1.5)

PhytoMedic Platform — Fabbi Software

V1 Scope — Explicitly Out (Revised Roadmap)

What's out	Phase	How it extends V1
Patient Portal	V1.5	New patient role + new UI on existing V1 APIs
Pharmacy Portal + Public Finder Lite	V2	Pharmacy org type + basic doctor/pharmacy finder + product catalog
Cannametrics Dashboards	V3	Analytics on V1 foundation data — no migration
Manufacturer Portal	V4	Manufacturer org type on same model
Full Public Growth Layer	V5	SEO engine, content platform, community
E-Rezept / Gematik TI	V2+	FHIR-ready architecture prepared in V1

Roadmap update: Per Alexander's suggestion, a lightweight Public Finder (doctor/pharmacy finder, product catalog) is now bundled with V2 Pharmacy Portal. V5 retains the full SEO/content engine.

Key principle: Adding a future phase = adding a role + a portal. No schema migration. No breaking changes.

Extensibility Axis	V1 Design	Impact on Future
Multi-tenant org_id	Every entity carries `org_id` from day 1	New portal = new role + new UI. No schema change.
RBAC role model	DOCTOR, ADMIN, COMPLIANCE, SUPER_ADMIN	Adding PATIENT, PHARMACIST = role additions only
API-first design	All features exposed as REST APIs	Patient Portal (V1.5) = new frontend on existing APIs
Modular Monolith	Domain modules, not microservices	Extractable to microservices if scale demands
Cannametrics tables	V1 writes structured data from day 1	V3 = read-only analytics on existing tables
i18n scaffolded	EN/DE from V1	Multi-language = content additions only

#	Item	Owner	Deadline
1	D-Trust sandbox credentials	Cannabis Ärzte (Alexander)	Before kickoff
2	Cannaleo API documentation + sandbox	Cannabis Ärzte / Cannaleo	Week 1
3	HiGreen API documentation + sandbox	Cannabis Ärzte / HiGreen	Week 1
4	AWS account (Frankfurt region) setup	Fabbi (with client access)	Sprint 0
5	Contract signing + kickoff payment (5%)	Cannabis Ärzte	Before kickoff

Component	Technology	Platform
Mobile App	React Native (native)	iOS + Android — biometric, geofence, camera, push
Doctor Web Console	React (responsive)	Desktop + iPad browsers
Admin Portal	React (responsive)	Desktop browsers
Patient Booking	React (responsive)	All browsers (unauthenticated)

Version	Scope	Man-Months	Budget Range
V1	Clinical Core + Cannametrics Foundation	13.86	$28,902 (fixed)
V1.5	Patient Portal + Treatment Continuity	4–6	$8,000–$13,000
V2	Pharmacy Portal + Public Finder Lite	8–12	$17,000–$25,000
V3	Cannametrics Intelligence Layer	5–8	$10,000–$17,000
V4	Manufacturer Portal	3–5	$6,000–$10,000
V5	Full Public Growth Layer	5–8	$10,000–$17,000
Total	Full PhytoMedic Platform	39–54	$80,000–$111,000

V1 Foundation	Future Versions Benefiting	Effort Saved
Multi-tenant architecture (org_id from day 1)	V1.5, V2, V3, V4	15–20% per version
RBAC role model	V1.5, V2, V4	~10% per version
Cannaleo / HiGreen integrations	V2, V3	~30% of pharmacy scope
Product normalization (PROD-001→004)	V2, V3, V4	~20% of product scope
Pharmacy routing logic	V2	~25% of routing scope
Audit & compliance foundation	All versions	10–15% per version
Cannametrics data foundation	V3	~40% of analytics scope
API-first architecture	V1.5	~60% is API reuse

PhytoMedic Platform

Technical & Commercial Proposal

We answer your 5 questions.

Q1 + Q5

Platform Vision & Scope Map

PhytoMedic — 5-Layer Platform Architecture

Platform Scope Map — V1 Highlighted

Q2

V1 Scope — In / Out / Future

V1 Scope — What Fabbi Builds

V1 Scope — Explicitly Out (Revised Roadmap)

Q3 + Q4

Architecture Extensibility & Data Foundation

Architecture Extensibility — V1 Does Not Block V1.5 → V5

Cannametrics — Why Data Collection Starts in V1

Cannametrics Data Collection Pipeline

V1 does not block any future phase.

What Fabbi Commits to Build in V1

Fabbi builds

Explicitly out of V1

Pre-Kickoff Requirements (Client)

V1 Delivery — App Scope Clarification

Roadmap & Budget Outlook

V1 through V5

Platform Roadmap — Budget Estimates (ROM)

V1 Foundation — Reuse Across Future Versions

Scope Confidence — Fixed vs. Assumption vs. Discovery

Investment & Delivery

Investment Summary

Timeline & Team — V1 (15 weeks)

Next Steps

Cannabis Ärzte

Fabbi

Let's build PhytoMedic.

Category	Scope Items	Confidence
Fixed scope — clear client requirements	Auth, KYC, QES, Prescriptions, Routing, Audit, Booking, Infrastructure	High
Assumption-based — Fabbi proposed, details may evolve	Cannametrics schema, Notification channels, Admin dashboards, Presence check, Web app	Medium
Discovery-dependent — known unknowns, resolved during dev	D-Trust API behavior, Cannaleo/HiGreen rate limits, BtMVV validation rules, Drug DB source, GDPR Art.9 specifics	Variable


Scope	95 SOW items (across 49 V1 feature modules)
Effort	~2,217 hours (13.86 man-months)
Timeline	15 weeks (13 dev + 2 UAT)
Team	1 PM · 1 BA · 2 FE · 3 BE · 1 QA (senior-level)
Subtotal	$32,113
Discount (10%)	−$3,211
Total	$28,902