Client Analysis

Analysis Process Overview

Every project starts with a thorough analysis of the client’s needs. We never write code without fully understanding the business requirements. This process ensures that the first version of the system matches real client needs.

Evidence-first: the only accepted sources are recorded meetings with screen sharing and e-mails. Every requirement must carry source: meeting:<date>#<timestamp> or email:<message-id>. Store transcripts (e.g. in openspec/evidence/) and link to the exact time/e-mail section in each specification.

graph TD
    subgraph "Phase 1: First Contact"
        A["Intro meeting"] --> B["Understand the business"]
        B --> C["Identify stakeholders"]
    end

    subgraph "Phase 2: Deep-Dive"
        C --> D["Discovery workshops"]
        D --> E["Process mapping"]
        E --> F["Requirements collection"]
    end

    subgraph "Phase 3: Documentation"
        F --> G["Business Requirements"]
        G --> H["Gap Analysis"]
        H --> I["Solution Proposal"]
    end

    subgraph "Phase 4: Validation"
        I --> J["Client review"]
        J --> K{Approved?}
        K -->|No| D
        K -->|Yes| L["Handover to development"]
    end

Process Phases

Phase	Goal	Outputs
First Contact	Understand overall context	Meeting notes, stakeholder map
Deep-Dive Analysis	Detailed process understanding	Workshop records, process maps
Gap Analysis	Map requirements to the system	Gap Analysis Report
Validation	Approval and handover to delivery	Project Charter

Analysis Artifacts

Document	Required	Template
Meeting notes	Yes	templates/meeting-notes.md
Stakeholder map	Yes	templates/stakeholder-map.yaml
Workshop records	Yes	templates/workshop-record.yaml
Process maps	Yes	Mermaid diagrams
Requirements list	Yes	templates/requirements.yaml
Gap Analysis	Yes	templates/gap-analysis.yaml
Solution Proposal	Yes	templates/solution-proposal.yaml
Project Charter	Yes	templates/project-charter.yaml

---

➡️ Continue with First Contact for the first analysis phase.