Service Analysis
Reverse-engineer user value, core flows and growth structure with evidence and metrics.
It doesn't stop at learning AI tools. In this hands-on course you analyze how a service grows, write design documents, build a real MVP, and present a POC and your final project.
Program Outcomes
AI does not build things for you. You learn to set goals and standards yourself and use AI as a partner for analysis, design, building and testing.
Reverse-engineer user value, core flows and growth structure with evidence and metrics.
Turn requirements, data, APIs, screens and done criteria into consistent documents.
Use Codex and Antigravity to build a product whose core user flow works.
Use test evidence and feedback, then demo the product's problem, solution and value.
Week 1 · Foundation & Guided Practice
In week 1 you set up a stable dev environment, then work through service analysis, AI design, document-driven building and backend integration in order.
Understand the goals and outputs of the 10-day course, and make sure every student starts on the same dev environment.
Analyze a finished service not as a feature list, but as a structure linking user value, behavior flow and growth metrics.
Don't jump straight into coding. Design requirements, data, APIs, screens and test criteria with AI first.
Use design documents as input for code generation, and build in small testable features instead of everything at once.
Separate data responsibilities behind the screen and build a simple server integration with Apps Script and Google Sheets.
Week 2 · Team Project & Delivery
In week 2 your team shares one product goal, leaves a result you can check each day, and finishes a project ready for the final presentation.
Agree on your team's problem, users, scope and roles, and make a realistic 5-day plan.
Agree on the screen, data and API structure of the core user flow, and get feedback from peers and instructors before building.
Build the most important user flow so it works from start to finish, and verify screens, logic and data connections.
Demo a real working POC, and list the defects and messages you must fix before the final presentation.
Clearly show the value of your finished project and how you built it, and define the next steps to grow it.
Core Toolchain
The goal isn't to memorize tool names — it's to use each tool safely at the right stage of development.
A development partner that understands the codebase, builds, investigates errors, tests and reviews.
A development environment for quickly building and iterating on screens and features from design documents.
Reviews long documents and alternatives, and structures requirements, designs and presentation messages.
Connects planning, engineering, design and QA reviews into the development flow.
Completion Checklist
The size of your final output matters less than whether problem, design, build and testing are connected — and whether your team can explain its decisions and reasons.