For each step, kawaru.app looks for what can do the work: a feature of a system already in place, a skill, a ready-made product, a flow or an agent. It links the step to similar activities in its knowledge base and checks each option against the setup.
The four rules
- Constraints cut. An option outside the chosen approach, above the autonomy allowed, or without a required certification is left out of the plan.
- The goal sorts. Among the options that remain, the goal decides the order: save money, save time, or grow with the same team.
- Economics warn. An option with a payback longer than allowed, or a saving below the minimum, stays in the plan with a warning. An option that costs more than it saves is not shown.
- Some steps stay with a person. When nothing passes the rules, the step stays with a person, and the reason is written on it.
What a step can become
| Outcome | When |
|---|---|
| Configure | A system already in the stack has an AI feature that covers the step. |
| Skill or prompt | A person runs it on an assistant subscription the company already pays for. |
| Ready-made product | One SaaS product covers the steps of the process. |
| No-code flow | Built on the platform chosen in Architecture. |
| Agent on a subscription | The step runs on a schedule, not on an event. |
| Agent on API | Always on, with a person reviewing. |
| Stays with a person | Nothing passed the rules, or the step decides rather than prepares. |
Fixed rules
- A tool already in the stack is never sold again. It can only be configured.
- A missing price reads "Not publicly available", never zero, and the option has no payback figure.
- Every model-judged number is marked "AI estimate" until a pilot measures it.
- Minutes are shown to one decimal.
Where to see the reasoning
On the Solution screen: Show reasoning on a process, and the card behind each step row, which ends with Instead: and the best alternatives.