DK Enterprise OS v0.4 - Complete Data Model & Implementation Guide
Executive Summary
Version: 0.4.0
Date: September 2025
System: Coda-based Personal Enterprise Resource Planning (ERP)
Purpose: Memory-first operational system for solopreneur service business with automation focus
What’s New in v0.4
Introduced Engagements table for commercial relationship tracking Added Deliverables and Results tables for outcome management Consolidated redundant tables (Activities + Outreach → Touchpoints) Clarified Service Blueprint framework implementation Added Workflows as discrete operational procedures Separated Process Templates from Resource Templates Removed redundant tables (Backlog, Opportunities, Launch Checklist) Core Concepts & Patterns
The Universal Business Pattern
Every business activity follows this hierarchy:
VENTURE (Business Line)
↓
OFFER (Value Proposition)
↓
ENGAGEMENT (Active Commercial Relationship)
↓
PROJECT (Work Container)
↓
TASKS (Executable Actions)
↓
DELIVERABLES (Work Products)
↓
RESULTS (Measured Outcomes)
The Three Perspectives Framework
1. Business Architecture (Strategic)
What you do and sell
Ventures: Your business lines Offers: Your products/services Service Blueprints: Complete journey maps Workflows: Step-by-step procedures Templates: Reusable resources 2. Commercial Management (Revenue)
Who you serve and how you earn
Organizations & People: Your market Engagements: Active client relationships Deliverables: What you produce Results: Outcomes achieved 3. Execution Management (Operational)
How you get work done
Projects: Work initiatives Sprints: Time-boxed periods Daily Thread: Continuity system Service Blueprint Framework
Service Blueprints map the complete service experience across five layers:
Customer Actions: What the customer does Frontstage: Visible interactions with customer Backstage: Behind-the-scenes work Support Processes: Systems and tools that enable service Evidence: Physical/digital artifacts customer receives This framework applies to ALL services—from automation audits to SaaS products to newsletters.
Table Structure & Relationships
1. Core Lookup Tables (Canonical References)
DB Outcomes
Purpose: Define types of work and their billable nature
DB Topics
Purpose: Hierarchical tagging system for content and market categorization
DB Areas
Purpose: Functional domains representing different roles/hats you wear
2. Business Architecture Tables
DB Ventures
Purpose: Top-level business lines or major initiatives
DB Offers
Purpose: Specific products or services sold within ventures
DB Service Blueprints
Purpose: Complete journey maps for service delivery
DB Workflows
Purpose: Discrete, repeatable procedures within service blueprints
DB Process Templates
Purpose: Reusable process checklists and procedures
DB Resource Templates
Purpose: Actual document/asset templates (formerly Templates)
3. Commercial Management Tables
DB Organizations
Purpose: Companies and organizations in your network
DB People
Purpose: Individual contacts and relationships
DB Deals
Purpose: Sales pipeline and opportunities
DB Engagements
Purpose: Active commercial relationships (NEW in v0.4)
DB Deliverables
Purpose: Actual work products delivered (NEW in v0.4)
DB Results
Purpose: Measurable outcomes from engagements (NEW in v0.4)
DB ICP Segments
Purpose: Ideal Customer Profile definitions
DB Touchpoints
Purpose: All CRM interactions (Merged Activities + Outreach Log)
4. Execution Management Tables
DB Projects
Purpose: Work containers for both client and internal initiatives
DB Tasks
Purpose: Executable work items
DB Sprints
Purpose: Time-boxed work periods (weekly)
DB Daily Thread
Purpose: Daily continuity and memory system
5. Knowledge & Learning Tables
DB Ideas
Purpose: Capture and develop potential initiatives
DB Experiment Log
Purpose: Hypothesis-driven testing framework
DB Decision Journal
Purpose: Document important decisions with context
DB Resources
Purpose: Reference materials and tools
DB Template Performance
Purpose: Track effectiveness of templates
DB KPIs
Purpose: Key performance indicators tracking
DB OKRs
Purpose: Objectives and Key Results
DB Prompt Library
Purpose: Reusable AI prompts
6. Financial Tables
DB Finance Snapshot
Purpose: Financial health tracking
DB Expenses
Purpose: Track spending
Key Formulas
Inheritance Formulas
Projects → Type: If(Engagement.IsNotBlank(), "Client Delivery", [Type])
Projects → Billable: Engagement.IsNotBlank() OR Type = "Client Delivery"
Projects → Revenue Expected: Engagement.[Contract Value] / Engagement.Projects.Count()
Tasks → Type: Project.Type
Tasks → Billable: Project.Billable
Sprint Calculations
Planned Billable Hrs: Tasks.Filter(Sprint = thisRow AND Project.Billable = true).Sum([Estimate (hrs)])
Planned Learning Hrs: Tasks.Filter(Sprint = thisRow AND Project.Type = "Learning").Sum([Estimate (hrs)])
Billable %: If([Capacity (hrs)] = 0, 0, [Planned Billable Hrs] / [Capacity (hrs)])
Learning Over Cap: [Planned Learning Hrs] > [Learning Cap]
Financial Calculations
Runway Weeks: If([Monthly Burn] > 0, [Cash On Hand] / [Monthly Burn] * 4.33, 0)
Deal Weighted Value: [Value (Est)] * [Probability]
Project Margin: [Revenue Expected] - [Expense Actual]
Organization LTV: Engagements.Filter(Organization = thisRow).Sum([Contract Value])
Active MRR: Engagements.Filter(Status = "Active").Sum([MRR])
Pipeline Value: Deals.Filter(Stage != "Won" AND Stage != "Lost").Sum([Value (Est)])
Performance Metrics
Engagement Health: Average([NPS Score]/2, [Deliverables].[Approval Status = "Approved"].Count() / [Deliverables].Count() * 5)
Template Response Rate: [Touchpoints Using Template].Filter([Reply Received] = true).Count() / [Touchpoints Using Template].Count()
Experiment ROI: ([Actual Results Value] - [Cost]) / [Cost]
Task Velocity: [Actual (hrs)] / [Estimate (hrs)]
Implementation Guide
Phase 1: Foundation (Day 1)
DB Outcomes (4 rows: Billable, Pre-Revenue, Learning, Ops) DB Topics (create hierarchy for Industries, Channels, Personas, Tools) DB Areas (your functional domains) Build Business Architecture Set Up Core Relationships Ventures → Offers (one-to-many) Offers → Service Blueprints (one-to-many) Service Blueprints → Workflows (one-to-many) Workflows → Resource Templates (many-to-many) Phase 2: Commercial Layer (Day 2)
Connect Commercial Relationships Organizations → People (one-to-many) Organizations → Deals (one-to-many) Deals → Engagements (one-to-one when won) Engagements → Deliverables (one-to-many) Engagements → Results (one-to-many) Phase 3: Execution Layer (Day 3)
Set Up Work Relationships Engagements → Projects (one-to-many) Projects → Tasks (one-to-many) Sprints → Tasks (one-to-many) Tasks → Deliverables (many-to-one) Phase 4: Knowledge & Optimization (Day 4)
Phase 5: Views & Dashboards (Day 5)
Enterprise HQ (command center) Pipeline Board (Deals by stage) Active Engagements (client work) Sprint Board (Tasks by status) Daily Thread (today’s focus) Financial Health (runway, MRR, burn) Pipeline Metrics (value, velocity, conversion)