Skip to main content
DayzeHelp
Back to Dayze
Guide

Projects & portfolio

If you run several ventures at once — e.g. Dayze, Keta Clinic, Dripped, Higher — Dayze can act as your life HUD + light ops layer. Use /projects for KPIs and revenue, plus Businesses, Calendar, and Playbook for CRM and rhythm.

Sign in required

/projects is a signed-in app route (like /businesses or /inventory). Open it from the profile menu while logged in, or sign in with /login?returnTo=/projects so you return to the portfolio after auth.

Short answer

Use Business Contacts for each venture (category company, tags like project), Calendar for ship dates and work blocks, Playbook for recurring daily rhythm per project, Finance for spend by project, and People for collaborators. Dayze Agent can create and link all of these from chat.

What exists today

Business Contacts

Meant for vendors and clinics — but works for your own companies. Add Dayze, Keta, Dripped, Higher as company rows with website, notes, tags ['project','active']. Each business modal shows linked calendar events (CRM timeline).

Calendar

Milestones, launches, investor calls, deep-work blocks. Filter by activity type (Events vs Food/Movies/TV). Agent: "Schedule Keta deploy review Friday 3pm" → create_event with location or description noting the project.

Playbook

Multiple schedule templates (?set=dayze, ?set=keta). One playbook per project for morning standup, ship window, outreach — separate from calendar appointments.

Finance

Tag expenses in description or merchant ("Vercel — Dayze", "Stripe — Keta"). Calendar finance overlay shows daily P&L. Agent: add_expense with clear project in the note.

People

Co-founders, contractors, advisors — humans stay in People; link their company in the person record. Business Contacts hold the venture entity. Relationship pulse and reach-out quests keep you from neglecting key partners across projects.

Example: @goh portfolio setup

  1. Tell Dayze Agent: "Add my projects Dayze, Keta Clinic, Dripped, and Higher to business contacts as companies I own." Confirm each Add to Businesses card.
  2. Create Playbook sets: /playbook?set=dayze (product + agent work), ?set=keta (clinical ops), etc.
  3. Log ship milestones on the calendar: "Dripped beta launch", "Keta intake form live" — they appear on your unified timeline and on each business CRM panel when linked.
  4. Use /calendar filters: Events for work, switch to Food/Movies/TV for personal life on the same grid.

Projects module (shipped)

Use /projects for portfolio + Venture HQ per slug (sign in first). KPI definitions, time-series snapshots, manual log, and optional dayze_platform connector for live MRR/MAU (admin). Agent: create_project, log_project_kpi.

Still on the roadmap:

  • Event/expense project_id foreign keys
  • Monthly spend rollup per project from Finance
  • Stripe connector per venture (Keta, Dripped)
  • GitHub/Linear webhook → calendar milestones

Business Contacts + Playbook + Calendar filters still complement Projects for CRM and daily rhythm.

Migration: npx tsx scripts/apply-sql-migration.ts migrations/20260617_user_projects.sql (requires network path to Supabase Postgres, or paste SQL in Supabase SQL editor).

Related