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.

CSLM WORKFLOW TEST BRIEF

Workflow: WF-004 — Proposal outline preparation
Business area: Sales
Best-fit audience: Consulting firms
Owner: [name the accountable owner]
System of record: [name the authoritative system]

Problem
Discovery notes take too long to turn into a reviewable scope.

Approved input
Approved discovery notes and service catalog

AI role
Extract requirements, gaps and a proposal outline

Human checkpoint
Seller confirms scope, price, claims, terms and delivery

Failure and stop path
Stop when evidence, authority or required details are missing

Data classification
Confidential business context

Measurement
Preparation time; factual corrections

Safe first test
Use a synthetic discovery brief without real customer information

PROMPT DRAFT
You are assisting with proposal outline preparation. Use only the approved information provided. Extract requirements, gaps and a proposal outline. 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: Extract requirements, gaps and a proposal outline.
5. Route the result to the named owner for this checkpoint: Seller confirms scope, price, claims, terms and delivery.
6. If anything fails or remains uncertain: Stop when evidence, authority or required details are missing.
7. Record the result using: Preparation time; factual corrections.
8. Keep the manual process available and stop the test if risk or correction effort increases.

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.

← Return to the 25-workflow atlas