An outdated offer can slip into a perfectly friendly client email. If you use Claude to help run a solo business, this guide gives you a small job for this week: review the business details it remembers, correct one stale assumption, and check a fresh draft before using it.
Set aside about 15 minutes. You will need your current offer details and access to your Claude settings. The goal is a short, accurate working brief you can trust yourself to maintain.
Why this is worth doing now
Anthropic’s August 25 update added editable memory topics and shared memory between chat and cloud-based Cowork. Its release notes also say memory is enabled by default on Free, Pro, and Max accounts. Local Cowork sessions do not share that memory.
For a solo owner, the useful question is simple: does the context traveling into the next task still describe the business you run today? A remembered preference for short emails may help. A remembered offer you stopped selling deserves a closer look.
This is a maintenance habit I recommend, not a claim that every Claude draft contains old information. You may find your saved details are already accurate. That is a useful result too.
Start with the facts you control
Before opening Claude, write a small current brief in a document you own. Choose one service or product you expect to discuss this week. Include its name, what the customer receives, and any wording you have retired.
Here is an invented example for a creator who teaches small workshops:
Current offer: a 60-minute beginner workshop on writing clearer customer emails. Includes a one-page practice sheet. The old offer was 90 minutes and included an individual follow-up call. That call is no longer included. Price and dates must be checked for each inquiry.
Keep this brief beside the screen. If an AI answer and your approved offer disagree, use the approved offer as your reference. Do not ask the assistant to decide which version of your own business is correct.
Review the saved topics
Open Settings, then Memory, then Topics. Select an entry to inspect it; use its edit control or Delete when needed. Deleting a chat alone does not remove memory entries generated from it. Projects have separate memory, so also inspect the project you actually use for this work.
For this first pass, focus on entries that could change a customer promise: an old package, a turnaround time, a delivery method, or an audience you no longer serve. You do not have to reorganize everything.
Make a note beside each relevant entry: keep, correct, or remove. Those are your review notes, not buttons to look for in the product.
Keep a lasting preference such as “use plain language.” Correct an inaccurate description of the business. Consider removing a temporary detail, such as a launch date, if you would rather supply the current value with each request.
With the workshop example, I would keep the preference for approachable teaching. I would replace the retired package description with the current workshop description, leaving variable price and date details in the current brief.
Write the correction narrowly
Avoid a sweeping instruction such as “remember everything about my business.” It makes the next review harder. A useful correction says exactly which fact changed.
For the fictional workshop, your replacement wording could be:
“My current beginner workshop on customer emails lasts 60 minutes and includes a one-page practice sheet. The retired 90-minute package and individual follow-up call are no longer part of this offer. Ask me for current dates and pricing.”
Read the saved entry after making the change. Check that it names the right offer and has not turned “ask me” into a made-up price. A confirmation message is less useful than seeing the wording you intended in the place you edited.
This is also a good moment to remove unnecessary customer-specific details from your working brief. The workshop’s format can be useful without a real client’s name, personal circumstances, or private correspondence.
Test a fresh draft
Open a new regular conversation in the same place you normally do this work. Use this prompt, adapted to your actual offer:
“Draft a short reply to a prospective customer asking what my beginner customer-email workshop includes. Use the current offer details available to you. If a detail is missing or conflicting, flag it for me rather than filling it in. Do not send anything. After the draft, list the offer facts you used and any details I need to confirm.”
Treat the output as a test. For our invented business, check the duration, the practice sheet, and whether the retired follow-up call appears. Look for invented dates or prices too. A fluent paragraph can fail this check.
If the old package returns, hold the draft. Inspect the instructions, files, and conversation context you are using for another copy of the old offer. For the immediate task, supply your approved brief explicitly and review the next draft against it. Do not keep retrying until a reply merely sounds right.
A successful test is modest: the sample draft matches the current offer and flags missing details. It does not establish that every future answer will be correct.
If you want a separate starting prompt for that email test, the free Professional Email Composer sample lets you specify the recipient, situation, tone, and facts to include. Keep your approved offer brief beside it.
Keep tomorrow easier
Save the current brief with a review date. Revisit it when an offer changes or when you catch an outdated detail in a draft. You can make this part of the same routine you use to update your website or customer handout.
For a one-off fictional exercise, Claude’s incognito mode can avoid adding the conversation to memory or chat history. It is not zero retention: Anthropic describes a default 30-day retention period, with organizational exceptions. Use invented customer details for practice.
Your finish line this week is concrete: one reviewed offer, corrected saved context where needed, and one checked sample reply. Then get back to the client work you opened Claude to do.
Sources
Claude release notes for August 25 2026
