Amoeba Management Analysis

Problem addressed

Amoeba management analysis is often split into isolated reports: revenue, cost, labor hours, and headcount live in different systems without a shared accounting lens. This skill narrows the task into one analysis path: identify the objective, collect the required fields, decompose performance around hourly value added, and produce a reviewable diagnostic.

How it works

• Goal routing: classify the request as organization division, hourly value accounting, management accounting reports, performance diagnostics, or internal pricing.
• Data intake: request revenue by amoeba, direct materials, direct labor, manufacturing overhead, allocated expenses, total hours, and headcount as needed.
• Five-level analysis: move from L1 data recording to L2 cause analysis, then L3 linkage analysis, L4 forecasting, and L5 decision support.
• Output: build a structured report using references/report-template.md, including operating philosophy and review checkpoints.

Boundaries and caveats

• It depends on amoeba-level operating data; missing fields limit how deep the conclusions can be.
• It provides an analysis framework and diagnostic logic, not an ERP, financial close, audit, or formal pricing approval.
• internal pricing and organization division require clear business rules, responsibility boundaries, and accounting conventions.