Try /btw

Having been involved in this sort of exercise before, I can explain.

What they will have done is asked a human who should be knowledgeable approximately how much time they spend on the activity (e.g.: how long do you normally spend copy and pasting? How long do you spend looking for the files you need? etc.). When you ask someone whose job it is, they tend to overestimate, and on top of that, you break down the questions as much as possible, so these small overestimations compound without it being obvious to the person that they're making a mistake. It's easy enough to spot that you've said 'four hours' but you know a task doesn't to take you a full morning.

Once you've got all these answers, you ask how often the person has to do it.

Then you ask someone in HR for an average salary you can use. Now that AI is doing that work, you multiply the number of hours saved by the average salary, and report that as your savings.

Something, as usual, stinks about these numbers. $1.6M in saved labour costs, and 3.25 years of work in 4 weeks are basically two ways of saying the same thing (labour costs vs improved productivity).

So let's say 3.25 years of work is around 160 weeks, minus the four weeks they actually took, so 156 weeks of productivity savings. Assume 40 hour weeks, that's 6,240 hours 'saved'. Which works out at around $250/hour, which... well. You decide if that's plausible.

A (small) majority of states require employers to grant time off to vote and a (large) minority require that time to be paid. Although as others have noted, it is often the case that the window for voting exceeds a single shift (dependent on your area of work).

https://www.adp.com/spark/articles/2024/10/time-off-to-vote-...

Even if the ID is nominally free, if I have to take a day off and pay for bus/train tickets to wait in line at some office, it’s not really free.

True, but you need to run the optimisation function to calculate at what X does the increased revenue at lower margin from Pro Max subscribers outweigh the reduced revenue at higher margin for API consumers, and adjust your pricing to approach X.

I'm sure that Anthropic have some very smart folks on that right now.