Three-person agency
A Monday plan that survives the week
How a tiny agency turns scattered client commitments into one ICE-scored weekly plan that is generated automatically every Monday morning.
- Notion
- Google Calendar
- Slack
- Gmail
Illustrative scenario. These walkthroughs describe how Founder OS is designed to be used. They are composites written by us — not real customer accounts, and they contain no measured results, testimonials or client names.
Before
The situation
Three people, nine active clients. Every Monday the team spends the first hour rebuilding a shared plan from Notion pages, inboxes and last week's leftovers — and by Wednesday the plan no longer matches reality, so it gets abandoned.
Where the week leaks
- Client commitments arrive by email and Slack and never make it into the plan.
- Priorities are argued from opinion because nothing scores the work.
- Calendar load is invisible while planning, so the week is over-committed by Tuesday.
- The plan is a document, so nothing notices when it goes out of date.
What Founder OS does
Step by step
This scenario leans mostly on weekly planner + notion and calendar sources.
- 01
Let the planner run before anyone is awake
A scheduled job generates the weekly plan every Monday at 08:00 from current company state — open projects, live goals, unfinished tasks and last week's carry-over — so the week starts with a draft instead of a blank page.
- 02
Score the work instead of debating it
Candidate tasks are ranked with ICE (impact, confidence, effort) against the goals actually recorded in state. Disagreement moves from “what matters more” to “is this score right”, which is a much shorter conversation.
- 03
Plan against real calendar capacity
The Google Calendar source feeds meetings and blocks into state, so the plan is built against the hours that actually exist rather than an imaginary empty week.
- 04
Keep the plan alive after Monday
As tasks close and new commitments are observed, the plan is updated in place and mirrored back into Notion. Nothing needs to be re-typed for the plan to stay true.
After
What changes
Described as behaviour, not as percentages — we do not publish numbers we have not measured.
- Monday starts with a reviewable draft plan, not an empty document.
- Prioritisation is explicit and reproducible instead of loudest-voice-wins.
- Over-commitment is visible at planning time, not on Thursday.
- The plan and the client tools stop drifting apart mid-week.
Other scenarios
Solo SaaS founder
Six tools, one company state
How a one-person SaaS keeps goals, tasks and decisions consistent across Obsidian, GitHub, Stripe and Calendar without a weekly manual clean-up.
Read itIndie developer
Support triage without a support team
How one developer handles a growing support load with agents that draft, classify and escalate — while every irreversible action still waits for a human.
Read itOr read the mechanics behind all of them in the Founder OS feature breakdown.
Start with one source of truth
Connect your first tool, let the engine build your company state, and see what one system that knows everything actually feels like.
Free tier, no credit card. We reply to every message within 24 hours on business days.