Guided workshop

Cron Job Lab:
Build Your Agent’s Weekly Rhythm

Create one recurring agent routine that supports the way you actually live and work.

“What could your agent quietly take care of, prepare, or remind you about so you have less to hold in your head?”

This is not about automating your entire life. It’s about giving your agent one small, useful place in your week.

Workshop promise

By the end of this workshop, you’ll have one useful cron job created inside The AI Surfer OS that supports a real recurring need in your personal life or business.

It might help you prepare, remember, notice, reflect, review, or stay connected to something important.

Part One · See the path

First, let’s look at the whole build.

We’re going to learn each step briefly, then immediately use that step with our own agent. You don’t need to figure out the whole thing before you start.

  • Notice
  • Choose
  • Schedule
  • Shape
  • Review
  • Create
  • Use
  • Step 1: Notice a recurring need

    What do you repeatedly need to remember, prepare, review, notice, or reflect on?

    Step 2: Choose the kind of support

    Should your agent remind you, prepare something, summarize something, help you reflect, or help you notice a pattern?

    Step 3: Choose one personal or business rhythm

    Pick one small idea that is useful, low-risk, and realistic to build today.

    Step 4: Choose when it should happen

    Decide what day, time, frequency, or recurring event makes the support useful.

    Step 5: Define what should arrive

    Decide what the agent should actually provide when the cron job runs.

    Step 6: Write and review the instructions

    Use your agent to create a first version, then ask it to simplify and improve the job.

    Step 7: Create the cron job and decide what happens next

    Set it up in The AI Surfer OS, then decide how you’ll use the result when it arrives.

    Presenter cue

    The full process is: Notice → Choose → Schedule → Shape → Review → Create → Use.

    Part Two · Choose your rhythm

    Before we build, let’s look at what’s possible.

    You do not have to invent an idea from scratch. As you listen, notice which ones make you think, “That would actually help me.”

    Personal life: daily support

    • A gentle morning check-in based on the day’s calendar
    • A weekday brief with the most important things to know
    • A daily “one important thing” prompt
    • A daily energy or capacity check-in
    • A reminder to prepare for an appointment
    • A recurring prompt to check whether the day’s schedule matches your capacity
    • A reminder to pause before opening social media
    • A short evening reflection

    Personal life: weekly rhythms

    • Sunday weekly reset
    • Monday personal priorities
    • Friday reflection on what felt good and what felt draining
    • Weekly meal-planning support
    • Weekly grocery-list preparation
    • Weekly household reset reminder
    • Weekly family logistics check-in
    • Weekly personal finance review
    • Weekly review of commitments that no longer fit
    • Weekly reminder to make space for something enjoyable

    Personal life: health, energy, and burnout support

    • Weekly movement planning
    • A recurring reminder to protect recovery time
    • A Sunday sleep and energy reflection
    • A weekly check-in for early burnout signals
    • A reminder to review whether the week has enough margin
    • A recurring prompt asking, “What am I carrying that I can put down?”
    • A weekly review of where they are overcommitted
    • A reminder to plan around actual energy instead of ideal energy

    The agent is helping them reflect, prepare, and notice patterns here. It is not making medical decisions or creating pressure.

    Personal life: organization

    • Monthly subscription review reminder
    • Weekly paperwork or admin reminder
    • Monthly digital-file cleanup prompt
    • Weekly review of important personal dates
    • A recurring reminder to follow up with family or friends
    • Monthly home-project review
    • Weekly “things I keep postponing” check-in
    • A recurring prompt to decide what can be delegated, deleted, or delayed

    Business: planning and priorities

    • Monday business-priority brief
    • Weekly open-loop review
    • Weekly project-status summary
    • Friday review of what shipped, what is stuck, and what needs a decision
    • Weekly review of tasks that keep getting moved
    • Weekly capacity check before accepting more work
    • Weekly review of what is actually driving progress
    • Monthly business-priority check-in

    Business: content and visibility

    • Weekly content-idea generation
    • Weekly review of what was published
    • Weekly list of unfinished content ideas
    • Weekly repurposing suggestions
    • Monthly content-theme planning
    • Weekly prompt to collect client questions for content
    • Weekly visibility check-in
    • Recurring prompt to identify one simple thing to share
    • Weekly review of what content felt easy or difficult to create

    Business: leads and sales

    • Weekly lead-follow-up preparation
    • Weekly review of conversations that need attention
    • Weekly pipeline summary
    • Weekly list of warm opportunities
    • Weekly review of unanswered inquiries
    • Monthly review of where leads are coming from
    • Weekly sales-conversation preparation
    • A recurring prompt to identify one relationship worth nurturing

    Business: client delivery

    • Weekly client-project review
    • Weekly preparation for upcoming client calls
    • Weekly review of open client decisions
    • Weekly reminder to prepare internal progress updates
    • Weekly check-in on deliverables due soon
    • Monthly client-results review
    • Weekly review of anything waiting on the client
    • Recurring prompt asking, “What could surprise the client if we don’t address it?”

    Business: finance and operations

    • Weekly bookkeeping preparation
    • Monthly revenue review
    • Weekly invoice or payment follow-up preparation
    • Monthly expense-category review
    • Weekly review of recurring software subscriptions
    • Weekly SOP-improvement prompt
    • Weekly review of tasks that should eventually be delegated
    • Monthly business-health check-in

    Business: founder support

    • Monday founder-focus brief
    • Weekly review of whether the business still fits the founder’s life
    • Weekly prompt asking, “What should I not be the one doing?”
    • Weekly review of energy, visibility, and revenue priorities
    • Friday reflection on what felt aligned or forced
    • Weekly decision-log review
    • Monthly vision check-in
    • Weekly reminder to protect time for high-value thinking

    The simple choice filter

    What do you repeatedly need to remember, prepare, review, notice, or reflect on?

    Prepare me
    Get me ready for something.

    Remind me
    Help me remember something at the right time.

    Help me notice
    Show me patterns or changes.

    Help me reflect
    Give me a recurring moment to think.

    01

    Step One

    Notice the recurring need.

    The first step is not “write a cron job.” The first step is identifying a recurring moment that takes up mental space.

    • Keep forgetting
    • Keep putting off
    • Keep preparing at the last minute
    • Keep reviewing manually
    • Keep needing to notice
    • Keep wishing someone would remind you about
    • Keep carrying mentally without a clear system
    I want to find one recurring agent routine that would genuinely support my life or business.
    
    Here are some ideas I’m considering:
    
    [PASTE YOUR IDEAS]
    
    Help me compare them based on:
    - How often the need actually happens
    - How much mental space it takes up
    - Whether an agent could meaningfully help
    - Whether it is low-risk enough for a first cron job
    - Whether I am likely to use the result
    - Whether it is small enough to build today
    
    Recommend one idea and explain why.
    Do not create the cron job yet.
    Workshop pause

    Give participants a few minutes to have the conversation with their agent. Then regroup briefly: “What kinds of things did people choose? Are you building something personal, business-related, or a combination?”

    02

    Step Two

    Choose the kind of support.

    A cron job might be a reminder, check-in, preparation brief, review, reflection, summary, decision-support report, or planning prompt.

    The same topic could become very different cron jobs. “Weekly content” could become a reminder to create content, a list of content ideas, a review of what performed well, a reflection on what felt aligned, or a preparation brief for the next week.

    Based on the recurring need we chose, help me decide what type of support would be most useful.
    
    My chosen idea is:
    
    [PASTE IDEA]
    
    Consider whether this should become:
    - A reminder
    - A check-in
    - A preparation brief
    - A review
    - A reflection
    - A summary
    - A decision-support report
    - A planning prompt
    
    Recommend the best format and explain what it would help me do.
    
    Keep it supportive and realistic. I do not want to create more pressure or unnecessary notifications.
    Workshop pause

    Ask participants to finish this sentence: “I want my agent to help me…”

    03

    Step Three

    Define the purpose.

    Clarify the role of the cron job without recreating the entire Automation Contract workshop. You simply need to establish what this recurring routine is there to support.

    Help me clarify the purpose of this cron job.
    
    My idea is:
    
    [PASTE IDEA]
    
    Complete these sentences:
    - This cron job exists to help me...
    - It should make it easier for me to...
    - It should reduce the need for me to remember...
    - When the result arrives, I should be able to...
    - This should feel supportive rather than...
    
    Keep the purpose simple, practical, and connected to my real life.
    Workshop pause

    Have them identify one sentence that describes the purpose clearly.

    04

    Step Four

    Choose the schedule.

    A useful cron job at the wrong time becomes noise. Everything does not need to run every morning.

    • When the information becomes useful
    • When you have the capacity to read it
    • Whether it belongs before or after a recurring event
    • Whether it should run daily, weekly, monthly, or occasionally
    • Whether you actually want to receive it that often
    Help me choose a realistic schedule for this recurring agent routine:
    
    [PASTE ROUTINE]
    
    Ask me only the most useful questions about:
    - When this information becomes relevant
    - When I would realistically have time to read it
    - Whether I need it daily, weekly, monthly, or occasionally
    - What day or event it should happen before or after
    - My timezone and normal availability
    
    Then recommend a schedule that supports my actual life instead of creating more notifications.
    Workshop pause

    Have each participant write down the frequency, day, time, timezone, and why that timing makes sense.

    05

    Step Five

    Decide what should arrive.

    The output should be useful enough to read and small enough not to ignore.

    A useful output might include

    • A short summary
    • Three priorities
    • A preparation checklist
    • A few questions
    • A list of decisions waiting
    • A reflection prompt
    • A review of what changed
    • One recommended next step

    Keep asking

    What would make this result feel helpful instead of like another report?

    More information does not automatically mean more useful.

    Help me design the output for this cron job:
    
    Purpose:
    [PASTE PURPOSE]
    
    Schedule:
    [PASTE SCHEDULE]
    
    Recommend a simple output that I would realistically read and use.
    
    Include:
    - The ideal length
    - The sections or headings
    - The most important information
    - What should be left out
    - Whether it should end with a question, recommendation, checklist, or next step
    
    Keep it focused enough that I will not ignore it.
    06

    Step Six

    Write the first version.

    Combine the decisions you’ve made. This is the first real draft. It does not need to be perfect.

    The instructions should communicate:

    • What the job is for
    • When it runs
    • What kind of support it provides
    • What the output should include
    • What tone it should use
    • What it should not do
    Help me write the first version of a cron job for my AI Surfer OS.
    
    Purpose:
    [PASTE PURPOSE]
    
    Schedule:
    [PASTE SCHEDULE]
    
    Type of support:
    [PASTE TYPE OF SUPPORT]
    
    Desired output:
    [PASTE OUTPUT]
    
    Write clear, practical instructions for the recurring job.
    
    Keep the tone supportive and concise. The result should help me take the next useful step without overwhelming me.
    
    Do not include actions that send messages, publish content, spend money, change records, or make important decisions without my approval.
    Workshop pause

    Have participants read the draft once without editing it. Ask: Does this sound like something you would actually want to receive? Is it asking for too much? Does it match the purpose you chose?

    07

    Step Seven

    Review and simplify.

    Before setting it up, ask the agent to critique the job. Make one improvement, not ten.

    • Too much information
    • Too much frequency
    • Vague instructions
    • Hidden assumptions
    • Unnecessary complexity
    • Unclear approval boundaries
    • Outputs you are unlikely to use
    Review this proposed cron job as a practical support routine:
    
    [PASTE CRON JOB]
    
    Look for:
    - Unclear instructions
    - Too much information
    - An unrealistic schedule
    - Hidden assumptions
    - Repetitive or unnecessary output
    - Actions that require my approval
    - Anything that could make this feel noisy or overwhelming
    
    Suggest the smallest changes that would make it more useful and easier to keep.
    
    Do not expand the scope. Help me simplify it.
    08

    Step Eight

    Create it in The AI Surfer OS.

    Now everyone creates the actual job in their OS. This is where the workshop becomes a real build instead of an exercise.

    Setup checklist

    • Give the cron job a clear name
    • Choose the schedule
    • Confirm the timezone
    • Add the final instructions
    • Check where the result will appear
    • Save the job
    • Review the saved version

    Before you save

    Make sure the job is focused, realistic, and bounded. The goal is not to create the biggest possible routine.

    I’m ready to create this cron job in my AI Surfer OS.
    
    Before I save it, give me a final setup checklist based on the instructions below:
    
    [PASTE FINAL CRON JOB]
    
    Check:
    - The name is clear
    - The schedule is realistic
    - The timezone is correct
    - The instructions match the purpose
    - The output is focused
    - Approval boundaries are clear
    - No external or irreversible actions are included without approval
    
    If anything needs to change, show me the exact revised wording.
    Workshop pause

    Have everyone confirm: “My cron job is created.” “My cron job is not created yet because…” or “I need help with…”

    09

    Step Nine

    Decide how you’ll use the result.

    A cron job only helps if the person knows what to do when it runs. You do not need to act on everything the agent says.

    The result might help you

    • Choose one priority
    • Prepare for a meeting
    • Notice a pattern
    • Take one small action
    • Ask your agent a follow-up question
    • Reflect and decide
    • Leave something alone

    Keep it lightweight

    Decide what you should look at first, what you can ignore if you do not have capacity, and how you will know the cron job is actually helping.

    Help me decide how I want to use the result when this cron job runs.
    
    Here is the routine:
    
    [PASTE ROUTINE]
    
    Tell me:
    - What I should look at first
    - What decision or action it should help me make
    - What I can ignore if I do not have capacity
    - When I should ask my agent a follow-up question
    - How I will know the cron job is actually helping
    
    Keep this lightweight and realistic.
    10

    Step Ten

    Review and improve it later.

    The first version does not have to be perfect.

    You can decide to

    • Keep it as-is
    • Revise it after the first run
    • Make it shorter
    • Change the timing
    • Reduce the frequency
    • Pause it if it creates noise
    • Expand it only after you trust the basic version

    The real test

    Does it reduce mental load? Did you actually read or use the output? Is it worth keeping in your week?

    Help me create a simple review plan for this cron job:
    
    [PASTE CRON JOB]
    
    After it runs a few times, help me evaluate:
    - Was the timing useful?
    - Did I read or use the output?
    - Was anything missing?
    - Was there too much information?
    - Did it reduce mental load?
    - What should I revise, pause, or keep?
    
    Recommend a simple time to review it and only a few questions that will help me improve it.

    Part Five · Close the workshop

    Give your agent one small, supportive place in your week.

    Final reflection

    Share what your cron job supports, whether it is personal, business, or both, when it will run, and what you hope it makes easier.

    “I built a cron job to help me with ________. It will run ________, and I hope it helps me ________.”

    Closing message

    You don’t need to automate your entire life or business today.

    You can start by giving your agent one small, supportive place in your week.

    Maybe it helps you prepare. Maybe it reminds you. Maybe it helps you notice something you’ve been too busy to notice.

    The point isn’t to add another system you have to manage.

    The point is to create one recurring moment that gives a little space back.