Cases and retrospectives

Turn experience into assets

Retrospectives are not summaries; they turn experience into “assets that can be reused directly next time.” At the same time, understanding the paths others have taken is 10 times faster than figuring it out yourself.

Three super-individual prototypes

Indie Hacker type
One person · A small set of products · Ads / subscription

Operate multiple narrow niche small products simultaneously (in a Nomad List / PhotoAI style), reducing maintenance costs with shared infrastructure and templates. The core capability is productization speed + SEO compounding.

Monthly passive income > operating costs
3 to 5 products share the same tech stack
Highly automated, with humans handling only edge cases
Independent consultant / hands-on support
Single-client, high-ticket · Professionally verifiable · Quarterly delivery

Serve a small number of high-value clients and charge monthly / quarterly. In the early stage, build trust with 1–2 public case studies, and attract similar clients through precise content. The core capability is quantifiable professional results.

Average order value: 50,000–500,000 RMB range
Customers mainly come from referrals / content
Able to stay in the same field for 3-5 years
Content + product hybrid
Writing / Video → Trust → Courses / Tools / Community

Use content as the traffic entry point, build authority in a niche field, and then package experience into courses, tools, or private communities. The core capability is consistent output + productizing experience.

Content views / subscriptions steadily increasing
Multiple revenue curves funnel traffic into one another
The core asset is the reader's trust

Assetizing outcomes · Four repositories

If you organize the outputs of each project into these four repositories, after 3-6 months you'll have a "replicable system".

Delivery template library

Reusable skeletons for PRD / proposals / reports / contracts / acceptance documents.

Code and script repository

Frequently used automation scripts, utility functions, Skill configurations, and Agent flows.

Content and portfolio

Blog posts, videos, demos, case studies — let the next batch of customers find you on their own.

SOPs and checklists

Standard operating procedures for kickoff / project delivery / after-sales follow-up / retrospective.

Weekly review checklist (30 minutes recommended)

What did you do this week? What can be reused?
Which actions produced results? Which ones were just busywork?
What is a "minimal change"? Next week, change only this one thing.
Turn outputs into: templates / checklists / scripts / pages / code snippets.

Monthly Review Checklist (90 minutes recommended)

What was the biggest “result” this month? Review the complete decision-making chain.
Which customers / projects are actually profitable? Which ones are loss leaders?
Content / product / service, which line is growing? What is the reason?
Next month, do only 3 things and delete the rest.

Do it today: a 30-minute action

  • Create a new "Asset Library" in the notes, and divide it into four folders at the top;
  • Put the best deliverable created in the last 2 months back into the corresponding folder;
  • Write one sentence: "How can this output be reused next time?";
  • Starting next week, set aside a fixed 30 minutes every Friday for a weekly review.