Workflow studio
Choose a business task, add your context, and run the workflow.
Starting context · Document to decision
From information to a defensible next step.
Saved company fields keep their recorded origin. Turning background off excludes automatic workspace context and keeps your explicit draft inputs.
Use your documents
Create a free workspace to upload and select private documents. Pasted context works without registration.
One workflow allowance per run. External destinations are simulated.
not run
Document to decision
Next workflow draftDecision memo
not run
Purpose
Provide the starting context and evidence for this task.
Input
No step has run yet. The draft starting context is shown separately below.
Draft starting context
The starting context in this draft.
- Company Context
Harbor Distribution is a regional industrial supplier. Our six-person customer service team handles about 600 orders a week and spends 60 hours a week answering order-status questions.
- Role
Operations Director preparing a decision for our leadership team.
- Objective
Recommend whether our team should approve a limited order-status pilot or a full customer rollout within the next 12 weeks.
- Evidence behind the recommendation
Our implementation budget is $120,000, with a separate operating ceiling of $6,500 per month. Option A: a six-week read-only pilot for 20 customers costs $65,000 for implementation, integration and training, then $2,000 per month to operate. Option B: a 12-week rollout to all 200 customer accounts costs $110,000 for implementation, integration and training, then $6,000 per month to operate. Both use our existing order system and leave order changes with staff. Security lead Priya Shah will finish the review in week 3; written approval is required before any customer access. The pilot success criteria are at least 95% correct answers in a reviewed test set and 25% fewer routine order-status tickets among participating accounts, without an increase in complaints. These are targets, not measured results. We can reserve 20 customers for the pilot and measure results weekly. We have not yet tested answer quality or customer adoption. A full rollout can be reconsidered after the pilot review.
Step result
No result has been recorded for this step.
Technical details
Raw draft starting context
{
"companyContext": "Harbor Distribution is a regional industrial supplier. Our six-person customer service team handles about 600 orders a week and spends 60 hours a week answering order-status questions.",
"role": "Operations Director preparing a decision for our leadership team.",
"objective": "Recommend whether our team should approve a limited order-status pilot or a full customer rollout within the next 12 weeks.",
"evidence": "Our implementation budget is $120,000, with a separate operating ceiling of $6,500 per month. Option A: a six-week read-only pilot for 20 customers costs $65,000 for implementation, integration and training, then $2,000 per month to operate. Option B: a 12-week rollout to all 200 customer accounts costs $110,000 for implementation, integration and training, then $6,000 per month to operate. Both use our existing order system and leave order changes with staff. Security lead Priya Shah will finish the review in week 3; written approval is required before any customer access. The pilot success criteria are at least 95% correct answers in a reviewed test set and 25% fewer routine order-status tickets among participating accounts, without an increase in complaints. These are targets, not measured results. We can reserve 20 customers for the pilot and measure results weekly. We have not yet tested answer quality or customer adoption. A full rollout can be reconsidered after the pilot review."
}Step configuration
{}A small example. A bigger possibility.
Explore the method, assumptions, and limits behind this template.