Seven questions about one repeated manual process. You get a plain description of the workflow as you've described it, whether a single Automation Sprint likely fits, and what would need inspecting first. No email to see it, and no made-up savings figure.
Checked in this order: (1) if it only happens occasionally, the honest answer is that automating it probably isn't the highest-leverage fix yet — that check runs first, before the shape of the process looks attractive; (2) if it's daily or weekly and touches one to three systems, it's within the Automation Sprint's published scope (one workflow, up to three systems); (3) anything with four or more systems, or a shape beyond one sprint's scope, is a broader scoping conversation.
This tool doesn't ask how much time the process takes or what an hour of your team's time costs — the two inputs a real savings estimate needs. Without them any figure would be invented, so none is shown. If you want the arithmetic on a specific process, the AI Receptionist Cost Calculator does exactly that for enquiry handling, with every assumption visible.
Deterministically — from the categories you picked, not generated by a language model. It's a plain restatement of the shape of the process you described, meant to make it easy to see what would need looking at, not to pretend it knows your systems.
It's the list of things a real scoping conversation would need to look at for a process shaped like yours — which systems can realistically connect, who approves what, what's being copied by hand. It's a preview of the questions, not an audit of your actual setup.
No. The full result appears on screen once you've answered the seven questions. Email is only if you want a written copy.
One clearly defined business workflow, up to three systems or services, one primary path with reasonable branching, implementation and testing, error handling and handoff documentation — for a fixed published price shown on its own page. Anything materially outside that is quoted separately.
That's a real answer, not a soft no. At low frequency the setup effort usually costs more than the manual work saves. It's worth revisiting if the frequency changes, or if this is one of several similar processes worth automating together.
It doesn't assume any. Which of your systems can realistically connect — through an API, a webhook or otherwise — is one of the specific things confirmed during scoping, never assumed from these answers.