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
    %% Project Start and Initial Payment
    Start([Project Start]) --> Init[Project Initialization]
    Init --> Pay1[Initial Payment 50%]
    
    %% Main Stages
    Pay1 --> S1[Stage 1: Requirements & Design]
    S1 --> D1{Design Approval}
    D1 --> S2[Stage 2: Static Implementation]
    S2 --> D2{Static Site Approval}
    D2 --> Pay2[Final Payment 50%]
    Pay2 --> S3[Stage 3: Backend Implementation]
    S3 --> D3{Technical Approval}
    D3 --> S4[Stage 4: Dynamic Integration]
    S4 --> D4{Integration Approval}
    D4 --> S5[Stage 5: Documentation & Handover]
    S5 --> D5{Final Approval}
    D5 --> M[Maintenance Phase]
    
    %% Maintenance Breakdown
    M --> MS[Monthly Services]
    M --> OS[Optional Services]
    
    %% Styling
    classDef stage fill:#2196F3,color:white
    classDef decision fill:#FFA726,color:white
    classDef payment fill:#4CAF50,color:white
    classDef maintenance fill:#9C27B0,color:white
    
    class S1,S2,S3,S4,S5 stage
    class D1,D2,D3,D4,D5 decision
    class Pay1,Pay2 payment
    class M,MS,OS maintenance
Loading
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment