Demo: try daily reports through evaluation, hands-on
No sign-in, no setup — try it right away. Walk through the real screens: writing a daily report, AI assist, manager approval, and evaluation based on facts.
Try entering a daily report ↓Business plan (sample)
This feature is included in Standard. See pricing →
A sample for a fictitious company, “Sample Trading”. All figures are fictitious, and nothing is saved on this screen.
Sales plan: 60 million yen for the year (allocated by month)
- Philosophy: turn small improvements on the floor into the company’s strength.
- Key initiative: launch a new service (owner: Sales, due: end of March next year)
Goal tree (sample)
This feature is included in Standard. See pricing →
A sample for a fictitious company, “Sample Trading”. All figures are fictitious, and nothing is saved on this screen.
| Period | Target | Actual | Achieved |
|---|---|---|---|
| Year | 60,000,000 JPY | 21,000,000 JPY | 35% |
| Q1 | 15,000,000 JPY | 14,100,000 JPY | 94% |
| Q2 | 15,000,000 JPY | 6,900,000 JPY | 46% |
Today’s goal: Sales 227,273 yen (one tap puts it into the “plan” of the daily report)
- Role “Sales”: quarterly 15 million yen split equally among 3 people (5 million yen each)
- Individual “New hire A”: ratio 50% (share 2.5 million yen)
AI drafts (Evaluation Pro, sample)
This is a sample (a fictitious company). A real draft is built from your other chapters and your company policy.
1. Philosophy and vision
Build up small improvements on the shop floor and increase the number of local small businesses where people can work with peace of mind. (sample)
4. Products and pricing
- Two tiers: Standard (daily reports, approval and team-wide goals) and Evaluation Pro (evaluation, editing role-level and individual goals, and AI drafts for the business plan) - No setup fee on either; a monthly charge per seat
Draft goals from the business plan
- Sales: 60,000,000 JPY
- New customers: 240
This is a demo. What you type is not saved (reload to reset).
Daily report (PDCA)
This feature is included in Standard. See pricing →
Basics
Team Demo Sales Team / Name Sato (Sales)
Today’s goal (team)
- Sales（Team）：Today’s goal 227,273 JPY ／ Team actual (so far today) 159,091 JPY
- Gross profit（Team）：Today’s goal 68,182 JPY ／ Team actual (so far today) 47,727 JPY
- New customers（Team）：Today’s goal 2 ／ Team actual (so far today) 1
P — Today's goal
D — What you did
C — Reflection (what went well / what didn't)
A / Next-day P — Improvement and tomorrow's plan
Growth mode (manual)In the demo, a sample draft is shown (in the real app, the AI drafts it from what you wrote in your reflection (C)).
Based on your reflection (C), the AI suggests a one-sentence draft for the improvement and the next-day plan. It does not give answers; the person makes the final call.
Enter at least one of P, D or C.
Approve (manager)
Pending approval
2 item(s)- P: Book follow-up meetings with 3 existing customers.
- D: Called 3 customers; booked 2 meetings, 1 was unavailable. Prepared a proposal for one of them.
- C: What won the meetings was leading with a case study. The unavailable one may have been the wrong time of day.
- A: Shift calls to the 10-11am window and standardize the case-study talk track for every call.
- Next P: Call the unavailable customer again in the morning and finish the proposals for the 2 booked meetings.
- P: Reach out to 20 new prospects.
- D: Called 20; spoke with the contact at 5, sent materials to 2.
- C: Response varies by day. Monday mornings connect to decision-makers more easily.
- A: Concentrate outreach on Monday mornings and follow up the day after sending materials.
- Next P: Follow up by phone with the 2 who received materials and start 15 new prospects.
| Date | Name | P | D | C | A / Next P | Input | Send back |
|---|---|---|---|---|---|---|---|
| Sato (Sales) | Book follow-up meetings with 3 existing customers. | Called 3 customers; booked 2 meetings, 1 was unavailable. Prepared a proposal for one of them. | What won the meetings was leading with a case study. The unavailable one may have been the wrong time of day. | Shift calls to the 10-11am window and standardize the case-study talk track for every call. / Call the unavailable customer again in the morning and finish the proposals for the 2 booked meetings. | AI assist | ||
| Tanaka (Sales) | Reach out to 20 new prospects. | Called 20; spoke with the contact at 5, sent materials to 2. | Response varies by day. Monday mornings connect to decision-makers more easily. | Concentrate outreach on Monday mornings and follow up the day after sending materials. / Follow up by phone with the 2 who received materials and start 15 new prospects. | Manual |
Approve
The manager approves once a day. On approval, everyone's reports are written to your spreadsheet. The raw data on our server is erased immediately when a manager approves. A daily report is recorded in your spreadsheet when the manager approves it within 24 hours of submission. A report not approved within 24 hours is not recorded and disappears, because we are designed not to keep it on our server.
PDCA history
History
3 item(s)Policy × Behavior Alignment Report (AI)
Evaluation ProAI summarizes how well the company's coaching policy aligns with actual behavior (report facts) in this period. It is a draft and suggestion; the final evaluation is made by a human.
A feature of Evaluation Pro (paid plan) — this is a demo sample
Alignment summary
In recent daily reports, Sato's actions largely align with the company's coaching policy (find issues yourself rather than wait for instructions, and turn improvements into the next day's actions).
Where behavior matches the policy
For the customer who was unavailable, Sato identified the likely cause on their own (the time of the call) and turned the improvement — shift calls to the 10-11am window — into the next day's plan (call again in the morning). This fits the policy of finding issues yourself and turning improvements into the next day's actions.
Gaps with the policy
The cause of the missed call is still a guess ("may have been the wrong time of day"); the result of checking it has not yet been written in the reflection (C).
Points to discuss in the 1-on-1
In the meeting, check together whether Sato writes in the reflection (C) if the morning call got through, so that checking a guess becomes a habit.
* This is an AI draft and suggestion. The final evaluation is made by a human.
Weekly AI summary (evaluation draft) / 1:1 support
This feature is included in Standard. See pricing →
The demo shows sample text (in the real app, the AI writes it from your coaching policy and a week of daily reports).
Weekend feedback for the employee
This week Sato has been turning each day's plan into the next day's action. Sato asked about each customer's situation first, picked case studies close to the challenges that came up, and called 3 customers to book 2 meetings. It is also good that Sato noticed independently that opening with a case study worked. Next week, write in your reflection (C) what you found out when you checked whether the unavailable customer was a matter of timing.
Manager's quiet status report
Sato finds issues independently and turns them into the next day's actions. One point to watch: the cause of the unavailable customer is still a guess ("maybe the time of day"), and the result of checking it is not yet written down. This is not a moment to criticize, but to support the habit of following through to checking.
1:1 meeting sheet
- Did the morning follow-up call reach the customer who was unavailable? Was the "time of day" guess right?
- How would Sato explain, in their own words, why opening with a case study worked? Could it become a form that works with other customers too?
- Before finishing the proposals for the 2 booked meetings, is there anything to settle first, or anything you can help with?
AI usage rate / manual-rate dashboard
This feature is included in Standard. See pricing →
These are sample numbers. At first they match the 3 approved reports in the demo’s history (2 with AI assist, 1 manual). When you approve in the demo, they are recounted to include those reports (on this screen only; nothing is saved).
Submission status · 1 not submitted
- Sato (Sales)Pending
- Tanaka (Sales)Pending
- Suzuki (Sales)Not submitted
AI assist
This feature is included in Standard. See pricing →
Based on your reflection (C), the AI suggests a one-sentence draft for the improvement and the next-day plan. It does not give answers; the person makes the final call.
Manager approval
The manager approves once a day. On approval, everyone's reports are written to your spreadsheet. The raw data on our server is erased immediately when a manager approves. A daily report is recorded in your spreadsheet when the manager approves it within 24 hours of submission. A report not approved within 24 hours is not recorded and disappears, because we are designed not to keep it on our server.
Fact-based evaluation
This feature is included in Evaluation Pro. See pricing →
The accumulated daily reports become the basis for evaluation grounded in written facts, not impressions (Evaluation Pro).
A list of the work and everyday tools made by the same company. Norolu Works(opens in a new tab) How to Write OKRs(opens in a new tab)