Organize evidence
Paste redacted notes into a chat or project. Ask for themes with a quote or note ID. Open each underlying note before deciding to build.
Official tool guide ↗Choose a workflow and press Play. Each handoff shows what goes in, what comes out, and the instruction you can reuse. You can run the roles in separate chats or do them all yourself.
Three anonymized inquiry notes from a florist.
A short list of missing details, each tied to a note.
Read these anonymized inquiries. Quote the words behind each missing detail. Put assumptions in a separate list. Which single question would most reduce a follow-up email?
The verified questions and the florist’s preferred order.
A blank quote brief and one fictional completed example.
Turn these verified questions into a one-page editable florist quote brief. Group them in the order a client can answer them. Add a fictional example and leave unknowns visibly blank.
The draft and an inquiry without a confirmed venue.
A revised field for unknowns and a sample ready to share.
Read the example as a first-time client. Can I answer each field without guessing? Can the florist see what to ask next? Fix one point of friction before sharing.
An agreed test date and a blank feedback log.
A reminder to review the tester’s actual feedback.
Draft a reminder for Friday to review my florist brief test. Include these questions: What did the tester skip? What did they ask for? Show me the reminder and time before scheduling.
Public vendor discussions or interview notes you supply.
Two recurring stock-count problems with source links or note IDs.
From these sources, pull only firsthand descriptions of how makers count leftover stock. Include a link or note ID and a short quote. Flag questions we still need to ask a vendor.
One stock-count problem and a fictional item.
A table with packed, sold, remaining, target and restock quantities.
Draft a restock table for a vendor. If 12 units were packed, 9 sold and the next-event target is 12, show the remaining and restock calculations. Flag missing entries and sales above packed stock.
Three cases: zero sales, a sellout and a missing count.
Expected values checked by hand and one fix for an ambiguous cell.
With 12 packed and 9 sold, 3 remain. To reach 12, I need 9. Check a sellout and a missing count. Ask a vendor which number they would actually use to pack.
The market date and an empty experiment log.
A draft follow-up and a reminder you choose whether to use.
Prepare a private post-market review for Sunday. Ask what sold out, what came home, and whether the sheet changed a packing decision. Leave the message as a draft for me to review.
Fictional notes: 12 country loaves confirmed, 7 more confirmed, and an inquiry about 4.
19 confirmed loaves. Keep the 4-loaf inquiry in a separate follow-up list.
Group these anonymized notes by pickup and bread variety. Count confirmed quantities only. Return one line per order with its note ID, then a separate list of unclear orders. Show the sum.
19 confirmed loaves, 2 ready for this pickup and a yield of 6 per batch.
17 loaves needed. Round up to 3 batches. After pickup, 1 loaf remains.
Design one spreadsheet row for confirmed loaves, ready stock and batch yield. Give formulas for whole batches and remaining stock. Treat an empty input as unknown and flag a zero batch size. Check the example by hand.
A client cancels 4 of the 19 loaves. Ready stock and yield stay the same.
15 confirmed, 13 needed, 3 batches and 5 extra. The baker verifies the decision.
Reconcile the confirmed total against the source notes. Then check no orders, enough ready stock, a missing yield and a cancellation. Note the expected result before opening the sheet.
An agreed review time and the test sheet, with customer details removed.
A private reminder to compare planned and actual counts after pickup.
Draft a reminder for my agreed review time. Ask how many loaves were collected, what had to be recalculated, and whether the baker would use the file next week. Show me the draft and time before scheduling.
A simple robot can be a calendar reminder or a spreadsheet rule. Start with the trigger and the result you can check.
Paste redacted notes into a chat or project. Ask for themes with a quote or note ID. Open each underlying note before deciding to build.
Official tool guide ↗Give Claude the field list and a fictional case. Ask for a one-page artifact, edit it, and check it with someone who knows the task.
Official tool guide ↗Give Muse a deadline, acceptable sources and the exact output. Ask it to prepare a review plan or a reminder. Check the time and recipient before approving an action.
Official tool guide ↗Use a public topic to identify leads for research. Ask for links to original statements. Open each source and distinguish a real buyer complaint from a repost.
Official tool guide ↗In your spreadsheet, add columns for tester, agreed review date and status. Filter for reviews due today with status “waiting.” Set a repeating calendar reminder linking to this view. When it fires, review the row, write the follow-up yourself, and mark the row complete after you send it.
Pick one channel and track what people actually do.