Run a Weekly Business Review in Muse With Scheduled Tasks and Dashboards

One Weekly Review Beats Ten Clever Prompts

Most small business owners try an AI agent with a few one-off questions, get an answer, and then forget about it. The most useful first habit is not a library of clever prompts. It is one recurring review: every week, Muse pulls the same sources, updates the same scorecard and dashboard, writes a short memo of what changed and what looks off, and proposes next actions that wait for your approval. The value comes from consistency and from a review routine on the owner's side, not from the agent running unattended.

Picture a Monday morning. You open Muse and see a message that the weekly review finished. You tap into the conversation. There is an updated scorecard spreadsheet showing this week's numbers next to last week's. There is an updated single-page dashboard you can open in a browser. There is a one-page memo that calls out which posts and ads drew attention, which customers went quiet, and what looks off in the numbers. Below that, a short list of proposed actions: a draft Instagram post, a draft email to three customers who have not ordered in six weeks, and a campaign plan for review. Each one waits for your yes or no. You spend twenty minutes checking the facts, approving two actions, denying one, and noting a change to make next week. Then you close Muse and get back to running the business.

This post is the build guide for that one routine. You will decide what to review, pick the sources, write the recurring task, choose the artifact formats, set permissions for scheduled work, review the output in a fixed amount of time, turn findings into approved actions, and tune it over the first month. If you have not yet set up goals, connectors, and approvals in Muse, start with the Muse for Small Business playbook and come back to this guide when you are ready to build the weekly review.

What Muse Brings to a Weekly Review

Muse can run recurring tasks on a schedule. You describe the task and how often you want it to run: daily, weekly, or a custom interval. Muse creates the task and confirms it. Each time the task is due, you get a message in your Muse conversation. The task keeps running after you close the app until you cancel it. Times follow your time zone. You can view scheduled tasks by asking "What reminders do I have?" or by tapping the assistant icon and opening the Upcoming tab. You can change or cancel a task by telling Muse, and Muse confirms the change.

Muse creates and edits artifacts: spreadsheets in XLSX or CSV, documents in PDF or DOCX, and interactive single-page dashboards and visualizations you open in a browser. You can ask Muse to update a previous artifact by referencing it by name, so the same scorecard file gets a new row each week instead of creating a new file. Artifacts are saved to your Library and are not shared externally unless you turn on sharing or approve when Muse asks.

Muse can use information from Facebook Pages, Instagram professional accounts, and Meta ad accounts alongside other connected services. The list of available connectors varies by account and includes services like Shopify, Stripe, Intuit QuickBooks, Klaviyo, Notion, Asana, Slack, Dropbox, Box, Canva, Zoom, and HighLevel. You can check which connectors are available to you in Settings under Connectors. Meta connectors for Facebook, Instagram, and Threads are connected automatically if they are in the same Accounts Center.

Muse keeps multi-step or scheduled work moving after you close the app. The Goals tab tracks goals and plans. Muse evaluates whether a result is worth surfacing and notifies you only when something is meaningfully new or needs your input. You can adjust proactive messages by telling Muse to turn them off, dial them down, or dial them up.

Muse expanded to Japan in October 2026 and to Singapore shortly after. The Muse for Small Business help pages list availability for people 18 and older in the US and Canada. Check what your account supports in Settings. Muse Wonder, announced on October 12, 2026, will soon power experiences in Muse, rolling out first to subscribers.

Muse has a free plan that covers most needs. Power and Maximum subscriptions offer higher weekly usage limits. A heavy weekly routine uses capacity, so check your usage in Settings and watch it over the first month.

Decide What the Review Is For Before You Build It

The first mistake is trying to track everything. Start by writing down the five to eight questions you actually ask yourself every Monday morning. Not the questions you think you should ask. The ones you do ask.

Picture a two-location bakery that sells on Shopify and runs Instagram ads. The owner might ask: What sold this week compared to last week? Which Instagram posts and ads drew the most attention? How many new customers placed an order? How many repeat customers went quiet? What is on the calendar for this week? What looks off in the revenue or ad spend numbers? What decisions are pending from last week?

Imagine a home services company that books jobs through a CRM. The owner might ask: How many jobs did we complete? How many estimates are still open? Which lead sources brought in new inquiries? What is the average job value this week? Which customers have not scheduled a follow-up? What is on the schedule for the next seven days? What looks off in the close rate or average ticket?

Turn each question into a row on a scorecard. The bakery scorecard might have rows for total revenue, order count, new customer count, repeat customer count, the reach or engagement figures Muse can see for your posts, ad spend and results Muse can see in your connected ad account, and a yes or no flag for whether anything is outside the range you set. The home services scorecard might have rows for jobs completed, estimates sent, estimates closed, lead count by source, average job value, and open follow-ups.

The rule is simple: if you would not look at the number every Monday, do not put it on the scorecard. The review is not a data warehouse. It is a decision tool.

Pick the Sources and Connect Only Those

Once you know what the scorecard measures, you know which sources Muse needs to read. Start with your Meta business assets: the Facebook Page, the Instagram professional account, and the Meta ad account. Then add one or two connected services: the store, the accounting system, the CRM, the project tool, or the file storage where you keep a customer list.

The rule is the same as for the scorecard: if you would not open the tool every Monday yourself, do not connect it for the review. Every connector you add is one more place where the task can stall if access breaks or the account changes.

Go to Settings and then Connectors. Connect the services you need. Many connectors can be set to only retrieve data. Use that option for sources that only need to supply numbers, not receive changes. Check which account each connector uses. If you have a personal Instagram account and a business Instagram account, make sure Muse is reading from the business account. If you manage multiple ad accounts, confirm which one is connected.

For tools that do not have a Muse connector, export a CSV or XLSX file and upload it to the Muse conversation. Each week, upload the fresh export and tell Muse to use the newest upload. Muse remembers files from the conversation so you can refer to them by name.

For example, if your CRM is GoHighLevel, you can connect it directly since HighLevel is in the connector list. If you use Sumo AI CRM, an AI-first CRM positioned as the best GoHighLevel alternative, with an AI receptionist for customer calls and messages, and it does not have a Muse connector, export a CSV of your pipeline or customer list and upload it. Tell Muse the file name and what it contains, and reference that file in the recurring task.

Write the Recurring Task

Now you write the task that Muse will run every week. Open Muse and type the full task description in one message. Here is a hypothetical example for the bakery:

Every Monday at 8:00 AM Eastern time, run a weekly business review. Pull data from my connected Shopify store, my Instagram professional account, my Meta ad account, and the customer list CSV I uploaded, all for the past seven days ending Sunday night. Update the scorecard spreadsheet named Weekly Scorecard with a new row. The columns are: week ending date, total revenue, order count, new customer count, repeat customer count, the reach or engagement figures you can see for my posts, ad spend and results you can see in my connected ad account, and a flag column that says Yes if any number is more than a quarter above or below the four-week average or No if everything is within range. Update the dashboard named Weekly Dashboard with the same data, showing this week and the prior four weeks as a line chart for revenue and order count, and a bar chart for new versus repeat customers. Write a one-page memo in PDF named Weekly Memo with three sections: What Changed This Week, What Looks Off, and Proposed Actions. In What Changed, list the three biggest changes in the numbers. In What Looks Off, note anything outside the range I set and any customer who ordered in three of the past four weeks but not this week. In Proposed Actions, draft one Instagram post highlighting a popular product from this week, draft one email to customers who went quiet, and note any decision I marked as pending last week. Do not send, publish, spend, or change any records. Save all drafts and wait for my approval. Reuse the same file names each week so the scorecard and dashboard have history. Tell me when you finish.

After you send that message, Muse will confirm the schedule. It will repeat back the cadence, the time, and the time zone. Check the Upcoming tab by tapping the assistant icon. You should see the task listed with the next run date and time. You can also ask "What reminders do I have?" and Muse will list the scheduled tasks.

If you need to change the task, tell Muse what to change. If you need to cancel it, say "Cancel the weekly business review task" and Muse will confirm.

Choose the Artifacts

The weekly review produces three artifacts: a scorecard, a dashboard, and a memo. Each one serves a different purpose in the twenty-minute review.

The scorecard is a spreadsheet. Use XLSX if you will open it in Excel, Google Sheets, or Numbers. Use CSV if another tool will import it automatically. The scorecard has one row per week, so you can see the trend over time. Ask Muse to add a new row each week to the same file. Do not ask it to create a new scorecard each week, or you will end up with dozens of files in your Library. The file name stays the same. The history builds inside the file.

The dashboard is an interactive single-page tool or visualization you open in a browser. Muse can create line charts, bar charts, and tables. A dashboard is faster to scan than a spreadsheet when you want to see a trend at a glance. Ask Muse to update the same dashboard each week, not create a new one. Reference the dashboard by name in the recurring task, just like the scorecard.

The memo is a one-page document in PDF or DOCX. Use PDF if you want a fixed format that you can file or forward. Use DOCX if you want to edit the memo before you save it. The memo has sections: What Changed This Week, What Looks Off, and Proposed Actions. The memo is where Muse interprets the numbers and flags what needs your attention. Keep it to one page. If the memo runs longer than one page, the task is trying to cover too much.

You can read how Muse creates and edits artifacts in the Meta Help Center. You can also read Meta's guide to reminders and scheduled tasks in Muse for more detail on scheduling and managing recurring tasks.

Naming matters. Pick simple, consistent file names: Weekly Scorecard, Weekly Dashboard, Weekly Memo. Tell Muse to reuse those names. If you change the name mid-month, Muse may create a new file and you will lose the history in the old file. If you want to start fresh, ask Muse to save a copy of the old file under a new name before starting fresh.

Ask Muse where a file is if you cannot find it. Muse will tell you the file name and confirm it is in your Library. You can delete files from the Library anytime. Nothing is shared externally unless you turn on sharing or approve when Muse asks. You can control whether Muse uses your conversations and files for training in Settings under Data controls.

Permissions for Scheduled Work

Scheduled tasks need permission to read sources and save artifacts. Go to Settings, then Permissions, then Manage permissions. You will see sections for Connectors, Artifacts and scheduled tasks, and Allowed websites.

Under Connectors, the default is Ask for some actions or Always ask. For the weekly review, Muse needs to read from your connected store, ad account, and other sources. It does not need to send, publish, spend, or change records. Set connectors that only supply data to retrieve-only where the option exists. If a connector does not have a retrieve-only option, leave it at Ask for some actions and approve the read actions when Muse asks the first time.

Under Artifacts and scheduled tasks, you will see approvals for each scheduled task. When the weekly review runs, Muse may ask for permission to save the updated scorecard, dashboard, and memo. You can choose Allow once, Allow for this task, Always allow, or Deny. Use Allow for this task for repeated write steps in the same recurring task. Always allow lets Muse take that type of action for that connector in the future without asking again, so keep it for low-risk reads. Do not use Always allow unless you want that permission to apply to every task Muse runs, now and in the future.

You can tap See task details to review what the task does and what permissions it has. If an approval card arrives while the task is running and you do not answer it, the task can stall. Schedule the task for a time when you will see the notification and can approve within a few minutes.

The weekly review is read-only on the source side and draft-only on the action side. Muse reads data, updates artifacts, and drafts proposed actions. It does not send emails, publish posts, spend money, or change records in connected services unless you approve each action individually. Keep it that way. The Muse for Small Business playbook mentioned above covers the full permission ladder and governance model. For the weekly review, the rule is simple: reading and saving artifacts can be Allow for this task; sending, publishing, spending, and sharing stay behind approval cards.

The Twenty-Minute Owner Review

When the Monday message arrives, you have twenty minutes of work. Not twenty minutes of reading. Twenty minutes of decisions. Here is the checklist.

Open the memo. Read the What Changed This Week section. Read the What Looks Off section. Read the Proposed Actions section. Do not skip to the actions. The memo is the context for the actions.

Open the scorecard. Check three numbers against the source. Pick the three that matter most this week. If the scorecard says total revenue was 4,200 and the Shopify dashboard says 4,180, that is close enough. If the scorecard says ad spend was 850 and Ads Manager says 1,100, that is not close enough. Ask Muse which sources it used and what date range. Confirm it pulled from the right account. Spot-check the ad performance figures against Ads Manager.

Open the dashboard. Scan the charts. Look for anything that contradicts what the memo said. If the memo says new customers are up but the chart shows them flat, ask Muse to explain.

Ask Muse which sources it used for this review. Muse will list the connectors and files. Confirm the right accounts. If you manage two Instagram accounts and Muse pulled from the personal account instead of the business account, disconnect the personal account and reconnect the business account, then ask Muse to re-run the review.

Read what Muse flagged as off. Decide whether each flag is a real problem or normal variation. If repeat customers dropped noticeably and you know you ran a new-customer promotion last week, that is normal. If repeat customers dropped noticeably and you do not know why, that is a problem. Make a note.

Review each proposed action. Approve, edit, or deny. If Muse drafted an Instagram post highlighting a popular product, read the draft. Check the product name, the price, and the claim. If it is accurate, approve. If the price is wrong, edit it, then approve. If the product is out of stock, deny the action and tell Muse why.

If Muse drafted an email to customers who went quiet, read the email. Check the customer names. Check the tone. Check the offer. If you do not want to send that email this week, deny it. If you want to send it but change the subject line, edit it, then approve.

If Muse noted a decision pending from last week, decide. If the decision was whether to run a new ad campaign and you are ready, tell Muse to draft the campaign plan. If you are not ready, tell Muse to carry the decision forward to next week.

Note one change to make to the task for next week. Maybe the memo is calling out too many small changes and you want to raise the threshold. Maybe the scorecard is missing a column you wish you had. Maybe the dashboard chart is hard to read and you want a table instead. Write it down. After you finish the twenty-minute review, tell Muse the change and ask it to update the task.

The Business Help guidance from Meta is clear: check facts, prices, names, numbers, and account details. Confirm the work uses the right sources and business information. Confirm that work in a connected service appears in the right account. Edit drafts before you send or publish anything. You are responsible for approved actions. Muse can make mistakes, and you own the decisions.

Turn Findings Into Approved Actions

The weekly review finds problems and opportunities. The proposed actions are how you act on them. Muse drafts the actions and waits for your approval. One decision per proposed action. Some actions can be reversed. Some cannot.

Picture the bakery example. The Monday memo says repeat orders dropped noticeably. The What Looks Off section lists three regulars who ordered in three of the past four weeks but not this week. The Proposed Actions section includes a draft email with the subject line "We miss you" and a discount code you already created, addressed to all three customers.

You open the draft. The names are correct. The discount code is one you created last month. The tone is friendly. You approve the action. An approval card appears. You check the recipients and wording on the card. You approve the send. The email goes to the three customers. That action cannot be reversed. If you had denied the action, Muse would not send the email and would ask if you want to revise the approach or skip it this week.

The memo also says the most popular product this week was the sourdough loaf. The Proposed Actions section includes a draft Instagram post with a caption about the recipe and a call to action to order online. You open the draft. The caption is accurate. The call to action links to the right product page. You approve the post draft. Then you either publish it yourself or approve Muse's request to publish if your connected account supports it, after checking the approval card details.

The memo notes that ad spend rose while impressions barely moved. The Proposed Actions section includes a recommendation to review the ad account for bid changes or audience overlap. You read the recommendation. You decide this is not urgent enough to act on today. You deny the action and tell Muse to add it to next week's pending decisions.

What to never auto-approve: sending messages to customers, publishing posts or ads, spending money, sharing files externally, or changing records in a connected service. Every one of those actions should wait for an approval card. If Muse asks for Always allow on any of those actions, choose Deny or Allow for this task instead.

Remember that some actions like sending an email cannot be reversed. Once you approve, the email is sent. Once you approve a post, the post is published. Approved actions are yours. Muse checks with you before you publish, send, spend, or share, but after you say yes, the action belongs to you.

Where the Review Fits in Your Stack

Muse is the owner's back-office agent. It runs the weekly review, tracks goals, drafts plans, and keeps multi-step work moving. It is not the customer-facing chatbot.

Customer messaging belongs to Meta Business Agent, which handles conversations on WhatsApp and Messenger, with Instagram Direct coming soon. Meta Business Agent can message customers, capture leads, and book appointments. If your CRM has its own AI agent, that is another option. GoHighLevel offers Managed Agents for customer conversations. Sumo AI CRM is an AI-first CRM positioned as the best GoHighLevel alternative, with an AI receptionist for customer calls and messages.

Ad account diagnostics belong to Meta AI Business Assistant, which lives inside Ads Manager. Meta AI Business Assistant can analyze Meta ad campaigns, flag account issues, surface recommendations, and show benchmarks. If you need to troubleshoot why an ad is not delivering or compare your cost per result to your industry, ask Meta AI Business Assistant, not Muse.

Muse pulls data from all of those places and turns it into the weekly review. The review tells you what to look at in Ads Manager, which customers to message, and which goals need attention. The review does not replace those tools. It connects them.

When the Weekly Run Goes Wrong

Run Did Not Arrive

If Monday morning comes and you do not see a message from Muse, check the Upcoming tab. Tap the assistant icon and open Upcoming. Look for the weekly review task. If it is not listed, the task was canceled or never created. Ask Muse "What reminders do I have?" and it will list active scheduled tasks.

If the task is listed but the run did not happen, check the time zone. Muse uses your time zone, but if you traveled or changed your device settings, the time zone might be wrong. Ask Muse what time zone it is using for the task. If it is wrong, cancel the task and create a new one with the correct time zone.

If the time zone is correct and the task is active, ask Muse whether it ran, and check the Activity log for what it did.

Muse Stopped Partway

If the Monday message says Muse started the review but did not finish, ask "What did you complete and what stopped you?" Muse should list the steps it completed and the step where it stopped. Common reasons: a connector lost access, a source returned an error, an approval card was not answered, or the task hit a usage limit.

Check connection access in Settings under Connectors. If a connector shows an error or asks you to reconnect, do that first. Then ask Muse to continue the review from where it stopped.

If Muse stopped because it needed a piece of information, add the missing source, result, format, deadline, or rule to the task. For example, if Muse stopped because the customer list CSV was not uploaded, upload the file and ask Muse to continue.

If Muse stopped because an approval card was not answered, answer the card. Then ask Muse to continue. If you do not want to approve that step, deny it and ask Muse to skip that step and finish the rest of the review.

Numbers Do Not Match

If the scorecard says total revenue was 4,200 but the Shopify dashboard says 3,800, ask Muse "What sources did you use for total revenue and what date range?" Muse should tell you which connector it used and what dates it pulled.

Common mismatches: Muse pulled from the wrong account, Muse used a different date range than you expected, Muse included or excluded refunds or discounts differently than the source, or the source data updated after Muse pulled it. Check which account each connector is reading from in Settings under Connectors. If Muse is reading from the wrong account, disconnect the wrong account, connect the right account, and ask Muse to re-run the review.

If the date range is wrong, check the task description. If you said "the past seven days" and today is Monday, Muse might interpret that as Monday through Sunday or Sunday through Saturday. Be explicit: "the past seven days ending Sunday night" or "Monday through Sunday of last week."

If the numbers are close but not exact, decide whether the difference matters. A difference of twenty dollars on four thousand dollars of revenue is not worth chasing. A difference of two hundred dollars is.

Dashboard Duplicated or a New File Each Week

If you open your Library and see Weekly Dashboard, Weekly Dashboard 2, Weekly Dashboard 3, Muse is creating a new file each week instead of updating the same file. This happens when the task does not reference the file by name or when the file name changes slightly each week.

Tell Muse "Update the file named Weekly Dashboard, do not create a new file." Add that instruction to the recurring task. Delete the duplicate files from your Library. The next time the task runs, check that Muse updated the existing file.

Too Many Proactive Messages

If Muse is sending you messages every day about small changes, dial down the proactive messages by telling Muse to turn them off, dial them down, or dial them up. For the weekly review, you want one message per week when the review finishes, not a message every time a number changes.

You can also raise the threshold in the task. If the task flags anything outside the range you set and that is too sensitive, change it to a wider range.

Usage Limits

If runs start stopping early or Muse tells you that you have reached a limit, check your usage in Settings. Muse has a free plan for most needs and Power and Maximum subscriptions for higher weekly usage limits. A weekly review that pulls from multiple connectors, updates three artifacts, and drafts several proposed actions will use more capacity than a simple one-off question.

If you hit the limit, you can upgrade to a higher plan or simplify the task. Simplify by reducing the number of sources, reducing the number of proposed actions, or running the review every two weeks instead of every week.

Tune It Over Four Weeks

Do not expect the first run to be perfect. Plan to tune the task over four weeks. Here is the schedule.

Week one: read-only, draft-only. The task pulls data, updates the scorecard and dashboard, writes the memo, and drafts proposed actions. You review everything. Approve only the artifact saves the routine needs. Approve no sends, posts, spending, or record changes. You spend the twenty minutes checking whether the numbers are right, whether the memo makes sense, and whether the proposed actions are reasonable. You note what is wrong and tell Muse the changes.

Week two: fix columns and thresholds. The task runs again. You check whether the changes from week one worked. You look at the scorecard columns. Are there columns you never look at? Remove them. Are there columns you wish you had? Add them. You look at the What Looks Off section. Is it flagging too many small changes? Raise the threshold. Is it missing real problems? Lower the threshold. You still approve nothing beyond artifact saves. You note the changes and tell Muse.

Week three: add one proposed-action type. The task runs again. The scorecard and memo are stable. You pick one type of proposed action to start approving. Maybe it is the Instagram post. Maybe it is the email to quiet customers. You approve that one action type if the draft is good. You still do not approve the other action types. You note how the approved action performs during the week.

Week four: prune what nobody reads and decide what earns Allow for this task. The task runs again. You review the full output. You ask yourself: what did I not look at this week? If you did not open the dashboard, remove it from the task. If you did not read a section of the memo, remove that section. You decide which approval steps happen every week without variation. Those steps can move to Allow for this task. Steps that need judgment every week stay as approval cards.

At the end of week four, you also run a monthly cleanup checklist. Open the Upcoming tab and confirm the weekly review task is the only scheduled task, or that you know what the other tasks are. Open the Activity log and scan the actions Muse completed in the past month. Disconnect any connectors you are not using. Check Allowed websites in Settings under Permissions and remove any sites you do not recognize. Open your Library and delete old files you do not need. Check Memory files and ask Muse to forget anything that is out of date. Review Data controls and confirm your training toggle is set the way you want it.

Common Mistakes

New File Every Week

The biggest mistake is letting Muse create a new scorecard, dashboard, or memo file every week. You end up with dozens of files in your Library and no history in any of them. The fix is to reference the file by name in the task and tell Muse to update the same file, not create a new one. Add a new row to the scorecard each week. Update the dashboard with the new data. Overwrite the memo with the new content. Keep the file names the same.

Tracking Everything

The second mistake is trying to track every metric you can think of. The scorecard grows to twenty columns. The memo grows to three pages. The twenty-minute review turns into an hour. The fix is to prune. Ask yourself every week: did I look at that number? Did I make a decision based on it? If the answer is no twice in a row, remove it.

Letting the Memo Replace Looking at the Source

The third mistake is trusting the memo without checking the source. The memo is an interpretation. The source is the truth. If the memo says ad spend rose noticeably, open Ads Manager and confirm. If the memo says a customer went quiet, open the CRM or the order history and confirm. You are responsible for the decisions you make based on the memo.

Approving Cards on the Phone Without Reading

The fourth mistake is approving actions on your phone while you are doing something else. You see the approval card, you tap Allow, you move on. Then you realize later that the email went to the wrong customer or the post had the wrong price. The fix is to set a rule: no approvals on the phone unless you have read the full draft on a bigger screen first. If you cannot read it now, deny the card and review it later.

Connecting a Personal Account by Mistake

The fifth mistake is connecting a personal account when you meant to connect a business account. You have a personal Instagram and a business Instagram. Muse connects the personal one. The weekly review pulls data from the wrong account for a month before you notice. The fix is to check which account each connector is using right after you connect it. Go to Settings, then Connectors, and confirm. If it is wrong, disconnect and reconnect the right account.

Leaving a Dead Scheduled Task Running

The sixth mistake is leaving a scheduled task running after you stop using it. You built a weekly review, ran it for a month, then decided to change the format. You created a new task but forgot to cancel the old one. Now you have two tasks running every Monday and you ignore both messages. The fix is to check the Upcoming tab once a month and cancel any task you are not using.

Turning the Review Into Your Customer Messaging System

The seventh mistake is turning the weekly review into your customer messaging system. A few targeted, approved check-ins drafted by the review are fine. Ongoing conversations, replies, lead capture, and booking belong in Meta Business Agent or the CRM's customer-facing agents. The weekly review should flag which customers to message and draft the message, but the sending and the conversation should happen in the tool where you manage customer interactions.

Skipping the Twenty-Minute Review

The eighth mistake is letting the Monday message sit unread. You see it, you tell yourself you will look at it later, and later never comes. By Thursday you have forgotten about it. The next Monday a new message arrives and you still have not looked at the first one. The fix is to block twenty minutes on your calendar every Monday morning right after the task runs. Treat it like a meeting with yourself. If you miss it, reschedule it for Monday afternoon, but do not skip it.

How SumoGrowth Labs Helps

SumoGrowth Labs is an AI implementation and consulting agency. We are the team that implements and sets things up. For a weekly business review in Muse, we help you define the scorecard, connect the right sources, write the recurring task, set permissions, and train the owner's review habit. We do not build software. We build the routine and make sure it works every Monday for a month. Then we hand it off and you run it.

If you want help building your weekly review in Muse, or if you built it and it is not working the way you expected, reach out. We will scope the work, build the task, and train your team to run the twenty-minute review.

by Darius Gaynor