Vrida — Roadmap

Foundation (pre-v1.0) — REQUIRED MILESTONE

⚠️ Revised 2026-05-13 per PROJECT_DECISIONS "Nursery-Only Focus". The "core layer" and "item-first refactor" are retired. Vrida is nursery-only; masters live in owning modules. The remaining Foundation work is: build the Platform / Identity / Payments / Integrations / AI layers, ship Files + Search shared services, and execute the three remaining nursery-module refactors (CRM, Customer App, Admin).

Per PROJECT_DECISIONS "Platform Module (Locked 2026-05-13)" + "Nursery-Only Focus (2026-05-13)", the foundation work must complete BEFORE v1.0 nursery-module build proceeds.

Build: Platform + Identity + Payments + Integrations + AI layers

  • platform — Vrida's control plane. 16 tables locked (see PROJECT_DECISIONS "Platform Module (Locked 2026-05-13)").
  • identity — users, roles, permissions, sessions, 2FA, SSO (extracted from Admin)
  • payments — single PaymentsService over Stripe (Terminal + Customer/subscriptions + Connect)
  • integrations — unified external-connector layer (QuickBooks now; Shopify / Sage / Xero / workforce later). Also owns the AI-powered self-serve onboarding pipeline (import_job, import_file, import_record).
  • ai — single AIService over AWS Bedrock; model-as-config; routing, rate limits, fallback, future RAG corpus
  • files (shared service) — Cloudflare R2 ownership
  • search (shared service) — single search abstraction

Refactor: three remaining nursery modules

  • Inventory — item-first refactorCANCELLED per Nursery-Only Focus. Inventory stays nursery-first; plant master IS the item (plant fields directly on item).
  • CRM — customer is tenant-scoped, in crm schema. charge_account moves to Billing module per Billing Ownership Split.
  • Customer App — multi-nursery consumer linkage tables (plant_library, garden_plan, chat_session) live in customer_app schema directly (no "extension layer" framing). Still consumer-owned, cross-tenant — only the layering label changes.
  • Admin — Identity/Auth (Group 3 features 3.1–3.14) extracted to Identity module; Integrations (Group 10) extracted to Integrations module; Admin retains tenant configuration + tenant HR (Group 3 features 3.15–3.19).

Gate

v1.0 nursery-module build does not proceed until Foundation is complete and verified. This includes:

  • Platform schemas built and tested (16 tables)
  • Identity, Payments, Integrations, AI specs locked and schemas built
  • Files + Search shared services live
  • Three refactored nursery modules building cleanly
  • Billing module renamed; charge_account moved from CRM to Billing; SaaS subscription moved from Billing to Platform
  • AI-powered self-serve onboarding pipeline operational in Integrations

v1.0 — Pro tier publicly launched

v1.0 builds on the Foundation milestone; all nursery modules sit on the Core & Platform Layer.

Target build: 8–12 weeks for inventory module alone given 89 features; realistic full v1.0: 15–18 months for the full platform.

v1.0 ships 13 modules with 1,694 features total:

  • Module 1 (Inventory): 94 features
  • Module 2 (POS): 204 features
  • Module 3 (Customer Orders): 149 features
  • Module 4 (Purchasing & Suppliers): 134 features
  • Module 5 (CRM): 158 features
  • Module 6 (Reporting & Analytics): 146 features
  • Module 7 (Production / Propagation): 41 features (81 deferred to v1.2/v1.5)
  • Module 8 (Customer-facing App): 145 features
  • Module 9 (Multi-location): 107 features (schema-ready; multi-site UI v1.5+)
  • Module 10 (Admin): 165 features
  • Module 11 (Billing): 115 features
  • Module 12 (Audit & Compliance): 108 features
  • Module 13 (Notifications): 128 features

Modules 14 (Delivery & Logistics) and 15 (Services & Jobs): Deferred indefinitely — will spec when customer demand justifies it.

Schema-ready but UI-deferred:

  • Multi-site UI (in v1.5)
  • Production UI (in v1.2)
  • Starter tier UI (in v1.1)
  • Enterprise tier UI (in v1.5)

v1.1 — Starter tier launch

  • Starter tier publicly available
  • Feature flag toggles and SKU/user/zone caps enforced
  • Notification SMS channel (Twilio) — via Integrations module
  • Marketing emails for CRM
  • Picas CSV import with guided migration playbook — via Integrations module

v1.2 — Production-light and full Purchasing

  • Production / Propagation module UI activated
  • Production module expansion — mother plant management (Group 9, 8 features), inspections & grading depth (Group 5 additions), between-zone moves (4.7), treatment depth (Group 6 additions), pest catalogs, loss analytics, expanded production setup, multi-year planning prep. 55 features moved from v1.0 trim. See docs/modules/07_production.md → "Deferred to v1.2 / v1.5" section.
  • Full Purchasing module: POs, three-way match, AI invoice OCR (AI via AIService)
  • Reorder forecasting (via AIService)
  • Weather-tied inventory AI forecasting integrated with reorder suggestions; hyper-local SKU-level reorder using prior years' sales + local weather (via AIService)
  • Workshops as sellable items with capacity, schedule, attendee list
  • AI staff training assistant — answer staff questions, generate role-specific training content (via AIService)
  • AI markdown optimization recommendations across inventory and reporting; AI marketing copilot (segment/copy/timing suggestions); decision support layer at POS and Reporting (all AI via AIService)
  • Sandbox tier — forever-free non-production developer account for consultants and integrators
  • Curated answer-dashboards layer for Reporting — opinionated nursery-specific weekly/seasonal dashboards

v1.5 — Multi-location and Enterprise tier launch

  • Multi-location UI rollout
  • Enterprise tier publicly launched
  • Module 14: Delivery & Logistics (initial)
  • SSO, custom roles, API access for Enterprise
  • White-label support
  • Multi-currency UI
  • Native Shopify, WooCommerce, Wix ecommerce sync connectors — via Integrations module
  • Job costing module — central job object with budget/phases/labor/profitability per project
  • Unified AI copilot — weekly recommendation surface across inventory/CRM/marketing/operations (via AIService)
  • Accounting integrations — Sage, Sage Intacct, Xero — via Integrations module
  • Nursery-pretrained AI knowledge base — RAG corpus from operational data + seasonal patterns (RAG corpus owned by AIService)
  • Workforce management integrations — Gusto, ADP, Deputy — via Integrations module
  • Pesticide/chemical compliance records — REI tracking, applicator license linkage, state pesticide application records
  • Production module full grower features — multi-year crop planning (Group 11, 8 features), scenario modeling, advanced forecasting, WIP valuation, advanced production reporting. 26 features moved from v1.0 trim. See docs/modules/07_production.md → "Deferred to v1.2 / v1.5" section.

Consumer Layer Phase — post-merchant-core (not yet scheduled)

Direction agreed 2026-06-09 — architecture not yet designed; schema not yet built. See PROJECT_DECISIONS "Consumer Layer Architecture." Built after the merchant core (structurally depends on POS for rewards earn).

~4 new modules:

  • consumer — platform-level Vrida consumer identity; social-login auth (Google/Apple); own non-tenant consumer schema
  • rewards / loyalty — per-business points, earning rules, tiers, expiry, redemptions; bridges consumer × tenant
  • offers — business-issued or Vrida-issued discount / promo offers; funding-source flag (vrida / business)
  • consumer_app — app experience: view my stores, points balances, offers, AI care chat, purchase history across linked stores

v1 consumer scope: rewards + informational. In-app commerce (buying inside the app) is deferred to a later sub-phase.

Modules 14 (Delivery) and 15 (Services) remain deferred indefinitely; consumer layer is separate from those.


v2.0 — Full platform maturity

  • Module 15: Services & Jobs
  • Picas CSV integration — via Integrations module
  • Advanced AI features (via AIService)
  • SOC 2 certification
  • Audit external attestation upgrade: R2 Object Lock (replaces v1.0 signed-export-only when SOC 2 audit prep begins). See ARCHITECTURE.md "Audit Architecture".
  • Third-party app marketplace / extension ecosystem

Explicitly Out of Scope (NEVER building)

See OUT_OF_SCOPE.md

Last modified: Jun 17, 2026, 6:57 PM PT
On this page
Esc