The Core Operational Engine
After a deal is won in the CRM, the real work begins. This guide shows how to build the Project Delivery Function, the most critical part of LAIKA’s operating system. This single Function will manage a project’s entire lifecycle, from the initial planning phase through design, construction, and final invoicing, creating a single source of truth for the entire delivery team.As before, you can switch between the Blueprint tab for design specs and the Build Tutorial tab for hands-on instructions.

1. Function & Scope

  • Function Name: Project Delivery
  • Scope: To manage all post-sale activities for a client project, unifying the Design, Site, and Finance teams into a single, cohesive workflow.

2. Universal Objects & Data Fields

This function uses a central “hub” Object with several supporting “spoke” Objects.
  • Project (The Hub): The central record for a client engagement.
    • Fields: Project Name (Text), Client (Object Connection to Contact), Total Budget (Currency), Start Date (Date), End Date (Date).
  • Design Concept: Tracks a specific creative design and its approval cycle.
    • Fields: Version (Text), Status (Workflow), Design File (Attachment).
  • Site Report: A report filed from the construction site.
    • Fields: Report Date (Date), Progress Photos (Attachment), Notes (Text).
  • Invoice: A financial record for a specific payment milestone.
    • Fields: Invoice Amount (Currency), Due Date (Date), Status (Workflow).

3. Object Connections

  • The Project object is the “parent.”
  • Design Concept, Site Report, and Invoice are “children” that are always linked to a specific parent Project.

4. Workflows & Statuses

  • Project Workflow:
    • PLANNINGDESIGNCONSTRUCTIONWARRANTYCOMPLETED
  • Design Concept Workflow:
    • PENDINGIN PROGRESSIN REVIEWAPPROVEDREJECTED
  • Invoice Workflow:
    • DRAFTSENTPAIDOVERDUE

5. Workviews & Dashboards

  • “All Active Projects (List)”: A master list of all ongoing projects.
  • “Project Delivery Timeline”: A timeline/Gantt view of all projects, using their Start and End Dates.
  • “Design Approval Kanban”: A Kanban board for the Design Concept object, grouped by its status.
What’s Next? We have now built the two core Functions for LAIKA’s operation. The next critical step is to connect them. We will use Universal Automation to make the handoff from the Sales team to the Project Delivery team seamless and instant.