Free browser-based planning tool
Turn one workflow idea into a test brief, prompt, and SOP.
Choose one of 25 CSLM workflow designs. Add an owner and system of record, then download a planning draft. Your entries stay in this browser and are not submitted to CSLM.
Use safe inputs
Do not enter customer records, credentials, payment data, regulated information, or confidential files here. CSLM does not receive these fields.
Generated planning draft
CSLM WORKFLOW TEST BRIEF Workflow: WF-013 — CRM note normalization Business area: CRM Best-fit audience: Growing teams Owner: [name the accountable owner] System of record: [name the authoritative system] Problem Free-text notes are inconsistent and hard to search. Approved input Approved note and controlled vocabulary AI role Propose a summary and category in new fields Human checkpoint Owner verifies nuance and sensitive content Failure and stop path Preserve the original and reject low-confidence proposals Data classification Business correspondence Measurement Accepted suggestions; search success Safe first test Normalize 20 synthetic notes without overwriting originals PROMPT DRAFT You are assisting with crm note normalization. Use only the approved information provided. Propose a summary and category in new fields. Identify missing or conflicting information instead of guessing. Do not send, publish, pay, delete, merge, approve, or make a commitment. Return: (1) proposed result, (2) source fields used, (3) uncertainties, and (4) items for the human reviewer. SOP DRAFT 1. Confirm the request is in scope and the input is approved. 2. Preserve the original source and stable record identifier. 3. Run exact validation rules before the AI step. 4. Use AI only for: Propose a summary and category in new fields. 5. Route the result to the named owner for this checkpoint: Owner verifies nuance and sensitive content. 6. If anything fails or remains uncertain: Preserve the original and reject low-confidence proposals. 7. Record the result using: Accepted suggestions; search success. 8. Keep the manual process available and stop the test if risk or correction effort increases.
What this tool does not do
A plan is not a production implementation.
Verify requirements with the people who perform the work. Test with synthetic or specifically approved data, review permissions, confirm vendor terms, exercise failure cases, and keep consequential actions under accountable human approval.