2
1 Comment

How I close out a work week in one question using FoundersOS

Coming from a product background, I always liked the retro around how a sprint or release went. When using FoundersOS with Claude, I thought it would be cool to have a similar retro each week on how the week went. So, we wired the retro into Founders OS. Now I ask one thing at the end of the week: "give me my weekly retro." It reads across the whole business and hands back one picture:

what I actually finished versus what slipped
cash that came in and went out, and which invoices are still open
who I interacted with and which client threads went quiet
what has been sitting stuck long enough that it needs a decision Monday

The point is not that any one of those is hard to look up. It is that the answer joins all of them. "This task stalled, the client tied to it hasn't been contacted in nine days, and their invoice is still unpaid" is the kind of sentence I never got when each system lived in its own tab. One question, four domains, straight answer. Also helps me setup the next week.

It works with Claude, Cursor, or any MCP client, and it is open source and live today.

Curious how other builders here run their weekly retro. Do you have one system that sees the whole week?

Repo: https://github.com/OurThinkTank/founders-os
Site: https://foundersmcp.com
npm: @ourthinktank/founders-os

on July 17, 2026
  1. 1

    The interesting value isn't generating a weekly retro with AI—it's surfacing relationships between disconnected business signals that would otherwise stay invisible. I'd keep validating whether founders return because it saves them time or because it consistently highlights the next decision they didn't realize they needed to make. That's a much stronger product.