Money-Timer Simple

[Examples of Use Cases]
* Savings & Frugality: Automatically counts up daily savings with 500 yen coins. Sudden expenses and unexpected income are immediately reflected in the addition/subtraction items, maintaining motivation to achieve goals.
* Business & Sales Management: Displays the budget per hour during business hours. Real-time sales requirements can be grasped by entering returns and discounts in the "Adjustment Items."
* Learning & Diet: Manage daily progress numerically, such as memorizing English vocabulary goals or calculating calories burned during walks (supports decimal input using METs calculations).
* On-site Management: Ideal for managing target numbers on factory production lines and managing the progress of store labor cost budgets (in 15-minute increments).

Actual Example
1. --<<500 Yen Coin Savings>>---
Save 15,000 yen in one month (assuming 30 days) by saving 500 yen coins. 1. Set the count value to 500, the period to 1 month, and since it's 500 yen per day, set the time to 5pm to 6pm and the interval to 1 hour. This counts up 500 yen each day. When saving any leftover change, enter this amount in the addition column as the cumulative total. When spending it, enter it in the subtraction column as the cumulative total. This allows you to see at a glance how much more you need to save and how much you've saved so you can maintain your motivation for saving.

2. --<>--

I used this to set a goal of memorizing 120 English words per month. The count value was set to memorize 4 words per day. The time was set to 15 minutes, from 7pm to 7:15pm. I selected a 15-minute interval and counted up after the time slot passed. After memorizing, I tested myself on the English words learned up to that day. If I made a mistake or forgot something, I recorded it in the subtraction column as a mistake on that day's test. While studying every day, I was able to use it to determine how many words I needed to memorize in the remaining time, to record my mistakes so I could see when I would hit a wall after starting to learn, and to judge how easily I would forget things.
3. --<>--
I used it with the goal of losing 1 kg in a month and a half by walking for an hour every day. I converted 1 kg of fat into calories and entered 7200 kcal as the target value. For the count-up value, I specified the calorie value burned during a one-hour walk as the calories burned. (1.05 × 2.5 (METs) × 53 kg) 139 kcal. I basically walked for an hour every day. On rainy days or when I was too busy to walk, I entered the cumulative value including past days in the subtraction item. If I walked for more than an hour, I entered the cumulative value in the addition item. Since decimal input is possible, it was able to handle numbers like 69.5 for 30 minutes. Seeing the calorie consumption numerically and being able to directly input adjustment values ​​made me want to raise the bar a little and use it for walking next time. 4. --<>--
Enter "Break-Even Point" as the title and "Cumulative Sales Amount" as the target value. Enter the actual cumulative sales amount up to that day as the number. Divide the daily variable cost budget by 8 hours and count up the variable cost budget per hour. Enter "Fixed Costs" as the name of the increased item and enter the fixed cost amount as the value. The difference display shows the profit/loss amount up to that day, and by entering the amount to adjust using the addition and subtraction items, it becomes closer to the actual amount (profit/loss amount), which increased motivation. I felt that this was very useful in raising awareness of whether to focus on sales or securing profits at any given time.

5. --<>--
From the monthly sales budget, count up the unit sales budget amount per hour during business hours and add the individual total amounts to display the remaining required sales amount. By entering returns, discounts, and adjustments, I tried to understand how much more sales were needed from the actual sales budget. I think it's a pretty good app because you can check it whenever you want and grasp the information at a glance.

6. --<>--
We tested displaying the remaining required production quantity by counting up the planned production quantity per unit (per hour) up to the point where the target production quantity for the period has been reached. Because it can take into account the production quantities for waste, defective products, and adjustments, it became possible to check (see) quantities that are closer to the actual values ​​on the ground in a timely manner. Normally, data is compiled at a fixed time each time the line changes on a board, so I think this is a good app that allows you to see at a glance how much more production is needed even while the line is running.

7. --<>--
We allocated the hourly raw material consumption budget as a count value from the monthly raw material budget (inventory). Since you can input the quantities for waste and adjustments, we used it to reflect the values ​​on the ground each time and check the raw material balance. Comparing it with the actual inventory count felt very good for checking if anything had been overlooked. In particular, I felt it was effective in raising awareness regarding yield.

8. --<>--
We used this tool to track the monthly labor cost budget for part-time and temporary staff, calculating the store's necessary labor costs in 15-minute increments, and then counting up the budget to see at a glance whether it was within budget or how much more labor cost could be spent by the end of the month. While exceeding labor costs is unavoidable during busy periods (high sales), it was used as a basis for deciding to reduce labor costs during periods of low customer traffic (low sales).
We felt it became more realistic by reflecting lateness and early departures in the adjustment items to increase available labor costs, and reducing overtime and outsourcing costs. It seemed useful for quickly deciding on part-time and temporary staff time adjustments.

9. --<>--
To be mindful of the 1.06 million yen annual income barrier, we set the hourly wage at 1050 yen as the count value, for a 4-hour workday on weekdays only, from April 1st to the end of March. Normally, I wouldn't exceed this limit, but sometimes I have to come in to help out, or I can't work on holidays or during long weekends. When I worked extra hours, I entered the cumulative value in the increase column, and when I didn't work on holidays or days off, I entered the cumulative value in the decrease column, using the app to stay within the 1.06 million yen annual income threshold. I could just look at my payslip, but I don't like having others see such realistic data. It's safer and easier to display this app and check it discreetly.

10.--<>---

I set a target amount of money I wanted to earn (net income) per month, and tested the app by counting up the amount earned every 15 minutes of work and showing how much more I needed to earn. Working hours were 8 hours, transportation expenses and allowances were entered as addition items, and resident tax, income tax, social insurance, and employee pension were entered as deduction items, showing how much more I needed to earn by the last day. While looking at the amount displayed in the app, I used it to determine how much more overtime I needed or how much I needed to reduce my expenses. I've become more conscious of the actual amount I'm spending.
11. --<>--
My goal is to schedule 88 appointments with clients per month, aiming for 4 appointments per day on weekdays. Each appointment takes approximately 1 hour. Since the goal is 4 appointments per day, I count up every hour between 10 AM and 2 PM (therefore the count value is 1). In reality, there are days when I schedule more than 4 appointments, and there are also days when scheduled appointments are canceled or there are no appointments at all. In these cases, I used the addition/subtraction items to keep track of my target number of appointments until the end of the period. Knowing that this was displayed on a smartphone app made me feel more focused.