MENTA
Menta-kun
Don't just ship it and forget it.
AI-driven maintenance that keeps watch over your live system.
Beyond ordinary maintenance, Menta-kun reads your operation logs—how the frontline really uses it, how well it's taking hold, improvement ideas, new-feature ideas, even where things got slow as data grew—and delivers it all as a regular report.
In short, an AI-driven “proactive maintenance service” — maintenance, with a mentor's eye.
Notice trouble and untapped potential before anyone has to raise a hand.
Can be retrofitted onto your existing live systems.
ARCHITECTURE
Our vision for building a competitive foundation
Every IPLoT product and service takes a place in this shared OS of competitive strength. Menta-kun covers the highlighted part (Activity-DB layer + Agent layer).
How IPLoT supports this model
The areas covered by each IPLoT product and service within the model above.
| Layer | Products & services in charge |
|---|---|
| Structured-UI layer (the window) | Brain Pro / Shiftly / System development |
| Knowledge layer (what AI is taught) | iPro Manual / AI Strategist Training / Knowledge Loop Consulting |
| Activity-DB layer (store the data) | AI Data Analysis / Yomitoru-kun / Kakikomu-kun / Wholesale core system |
| Agent layer (where AI acts) | IPRO-kun / Menta-kun / System development |
| Designing & applying the whole structure | IT consulting (overall design) / HRobo (all layers for HR & talent) / Knowledge Loop Consulting (full rollout) |
Menta-kun covers: Activity-DB layer + Agent layer
From reactive to proactive operations
Ordinary maintenance
Fix it when it breaks
Mostly incidents and support tickets. Improvement keeps getting put off.
Menta-kun
Find the upside first
Reads early signs of trouble and improvement from logs, and gets ahead of them.
─ REPORT
A monthly “health report” for your system
Overall score, how the frontline uses it, improvement and new-feature ideas, signs of regression. A sample of the regular report that tells you the next move at a glance.
MONTHLY HEALTH REPORT
Target system
Order & inventory core system
Period: May 2026 ／ generated 2026/06/01
Overall health score
78/ 100
+4 vs last month
Adoption rate
64%
+6pt
Weekly active
71%
+3pt
Key actions run
12,480
+8%
Avg. response
1.9s
+0.4s
Improvement ideas
- High
High drop-off at “customer select” in order entry
2.3 retries on average. Re-ordering suggestions by recent use alone would speed it up.
- Med
Shipment list render slowed +0.6s vs last month
Heavy table rendering past 50k line items. Suggesting paging / virtualization.
- Low
“Invoice PDF export” is barely used
4% usage after 3 months. Revisit the entry point or internal awareness.
New feature ideas
One-tap “favorite products”
The same products are hand-entered 3,200 times a month. A saved list would shorten input.
Auto-deliver routine reports
Detected the same Excel summary being built at month start. A candidate to automate.
Usage by screen
Silent signals from the field
- Errors128 validation errors a month on “due-date entry”
- Redo“Amount fix” undo up +40% vs last month
- StalledApproval items sit 2.8 days on average
* Signs that never became a ticket
NEXT ACTION
Hand the two “high” items to IPRO-kun / the dev team.
* For illustration. Real data varies by connected system.
─ WHAT IT WATCHES
What Menta-kun keeps an eye on
Starting from operation logs, it continuously checks your system and the people using it from many angles.
Read how it's actually used
See who uses which screens and features, and how much, straight from the logs.
Measure adoption
Quantify active rates and usage growth by team or site to see whether rollout is sticking.
Suggest improvements
Turn drop-off points and friction into concrete UI and workflow fixes.
Propose new features
Spot repeated manual work and routine patterns, and propose features that would actually help.
Catch what got slow
Find screens and jobs that slowed down as data grew, with how much they regressed.
Hear the unspoken
Detect frequent errors, redo loops, and stalled items—the friction no one files a ticket for.
BLIND SPOTS
The blind spots it catches
Slow, but no one says so
As data grows, one screen quietly gets slower each month—and the pain goes unspoken.
Features that go unused
A feature you put real effort into is barely opened on the ground. You find out months later.
Requests that never surface
Small frustrations like “I do this by hand every time” never make it into a request.
No idea if it's sticking
You rolled it out, but no one can say in numbers whether it's actually being used.
─ HOW IT WORKS
From logs to the next move
STEP 01
Collect the logs
Embed measurement in your live system to safely capture who did what, on which screen, and how often.
STEP 02
Analyze from many angles
AI reviews usage, adoption, performance, and friction together, across the board.
STEP 03
Report and propose
Compile monthly and weekly reports, with improvement and new-feature ideas backed by evidence.
STEP 04
Drive the next move
Suggest prioritized next steps, handed straight to IPRO-kun or your dev team.
─ BEFORE THEY SPEAK UP
anyone raises a hand.
─ WORKS WITH
IPRO-kun before launch, Menta-kun after
IPRO-kun turns frontline pain into workflows, requirements, and estimates; after launch, Menta-kun watches how it's used and proposes improvements. People and AI, walking with your system through its whole life.
BEFORE ／ pre-launch & build
IPROくん
An always-on AI consultant that spots pain from frontline talk and shapes workflows, requirements, and estimates.
See IPRO-kunMEMORY ／ the project brain
Brain Pro
Project management that holds AS-IS/TO-BE, issue trees, and WBS as structure—where Menta-kun's proposals accumulate as context.
See Brain ProIPLoT METHOD
From finding the problem to running it—one continuous flow.
While other firms take on just “development” or just “maintenance,” IPLoT delivers all three as one: (1) problem discovery & consulting, (2) development powered by generative AI, and (3) post-launch operations. The map below shows where each of our services sits across these three pillars.
Three parts, one offering: Discover → Build → Operate
Problem discovery & consulting
Before “what to build,” we ask “what is the real problem.” A standardized method distilled from our 36 in-house courses structures the issues on the ground.
Development
We make the most of generative AI to go from requirements to implementation fast and at lower cost.
Operations & maintenance
We don’t just ship and leave. We keep watching the live system through its operation logs and keep improving it.
Menta-kun
AI service that watches the live system
Every phase does not have to be ours. We agree the split of responsibilities—and how records are shared—with you and your existing vendors, and keep the information connected.
How we differ from a typical dev firm
| Aspect | A typical dev firm | IPLoT |
|---|---|---|
| Entry point | Builds what it’s told (spec-first) | Starts from problem discovery & consulting |
| Consulting | Relies on the individual’s experience | Repeatable via a standard method (36 courses) + Brain Pro |
| Development | Cost piles up with man-hours | Compresses build cost with generative AI |
| Operations | Passive—fixes things once they break | Menta-kun watches and proposes improvements proactively |
| Delivery | Split by phase, with gaps at the seams | One team, from discovery through operations |
“A typical dev firm” describes what commonly happens when phases are split between parties; it does not refer to any specific company.
FAQ
Frequently Asked Questions
Yes. Once measurement for operation logs is embedded, it can be retrofitted to a running system. The scope can be tuned screen by screen and feature by feature.
Maintenance is mostly reactive—fix it when it breaks. Menta-kun reads usage, adoption, regression, and room for improvement from the logs and proposes ahead of time. It covers both maintenance and mentoring—that's the dual meaning of MENTA.
No. The goal is improving the system and the work, not evaluating or scoring people. Analysis is handled anonymously or in aggregate where appropriate.
Monthly by default, with weekly and on-demand alerts planned. Significant regressions or anomalies are flagged without waiting for the report.
Menta-kun presents prioritized next steps. Implementation can be handed straight to IPRO-kun or your dev team, and the content accumulates in Brain Pro as project context.
First we decide the target system and scope and embed operation-log measurement. Over a roughly one-month trial we tune the report's perspectives and accuracy, then deliver it continuously on a monthly and weekly cadence.
