This document serves as the architectural blueprint for the entire global-level configuration of the Luklak system for LAIKA. It is the single source of truth for all cross-functional relationships, reporting structures, and automations.

​
PART 1: STRUCTURE, NAVIGATION & REPORTING

​
1.1. Unified Organizational Structure

This diagram details the complete hierarchical structure of Areas, Spaces, Functions, and Object Types for LAIKA. 
LAIKA (Organization)
│
├── 📂 MARKETING (Area)
│   └── ⏹️ Marketing Campaigns (Space)
│       └── 📋 Function: Marketing Campaigns
│           ├── 🧊 Campaign
│           │   └── 🧊︎ Ad (Sub-Object)
│           ├── 🧊 Event
│           └── 🧊 Content Production
│
├── 📂 SALES (Area)
│   └── ⏹️ Sales & CRM (Space)
│       └── 📋 Function: CRM
│           ├── 🧊 Customer
│           │   └── 🧊︎ Demo (Sub-Object)
│           └── 🧊 Deal
│               └── 🧊︎ Proposal (Sub-Object)
│
├── 📂 ACCOUNTING (Area)
│   └── ⏹️ Contracts & Receipts (Space)
│       └── 📋 Function: Accounting
│           ├── 🧊 Contract
│           └── 🧊 Receipt
│
├── 📂 PROJECT DELIVERY (Area)
│   ├── ⏹️ Project Management (Space)
│   │   └── 📋 Function: Project Management
│   │       ├── 🧊 Project
│   │       │   ├── 🧊︎ Design (Sub-Object)
│   │       │   ├── 🧊︎ Construction (Sub-Object)
│   │       │   └── 🧊︎ Acceptance (Sub-Object)
│   │       └── 🧊 Task
│   └── ⏹️ Field Operations (Space)
│       └── 📋 Function: Field Operations
│           └── 🧊 Site Survey
│
├── 📂 CUSTOMER SUCCESS (Area)
│   └── ⏹️ Customer Care (Space)
│       └── 📋 Function: Customer Care
│           └── 🧊 Customer Care
│
└── 📂 HUMAN RESOURCES (Area)
    └── ⏹️ HR Operations (Space)
        └── 📋 Function: HR Management
            ├── 🧊 Employee
            └── 🧊 Request

​
PART 2: OBJECT CONNECTIONS

This section defines the critical relationships between different Object Types across the entire system, enabling a 360-degree view of operations.
Source Object TypeRelationship TypeDestination Object TypeDescription & Purpose
CRM.CustomerOne-to-ManyCRM.DealConnects a Customer to their active Deals, providing a complete sales funnel view.
CRM.DealOne-to-OneAccounting.ContractLinks a closed-won Deal to its corresponding legal Contract for financial tracking.
Accounting.ContractOne-to-OneProject.ProjectAssociates a signed Contract with the Project to be delivered, ensuring seamless handover.
Project.ProjectOne-to-ManyProject.TaskBreaks down a master Project into actionable Tasks for team members.
Project.ProjectOne-to-OneCS.Customer CareConnects a completed Project to a post-delivery customer care cycle for support and retention.
CRM.CustomerOne-to-ManyProject.ProjectProvides a complete history of all projects delivered for a specific Customer.

​
PART 3: GLOBAL AUTOMATIONS

These automation rules operate across different ⏹️ Spaces and 📋 Functions to ensure a smooth, uninterrupted flow of information and value.
laika-sequence-level1-en.png
IDRule NameTriggerActionLogic Description
CF-01Deal Won → Create ContractStatus Change: CRM.Deal / Status “CONTRACT SIGNED”Create: Accounting.ContractAutomatically generates a Contract Object and links it to the source Deal when a sale is successfully closed.
CF-02Contract Signed → Create ProjectStatus Change: Accounting.Contract / Status “SIGNED”Create: Project.ProjectKicks off the delivery process by automatically creating a Project Object once the customer signs the contract.
CF-03Project Complete → Initiate Customer CareStatus Change: Project.Project / Status “COMPLETED”Create: CS.Customer CareEnsures a smooth handover to the support team by creating a customer care cycle as soon as a project is finished.
CF-08Calculate Project Profit MarginUpdate: Project.Project / Fields “Total Revenue” OR “Total Cost”Update: Project.ProjectInstantly calculates and updates the “Profit Margin” field on the Project whenever revenue or cost figures are changed.
CF-11Calculate Customer Lifetime Value (LTV)Status Change: Project.Project / Status “COMPLETED”Update: CRM.CustomerAutomatically calculates and updates the voucher value on the original Customer Object.
CF-13Periodic Care & Voucher DispatchBackground Rule: Scheduled (runs every 2 months) on CS.Customer CareSend: Email to CustomerAutomatically sends a follow-up email, potentially including a discount voucher stored on the CRM.Customer Object.

​
PART 4: USER & ACCESS MANAGEMENT

​
4.1. Global Roles

Role NameDescription & Responsibilities
Marketing ManagerManages campaigns, advertising budgets, and overall marketing performance.
Sales ExecutiveNurtures and advises customers, responsible for closing deals.
Project ManagerCoordinates the entire project lifecycle, ensuring on-time, high-quality delivery.
Design LeadResponsible for the quality and creative direction of all design work.
Site SupervisorOversees all survey and construction activities on-site.
AccountantManages contracts, accounts payable/receivable, and financial matters.
Customer Care AgentProvides post-project support and manages customer relationships.

​
4.2. Global Permission Scheme

  • Default Implementation: The system will utilize Luklak’s standard, out-of-the-box Permission & Notification scheme as the default setting.
  • Note: More granular permission adjustments will be configured at the 📋 Function and ⏹️ Space levels to meet specific team requirements.