Choose one input format with the fewest exceptions.
BEGINNER DECISION GUIDE
Before you price AI automation, calculate the time first.
Tool prices are only one line. Start with frequency, minutes per run, input stability, and human review before choosing a platform or workflow.
Make the free work receipt →Why API price is not the whole cost
For a beginner workflow, the first meaningful cost is often not the model call. It is the time spent checking output, fixing missing inputs, and recovering a failed run. Start with work at stake, not a currency claim.
Monthly work at staketimes per week × 4.3 × minutes per run ÷ 60
Keep the first pilot to four boundaries
End in one inspectable draft, table, tag, or packet.
Do not send or decide automatically in the first run.
Keep the old manual path available when the run fails.
Example: meeting notes → draft email
At five runs per week and 15 minutes per run, the monthly work at stake is about 5.4 hours. That is not savings or revenue; it is the work to observe. It becomes a pilot candidate only when the input is stable and a person reviews every draft.
Calculate this example yourself →Only add paid files when you want to repeat the result.
The $19 AI Work Starter System is an offline file set for one task: scope, review gate, run log, and completion receipt. It does not include consulting, calls, or account access.
Inspect the $19 system scope →FAQ
Does this calculate ROI?
No. It calculates work at stake and a first scope. Savings, revenue, and ROI require real before-and-after evidence.
What task should I enter?
Use one task that already repeats and can be reviewed by a person. Never enter personal or confidential data.