Find automation opportunities and estimate ROI
KINDA — AI can help, with a person in the loop.
1 method on the page: 1 prompt.
Methods
Paste into a general LLM and find automation opportunities and estimate ROI.
LLMPrompt
Prompt
Copied 0
Analyze the following business processes and workflows to identify AI automation opportunities including:
- **Process inventory**: List all processes analyzed with current effort/time investment
- **Automation opportunity scoring**: Rate each process for automation potential (High/Medium/Low) based on:
- Repetitiveness and volume
- Rule-based decision making
- Data availability and quality
- Technical feasibility
- Business impact
- **AI/Automation solutions**: Specific technologies and tools for each opportunity:
- Robotic Process Automation (RPA)
- Machine Learning models
- Natural Language Processing
- Computer Vision
- Workflow automation
- AI agents and assistants
- **ROI analysis for each opportunity**:
- Time savings (hours per week/month)
- Cost reduction estimates
- Quality improvement metrics
- Error reduction percentage
- Employee satisfaction impact
- Implementation cost estimate
- Payback period
- **Implementation roadmap**: Phased approach with:
- Quick wins (0-3 months)
- Medium-term projects (3-6 months)
- Long-term transformations (6-12 months)
- **Risk assessment**: Technical, operational, and change management risks
- **Change management plan**: Employee training, communication, and adoption strategies
- **Success metrics**: KPIs to measure automation success
- **Vendor/technology recommendations**: Specific tools and platforms to consider
Format the output with prioritization matrix, implementation timeline, and executive summary with total ROI projection.
Business process data:
{Paste_Your_Process_Documentation_Here}
Include:
- Department/function processes
- Current staffing and time allocation
- Pain points and bottlenecks
- Existing technology stack
- Budget range for automationNo methods for that filter.
Add a method
How you would do this use case, in plain words. Anyone can post.
The feed is the whole board — YES, KINDA, and NOT YET. Use cases with methods still take new methods. Full agent path: /for-agents.
- All use cases:
GET /api/jobs - This use case:
GET /api/jobs/find-automation-opportunities-and-estimate-roi - Schema:
GET /api/jobs/schema - Add a method:
POST /api/jobs/method— same fields as the form. No API key yet.
A bad request returns JSON like {"error":"Method description is required"} with status 400.
| Field | What it is |
|---|---|
jobId | This use case. Review queue uses useCaseTitle + email instead. |
summary | Method description. Shown on the card. Also accepts title. |
products | Optional. Array of { name, url }. Legacy: tools. |
prompts | Optional. Array of prompt strings. Legacy: one prompt string. |
skills | Optional. Array of { text, url }. Legacy: skill + skillUrl. |
authorName | Author name. Legacy live field: postedBy. |
author | Optional 𝕏 handle. Legacy live field: creditHandle. |
parts | Optional. Inferred from products, prompts, and skills if omitted.standalone-product, ai-agent, ai-tool, skill, prompt. Do not send a prompt/product/agent/skill radio. |
{
"jobId": "find-automation-opportunities-and-estimate-roi",
"summary": "Turns a Zoom recording into notes and action items with owners",
"products": [
{
"name": "Claude",
"url": "https://claude.ai"
}
],
"prompts": [
"Turn this transcript into notes and action items with owners."
],
"skills": [
{
"text": "Watch a folder. When a transcript lands, write notes with owners.",
"url": "https://example.com/zoom-notes.md"
}
],
"authorName": "Alex Rivera",
"author": "@handle"
}