@synap-core/workspace-templates 0.2.2 → 0.4.0

package/src/finance.yaml

@@ -0,0 +1,485 @@
+# Finance workspace template
+# A pragmatic startup CFO's operating model: cash, receivables, spend, revenue,
+# budgets, and the vital signs (runway / burn / MRR). Provider of the `finance`
+# domain; consumes `strategy` from Foundation for pricing/positioning context.
+
+meta:
+  slug: finance
+  name: Finance
+  description: The company's money model — accounts, receivables, spend, revenue streams, budgets, and runway.
+  icon: banknote
+  color: "#16A34A"
+  tags: [finance, accounting, revenue]
+  isPublic: true
+
+workspace:
+  name: Finance
+  description: Startup finance workspace — bank/ledger accounts, invoices (AR), expenses (AP), revenue streams, budgets, and the runway/burn/MRR metrics that keep the company alive.
+  proposalId: finance-v1
+  subtype: finance
+  visibility: members
+  workspaceType: operational
+  capabilities:
+    - finance.accounts
+    - finance.revenue
+    - finance.expenses
+  # Finance PROVIDES the finance domain, and CONSUMES strategy (Foundation) so
+  # pricing/positioning context informs revenue modeling. The concrete provider
+  # workspaceId for `strategy` is resolved at runtime (defaultSources), so it is
+  # expressed here declaratively via the consumer source role.
+  sourceRoles:
+    finance: provider
+    strategy: consumer
+
+profiles:
+  - slug: account
+    displayName: Account
+    icon: landmark
+    color: green
+    description: A bank, credit, or ledger account holding company cash.
+    properties:
+      - slug: account-type
+        label: Type
+        valueType: string
+        inputType: select
+        enumValues: [checking, savings, credit-card, ledger, investment, other]
+        constraints: { defaultValue: checking }
+      - slug: institution
+        label: Institution
+        valueType: string
+        inputType: text
+        placeholder: e.g. Mercury, Chase
+      - slug: balance
+        label: Current Balance
+        valueType: number
+        inputType: number
+      - slug: currency
+        label: Currency
+        valueType: string
+        inputType: select
+        enumValues: [USD, EUR, GBP, other]
+        constraints: { defaultValue: USD }
+      - slug: status
+        label: Status
+        valueType: string
+        inputType: select
+        enumValues: [active, dormant, closed]
+        constraints: { defaultValue: active }
+      - slug: last-four
+        label: Account (last 4)
+        valueType: string
+        inputType: text
+
+  - slug: invoice
+    displayName: Invoice
+    icon: receipt
+    color: blue
+    description: An accounts-receivable invoice — money customers owe us.
+    properties:
+      - slug: invoice-number
+        label: Invoice #
+        valueType: string
+        inputType: text
+      - slug: status
+        label: Status
+        valueType: string
+        inputType: select
+        enumValues: [draft, sent, paid, overdue, void]
+        constraints: { defaultValue: draft }
+      - slug: amount
+        label: Amount
+        valueType: number
+        inputType: number
+      - slug: currency
+        label: Currency
+        valueType: string
+        inputType: select
+        enumValues: [USD, EUR, GBP, other]
+        constraints: { defaultValue: USD }
+      - slug: customer
+        label: Customer
+        valueType: string
+        inputType: text
+      - slug: issue-date
+        label: Issue Date
+        valueType: date
+        inputType: date
+      - slug: due-date
+        label: Due Date
+        valueType: date
+        inputType: date
+      - slug: paid-date
+        label: Paid Date
+        valueType: date
+        inputType: date
+
+  - slug: expense
+    displayName: Expense
+    icon: credit-card
+    color: orange
+    description: An accounts-payable expense or spend commitment.
+    properties:
+      - slug: category
+        label: Category
+        valueType: string
+        inputType: select
+        enumValues: [payroll, software, marketing, rent, travel, contractors, taxes, other]
+        constraints: { defaultValue: other }
+      - slug: status
+        label: Status
+        valueType: string
+        inputType: select
+        enumValues: [pending, approved, paid, reimbursed, rejected]
+        constraints: { defaultValue: pending }
+      - slug: amount
+        label: Amount
+        valueType: number
+        inputType: number
+      - slug: vendor
+        label: Vendor
+        valueType: string
+        inputType: text
+      - slug: expense-date
+        label: Date
+        valueType: date
+        inputType: date
+      - slug: recurring
+        label: Recurring
+        valueType: boolean
+        inputType: checkbox
+      - slug: payment-method
+        label: Payment Method
+        valueType: string
+        inputType: text
+
+  - slug: revenue-stream
+    displayName: Revenue Stream
+    icon: trending-up
+    color: teal
+    description: A source of revenue — recurring subscription, services, or one-off.
+    properties:
+      - slug: stream-type
+        label: Type
+        valueType: string
+        inputType: select
+        enumValues: [subscription, usage, services, one-off, licensing, other]
+        constraints: { defaultValue: subscription }
+      - slug: status
+        label: Status
+        valueType: string
+        inputType: select
+        enumValues: [active, paused, churned, planned]
+        constraints: { defaultValue: active }
+      - slug: mrr
+        label: MRR
+        valueType: number
+        inputType: number
+      - slug: arr
+        label: ARR
+        valueType: number
+        inputType: number
+      - slug: billing-cadence
+        label: Billing Cadence
+        valueType: string
+        inputType: select
+        enumValues: [monthly, quarterly, annual, one-time]
+        constraints: { defaultValue: monthly }
+      - slug: customer-segment
+        label: Customer Segment
+        valueType: string
+        inputType: text
+      - slug: start-date
+        label: Start Date
+        valueType: date
+        inputType: date
+
+  - slug: budget
+    displayName: Budget
+    icon: pie-chart
+    color: violet
+    description: A planned spend allocation for a category and period, tracked vs actual.
+    properties:
+      - slug: category
+        label: Category
+        valueType: string
+        inputType: select
+        enumValues: [payroll, marketing, product, sales, ops, g-and-a, other]
+        constraints: { defaultValue: other }
+      - slug: period
+        label: Period
+        valueType: string
+        inputType: select
+        enumValues: [monthly, quarterly, annual]
+        constraints: { defaultValue: quarterly }
+      - slug: fiscal-year
+        label: Fiscal Year
+        valueType: string
+        inputType: text
+        placeholder: e.g. FY2026
+      - slug: budgeted-amount
+        label: Budgeted
+        valueType: number
+        inputType: number
+      - slug: actual-amount
+        label: Actual
+        valueType: number
+        inputType: number
+      - slug: status
+        label: Status
+        valueType: string
+        inputType: select
+        enumValues: [on-track, at-risk, over-budget]
+        constraints: { defaultValue: on-track }
+      - slug: owner
+        label: Owner
+        valueType: string
+        inputType: text
+
+  - slug: financial-metric
+    displayName: Financial Metric
+    icon: gauge
+    color: amber
+    description: A tracked vital sign — runway, burn rate, MRR, cash balance, margin.
+    properties:
+      - slug: metric-type
+        label: Metric
+        valueType: string
+        inputType: select
+        enumValues: [runway, burn-rate, mrr, arr, cash-balance, gross-margin, cac, ltv, other]
+        constraints: { defaultValue: runway }
+      - slug: value
+        label: Value
+        valueType: number
+        inputType: number
+      - slug: unit
+        label: Unit
+        valueType: string
+        inputType: select
+        enumValues: [months, currency, percent, ratio]
+        constraints: { defaultValue: months }
+      - slug: as-of-date
+        label: As Of
+        valueType: date
+        inputType: date
+      - slug: period
+        label: Period
+        valueType: string
+        inputType: select
+        enumValues: [point-in-time, monthly, quarterly, annual]
+        constraints: { defaultValue: point-in-time }
+      - slug: target
+        label: Target
+        valueType: number
+        inputType: number
+      - slug: trend
+        label: Trend
+        valueType: string
+        inputType: select
+        enumValues: [up, flat, down]
+
+views:
+  - name: Accounts
+    slug: accounts
+    type: table
+    scopeProfileSlug: account
+    description: All cash, credit, and ledger accounts with balances.
+    config:
+      columns: [title, account-type, institution, balance, currency, status]
+  - name: Invoices
+    slug: invoices
+    type: table
+    scopeProfileSlug: invoice
+    defaultView: true
+    description: Accounts receivable — who owes us, how much, and when it's due.
+    config:
+      columns: [title, invoice-number, status, amount, customer, due-date, paid-date]
+      defaultSort:
+        field: due-date
+        direction: asc
+  - name: Expenses
+    slug: expenses
+    type: kanban
+    scopeProfileSlug: expense
+    groupBy: status
+    description: Accounts payable and spend, grouped by approval/payment status.
+    config:
+      groupBy: status
+      cardFields: [category, amount, vendor, expense-date]
+  - name: Revenue
+    slug: revenue
+    type: table
+    scopeProfileSlug: revenue-stream
+    description: Revenue streams with MRR/ARR and billing cadence.
+    config:
+      columns: [title, stream-type, status, mrr, arr, billing-cadence, customer-segment]
+      defaultSort:
+        field: mrr
+        direction: desc
+  - name: Budget vs Actual
+    slug: budget-vs-actual
+    type: table
+    scopeProfileSlug: budget
+    description: Planned spend against actuals, by category and period.
+    config:
+      columns: [title, category, period, fiscal-year, budgeted-amount, actual-amount, status]
+  - name: Runway & Metrics
+    slug: runway-metrics
+    type: table
+    scopeProfileSlug: financial-metric
+    description: The vital signs — runway, burn, MRR, cash balance — vs target.
+    config:
+      columns: [title, metric-type, value, unit, target, trend, as-of-date]
+      defaultSort:
+        field: as-of-date
+        direction: desc
+
+# Schema-level links — give the finance graph and relation picker sensible
+# domain edges from day one.
+entityLinks:
+  - sourceProfileSlug: invoice
+    targetProfileSlug: account
+    type: deposited_to
+    label: Deposited to
+  - sourceProfileSlug: expense
+    targetProfileSlug: budget
+    type: counts_against
+    label: Counts against
+  - sourceProfileSlug: expense
+    targetProfileSlug: account
+    type: paid_from
+    label: Paid from
+  - sourceProfileSlug: revenue-stream
+    targetProfileSlug: account
+    type: deposits_to
+    label: Deposits to
+
+onboarding:
+  goal: Capture the company's real money model — where cash sits, what revenue comes in, what it burns on, and its current runway — so the workspace reflects the actual financial position, not a generic ledger.
+  framing: >
+    THE CFO: Act as a pragmatic, numerate startup CFO. Get to the truth of the
+    company's finances fast: how much cash is in the bank, what's coming in and
+    from where, what it burns each month, and how many months of runway that
+    leaves. Push for real numbers over estimates, flag anything that doesn't add
+    up, and tie revenue back to the company's positioning and pricing (from
+    Foundation) so the model is grounded in strategy, not spreadsheets.
+  expertise:
+    starters:
+      - >
+        Don't reconstruct a full P&L on day one — default the model to the three
+        numbers that keep a startup alive: cash in bank, monthly net burn, and
+        runway (cash ÷ burn, in months). Propose those first and layer detail later;
+        a founder who knows their runway to the month is ahead of one with a
+        beautiful chart of accounts.
+      - >
+        Add a small set of unit economics, not a whole finance stack: gross margin,
+        CAC, and LTV (or at minimum LTV:CAC ratio). Propose sensible defaults —
+        payback under ~12 months, LTV:CAC above ~3:1 — as reference points to react
+        to, rather than asking them to define metrics from scratch.
+      - >
+        Model cash on a timing basis, not an accrual one. When they give you revenue,
+        ask when the cash actually LANDS — Net-30/60 invoices, annual prepay,
+        Stripe payout lag — and capture that gap explicitly, because a profitable
+        month can still run the account dry.
+    blindSpots:
+      - >
+        Revenue ≠ cash. Founders book an annual contract and feel rich, but the cash
+        arrives monthly or after Net-60 — meanwhile payroll is due Friday. If they
+        conflate the two, separate signed bookings from collected cash before
+        computing anything.
+      - >
+        Runway is THE number that predicts survival, and it's the one most often
+        stale. If there's no current runway figure — or it hasn't been recomputed
+        since the last big hire or price change — that's the first gap to close.
+        Everything else is secondary to "how many months of oxygen is left".
+      - >
+        Bookings, revenue, and cash are three different numbers and founders routinely
+        merge them. A signed deal (booking), revenue recognized over its term, and
+        the money in the account are rarely equal in any given month. Name which one
+        each figure is, or the whole model lies.
+    bar: >
+      A stranger could open the workspace and answer three questions in ten seconds:
+      how much cash is in the bank, how much it burns a month, and how many months of
+      runway that leaves — with revenue captured on a cash-timing basis, bookings kept
+      distinct from collected cash, and at least a rough gross margin and LTV:CAC in view.
+  collect:
+    - profileSlug: account
+      what: The bank and credit accounts holding company cash, with current balances.
+      cardinality: few
+      keyFields: [title, account-type, balance]
+    - profileSlug: revenue-stream
+      what: How the company makes money — each recurring or one-off revenue stream and its MRR/ARR.
+      cardinality: several
+      keyFields: [title, stream-type, mrr]
+    - profileSlug: expense
+      what: The biggest recurring and one-off costs — payroll, software, contractors, rent.
+      cardinality: several
+      keyFields: [title, category, amount]
+    - profileSlug: financial-metric
+      what: The current vital signs, above all RUNWAY (months of cash left) plus burn rate and MRR.
+      cardinality: few
+      keyFields: [metric-type, value, unit]
+  openingQuestions:
+    - How much cash is in the bank right now, and across which accounts?
+    - Where does revenue come from today, and roughly what's the monthly recurring amount?
+    - What do you burn in a typical month — and how many months of runway does that leave?
+  doneWhen: At least one account with a balance, the main revenue streams, the largest expenses, and a runway metric are all captured with real numbers.
+
+app:
+  kind: stored
+  cellKey: entity-detail
+
+layout:
+  defaultView: Invoices
+  defaultApp: null
+  pinnedApps: [dashboard, data, intelligence]
+  sidebarItems:
+    - kind: view
+      viewName: Runway & Metrics
+      label: Runway & Metrics
+      icon: gauge
+    - kind: view
+      viewName: Accounts
+      label: Accounts
+      icon: landmark
+    - kind: view
+      viewName: Invoices
+      label: Invoices
+      icon: receipt
+    - kind: view
+      viewName: Expenses
+      label: Expenses
+      icon: credit-card
+    - kind: view
+      viewName: Revenue
+      label: Revenue
+      icon: trending-up
+    - kind: view
+      viewName: Budget vs Actual
+      label: Budget vs Actual
+      icon: pie-chart
+    - kind: app
+      appId: data
+      label: All Data
+      icon: database
+
+bento:
+  viewName: Finance Command Center
+  blocks:
+    - kind: view
+      viewName: Runway & Metrics
+      pos: { x: 0, y: 0, w: 8, h: 4 }
+    - kind: view
+      viewName: Accounts
+      pos: { x: 8, y: 0, w: 4, h: 4 }
+    - kind: view
+      viewName: Invoices
+      pos: { x: 0, y: 4, w: 6, h: 4 }
+    - kind: view
+      viewName: Expenses
+      pos: { x: 6, y: 4, w: 6, h: 4 }
+    - kind: view
+      viewName: Revenue
+      pos: { x: 0, y: 8, w: 6, h: 4 }
+    - kind: view
+      viewName: Budget vs Actual
+      pos: { x: 6, y: 8, w: 6, h: 4 }

package/src/foundation.yaml

@@ -254,6 +254,40 @@ onboarding:
     THE COFOUNDER: Act as a sharp, skeptical co-founder. Pressure-test why-now, why-you, and
     why-this. Refuse fuzzy answers; push for specifics and evidence. Be
     respectful but direct — a vague mission helps no one.
+  expertise:
+    starters:
+      - >
+        A mission is a CHANGE in the world, not a description of the product
+        ("make complex products understandable", not "we make explainer videos").
+        If they describe the deliverable, reflect the underlying change back and
+        propose THAT as the mission.
+      - >
+        Positioning is sharpest as ONE sentence — "the <X> for <who>" or "the only
+        <category> that <wedge>". If they give you a vague "we help companies with
+        Y", propose a crisp category+wedge framing from what they've told you and
+        let them sharpen it — never file the vague version.
+      - >
+        Audience is a SPECIFIC buyer at a specific stage ("Head of Product
+        Marketing at Series A–B technical SaaS"), not a market ("SaaS companies").
+        Push from the market to the person who actually signs off.
+    blindSpots:
+      - >
+        Founders skip the NON-goal — what they deliberately DON'T do. A company
+        with no "no" has no focus. If they haven't named boundaries, ask what they
+        turn down.
+      - >
+        A differentiator that's just "we're better / faster / care more" isn't
+        defensible. Push for a structural moat a competitor can't easily copy — and
+        if it's founder-dependent (bus-factor), capture that honestly rather than
+        dressing it up.
+      - >
+        The #1 tells of fuzzy strategy: a mission that's really a deliverable, and
+        positioning that's really a feature list. When you see either, name it and
+        dig.
+    bar: >
+      A stranger could read the mission, audience, and positioning and instantly
+      explain WHO this is for, WHAT changes for them, and WHY this company over the
+      alternatives — in one breath, with no fluff.
   collect:
     - profileSlug: mission
       what: The one mission that anchors the company — what we serve, what we change, why now.
@@ -334,11 +368,3 @@ bento:
     - kind: view
       viewName: Pain Points
       pos: { x: 6, y: 4, w: 6, h: 4 }
-
-seedEntities:
-  - profileSlug: mission
-    title: Example Mission
-    properties:
-      statement: "Example — replace this: we help [audience] [change] so they can [outcome], starting now because [why now]."
-      time-horizon: 3 years
-      status: active