The AI Ops Stack for
a Lean Startup Team
Most founders use AI for one-off tasks — a draft email here, a quick summary there. The real leverage comes from building AI into your weekly operating rhythm. Here’s the stack: which tasks to systematise, and the prompts that make it work every week.
- The difference between using AI and operationalising it
- The Monday morning AI routine
- Turning meeting notes into action automatically
- The weekly metrics digest
- Drafting first-pass responses for repetitive communication
- The end-of-week reflection prompt
- Building your own prompt library
Using AI vs Operationalising It
Most founders use AI reactively — they hit a task that feels tedious and think “let me try AI for this.” This is useful but limited. The bigger unlock is identifying the recurring tasks in your week and building AI into the routine itself, so it happens automatically rather than being remembered each time.
The shift is from “AI as a tool I sometimes reach for” to “AI as a step in my process.” The second version compounds — every week, the time saved adds up, and the quality of output improves as you refine the prompts.
The best prompts aren’t written from scratch each time. They’re refined over weeks — you notice what’s missing from the output, adjust the prompt, and next week it’s better. Treat your prompts like code: version them, improve them, reuse them.
The Monday Morning AI Routine
Mondays set the tone for the week. A 15-minute AI-assisted routine at the start of the week can replace what might otherwise be an hour of scattered planning.
The routine: review what happened last week (pull from your notes, Slack, or weekly updates), identify priorities for this week, and draft your own communication — a note to the team, a focus list, or both.
“Here’s what happened last week: [paste notes, key events, what got done and what didn’t]. Here’s what’s on my plate this week: [list known commitments and deadlines]. Help me: (1) Identify the 3 priorities that matter most this week given what’s outstanding from last week and what’s coming up, (2) Flag anything from last week that seems to need follow-up but might get missed, (3) Draft a short Monday message to my team highlighting this week’s priorities.”
Turning Meeting Notes Into Action Automatically
Meetings produce decisions and action items that frequently get lost the moment everyone goes back to their work. A simple habit — paste rough notes into a prompt immediately after every significant meeting — turns this into a non-issue.
“Here are my rough notes from a meeting: [paste notes — can be messy, bullet points, fragments]. Extract: (1) Every decision that was made, stated clearly, (2) Every action item, with who owns it if mentioned — flag any that don’t have a clear owner, (3) Anything that was discussed but not resolved and needs follow-up, (4) A 2-sentence summary I could share with someone who wasn’t in the meeting.”
The Weekly Metrics Digest
Most founders look at their metrics dashboard and see numbers without immediately seeing the story. AI can help surface what matters in the numbers — especially useful for spotting trends before they become obvious.
“Here are my key metrics for this week vs last week and the week before: [paste metrics — revenue, signups, churn, usage, whatever you track]. Analyse this: (1) What’s the most important change worth paying attention to, (2) Is there anything that looks like the start of a trend rather than normal week-to-week noise, (3) What questions should I be asking based on this data, (4) Is there anything here that contradicts what I’d expect, and might be worth investigating?”
Drafting First-Pass Responses for Repetitive Communication
Every founder has categories of messages that come up repeatedly — investor questions, customer support escalations, partnership inquiries, candidate responses. Each one feels like it deserves a custom response, and writing each from scratch is a significant time cost.
The solution isn’t templates — templates feel impersonal. The solution is a prompt that generates a first draft tailored to the specific situation, which you then edit. This is faster than writing from scratch and more personal than a template.
“I received this message: [paste the message]. Context: [any relevant background — who this person is, what’s the relationship, any history]. Draft a first-pass response that: addresses what they actually asked, matches a [describe your tone — direct/warm/formal] tone, and is something I can quickly edit rather than needing to rewrite. If there’s anything ambiguous in their message that I should clarify before responding fully, flag it.”
The End-of-Week Reflection Prompt
Reflection is one of the highest-value, most frequently skipped founder habits. A 10-minute Friday reflection — supported by AI — helps you learn from the week rather than just surviving it.
“Here’s what happened this week: [brief summary of key events, decisions, wins, frustrations]. Help me reflect: (1) What’s the most important thing I learned this week — about the business, the market, or myself, (2) Is there a decision I made this week I should revisit, (3) What’s one thing I did this week that I should do more of, and one thing I should do less of, (4) Based on this week, what’s the one thing I should prioritise differently next week?”
Building Your Own Prompt Library
The prompts in this playbook — and across our other playbooks — are starting points. The real value comes from adapting them to your specific business, then saving the versions that work.
Keep a simple document — a Notion page or even a text file — with the prompts you use regularly, organised by category. When a prompt produces a great result, note what made it work. When it falls short, note what was missing. Over a few months, you’ll have a personalised library that reflects exactly how your business operates — far more valuable than any generic prompt collection, including this one.
“I’ve been using this prompt: [paste your current prompt]. The output I’m getting is [describe what’s wrong — too generic, missing something, wrong tone, etc]. Here’s an example of output I got: [paste an example]. Help me rewrite this prompt to address the issue — what’s missing from the prompt that’s causing this output problem, and how should I restructure it?”
Get 50 more prompts for ops, productivity, and running a leaner startup — free.