Planning
What AI Solution Type Fits This Use Case?
Decide whether your use case is better served by automation, a chatbot, RAG, a copilot, or a more capable agent.
What the tool does
This tool helps you decide whether a use case is better handled as automation, a chatbot, a RAG assistant, a copilot, or a more capable agent.
Who it's for
It is for founders, operators, and engineering teams who are still shaping what they should build.
When to use it
Use it early, before architecture debates turn into tool shopping or vague agent plans.
Practical Use Case
Use this before stakeholder meetings when people agree that “AI should help” but do not yet agree on what kind of system actually fits the workflow.
Share The Result
Export results as a PDF to share in meetings, planning docs, or internal documentation.
Why This Result
- You prioritized helping staff move faster rather than replacing the workflow entirely.
- The workflow depends on internal context, which favors copilots over generic chat surfaces.
- Human approval is still part of the operating model, so fully autonomous patterns are less suitable.
Recommended Direction
Internal Copilot
The system should help trained users work faster by combining company context, preferences, and guarded actions.
Confidence
High confidence
The signals are relatively aligned.
Do Not Build This As
Do not widen the scope before you can explain why this pattern is the best fit.
Why it fits: Copilots are strong when a human is already in the loop and wants faster drafts, better search, or help with internal tools.
Watch out for: Internal copilots drift when memory is sloppy or tool permissions are broader than the human actually needs.
Best next step: Focus on one team, one workflow, and one approval model before trying to support the entire company.
Runner-Up
Human-in-the-Loop Agent
The agent can prepare recommendations or draft actions, but meaningful decisions still need review or approval.