Every small business has work that comes back each week. The Friday client update. The Monday sales summary. The reminder to follow up on an unanswered proposal.
None of these tasks looks large on its own. But each one needs your attention again: find the information, remember the format, prepare the draft, check the details.
A personal AI assistant can help turn that recurring work into a scheduled routine. The useful place to start is not your entire to-do list. It is one task with clear inputs, a predictable schedule, and a result you can check.
What makes a task worth turning into a routine?
Look for work that repeats without changing its basic shape.
A weekly client update might cover different developments each Friday, but its structure stays the same: completed work, next steps, blockers, and decisions needed.
That makes it a stronger starting point than something like “help me grow my business.” One has a clear result. The other needs a conversation before anyone knows what to do.
Before choosing your first routine, ask:
- Does this task repeat on a schedule I can name?
- Can I provide the information it needs?
- Can I describe what a useful result looks like?
- Can I check the output without rebuilding it myself?
Start with a task that meets all four conditions.
Choose one recurring task, not your whole workload
Pick something small enough to review but useful enough to matter.
Good starting points include:
- A weekly client update prepared from your project notes.
- A sales summary based on a spreadsheet you provide.
- A briefing before a recurring meeting.
- A reminder to review outstanding proposals.
- A weekly plan assembled from your priorities and deadlines.
Avoid handing over several unfamiliar routines at once. If the results need changes, you want to understand which instruction caused the problem.
The aim is to establish one dependable workflow before adding another. Our note on giving the work away once, not every week explains why remembered context matters when work repeats.
Tell your AI assistant what a good result looks like
“Prepare my weekly report” leaves too much open.
A useful instruction explains the source, the contents, the format, and the limits. You do not need technical language. You need the details you would give someone helping you for the first time.
For example:
Every Friday at 3 p.m., prepare a client update using the project notes I provide. Include completed work, next week's priorities, blockers, and decisions I need from the client. Keep it short. If something is missing, flag it rather than guessing. Prepare a draft for my review; do not send it.
This instruction gives the assistant a clear job:
- Source: the project notes you provide.
- Schedule: Friday at 3 p.m.
- Contents: progress, priorities, blockers, and decisions.
- Format: a short client update.
- Missing information: flag it instead of inventing an answer.
- Approval boundary: draft only; do not send.
Include your time zone when setting the schedule, especially if you work with people in different locations.
Make sure the information is available
A scheduled task is only useful if the assistant has the information needed to complete it.
Before relying on a routine, decide how its inputs will arrive. Will you upload a file, share updated notes, or use a supported app connection?
Be specific about which source to use. “Use the weekly sales spreadsheet” is clearer than “check my numbers.” If several files look similar, identify the right one.
Also explain what should happen when the source is missing or out of date:
If this week's notes are unavailable, tell me what is missing. Do not present last week's information as a current update.
Do not assume the assistant can access an account or document simply because you mentioned it. Confirm access during setup, and share only what the task needs.
Test the output before scheduling it
Ask for a sample first.
Read it as though you were about to use it. Are the facts supported by the source? Are the important points easy to find? Is anything missing? Does the tone sound like you?
Correct the instruction where necessary:
- “Put decisions needed before the progress summary.”
- “Use bullets instead of long paragraphs.”
- “Keep internal notes out of the client-facing draft.”
- “Separate confirmed deadlines from proposed dates.”
Then ask for another version. Once the result is useful, confirm the recurring schedule and where you want it delivered.
With Rilke, the intended workflow is to describe the task, refine it, and schedule the recurring work. You can explore the product's approach in how Rilke works.
Review the first few runs
Treat the first few scheduled outputs as a trial, not proof that the routine will always be right.
Check that the assistant used the correct information, covered the right period, and followed your instructions. If something is wrong, correct the underlying instruction rather than only editing that week's output.
For example:
Use the reporting period written in the spreadsheet, not the date the file was uploaded.
Ask the assistant to confirm the revised instruction, then check that the next run follows it. Remembered preferences are useful, but they do not remove the need to verify important work.
If reviewing the output takes as much effort as doing the task yourself, simplify the routine or choose a better-defined task.
Keep decisions and approvals with you
Preparing work and approving it are different responsibilities.
An assistant can help assemble a report or draft a follow-up. You still decide whether the report supports a business decision or whether the message is appropriate to send.
For your first routine, set a clear boundary:
Prepare the work for review. Do not send, publish, spend, or make commitments.
Keep that boundary explicit when you revise the task. A successful draft is not a reason to quietly expand what the routine is allowed to do.
Change the routine when the work changes
A routine should fit your work, not become another obligation you maintain out of habit.
If a project ends, stop its update. If a meeting moves, change the schedule. If a report no longer helps you make a decision, simplify it or retire it.
Review your active routines periodically:
- Is this still useful?
- Is it using the right source?
- Is the schedule still appropriate?
- Does the output still need the same approval?
- Should it continue at all?
The point is to reduce recurring work, not create more messages to read.
Start with one useful result this week
Choose one task you repeat, identify its source, and describe the output you want. Ask for a sample before putting it on a schedule.
Keep the first version modest: one source, one clear result, and a review before anything goes out.
If you want to try that approach with Rilke, explore the personal AI assistant or compare the plans for current scheduled-task and app-connection allowances.
You do not need to automate your whole week. Start with one piece of preparation you would be glad not to rebuild next Friday.