Aida
Decision engine that finds the first workflow worth automating, then ships a paste-ready AI scaffold.
The Problem
Solo practitioners have the most to gain from AI and the least slack to adopt it. The hard part is not finding another chatbot. It is deciding which workflow is safe, valuable, and specific enough to automate without touching clinical judgment or protected health information.
Aida narrows that choice to one practical next step: a skill, plugin, agent, prompt, or human handoff. The target user leaves with a decision and a starting artifact, not a generic list of AI ideas.
What I Built
Aida helps solo healthcare practitioners decide where AI should enter the practice first. It turns an operational pain point into a ranked automation path, then ships a paste-ready scaffold the user can put into Claude Code or OpenAI Codex.
Impact
Aida does not ask users to become AI system designers. It maps their real workload to the smallest useful artifact: SKILL.md, AGENTS.md, plugin layout, prompt, checklist, or human handoff.
The trust posture is explicit. v1 rejects PHI at intake, keeps the main metric on time saved, and puts the math behind a “show the work” layer so the practitioner can inspect the decision without being forced through decision-science jargon.
How It Works
Aida has two paths that share one decision engine.
| Path | Output | When To Use It |
|---|---|---|
| Find where AI saves time | Paste-ready AI scaffold | Admin work like referral coordination, pharmacy callbacks, billing, scheduling, intake, or follow-up |
| Help me decide given constraints | Ranked recommendation with method trace | Business choices like raising prices, capping intakes, hiring admin support, or expanding referrals |
The decision path uses a five-stage MCDA pipeline: values elicitation, constraints intake, weight assignment, ELECTRE outranking, TOPSIS ranking, and sensitivity analysis. The automation path scores candidate workflows by safety, leverage, implementation fit, and data readiness, then emits the first scaffold worth trying.
Why The Rename Matters
Decision Doctor was the build name. Aida is the product name: shorter, warmer, and easier to flex across the actual app surfaces - Ask Aida, Aida recommendations, Aida-generated scaffolds, and weekly Aida workflow audits.