How the business runs — demand to books across three entities (as of 2026-07)

How the business runs — demand to books across three entities (as of 2026-07) An architecture diagram generated by Mosofin. Demand · CRM · HubSpot · pipeline · Shared operating stack — one instance serves all three entities · customers · HubSpot Demand · CRM HubSpot · pipeline customers Commerce · Shopify · orders · tax · Shared operating stack — one instance serves all three entities · orders SoT · Shopify Commerce Shopify · orders · tax orders SoT Suppliers · vendors · lead times · Shared operating stack — one instance serves all three entities Suppliers vendors · lead times Supply chain · ERP · purchase orders · BOM · Shared operating stack — one instance serves all three entities · cost SoT Supply chain · ERP purchase orders · BOM cost SoT Inventory · 3PL · warehouse · fulfilment · Shared operating stack — one instance serves all three entities · units Inventory · 3PL warehouse · fulfilment units Payments · Stripe · fees · payouts · Architecture component · Stripe Payments Stripe · fees · payouts Spend · AP · bills · cards · approvals · Architecture component · approval gate · ramp.com Spend · AP bills · cards · approvals approval gate Payroll · HR · wages · taxes · Architecture component · Gusto Payroll · HR wages · taxes Bank · operating accounts · Architecture component · cash SoT · Chase Bank operating accounts cash SoT Books — Entity A · QuickBooks company A · Separate books — one entity per ledger, never consolidated here · books SoT · QuickBooks Books — Entity A QuickBooks company A books SoT Books — Entity B · QuickBooks company B · Separate books — one entity per ledger, never consolidated here · books SoT · QuickBooks Books — Entity B QuickBooks company B books SoT Books — Entity C · QuickBooks company C · Separate books — one entity per ledger, never consolidated here · books SoT · QuickBooks Books — Entity C QuickBooks company C books SoT Close · reporting · controller · per entity · Architecture component · owner Close · reporting controller · per entity owner accounts purchase orders receipts · COGS available to sell charge net payout vendor bills payment run wages · taxes bank feed bank feed bank feed sales + tax collected closes the period Shared operating stack — one instance serves all three entities Separate books — one entity per ledger, never consolidated here Legend Commerce Payments Ledger Bank Control Counterparty

Source of truth per domain

  • • Customers and pipeline: CRM · Orders and tax collected: Commerce
  • • Cost, purchase orders and inventory: ERP / WMS
  • • Settled cash: the bank · Revenue, AP, payroll and P&L: QuickBooks

Guardrails

  • • The operating stack is shared; the ledgers are not — one entity per company file
  • • No consolidation is drawn: eliminations are a separate, stated decision
  • • No amounts, balances or unit counts shown — none were supplied for 2026-07

How to read it

  • • Solid emphasis is the money rail: order → charge → payout → bank → books
  • • Dashed lines carry facts that are not cash: stock, COGS, sales sync
  • • Red-outlined nodes are approval gates — spend and payroll leave cash only through them