Day 10 Summary Service launch summary

Day 10. Launching the Service Course Summary

The last day of the 10-day journey - a full wrap-up of releasing the finished service, supporting users and looking back on the project.

📌 Part 1. Background - why Day 10 is the service launch

Looking back on the 10-day flow, the most natural ending is releasing the service to the world. No matter how great a service is, nobody uses it if it isn't introduced well to users.

DayTopicKey activity
Day 1~2PlanningIdea → business model
Day 3~4Requirements/designERD, API spec, wireframes
Day 5~6UI/screen developmentBuilding pages + Codex screen debugging
Day 7Finishing featuresAPI integration, event handling
Day 8Member serviceSign-up/login/onboarding UX
Day 9Payment servicePayment flow, reassuring errors, trust UI
Day 10Service launch ✅Introduction, FAQ, retro, presentation

📌 Part 2. General AI vs Codex Workspace

Work areaGeneral AI (chat)Codex Workspace (linked to the work folder)
Service introductionGives a generic SaaS introduction templateReads day10_service_overview.md and creates a tailored introduction with the real service name, features and audience
Writing FAQs20 generic app FAQ examplesAnalyzes the list of features actually built and creates questions specific to the service
Results reportA generic project report formReads day10_project_summary.md and writes a specific report reflecting the real development process and results
Version 2.0 roadmapLists generic feature improvement ideasAnalyzes finished/unfinished features, then gives a sprint plan with MoSCoW priorities and team size applied

📌 Part 3. Mapping of lab outputs

  • Task 01: day10_launch_materials.md — introduction + opening notices per channel + draft terms of use
  • Task 02: day10_faq_guide.md — 20 FAQs (5 categories) + 5 customer support scenarios
  • Task 03: day10_retrospective.md — results report + Keep/Problem/Try retro + MoSCoW roadmap
  • Mission 01: day10_launch_package.md — complete launch package combining all materials
  • Mission 02: day10_presentation.md + day10_v2_roadmap.md — final slides + 3-month sprint plan

📌 Part 4. Service launch journey diagram

[Service finished] ➔ (define the core value in one line) │ ▼ (Task 01: introduction + notices per channel + terms of use) [Prepare launch materials] ➔ (so users understand within 5 seconds) │ ▼ (Task 02: 20 FAQs + support scenarios) [Prepare user support] ➔ (head off the flood of first-day questions) │ ▼ (Task 03: results report + retro + roadmap) [Sum up the project] ➔ (share results with investors and stakeholders) │ ▼ (Mission 01: combine everything) [Launch package done] ➔ (ready to release today) │ ▼ (Mission 02: 10-minute talk + Q&A) [Final presentation] ➔ "The next project starts with Version 2.0"

📌 Part 5. Instructor guidance (discussion topics)

  1. The future of communicating with AI: "What was the most surprising moment working with Codex over 10 days? In what work do you think you'll use AI most from now on?"
  2. Planner vs developer views: "Preparing the launch, what felt most different between the developer's and planner's views?"
  3. If you built Version 2.0: "If this project continued for 3 more months, what one feature would you most want to add?"
  4. Limits of AI teamwork and how to overcome them: "Did Codex ever lead you in the wrong direction? How did you fix it?"

📌 Part 6. Day 10 key message

💡 "AI isn't just a tool; it's a partner you plan with."

Day 10 isn't just the end of a project. It completes the course by doing a real service planner's work with AI (Codex): service launch → user support prep → sharing results → retro and next planning. Writing the final Version 2.0 roadmap isn't the end of the course but the start of the next project.

← Back to Day 10 main classroom