DEV Community: Mikael Kolam

The Monday/Friday rhythm: a 60-minute weekly system for solo operators

Mikael Kolam — Mon, 19 Oct 2026 08:35:13 +0000

Disclosure: I sell a Notion pack built on this rhythm, and there's a free sampler at the end. Everything below works with paper, a text file or whatever tool you already use.

AI disclosure: this article was drafted with help from an AI assistant and reviewed and edited by me.

When you work alone, nobody runs your week for you. There's no standup, no sprint review and no manager asking what happened to that invoice. The work still happens, but it drifts. Client work expands to fill every day, outreach gets pushed to "later", and invoices go out whenever you remember them.

I tried a few heavy systems and dropped all of them. What stuck was much smaller: two short sessions a week, one on Monday and one on Friday, with mid-week left for actual work.

Monday is for choosing. Friday is for closing loops. Mid-week is for doing.

That's the whole idea. The rest of this article is the checklists that make it work.

Why two sessions and not a daily plan

Daily planning sounds disciplined, but for a solo operator it often turns into ten minutes of rewriting the same list every morning. A weekly frame fits better, because most freelance commitments are weekly anyway: a delivery by Thursday, a follow-up next week, an invoice at the end of the month.

Splitting the week into two sessions also separates two different kinds of thinking:

Monday is forward-looking. You choose what the week is for.
Friday is backward-looking. You check what actually happened and close what's open.

If you do both in one sitting, the review usually eats the planning, or the other way round.

The Monday plan (20–40 minutes)

Work top to bottom. Check a box when the block is finished, not when you thought about it.

[ ] Open your pipeline. Move any client or lead that already changed stage last week. Your list should reflect reality before you plan on top of it.
[ ] Every active client has a next action you can do in one sitting. "Work on the website" isn't a next action. "Send the homepage draft for review" is.
[ ] Every open pitch has a follow-up date this week, or a written reason to wait. This is the line that stops proposals from quietly dying.
[ ] Every lead older than 10 days gets a next action or gets closed. Old leads you never touch only make the list look busier than it is.
[ ] Write down three pieces of delivery work that must ship this week. Three, not ten. If everything is a priority, nothing gets protected.
[ ] Write down the outreach you'll actually send, with real names. Not "contact 20 agencies", but the five people you'll really write to.
[ ] List the invoices to send this week: client, amount, date.
[ ] Book an admin block in your calendar. Invoices, bookkeeping and follow-ups need a time slot, or they happen at 11 pm.

One rule keeps this list honest: if a plan item isn't tied to a client or a named deliverable, it doesn't belong on the page. "Improve my marketing" fails that test. "Publish the case study for Client B" passes.

The Friday review (20 minutes)

[ ] Count three numbers: outreach sent, replies, invoices (more on these below).
[ ] Which next actions slipped? For each one, move the date or kill the action. Don't just let it roll over silently.
[ ] Any active client with no contact in 7+ days? Put a follow-up on Monday's list, or pause them on purpose.
[ ] Run your invoice checklist for anything you delivered this week.
[ ] Write one sentence: what moved money or a decision this week?
[ ] Write one sentence: what will you not repeat next week?
[ ] Reset the page: duplicate it for next week, or clear it and change the date.

The two one-sentence questions matter more than they look. After a month you have eight short notes about what actually works for you, which is more useful than any productivity book.

Three numbers, and only three

In the first month, track exactly these:

Outreach sent. Messages you started yourself: a cold email, a proposal, a DM after a real trigger. Replies to existing threads don't count.
Replies. A human reply that moves the thread: yes, no, a question, a date. Auto-replies don't count.
Invoices. Invoices you issued this week. Keep the amount in your bookkeeping tool. Here you only count them.

Why so few? Because each one is something you can directly influence this week. Revenue, followers and website traffic are results. These three are the inputs that lead to them, and a bad week for any of them is something you can fix on Monday.

They're also a pulse, not a scoreboard. They're for you, not for posting screenshots.

A second rule: an empty box on Friday means you didn't track, not that the week was zero. Fill the numbers in honestly. If you skip tracking for a week, notice whether you missed it. That tells you whether the system is earning its place.

Where to keep it

It doesn't matter much. I use a single Notion page that I duplicate every week, but a text file named week-2026-10-19.md or a sheet of paper on the desk works just as well. The rhythm is the useful part. The tool only has to be fast to open.

If you want a minimal setup:

A pipeline: a list of clients and leads with a stage (Lead, Pitch, Active, Paused, Done) and a next action for each.
A weekly page: the Monday and Friday checklists above, plus three number boxes.

That's enough to start.

Common ways it breaks

Monday turns into a two-hour planning session. Set a timer for 40 minutes. If the plan isn't done, the week is too full, and that's useful to know.
Friday gets skipped when the week went badly. Those are exactly the weeks the review is for. Do the 20-minute version even if the numbers are uncomfortable.
The list keeps growing. Apply the rule: no client or named deliverable, no line.

Try it for four weeks

One week tells you nothing. After four Monday/Friday cycles you'll have four sets of numbers and eight short notes, and you'll see where your weeks actually go.

If you'd like the checklists ready to copy, I put the Monday/Friday rhythm, a 5-minute cold email check and an AI inbox-assistant setup into a free starter kit. Pay what you want, including $0: https://mikaelkolam.gumroad.com/l/qmhsd

How I split an AI assistant into 6 seats so nothing sends without a human yes

Mikael Kolam — Mon, 12 Oct 2026 07:51:57 +0000

Disclosure: I sell a template pack, link below. The approach in this article works without it.

AI disclosure: this article was drafted with help from an AI assistant and reviewed and edited by me.

If you've used an AI assistant for any length of time, you've probably felt the same two frustrations. First, one long chat becomes a junk drawer where inbox triage, research and pricing ideas all blur together. Second, you start to wonder what happens if the assistant is ever connected to something that can actually send, pay or publish.

I dealt with both by changing how I set the assistant up. Instead of one general helper, I use six standing seats, each with one job, a written "never" list, and a human gate on anything that leaves the chat. This article describes the structure so you can build your own.

The problem with one do-everything assistant

A general assistant has no boundaries unless you give it some:

Scope creep. You ask for an email draft and get a strategy memo.
Unclear authority. It isn't obvious what the assistant may do on its own.

The second matters most. If an assistant can email, post or pay, a vague instruction is a risk. I want the default to be "draft it and show me," and I want that default written down in the assistant's own instructions, not just in my head.

The idea: seats, not prompts

Think of each agent as a seat at a small table. Every seat has the same short structure:

Job: one sentence.
Owns: what it produces.
Never: what it must not do.
First task: what it does when you first talk to it.
Done when: an observable result.

Here is a seat written in that format. It's the one I'd start with:

# Inbox

## Job
Triage inbound messages the human pastes here. Draft replies. Do not send.

## Owns
Label (action / wait / archive), draft reply in the human's voice,
one-line risk note.

## Never
Click send. Promise deadlines the human did not set.
Soften bad news into fluff.

## First task
When given a pasted email/Slack thread: return Label + Draft + Risk
in under 12 lines.

## Done when
Human can copy-paste or discard without rewriting the structure.

"Promise deadlines the human did not set" is a real failure mode for email drafts: an assistant that helpfully writes "I'll have this to you by Friday" has just made a commitment on your behalf.

The six seats

The six seats I use are:

Chief: routes work to the other seats and never executes outside the chat.
Inbox: triages inbound messages and drafts replies.
Research: collects public facts and cites sources.
Builder: produces files or scripts on request.
Money: works on offers, KPIs and pricing maps.
Tuner: reviews each week what to cut and what to keep.

You don't need exactly these. The point is that each seat has one job.

The org chart

Everything runs through you:

You (human gate)
  └── Chief (routes, never executes outside chat)
        ├── Inbox
        ├── Research
        ├── Builder
        ├── Money
        └── Tuner

The human gate sits at the top on purpose. Chief decides who should do a task, but it doesn't have authority beyond the chat.

A handoff format

When Chief passes work to another seat, it uses a fixed block so nothing is implied:

HANDOFF
To: <seat>
Goal: <one sentence>
Constraints: <never-list items that apply>
Done when: <observable result>
Do not: send / pay / publish / create accounts

The last line is the important one. Every handoff repeats the limits, so the receiving seat doesn't have to guess.

The hard rules

I give every seat the same short list of rules:

Nothing leaves the chat (email, Slack, social, payment) without a human yes that names the object. "Sure, go ahead" is not enough. The yes has to say which email, which post, which payment.
Prefer reading and drafting over acting.
If a source is missing, say so and stop. Don't invent metrics.
One active product or campaign at a time unless Chief says otherwise.

The rule I like most is the third. It is easy for an assistant to fill a gap with a plausible number. Telling it to stop when the source is missing makes the gap visible, which is what you want.

Try it in an afternoon

Create six agents (or reuse empty ones) and name them after the seats.
Paste each seat's text into that agent's description or profile field.
Talk to Chief first and ask it to run an onboarding checklist, with an explicit "do not contact anyone."
Approve one job. Let the owner seat deliver inside the chat.
Note what was slow or unclear, and fix the seat text. That is Tuner's job later, but you can do it by hand at first.

I'd start with just Inbox and Chief. If those two feel useful, add the others one at a time.

It's not a hosted team: you create the agents and stay the decision-maker. The never-list matters most, so write it after you've seen the assistant behave badly once.

I sell a template pack, link below: Grok Bot Ops Pack is a $19 download with all six seats written out and ready to paste, the playbook, the handoff protocol, a worked 90-minute first run, and blank weekly tables. It's independent material and not affiliated with xAI or Grok.

A 5-minute pre-send checklist for cold emails (and a follow-up cadence that doesn't annoy people)

Mikael Kolam — Fri, 09 Oct 2026 06:08:22 +0000

Disclosure: I sell a template pack, link below. Everything in this article is free to use without it.

AI disclosure: this article was drafted with help from an AI assistant and reviewed and edited by me.

Most cold emails fail before the recipient reads a word. They fail at the moment you hit send without checking whether you should be sending at all.

I keep a short checklist for this. It takes five minutes, and it removes most of the mistakes that make cold email feel spammy. Below is the checklist, the follow-up cadence I use with it, and a couple of templates you can adapt.

The principle: one tailored email beats ten generic blasts

If you are a freelancer or a solo operator, you don't have a list of thousands. You have a handful of people who might plausibly need what you do. That is an advantage. You can afford to spend five minutes on each one, and the result reads like it came from a person, because it did.

The 5-minute check

Minute 1: confirm the fit

Ask two questions:

Do they clearly need what I sell?
Is there a public signal? A hiring post, a product launch, a broken page, a gap in their content, a funding announcement.

If you are unsure, don't email. This is the cheapest rule on the list and the one that saves you the most embarrassment. A cold email with no reason behind it is just noise.

Minute 2: find one specific hook

Look at their website, LinkedIn, X, Product Hunt, a recent blog post, or their About page. Then write one sentence that starts with:

I noticed ___.

It has to be true for them and only them. "I love your content" with no detail doesn't count. "You're hiring for a content lead and your blog hasn't been updated since spring" does.

If you can't find a hook in about three minutes, pick a different lead. That's a signal, not a failure.

Minute 3: swap the brackets and read it out loud

If you use a template (and there's nothing wrong with that), replace every [BRACKET] with something specific to them and to you. Then read the email out loud. If a sentence still sounds like a template, rewrite that sentence. Your ear catches things your eyes skip.

Minute 4: make one clear ask

End with a single, easy next step:

"Want the outline?"
"Reply yes and I'll send it."
"A or B?"

Avoid asking for a call to "explore synergies." A small, concrete ask is easier to say yes to than a vague meeting. If you are offering something, make it something you can deliver in one reply, and deliver it quickly.

Minute 5: add one proof line, then check and send

Add one line of proof: a type of client you have worked with, a named project, or a link to your portfolio. Only use real ones. If you don't have a result to cite, link to your work instead and skip the claim.

Then check the boring things:

Is the first name spelled correctly?
Is the company name right?
Are there any leftover brackets?

Send from a real mailbox, log the email somewhere, and schedule your follow-up for day 5 to 7.

A cadence that doesn't annoy people

The follow-up is where most people either give up too early or turn into a nuisance. I use three emails, with a clear stopping point.

Day	What you send
0	First email: a specific observation, a small offer, one ask
5 to 7	Follow-up with something new
12 to 14	A polite note giving them an easy way to say no

The third email can be as simple as: "Want me to send a tighter version, or close this out so I don't bother you again?" Binary choices are easy to answer. After that, you stop. Three emails in a thread is the maximum unless they reply. Respect a "no" or silence after the close-out. If it still makes sense months later, you can send one re-engagement email, but only if you have something new to say, such as a new piece of work or a faster way of delivering.

The most important rule for the second email: add new value. "Just checking in" gives the reader nothing and asks them to do work. A one-line idea, a small observation about their page, or a short sketch of what you would change gives them a reason to read it.

A template you can adapt

First email

Subject: Quick idea for [Company / project]

Hi [First name],

I noticed [specific observation].

I help [type of client] get [specific outcome], usually by
[one-sentence method].

Would it be useful if I sent over a short outline of how that could
look for [Company]? No pitch call required, just a few notes you can
use or ignore.

Best,
[Your name]
[One-line credential or link]

Only add a named example if you really have one. An honest short email beats one with an invented result.

Keep the log

The checklist only works if you track what you sent. Write down who, when, which email, and when the next follow-up is due. A simple spreadsheet is enough. Without a log, follow-ups slip, and the cadence falls apart.

Wrapping up

The checklist is five steps: fit, hook, brackets, one ask, proof and send. The cadence is three emails and then stop. None of it is clever. It just keeps you from sending email you wouldn't want to receive yourself.

I sell a template pack, link below: Cold Email Templates is a $12 pack of 12 copy-paste templates across six situations (first outreach, follow-up, value-first, referral asks, re-engagement and partnerships), with subject line patterns and this same checklist. The checklist and template above are all you need to get started without it.