# 1. CLIENT ONBOARDING SNAPSHOT Client Type: Small SaaS startup Service / Project: Complete website redesign Platform: Upwork + Slack + Google Drive Primary Onboarding Objective: Collect the information, assets, approvals, and access required to begin the website redesign without unnecessary delays. Recommended Onboarding Complexity: Structured Reason: A complete website redesign depends on brand assets, existing website information, stakeholder feedback, access permissions, and approval checkpoints. # 2. WELCOME MESSAGE Hi, Thanks for moving forward with the website redesign. Before production begins, we’ll complete a short onboarding process to make sure the project starts with the correct assets, priorities, website access, and expectations in place. Please begin by providing the requested brand materials and website information in the shared Google Drive folder. Project communication can then continue through Slack, while formal project actions can remain documented through Upwork where appropriate. Once the required materials are complete, the project can move into the kickoff stage. Next action: Upload the required website and brand assets to the shared Google Drive folder. # 3. CLIENT INTAKE QUESTIONS Business & Website - What is the primary purpose of the website? - Who is the main target audience? - What are the most important actions visitors should take? - Which existing pages must remain? - Are any new pages required? Brand - Do you have current brand guidelines? - Which fonts, colors, logos, or visual rules must be preserved? - Are there websites whose visual direction you like or dislike? Content - Will existing copy be reused? - Is new copy being supplied? - Are product screenshots, illustrations, testimonials, or case studies available? Approvals - Who gives final design approval? - Are other stakeholders involved before approval? # 4. REQUIRED ASSETS CHECKLIST REQUIRED BEFORE START ☐ Logo files ☐ Brand colors and fonts ☐ Existing website URL ☐ Website/CMS collaborator access ☐ Approved website copy or content status ☐ Product or service information ☐ Required images or media ☐ Primary decision-maker identified USEFUL BUT OPTIONAL ☐ Brand guidelines ☐ Competitor references ☐ Previous analytics insights ☐ Inspiration websites ☐ Customer personas # 5. ACCESS & PERMISSIONS PLAN Potential access required: - Website/CMS collaborator access - Shared Google Drive folder - Relevant design or brand files Use role-based or collaborator access whenever possible. Do not send raw account passwords if a safer invitation-based method is available. # 6. ONBOARDING WORKFLOW STEP 1 — Confirm project scope Owner: Both Purpose: Align on the website redesign requirements. Completion Condition: Core scope and required pages are understood. STEP 2 — Complete client intake Owner: Client Purpose: Capture business, audience, brand, and website requirements. Completion Condition: Required questions are answered. STEP 3 — Upload project assets Owner: Client Purpose: Centralize all necessary material. Completion Condition: Required assets are available in Google Drive. STEP 4 — Confirm access Owner: Both Purpose: Ensure required website systems can be accessed securely. Completion Condition: Necessary collaborator permissions work. STEP 5 — Kickoff Owner: Both Purpose: Confirm priorities, responsibilities, and immediate next steps. Completion Condition: Project is cleared for design work. # 7. KICKOFF MEETING AGENDA - Website objective - Target audience - Required pages - Brand direction - Content readiness - Technical requirements - Approval process - Immediate first milestone # 8. COMMUNICATION PROTOCOL Primary communication channel: Slack Use for: Questions, project updates, and operational communication. Google Drive: Use for project files and assets. Upwork: Use where formal marketplace project documentation is appropriate. VERIFY PLATFORM RULE for any Upwork-specific communication or transaction requirement not supplied here. # 9. EXPECTATIONS & BOUNDARIES - Client supplies required assets and access. - Provider organizes and executes the agreed website redesign. - Missing assets may delay dependent work. - Feedback should be consolidated before approval. - Scope changes should be identified before execution. CONTRACT CHECK: Payment, ownership, cancellation, refund, and formal revision terms should follow the applicable agreement. # 10. MILESTONE FRAMEWORK Milestone: Onboarding Complete What happens: Required information and assets are collected. Client input required: Yes Approval required: No Completion signal: Project is ready for kickoff. Milestone: Initial Design Direction What happens: First design direction is prepared. Client input required: Feedback Approval required: Yes Completion signal: Design direction approved. Milestone: Website Build What happens: Approved direction is implemented. Client input required: As needed Approval required: Yes Completion signal: Build approved for final review. # 11. FIRST-WEEK ACTION PLAN Stage 1 Service Provider: Send intake and asset checklist. Client: Complete required information. Expected Result: Requirements captured. Stage 2 Service Provider: Review materials. Client: Supply missing assets or access. Expected Result: Project dependencies cleared. Stage 3 Service Provider: Prepare kickoff. Client: Confirm priorities. Expected Result: Website redesign ready to begin. # 12. ONBOARDING RISK CHECK Risk: Missing website or brand assets Why it matters: Design work may begin with incomplete information. Prevention: Complete the required asset checklist before kickoff. Risk: Multiple stakeholder opinions Why it matters: Feedback can become conflicting. Prevention: Identify one final decision-maker. # 13. READY-TO-START CHECK ☐ Scope confirmed ☐ Intake completed ☐ Brand assets received ☐ Website access confirmed ☐ Required content status confirmed ☐ Decision-maker identified ☐ Communication workflow established ☐ Project cleared to start # 14. NEXT CLIENT ACTION Upload the required website and brand assets to the shared Google Drive folder.