Skip to content

Instantly share code, notes, and snippets.

@anhedonix
Last active October 29, 2024 07:58
Show Gist options
  • Select an option

  • Save anhedonix/3bcddc8660a6006913dddb9b95cd09b0 to your computer and use it in GitHub Desktop.

Select an option

Save anhedonix/3bcddc8660a6006913dddb9b95cd09b0 to your computer and use it in GitHub Desktop.
2024 10 29 - Marvel Vinyls Meeting - Web Dev

Marvel Vinyls Meeting

Online Google hangouts meeting with Marvel Vinyls and Morpheus Plus.

1. Meeting Structure & Flow

  • A loose schedule for the <2-hour meeting:
    • Introduction (5 mins)
    • Requirement gathering & scope finalization (20-30 mins)
    • Deliverables & solutions overview (10-15 mins)
    • Pricing discussion (10-15 mins)
    • Final wrap-up (10-15 mins)
  • Plan checkpoints to confirm the client’s agreement before moving on (e.g., “Does this design match your vision?”).

2. Client's Goals and Expectations

  • Clarify the client's main focus: Performance improvements (loading speed, security, code issues) vs. a full design overhaul (UI/UX).

    From previous discussion:

    • Optimize website design to be more modern and easy to use.
    • Provide interface for showcasing employees. (Need details on level of detail shown to public vs internal parties).
  • Clarify client's Branding related details. Personality, tone, PR specifications, presence and relevant details.

  • Ask about CMS/platform/framework preferences if not already finalized, provide suggestions as required.

  • Inquire if they have competitors or reference websites they like to align the design/technical work more closely with their vision.


3. Communication

  • Ensure we have the client's mobile numbers/email as backup.
  • Identify points of contact for Technical, Artistic, and Informational queries during the meeting.

4. Post-Meeting Follow-up

  • Send Marvel Vinyls post-meeting summary email with clear action points, pricing, and deliverables.
  • Set a soft deadline for client feedback/questions post-meeting to keep the project moving forward.
flowchart TB
    subgraph Legend
        A[Project Stage]
        B{{Decision Point}}
        C[(Deliverable)]
        D[/Client Input/]
    end

    Start((Project Start)) --> Init[Project Initialization]
    Init --> Payment1[/Initial Payment - 50% of Fixed Fee/]
    
    subgraph Stage1[Stage 1: Requirements & Design]
        direction TB
        S1[Requirement Gathering] --> S1D{{Design Approval}}
    end

    subgraph Stage2[Stage 2: Static Implementation]
        direction TB
        S2[Static Website Development] --> S2D{{Static Site Approval}}
    end

    subgraph Stage3[Stage 3: Backend Implementation]
        direction TB
        S3[Backend Infrastructure Setup] --> S3D{{Technical Approval}}
    end

    subgraph Stage4[Stage 4: Dynamic Integration]
        direction TB
        S4[Dynamic Features Implementation] --> S4D{{Integration Approval}}
    end

    subgraph Stage5[Stage 5: Documentation & Handover]
        direction TB
        S5[Documentation Creation] --> S5D{{Final Approval}}
    end

    subgraph Maintenance[Ongoing Maintenance]
        direction TB
        M1[Monthly Services] --> M2[Optional Services]
    end

    Payment1 --> Stage1
    Stage1 --> Stage2
    Stage2 --> Payment2[/Remaining 50% of Fixed Fee/]
    Payment2 --> Stage3
    Stage3 --> Stage4
    Stage4 --> Stage5
    Stage5 --> Maintenance

    style Start fill:#4CAF50
    style Stage1 fill:#2196F3
    style Stage2 fill:#2196F3
    style Stage3 fill:#2196F3
    style Stage4 fill:#2196F3
    style Stage5 fill:#2196F3
    style Maintenance fill:#9C27B0
    
Loading
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment