01
How many conversations a month
Your weekly requests multiplied by 4.33, the average number of weeks in a month, then by the share you marked as repetitive. Only that share is counted as automatable.
How much do repetitive questions cost you?
Every request you answer by hand costs time and money. Enter your numbers and see how much you could get back by automating routine questions.
These are indicative values: replace them with yours.
Your estimate
15Hours saved per month
- Estimated messages per month758
- Saved per month€379
- Saved per year€4,547
- Cost of the Starter plan-€29
- Net saving per month€350
Estimate based on the values you entered, assuming around 5 messages per conversation. The plan is chosen from your estimated volume.
How the estimate is worked out
No black box: here is exactly what happens to the four numbers you type in, so you can check the result against your own accounts.
02
How much time they take
Those conversations multiplied by the average minutes each one costs you, divided by 60. That is the hours the chatbot could take off your hands every month.
03
What those hours are worth
Hours multiplied by the hourly cost you entered, which gives the monthly figure, and by twelve for the yearly one. Use your fully loaded cost, not the net wage, if you want a realistic number.
04
Which plan it needs
Each conversation is counted as 5 messages, that is two or three back-and-forth exchanges. The calculator then picks the smallest plan that covers the resulting monthly volume.
A worked example
A neighbourhood gym gets 120 requests a week, takes about 5 minutes to answer each one, works with an hourly cost of €22 and reckons 70% of the questions are routine: opening hours, memberships, how to sign up.
The calculation returns 30 hours recovered per month, worth €667 a month and €8,002 a year at their costs. The estimated volume fits inside the Starter plan at €29 a month, so the net saving is €638 a month.
See how it works for gymsWhat the estimate does not include
A number is only useful if you know where it stops. These are the limits of this one, worth reading before you take it to a meeting.
- Not every repetitive question disappears. Some visitors want a person anyway, and some requests are only half routine.
- Time saved is not automatically money saved. It becomes money if you reassign that work or actually cut those hours, otherwise it is capacity you got back.
- Setup time is not counted. Indexing the site, uploading documents and reviewing the first replies take a few hours at the start.
- The estimate is conservative in one respect: it ignores the requests you lose today outside office hours, which the chatbot would answer anyway.
Questions about the calculation
Entirely from what you type in. The calculator adds only two assumptions: 4.33 weeks in an average month and around 5 messages per conversation. There is no hidden industry benchmark or averaged database behind it, which is exactly why you should replace the starting values with yours.
It answers what your content covers. Widgeto replies only from the pages and documents you give it, and when a question falls outside that scope it says so and points the visitor to you instead of inventing an answer. That is why the share of repetitive questions is a field you set: be honest with it and the estimate stays useful.
The suggested plan is the smallest that covers your estimated volume, so there is little headroom by design. If you go over the monthly messages the widget stops replying until the plan renews, and you can move up a plan at any time paying only the difference for the remaining days.
Use the fully loaded cost, not the net wage: gross pay plus contributions and overheads. It is usually a good deal higher than the figure on the payslip, and using the wrong one is the quickest way to end up with an estimate nobody believes.