Use-case recipes
Six worked examples of FoundersOS plus Cowork plus connectors. Each is the same handful of blocks snapped together a different way - copy one and adjust.
These are recipes, not rules. Each one is the same set of building blocks - FoundersOS tools, a connector or two, maybe a schedule - snapped together for a specific job. Like Lego: once you see how a few combine, you’ll start inventing your own. Every recipe ends with an “experiment from here” nudge for exactly that.
1. Hunt and win new work
Goal: find high-fit opportunities and turn the best into drafted proposals.
Blocks: Claude in Chrome + web search + memory + tasks + a playbook.
Flow: a playbook searches and scrapes listings, loads your scoring criteria from memory, scores each find against your sweet spot, files tasks for strong matches and drafts proposals for the exceptional ones, then writes a retro back to memory so the scoring rubric sharpens every run.
Experiment from here: point it at a different source, or have it open a draft email through your mail connector instead of a task.
2. Weekly ops autopilot
Goal: stay on top of the boring-but-important without remembering to.
Blocks: a scheduled task + a health-check connector (e.g. your database advisors) + Slack + the weekly retro.
Flow: on a fixed day each week, a scheduled task runs the checks, posts the findings to a channel, and turns your completed work into a retro you can drop straight into a build-in-public post.
Experiment from here: change the cadence, add a second check, or route the digest to email instead of chat.
3. Morning briefing
Goal: one glance that orients your whole day.
Blocks: get_session_start composing tasks, finance, CRM, and feeds.
Flow: “catch me up” pulls overdue and due-today tasks, the AI work queue, a finance pulse, cold customers, and unread feed headlines into a single view - a live widget in Cowork, a clean table on a local model.
Experiment from here: schedule it to land in your inbox at 6am, or pin it as a persistent artifact you reopen each morning.
4. Close-the-loop CRM
Goal: never let a conversation evaporate.
Blocks: Slack or email + interactions + tasks + memory.
Flow: a chat thread or inbound email becomes a logged interaction on the customer, a linked follow-up task so nothing slips, and a stored takeaway (the price they pushed back on, what they care about) for next time.
Experiment from here: add a playbook that runs your full onboarding sequence the moment a customer moves to “won.”
5. Research pipeline
Goal: build a backlog of validated ideas instead of one-off searches.
Blocks: web search + Claude in Chrome + memory + a project.
Flow: each run researches a space, deepens or adds to what you already found (recalled from memory), and files results under a research project so the backlog compounds rather than resets.
Experiment from here: schedule it weekly so the pipeline fills itself, or have it draft a one-pager for the strongest find.
6. Revenue pulse
Goal: answer “how’s the money?” in plain English.
Blocks: a billing connector (e.g. Stripe or RevenueCat) + the financial tools.
Flow: pull subscription and payment data alongside your ledger, and ask for a P&L, a month-to-date summary, or “how did we do versus last month?” - no spreadsheet wrangling.
Experiment from here: wrap it in a scheduled task that posts a weekly revenue line to your team channel.
Make your own
Every recipe above is just blocks in an order. Swap a connector, add a step, change the cadence, assign a step to the AI instead of yourself. Experimentation is the point - the worst case is a task that didn’t need doing, and the best case is a workflow you’ll run for years. If you build something good, the community would love to hear about it.