How a week works in a small human plus AI team.

The idea

A small team has limited hours. Tools can help with drafts, reminders and sorting. People are needed for choices, care and trust.

This is how I think about a week. It is a rhythm to try, not a rule, and I do not claim it fits every team.

A simple weekly rhythm

Try this shape:

• Monday: set the one big goal for the week.
• Tuesday and Wednesday: build and draft with tool help.
• Thursday: a person checks every draft and fixes it.
• Friday: review the week and write one lesson.

Pick a day and copy the plan

Choose a day, copy the plan, and change it to fit your team.

Two rules that protect quality

A sample week, hour by hour (illustrative)

• Monday morning: a person sets the three goals for the week and reviews last week's lessons.
• Tuesday and Wednesday: AI tools draft replies, summaries and opening versions. People edit them.
• Thursday: a different person checks the week's work against the checklist.
• Friday: fixes go out, and every mistake becomes one line in the lessons log.
• Weekend: no drafts go live without a person reading them.

Who does what, and why that split

The split matters more than the tools. A tool that drafts and a person who reads is a team. A tool that drafts and ships alone is a risk.

Tools and people, who does what

Keep this split written where the team can see it. Review it every quarter, because tools change and so do your customers. If you ever feel a tool is making replies colder, pause it, read ten messages as a customer would and adjust. The goal is to save time for care, not to replace it.

Start with one small task, measure how it feels for customers, and expand just if it helps.

A worked week, in more detail

This is a sample, not a client record. A small team of three runs customer chats for a food brand.

The point is the rhythm, not the numbers.

Handling a surprise during the week

Things go wrong. A courier delay hits many orders. A product runs out. A customer writes an angry post. A small team handles this by pausing the plan, deciding who speaks to customers, writing one clear message and sending it. Tools can help send it. People decide what to say.

After the event, add it to the lessons log with one line on what to do next time.

Keeping the team’s energy up

• Keep meetings short and useful.
• Celebrate good replies, not just fast ones.
• Let people rest. Tired people write cold messages.
• Share thanks from customers with the whole team.
• Rotate who writes the weekly report.

Adapting this to your own team

1. Draw your own week on one page.
2. Mark who drafts, who checks and who approves each task.
3. Mark the tasks that need a person just.
4. Choose one task to improve this month.
5. Review the page after a month and update it.

A 7 day action plan

A seven day way to try a small human plus AI rhythm.

1. Day 1: list your recurring tasks.
2. Day 2: pick one.
3. Day 3: assign draft, check and approve.
4. Day 4: run it once.
5. Day 5: note time and quality.
6. Day 6: fix one step.
7. Day 7: write a short weekly note.

A checklist before you start

• Who approves?
• Who checks?
• Where are lessons stored?
• What goes to a person just?
• When is the weekly review?

Mistakes brands make here

1. Skipping the check when busy.
2. Too many tools.
3. Unclear ownership.
4. No weekly note.
5. Promising numbers you have not measured.

A week in plain words

This page describes how a small team can work with a mix of people and AI tools in a week. It is a sample rhythm, not a promise about any client’s results.

The idea is that people set direction and care, and tools handle drafts and routine work.

A sample weekly rhythm

Who does what

• People decide priorities, approve work and answer sensitive messages.
• Tools help draft, sort and remind.
• A second person checks before anything goes live.
• Everyone adds to the lessons log.

Why we keep the team small

Small teams can keep a human voice. A message that passes through many hands often loses its warmth. A short chain from idea to reader keeps the work personal.

What we do not promise

We do not promise a number of leads, sales or hours saved from this rhythm, because we do not have verified figures to share. We share the method and the habit of checking.

Try a mini version

1. Pick one recurring task, such as replying to customer questions.
2. Write down who drafts, who checks and who approves.
3. Run it for one week.
4. On Friday, write what worked and one thing to change.
5. Keep the change and repeat.

What this guide does not promise

It does not promise sales, income or results. It describes how I work and what you can expect.

Written by Madhur Tyagi, founder of The Human Algorithm. 8+ years, 25+ brands, since 2017.

Scope note: Scripts and plans are examples, not a promise of results. Nothing on this page is sent unless you press the WhatsApp button. No outside facts or rates are quoted.