Technical & Commercial Proposal
PhytoMedic
Platform
Medical Cannabis Software Ecosystem
90 SOW Items · V1
13.86 Man-Months
~3 Months Delivery
$28,902 Fixed Price
Proposal v7 · April 2026 · Confidential

We answer your 5 questions.

This proposal directly addresses every point raised in Alexander's feedback — plus roadmap updates.
1

Platform Vision & Scope Map

What is PhytoMedic? What does V1 actually cover?

2

V1 Scope — Final SOW (90 items)

Line-by-line: in, out, future phase. One master count.

3

Architecture Extensibility

V1 does not block V1.5→V5. How reuse lowers future cost.

4

Cannametrics Data Model

Why data collection must start in V1. Pipeline explained.

5

Updated Roadmap (V1→V5)

Pharmacy + Public Finder in V2. ROM estimates. Timelines.

+

Scope Confidence & Investment

Fixed vs assumption vs discovery. $28,902 final V1 price.

All 8 points from Alexander's feedback are addressed in this proposal. Scope, pricing, ROM, reuse map, fixed vs assumption, app scope, roadmap suggestions, and app platform clarification.
Q1 + Q5
Platform Vision
& Scope Map
Both questions address the same thing: what is PhytoMedic and how big is it?

PhytoMedic — 5-Layer Platform Architecture

One integrated platform. Role-based portals, not disconnected products.
PhytoMedic Platform — 5-Layer Architecture 🌿
V1 Scope: Layers 0–1 + Doctor Portal + Admin Portal (highlighted in green)
≡ LAYER 0 — Shared Services ≡ V1 SCOPE
Multi-tenant Auth
Passkeys/WebAuthn + Biometric
JWT RS256 (15min)
+ Refresh rotation (7d)
RBAC: org_id-scoped
permissions
Append-only Audit Log
hash-chained, 10yr
Encrypted Doc Storage
AES-256
Notification Service
APNS + FCM + Email
≡ LAYER 1 — Clinical & Operational Core ≡ V1 SCOPE
Doctor KYC + QES D-Trust
SwissSign fallback
Presence Check
geofence + QR + liveness selfie
Patient Management + Consent
register, profile, consent
Prescription Lifecycle
+ BtMG Compliance
Pharmacy Routing:
Cannaleo + HiGreen APIs
Booking & Appointments
booking flow, calendar, reschedule, no-show
Cannametrics Data Foundation
7 tables + sync
≡ LAYER 2 — Stakeholder Portals ≡
V1: Doctor Portal
iOS + Android + Web
React Native + React
V1: Admin / Compliance Portal
Web Console
user mgmt, compliance dashboard, audit viewer
V1.5: Patient Portal
new role + existing V1 APIs
therapy history, prescriptions, retention
V2: Pharmacy Portal
pharmacy org type + inventory
+ public doctor/pharmacy finder
≡ LAYER 3 — Cannametrics Intelligence ≡ DASHED
V3: Analytics Engine
reads V1 tables — zero migration
Price Trend Analysis
historical data from V1
Supply Analytics
+ Pharmacy Reliability
Routing Performance
+ Partner Scoring
Demand by Product
/ Strain Popularity
≡ LAYER 4 — Manufacturer Portal ≡ DASHED
V4: Manufacturer org type on same data model
Product Registration + Batch Management
License Verification Portal
≡ LAYER 5 — Public Growth Layer ≡ DASHED
V5: Marketing Site + Public-facing Content
Separate deployment — no direct DB coupling
SEO-optimized (static/CDN)
org_id on every entity → role + UI additions only  •  API-first design → existing V1 APIs  •  RBAC → permission additions only

Platform Scope Map — V1 Highlighted

V1 builds the regulated clinical core. Every future portal extends it — no rebuilding.
Actor Model + RBAC roles  |  Green = V1 (Fabbi)  |  Gray dashed = V1.5→V5 Roadmap
PhytoMedic Platform
Fastify · PostgreSQL · AWS ECS Frankfurt
Layer 0 — Shared Services (V1)
Multi-tenant Auth
Passkeys/WebAuthn + Biometric + JWT RS256
RBAC with org-scoping
DOCTOR | SITE_ADMIN | COMPLIANCE_ADMIN | SUPER_ADMIN | SERVICE_ACCOUNT
Immutable Audit Log
Hash-chained, 10-year retention, tamper-evident (BfArM §15)
Notifications
Push (iOS+Android) + Web Push + Email · Templates
Infrastructure
CI/CD · GDPR config · Secrets Mgmt (Vault) · Drug Interaction DB
Web Shell + PWA
Responsive Web (WEB-001/002) + Installable PWA (WEB-003)
Layer 1 — Clinical & Operational Core (V1)
Doctor KYC + QES D-Trust
Document upload → admin review → eIDAS Level-qualified signing
Presence Check
Geofence GPS + rotating QR + liveness selfie · check-in/out
Site Management
Site catalog, access requests, physician approval, configuration
Patient Management
Search, register, profile, consent, visit history
Booking & Appointments
Location search, booking flow, calendar, reschedule/cancel, no-show tracking
Prescription Lifecycle
ICD-10 → dosage → DRAFT→SIGNED→ROUTED→CONFIRMED + BtMG
Pharmacy Routing
Cannaleo + HiGreen APIs · circuit breaker · fallback · onboarding
Cannametrics Foundation ★
7 tables (CANNA-001→007): catalog, snapshots, price history, outcomes, V3 API
Layer 2 — Stakeholder Portals
Doctor Portal V1
iOS + Android (React Native) + Web (React) + PWA
Admin / Compliance Portal V1
User mgmt, site admin dashboard, compliance dashboard, audit viewer
Patient Portal V1.5
Read + prescriptions on existing V1 APIs
Pharmacy Portal + Finder V2
Pharmacy org type + inventory + public doctor/pharmacy finder
Cannametrics Dashboards V3
Analytics on V1 foundation tables — no migration
Manufacturer Portal V4
Manufacturer org type on same multi-tenant model
Public Growth Layer V5
SEO, doctor/pharmacy finder full, education, GEO pages
V1 RBAC Roles: DOCTOR SITE_ADMIN COMPLIANCE_ADMIN SUPER_ADMIN SERVICE_ACCOUNT
Q2
V1 Scope
In / Out / Future
Final SOW: 90 items · One master count · All V1

V1 Scope — What Fabbi Builds (90 items)

Reconciled from SOW v7.2 · 90 V1 items across 13 feature groups · Authoritative master count
Feature✅ V1 — Fabbi BuildsFuture Phase
Auth & Multi-tenantBiometric, device binding, WebAuthn/Passkeys, JWT RS256, session mgmtSSO/OAuth2 (V1.5)
KYC & QESManual KYC + D-Trust enrollment, QES signing & verificationAI KYC (V1.5), SwissSign eval
Presence CheckGeofence GPS + rotating QR + liveness selfie, check-in/out
PatientsSearch, register, patient profile, consent management, visit history (PAT-001→005)Therapy diary (V1.5)
Site ManagementSite catalog, site details, access requests, site configuration, physician approval (SITE-001→005)
Booking & AppointmentsLocation search, booking flow, slot selection, calendar, create/reschedule/cancel, doctor availability, no-show tracking (BOOK-001→005, APT-001→008)
PrescriptionsICD-10, product select, dosage validation, preview, draft, history, QES-signTemplates (V1.5)
Pharmacy RoutingCannaleo + HiGreen API, product catalog, normalization, routing, statusFallback rules (V2)
Cannametrics Foundation7 tables: catalog, snapshots, price history, outcomes, V3 read API — data collection from Day 1Analytics UI (V3)
Doctor PortalsiOS + Android (React Native, native) + Responsive Web (React) + PWA (WEB-003, installable)
Admin PortalUser mgmt, site admin dashboard, compliance dashboardPharmacy onboarding ext. (V2)
Audit & ComplianceImmutable hash-chained audit, auth/presence/prescription logs, compliance reportsRegulatory export (V1.5)
NotificationsMulti-channel push (iOS/Android) + email + in-app + templatesSMS (V1.5)
Drug Safety & SecurityDrug interaction database (DRUG-001, BtMG caps + duplicate detection) · Secrets management (HashiCorp Vault)
InfrastructureDev environment, CI/CD, GDPR config, web app shell (WEB-001/002), PWA (WEB-003)
Pharmacy OnboardingBasic pharmacy registration & verification (PHARM-ONB)Full portal (V2)

V1 Scope — Explicitly Out (Updated Roadmap)

Per Alexander's feedback: Pharmacy + Public Finder Lite pulled forward to V2. Growth Layer full engine → V5.
What's out of V1PhaseHow it extends V1
Patient PortalV1.5New patient role + new UI on existing V1 APIs — zero schema change
Pharmacy Portal + Public Finder Lite
Doctor finder, pharmacy finder, public product catalog
V2 Pharmacy org type + PHARMACIST role + inventory APIs. Includes lightweight public-facing finder (doctor/pharmacy/product) — per Alexander's suggestion to pull forward from V5.
Pharmacy Portal + Public Finder Lite
Doctor finder, pharmacy finder, product catalog (public)
V2 Pharmacy org type + PHARMACIST role + public-facing finder. Reuses V1 product catalog data.
Cannametrics Dashboards & AnalyticsV3Read-only analytics on V1 tables — no migration needed, data already collected from Day 1
Manufacturer PortalV4Manufacturer org type on same multi-tenant model
Full Public Growth Layer
SEO engine, content platform, GEO pages, calculators, community
V5Separate marketing site — no clinical DB coupling. Basic finder already in V2.
E-Rezept / Gematik TIV2+FHIR-compatible architecture prepared in V1. Client obtains Zulassung independently.
📍 Roadmap update per Alexander's suggestion: A lightweight Public Finder (doctor/pharmacy finder + public product catalog) is bundled with V2 Pharmacy Portal — allowing discoverability to start ~3 months earlier than a standalone V5-only approach. Full SEO/content engine stays V5.

V1 Delivery — App Scope (Explicit)

PhytoMedic is one integrated platform with role-based stakeholder portals — not disconnected products.
📱
iOS App (Doctor)
React Native — true native compilation, not a web wrapper
Native biometric (Face ID / Touch ID) · GPS geofencing · Push notifications · Camera for KYC/liveness · Offline-capable presence check
✅ V1 Included
🤖
Android App (Doctor)
React Native — true native compilation, ~80% shared code with iOS
Native biometric (fingerprint / face) · GPS · Push · Camera · Same feature parity as iOS
✅ V1 Included
🖥️
Responsive Web (React)
React — Doctor Console + Admin Portal + Patient Booking flow (unauthenticated)
Desktop + iPad optimized · Chrome, Safari, Edge · All admin and compliance workflows · Passkeys / WebAuthn authentication
✅ V1 Included
Progressive Web App — PWA (WEB-003)
Installable web version of the Doctor portal — works across all browsers
Installable on home screen · Offline-capable (service worker) · Web Push notifications · No app store required · Complements native apps
✅ V1 Included
One integrated platform — 4 delivery surfaces. iOS + Android (React Native native) · Responsive Web · PWA (installable). One shared backend · One API · One data model. Adding a future portal = adding a role + a UI layer. No data migration. No architectural change.
Q3 + Q4
Architecture Extensibility
& Cannametrics Foundation
V1 is designed to make every future phase cheaper and faster.

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

Every architectural decision in V1 is made to maximize downstream reuse and minimize future migration risk.
Extensibility AxisV1 Design DecisionImpact on Future Phases
Multi-tenant org_idEvery entity carries org_id from day 1New portal = new role + new UI. No schema change.
RBAC role modelDOCTOR, ADMIN, COMPLIANCE, SUPER_ADMIN defined in V1Adding PATIENT, PHARMACIST, MANUFACTURER = role additions only
API-first designAll features exposed as typed REST APIsPatient Portal (V1.5) = new frontend on existing APIs — ~60% of work is reuse
Modular MonolithDomain modules with clear boundariesExtractable to microservices if scale demands — no lock-in
Cannametrics tables (7 tables)V1 writes structured data from Day 1, continuouslyV3 = read-only analytics on data already collected. No migration ever needed.
i18n scaffoldedEN/DE locale support from V1Multi-language content = translations only, no code change
Product normalizationCannaleo + HiGreen data normalized to internal modelV2 Pharmacy Portal + V3 Cannametrics reuse same catalog — ~40% effort saved
✅ Patient Portal (V1.5) · Pharmacy Portal + Finder (V2) · Cannametrics Intelligence (V3) · Manufacturer Portal (V4) · Full Growth Layer (V5) — none of these require schema migration or breaking changes to V1.

Cannametrics — Why Data Collection Starts in V1

V3 analytics needs historical data that can only be built over time. V1 lays the foundation.
The Problem

V3 Analytics needs historical data — price trends, availability patterns, routing outcomes — that can only be collected over months of real usage. You cannot retroactively generate this data.

The Solution

V1 writes to 7 Cannametrics tables from Day 1. By the time V3 launches, months of real market data are already stored and ready for analytics — no migration, no backfill.

TableSOW IDWhat it captures
product_catalogCANNA-001Schema + sync service foundation
catalog sync serviceCANNA-00215-min Cannaleo/HiGreen poll
pharmacy_availability_snapshotsCANNA-003Supply availability over time
price_historyCANNA-004Append-only price tracking
prescription_product_dataCANNA-005Demand by product (anonymized)
routing_outcomesCANNA-006Routing performance + idempotency
V3 Read API (internal)CANNA-007Read-only endpoint for V3 analytics team
Cannametrics Pipeline
Q5 — Updated Roadmap
Platform Roadmap
V1 → V5
Pharmacy + Public Finder pulled forward to V2 · ROM estimates per phase included

Platform Roadmap — ROM Budget Estimates

V1: 8-person senior team · 3 months · V1.5–V5: ROM estimates, ±30–40% accuracy · Not fixed-price commitments
✅ V1 — Active
Clinical Core + Cannametrics Foundation
13.86 MM
~3 months · 8 people (fixed team)
$28,902 (fixed)
• Doctor iOS + Android (React Native)
• Responsive Web (React) + PWA
• KYC · QES · Presence · Prescriptions
• Pharmacy Routing (Cannaleo/HiGreen)
• Cannametrics 7 tables · Audit
V1.5
Patient Portal & Treatment Continuity
4–6 MM
~1.5–2 months
$9K – $14K ROM
• Patient Dashboard
• Therapy History & Diary
• Medication Visibility
• Treatment Progression
• Retention & Engagement
V2 ← Updated
Pharmacy Portal + Public Finder Lite
8–12 MM
~2.5–3.5 months
$18K – $27K ROM
• Full Pharmacy Dashboard & Operations
• Prescription Intake & Order Mgmt
Doctor Finder (public)
Pharmacy Finder (public)
Public Product Catalog
V3
Cannametrics Intelligence Layer
5–8 MM
~1.5–2.5 months
$11K – $18K ROM
• Live Catalog & Availability dashboards
• Price Trend Analytics
• Per-Pharmacy Insights
• Procurement Intelligence
• Reorder & Sell-Through
V4
Manufacturer Portal
3–5 MM
~1–1.5 months
$7K – $11K ROM
• Manufacturer Dashboard
• Product Portfolio & Reports
• Commercial Visibility
• Focus Products
V5
Full Public Growth Layer
5–8 MM
~1.5–2.5 months
$11K – $18K ROM
• Full SEO & GEO Pages engine
• Education & Content Hub
• Calculators & Tools
• Conversion & Engagement
• Multi-Country & Localization
📊 Total program ROM: 39–54 MM · ~$85K–$117K indicative · V1 fixed ($28,902) + V1.5–V5 ROM · Timeline varies by team scaling and phase overlap
⚠️ ROM accuracy ±30–40%. Each phase is separately scoped and priced before commitment. Same 10% volume discount applies. Subject to discovery findings.

🌿 PhytoMedic — Program Landscape Overview

Quotation v7.1 · April 2026 · All numbers authoritative
90
V1 SOW Items
$28,902
V1 Fixed Price
~$85K–$117K
Total Program ROM
39–54 MM
Total Effort ROM
✅ V1 — Active
Clinical Core &
Doctor Portal
Auth · KYC · QES · Presence · Prescriptions · Pharmacy Routing · Cannametrics · Admin
13.86 MM
Effort
$28,902
Fixed
3 months · 8 people
V1.5
Patient Portal &
Treatment Continuity
Patient Dashboard · Therapy History · Medication Visibility · Prescription Status · Retention
4–6 MM
Effort ROM
$9K–$14K
Cost ROM
~2 months
V2 ← Updated
Pharmacy Portal +
Public Finder Lite
Pharmacy Dashboard · Prescription Intake · Orders · Doctor/Pharmacy Finder · Public Catalog
8–12 MM
Effort ROM
$18K–$27K
Cost ROM
~3 months
V3
Cannametrics
Intelligence Layer
Live Catalog · Price Trends · Per-Pharmacy Insights · Procurement Intelligence · Reorder Analytics
5–8 MM
Effort ROM
$11K–$18K
Cost ROM
~2 months
V4
Manufacturer
Portal
Manufacturer Dashboard · Product Portfolio · Commercial Visibility · Performance Insights
3–5 MM
Effort ROM
$7K–$11K
Cost ROM
~1.5 months
V5
Full Public
Growth Layer
SEO & GEO Pages · Education Hub · Calculators · Conversion & Engagement · Multi-Country
5–8 MM
Effort ROM
$11K–$18K
Cost ROM
~2 months
V1 Foundation — Cost Reduction in Later Phases
FoundationPhasesReduction
Multi-tenant org_idV1.5V2V3V4
10–15%
RBAC role modelV1.5V2V4
5–10%
API-first designV1.5
30–40%
Cannaleo/HiGreen APIsV2V3
15–20%
Audit & complianceAll
5–10%
Cannametrics 7 tablesV3
25–35%
Directional · Each phase re-scoped before commitment
Fixed Scope vs. Assumption-Based
ModuleTypeNote
Auth, KYC (manual), PresenceFixedFully specified
Booking, Appointments, AuditFixedFully specified
Cannametrics data collectionFixedSchema + jobs defined
QES (D-Trust)Fixed + Dep.⚠ D-Trust sandbox at kickoff
Pharmacy routingFixed + Dep.⚠ API docs by Week 1
Drug interaction DBAssumptionSource TBD
Advanced QES edge casesDiscoveryMay generate CRs
V1 App Scope — Explicit
📱
iOS App
React Native — native
V1
🤖
Android App
React Native — native
V1
🖥️
Responsive Web
React — Doctor + Admin
V1
PWA (WEB-003)
Installable web version
V1
Program Total — V1→V5
Total Effort (ROM)
39–54 MM
Total Budget (indicative)
~$85K–$117K
V1 (fixed)$28,902
V1.5–V5 (ROM)~$56K–$88K
ROM ±30–40% · Each phase re-scoped before commitment

Delivery Timeline — All Phases

V1: 8-person senior team · ~3 months · V1.5–V5: ROM directional estimates · Phases can partially overlap
V1
Clinical Core + Cannametrics · 13.86 MM · ~3 months · 8 people
$28,902 fixed
V1.5
Patient Portal · 4–6 MM · ~2 months
$9K–$14K ROM
V2
Pharmacy Portal + Public Finder Lite · 8–12 MM · ~3 months
$18K–$27K ROM
V3
Cannametrics Intelligence · 5–8 MM · ~2 months
$11K–$18K ROM
V4
Manufacturer Portal · 3–5 MM · ~1.5 months
$7K–$11K ROM
V5
Full Public Growth Layer · 5–8 MM · ~2 months
$11K–$18K ROM
ℹ️ V1 team: 1 PM · 1 BA · 2 FE · 3 BE · 1 QA (senior-level) · ~3 months. V1.5–V5 timelines are directional ROM estimates. Parallel phase tracks can compress the overall roadmap significantly.

V1 Foundation — Reuse Across Future Phases

Estimated effort reduction per phase — directional only. Actual savings confirmed at each version's scoping exercise.
V1 FoundationReused InEffort Reduction (est.)Visual
Multi-tenant architecture (org_id)
New portal = new role + new UI. No schema change.
V1.5 V2 V3 V4 ~10–15% per version
RBAC role model
Adding PATIENT, PHARMACIST = role additions only.
V1.5 V2 V4 ~5–10% per version
API-first design (all features as REST APIs)
V1.5 Patient Portal calls existing V1 APIs — backend largely complete.
V1.5 ~30–40% backend effort saved for V1.5
Cannaleo / HiGreen integrations
Integration code reused in V2 pharmacy operations.
V2 V3 ~15–20% of pharmacy integration scope
Product normalization layer (PROD-001→004)
Normalized catalog reused across pharmacy, analytics, and manufacturer modules.
V2 V3 V4 ~10–15% of product-related scope
Audit & compliance foundation
All portals write to same audit trail — no rebuild per phase.
All versions ~5–10% per version
Cannametrics data foundation (7 tables, collecting from Day 1)
V3 reads data already accumulated during V1 + V2 operation — no migration needed.
V3 ~25–35% of V3 analytics scope
Pharmacy routing logic
Core routing rules extended — not rebuilt — in V2 pharmacy portal.
V2 ~10–15% of V2 routing scope
⚠️ Note: Reuse estimates are directional. Actual savings depend on V2–V5 discovery, third-party API changes, and regulatory requirements per phase. Each version is re-scoped independently before any pricing commitment.

Scope Confidence — Fixed vs. Assumption vs. Discovery

~65% fixed · ~25% assumption-based · ~10% discovery-dependent (resolved during Sprint 0 and dev)
CategoryItemsConfidence
Fixed Scope
Clear client requirements, no dependency uncertainty
Auth (AUTH-001~006), KYC (KYC-001~007), QES (QES-001~005), Presence (PRES-001~007), Patient (PAT-001~005), Appointments (APT-001~008), Booking (BOOK-001~005), Infrastructure (INFRA-001~003), Admin (ADMIN-001~003), Audit (AUDIT-001~005) High — requirements documented
Assumption-Based
Fabbi-proposed, details may evolve in Sprint 0
Cannametrics schema design (CANNA-001~007), Notification channels (NOTIF-001~004), Compliance dashboard format (ADMIN-003), Presence check UX flow, Web app shell (WEB-001~002), Drug interaction DB source (DRUG-001), Pharmacy onboarding flow (PHARM-ONB) Medium — adjustable in Sprint 0
Discovery-Dependent
Known unknowns — resolved through API access & regulatory consultation
D-Trust API behavior & edge cases, Cannaleo/HiGreen API rate limits & schema, BtMVV validation rules, GDPR Art.9 specifics, Drug interaction DB licensing, QES multi-device flows Variable — may generate CRs
⚠️ Pre-kickoff client requirements (blocking start): (1) D-Trust sandbox credentials before kickoff · (2) Cannaleo API docs + sandbox by Week 1 · (3) HiGreen API docs + sandbox by Week 1. Delay in items 2–3 triggers pharmacy routing module timeline adjustment.

Investment Summary — Version 1

Final figures from Quotation v7.0 · Single authoritative baseline
90
SOW Items · V1 Final
13.86 MM
Total Effort
~3 months
Delivery Timeline (V1)
8 people
Fixed V1 Team (Senior)
Team Composition — 8 People
1 PM
Project Mgr
1 BA
Business Analyst
2 FE
React Native + Web
3 BE
Backend (senior)
1 QA
Quality Assurance
Version 1 — Final Price
Design (2.48 MM × $2,100)$5,208
UI/UX (0.66 MM × $1,800)$1,181
Core Dev (6.13 MM × $2,500)$15,313
Testing (3.34 MM × $2,100)$7,010
PM (1.26 MM × $2,700)$3,401

Subtotal$32,113
Discount (10%) ※−$3,211
VAT$0 (exempt)

TOTAL$28,902
Payment Schedule
① Contract Signing — 30%
Before Sprint 0 begins
$8,671
② Beta — All Main Flows Testable — 30%
All core flows testable by client
$8,671
③ Final Acceptance — 40%
UAT complete · production deploy approved
$11,561
※ 10% discount as special offer for this collaboration · VAT exempt · 12-month warranty & support included

Pre-Kickoff Requirements

The following must be in place before Fabbi can begin Sprint 0.
#ItemOwnerDeadlineRisk if delayed
1D-Trust sandbox credentialsCannabis ÄrzteBefore kickoffBlocks QES module entirely
2Cannaleo API documentation + sandboxCannabis Ärzte / CannaleoWeek 1Delays pharmacy routing sprint
3HiGreen API documentation + sandboxCannabis Ärzte / HiGreenWeek 1Delays pharmacy routing sprint
4AWS account (Frankfurt region) setupFabbi (client access)Sprint 0No major risk — internal
5Contract signing + 30% down payment ($8,671)Cannabis ÄrzteBefore kickoffBlocks project start
⚠️ E-Rezept / Gematik Zulassung is a German federal certification that Cannabis Ärzte must obtain independently. Fabbi prepares FHIR-compatible architecture in V1 — integration is a V2+ engagement.

Next Steps

What happens after this proposal is reviewed and aligned.

Cannabis Ärzte (Alexander)

Review and confirm V1 scope (90 SOW items, $28,902)
Confirm Cannametrics data foundation is included in V1
Confirm Pharmacy Portal + Public Finder Lite in V2 roadmap
🔐
Initiate D-Trust sandbox credentials (pre-kickoff blocker)
📡
Align on Cannaleo + HiGreen API access (Week 1 of Sprint 0)
✍️
Sign software development contract
💳
30% down payment at contract signing ($8,671)

Fabbi Software

📋
Finalize SOW (90-item acceptance criteria) — v7.0 baseline
✍️
Sign contract + issue 30% down payment invoice ($8,671)
🚀
Sprint 0 kickoff — setup, architecture, API integration planning
🏗️
Sprint 1 start — auth, infra, KYC, QES integration (D-Trust)
📊
Weekly progress updates + bi-weekly demo calls
🌿
Let's build
PhytoMedic.
Questions? Let's talk.
Alexander
Cannabis Ärzte · Germany
Hà LTT
Fabbi Software · Vietnam
Fabbi Software · fabbi.com.vn · Proposal v7 · April 2026
1 / 21 or use arrow keys